Webhooks

Webhooks allow external systems to trigger your ConjureForge agent in real time.

Incoming webhooks

ConjureForge provides a unique HTTPS webhook URL for each automation. When any system POSTs to this URL, the corresponding agent task runs.

Finding your webhook URL: Agent Studio then Automations, open or create a webhook-triggered automation. The URL is shown in the Trigger section.

Security: All incoming webhooks require a shared secret in the X-ConjureForge-Secret header. The secret is shown once when the automation is created and can be rotated from automation settings.

Payload format

The webhook payload can be any JSON object. The agent receives the full payload as context. Your task description tells the agent how to interpret it.

Entity change webhooks

Triggered by data changes within ConjureForge itself: record created, record updated (with old and new values), record deleted.

Outgoing webhooks

The agent can POST to external webhook URLs as an action. Add the target URL to your agent allowed endpoints list in Agent Studio then Security then Allowed Outbound URLs.

Testing webhooks

Use the Test button on any webhook automation to send a sample payload and verify the agent responds correctly.