Codique

DevelopersSend events in

Developers · Webhooks

Send events in

Push events from your systems into Codique and start workflows.

Inbound webhooks let your other systems, such as a shop, CRM, booking tool or form builder, push events into your workspace. Each event can start a workflow for the customer it is about, for example sending a booking confirmation and then asking for feedback.

  1. Create an endpoint in EngageAutomation › Inbound webhooks

    Give it a URL slug such as new-order and, optionally, a default workflow to start. Choose None — trigger-only if workflows should pick it up with the Inbound webhook received trigger instead.

  2. Copy the endpoint URL and its secret

    HTTP
    POST https://api.example.com/webhooks/inbound/<workspace-slug>/<endpoint-slug>
  3. Send signed JSON

    Sign the exact body you send with the endpoint’s secret, in the same format as outbound webhooks, and pass it in X-Webhook-Signature-256.

Attach the event to a customer

Include the customer’s phone number in one of phone, wa_id, contact.phone or data.phone. If the contact doesn’t exist yet it is created, using name or contact.name if you send one. Without a phone number the event is logged but no workflow starts.

Everything else in the body is available to the workflow, so a step can say “Your order A1001 is confirmed”.

BODY='{"phone":"919876543210","name":"Aarav","event":"order_placed","order_id":"A1001","total":"2499"}'SIG="sha256=$(printf '%s' "$BODY" | openssl dgst -sha256 -hmac "$INBOUND_SECRET" | awk '{print $NF}')"curl -X POST https://api.example.com/webhooks/inbound/<workspace-slug>/new-order \  -H "Content-Type: application/json" \  -H "X-Webhook-Signature-256: $SIG" \  -d "$BODY"

A valid request returns { "ok": true, "workflow_run_id": "…" }. Every call is logged on the endpoint with its result, so you can see rejected signatures and what was received.

Still stuck? Contact us with what you were doing and the exact message you saw.