Webhooks | Coperniq API
Webhooks | Coperniq API
Webhooks
Coperniq can send real-time notifications to your server whenever events occur — a project is created, a work order is completed, a phase starts, and more. These outbound webhooks are powered by Coperniq’s Automation engine.
Note: Webhooks are configured in the Coperniq UI, not via the API. See How to Set Up Outbound Webhooks for the full setup walkthrough.
Setup
- Navigate to Company Settings → Process Studio → Automations
- Click + AUTOMATION and give it a name
- Configure your Trigger (the event that fires the webhook)
- Set the Action to Call webhook and enter your endpoint URL
- Toggle the automation Active and save
Requirements for your endpoint:
- Must accept
POSTrequests withContent-Type: application/json - No authentication is required
- Return any
2xxstatus to acknowledge receipt — any other status triggers a retry
Webhooks only fire for records that meet the trigger criteria after the automation is activated. Records created before activation are not processed retroactively.
Payload structure
Every webhook is a POST request with a JSON body containing up to three top-level keys:
event
Always present. Contains metadata about what triggered the webhook.
Trigger-specific fields are added to event depending on the trigger type. See Triggers for the full list.
record
Present when the trigger is associated with a Project, Request, or Account.
workOrder
Present only for work order triggers.
Triggers
The triggerKey in the event object identifies which event fired. Some triggers add extra fields to event beyond the base set.
