Skip to content
  • There are no suggestions because the search field is empty.

HTTP Webhook Integration

This article describes how to integrate AlisQI with any external system using HTTP Webhook calls from workflows.

Overview

Webhook calls allow AlisQI to automatically trigger actions in external systems — such as ERP, MES, LIMS, CRM, or analytics platforms — in response to workflow events.
Typical examples include:

  • Sending batch release data to an ERP.

  • Notifying external systems when QC results are modified.

  • Pushing new incident or complaint data to third-party databases.

  • Orchestrating complex multi-system processes by chaining AlisQI events to external triggers.

Integration type

✅ Event-driven automation
✅ API-based integration
✅ Real-time push notifications via HTTPS webhooks

 

In this article

Key Capabilities

  • Automatically trigger external systems based on result entry, modification, deletion, or date-based events.

  • Transmit complete result data in JSON format to a specified endpoint.

  • Combine webhook calls with filters and field-specific triggers to precisely control when integrations run.

  • Chain multiple workflows for advanced automation logic.

  • Send data in real-time — ensuring synchronization across systems.

Architecture

Trigger types

The webhook triggers are derived from the workflow triggers, as webhooks are one of the delivery mechanisms in AlisQI.

  • Entry – triggers when a new result is created.

  • Modification – triggers when a result is changed. Can be limited to specific fields.

  • Deletion – triggers when a result is deleted.

  • On date – triggers based on a date field value.

  • Manual trigger – users can initiate the workflow manually from the results overview.

Technologies involved

Setup Instructions

Prerequisites

  • Active AlisQI subscription

  • Permission to configure workflows

  • API endpoint ready to receive HTTP POST calls

  • (Optional) External system authentication mechanism, e.g., Basic Auth or API key

Configuration Steps

A. Create a workflow with a webhook signal

  1. From the Results overview, click Toolbar → More → Workflows.

  2. Create a new workflow and specify:

    • Action: select one or more triggers (Entry, Modification, Delete, On date, or Manual).

    • Filter: define conditions for triggering (e.g., Status = Released).

  3. Under Signal, select Webhook as the signal type.

  4. Enter the target URL of your external system’s endpoint.

  5. Save and activate the workflow.

B. Example configuration

To send all released batch data to your ERP:

  • Trigger: Entry or Modification

  • Filter: status = "released"

  • Signal: Webhook

  • Endpoint: ERP API URL

  • Payload: Full result (JSON format)

 

Tip: Test your webhooks safely before connecting to production systems

When first configuring a webhook, it’s highly recommended to use a request inspection service such as:

These services generate a temporary URL that you can paste into your AlisQI webhook configuration.
When your workflow triggers, you’ll instantly see the incoming HTTP request, including headers and JSON payload.

This makes it easy to:

  • Verify the webhook is firing correctly

  • Inspect the data structure

  • Debug authentication or formatting issues

Once tested and confirmed, replace the temporary URL with your real endpoint.

Authentication

Method

Webhook calls can target:

  • Public endpoints (no authentication).

  • Endpoints secured by Basic Authentication or API keys.

  • Endpoints behind OAuth2 or token-based access (recommended for production).


Token management

Authentication credentials are managed by your receiving system.
For connections between AlisQI and Power Automate or ERP systems, it’s advised to use OAuth authentication profiles in AlisQI for secure token handling.

Manage your AlisQI authentication profile in the Integration Hub.

Payload Example

The webhook transmits the full result payload in JSON format.
Example (simplified):

{
  "action": "new",
  "subject": "Your custom workflow subject",
  "message": "Your custom workflow message" 
  "results": {
    "date":"2025-10-02",
    "batchnumber_": "B-1234",
    "status_": "released",
    "date": "2025-10-11",
    "operator_": "J. van Dijk"
}

Error Handling & Logging

Error visibility

  • In AlisQI: All webhook calls are logged in the Integration Hub.

  • In external systems: Use the receiving endpoint’s logs to verify message delivery.

Retries

  • AlisQI does not automatically retry failed webhook calls.

  • To ensure delivery, use AlisQI’s manual workflow triggers for re-execution.

Common errors

Error Cause Solution
401 Unauthorized Invalid credentials Verify or regenerate API token
404 Not Found Incorrect endpoint URL Check API path
429 Too Many Requests Rate limit exceeded Implement throttling or delay

 

Security & Rate Limits

  • Communication is secured via HTTPS/TLS 1.2+.

  • Webhook payloads contain sensitive data; configure your endpoint to require authentication.

  • AlisQI API rate limit: 30 requests per minute per key.


Troubleshooting

Problem Possible Cause Resolution
Webhook not triggered Filter condition not met Verify workflow trigger and filters
No data received Endpoint unreachable Check firewall or DNS
Wrong payload format Field type mismatch Validate expected JSON schema
Duplicate messages Multiple triggers active Review workflow actions