What are Webhooks?
A Webhook is a way for Connect Rocket to automatically send information to another system the moment a Workflow or call flow is activated. Instead of someone manually exporting data or copying details between tools, a Webhook does it instantly and automatically — in the background, without any additional steps.
If your organization uses other software — a dispatch system, an incident management platform, a logging tool, or a custom application — a Webhook can pass Connect Rocket activation data directly to that system at the moment it's needed.
How it works
When a Workflow or call flow containing a Webhook action is activated, Connect Rocket sends a package of data to a URL you specify. The receiving system processes that data however it's been set up to — logging the activation, triggering a follow-on process, updating a record, or anything else your system is configured to do.
Connect Rocket does not need to know what the receiving system does with the data. It simply sends it.
What data can be sent
When configuring a Webhook, you can include any of the following in the data package:
- The name of the Workflow or call flow that was activated.
- A unique identifier for that specific activation.
- A link to any voice recording captured during the activation, if available.
- The content of any inbound text message that triggered the activation, if available.
- The output of a Craig Prompt, if one was included in the Workflow or call flow.
You can also include any other fixed information you want to pass to the receiving system as part of the request body.
When to use a Webhook
Webhooks are most useful when Connect Rocket is one part of a broader response or operational workflow and you need other systems to be aware of an activation automatically. A few examples:
- Logging every EOC activation to an incident management system without manual data entry.
- Triggering a follow-on process in a dispatch platform when a callout Workflow is activated.
- Sending Craig situational awareness data to an external dashboard at the moment of activation.
- Recording inbound Message Line contacts in a separate case management system.
If your organization's response processes involve multiple tools, Webhooks are the mechanism that keeps them connected.
What you'll need
Configuring a Webhook requires a URL provided by the receiving system — the address Connect Rocket will send data to. This is typically set up by a developer or system administrator on the receiving end. The URL must be publicly accessible and use a secure connection.
If the receiving system requires authentication, Connect Rocket supports passing an authorization token as part of the request.
Configuring a Webhook
Webhooks are configured within the Workflow Actions section of a Workflow or call flow. See Configuring Workflows for step-by-step instructions.