Webhooks

Webhooks let external systems trigger your workflows by sending an HTTP POST request.

Creating a webhook

1. In the Workflows section, click Webhooks
2. Click New Webhook
3. Select the workflow to trigger
4. Configure the webhook

Webhook details

Each webhook provides:

Field	Description
URL	The unique endpoint to call
Token	Authentication token (include in requests)
Auth type	How to authenticate requests
Expected fields	What data the webhook expects in the payload
Field defaults	Default values pre-populated in the payload
Last triggered	When the webhook was last called
Trigger count	Total times the webhook has been called

Calling a webhook

Basic example

curl -X POST https://api.qomplement.com/api/webhooks/trigger/YOUR_TOKEN \
  -H "Content-Type: application/json" \
  -d '{
    "document_url": "https://example.com/invoice.pdf",
    "customer_id": "CUST-001"
  }'

With file upload

curl -X POST https://api.qomplement.com/api/webhooks/trigger/YOUR_TOKEN \
  -F "file=@invoice.pdf" \
  -F "customer_id=CUST-001"

Expected fields

Define what fields your webhook expects. This:

• Documents the API for other developers
• Generates example cURL commands automatically
• Sets up field defaults for common values

Integration examples

From a CRM

When a new document is uploaded to your CRM, send a webhook to qomplement to automatically process it.

From a file storage service

Watch a folder in Dropbox/Google Drive — when a new file appears, trigger processing.

From a custom application

Any application that can make HTTP requests can trigger a qomplement workflow.

Security

• Each webhook has a unique, unguessable URL
• Authentication tokens are required
• HTTPS encrypted in transit
• Rate limiting applies