Easily Integrate Callrail Webhooks with your application.
https://apidocs.callrail.com/#events
Steps to receive Callrail Webhooks
- Sign up for your free Hooky account.
- Create a new Webhook Source, and select Callrail. This will be the endpoint that receives webhooks on behalf of your application, and forwards them using the unified SDK.
- Step 1
- Step 2
- Once a webhook is received from Callrail, you'll see it under the Live Logs section of your webhook source.
- Next, follow the examples below to integrate the Hooky SDK in ruby or javascript, and start receiving webhooks.
Integrating Callrail Webhooks Using Javascript
- Sign up for your free Hooky account.
- Create a new Webhook Source, and select Callrail. This will be the endpoint that receives webhooks on behalf of your application, and forwards them using the unified SDK.
- Step 1
- Step 2
- Once a webhook is received from Callrail, you'll see it under the Live Logs section of your webhook source.
- Next, follow the examples below to integrate the Hooky SDK in ruby or javascript, and start receiving webhooks.
Integrating Callrail webhooks with Hooky in your Javascript based application is straight forward. Just grab the SDK, and call a function when that webhook is received.
Integrating Callrail Webhooks Using Ruby
Integrating Callrail webhooks with Hooky in your Ruby or Ruby on Rails application is straight forward. Just grab the SDK, and call a method when that webhook is received.
Configuring Callrail Webhook Authentication
Here's how it works
Supported Callrail Webhook Events
Pre-Call
Pre-Call The pre-call webhook executes the moment an inbound phone call is received by CallRail. Your server will receive the call information before the call is connected, allowing you to develop real-time systems for your representatives, such as screen-pops or CRM database lookups. Because the pre-call webhook executes before the call is connected, it contains less information than the post-call webhook. For example, the post-call webhook will contain the call duration, whether the call was answered, and a link to the recording (if applicable). This webhook sends the call object in the POST body, formatted as JSON as specified in the call endpoint. See Retrieving a Single Call for details. Additional fields are returned in the JSON and GET request line because of our Legacy API; however, we encourage users to build requests using the parameters outlined in this version of our API documentation for support purposes.
Call Routing Complete
The call routing complete webhook executes the moment an inbound phone call has been routed to its destination. Because the call routing complete webhook executes before the call is completed, it contains less information than the post-call webhook. For example, the post-call webhook will contain the call duration, a link to the recording (if applicable), and tags and/or qualified status applied through keypad scoring. The call routing complete webhook will contain more information than the pre-call webhook, and can be used to supplement information displayed to users handling a call while it is ongoing. This webhook sends the call object in the POST body, formatted as JSON as specified in the call endpoint. See Retrieving a Single Call for details. Additional fields are returned in the JSON and GET request line because of our Legacy API; however, we encourage users to build requests using the parameters outlined in this version of our API documentation for support purposes. Post-Call Webhook
Post-Call Webhook
The post-call webhook executes immediately after an inbound phone call has completed. It contains the full data about the call. This webhook sends the call object in the POST body, formatted as JSON as specified in the call endpoint. See Retrieving a Single Call for details. For legacy purposes some additional fields are returned in the JSON and in the GET request line, but new implementations are strongly encouraged not to rely upon parameters other than the ones currently documented. Call Modified
Call Modified
Call modified webhooks are sent when a call has changed after it’s ended. For example, if you add a tag or a note to a call after the call has ended, you’d use a call modified webhook to retrieve the latest version of the call. This webhook also contains a field called changes that notes which fields changed (like “note”, ”recording”, ”tag”). Please note, this webhook also fires when a call has been marked as spam. Call modified webhooks send the call object in the POST body, formatted as JSON as specified in the call endpoint. See Retrieving a Single Call for details. Additional fields are returned in the JSON and GET request line because of our Legacy API; however, we encourage users to build requests using the parameters outlined in this version of our API documentation for support purposes.
Outbound Post Call
Outbound post-call webhooks are sent after an outbound phone call has ended. The primary difference between Post Call Webhooks and Outbound Post Call Webhooks is that it is sent only after an outbound call has completed. As such, the call_type field will be set to "outbound". This webhook sends the call object in the POST body, formatted as JSON as specified in the call endpoint. See Retrieving a Single Call for details. Additional fields are returned in the JSON and GET request line because of our Legacy API; however, we encourage users to build requests using the parameters outlined in this version of our API documentation for support purposes. Outbound Call Modified
Outbound Call Modified
An outbound call modified webhook is sent when an outbound call has changed after it has ended. For example, if you add a tag or note to an outbound call, you’d use an outbound call modified webhook to retrieve the latest version of the call with the most recent information attached. This webhook sends the call object in the POST body, formatted as JSON as specified in the call endpoint. See Retrieving a Single Call for details. For legacy purposes, some additional fields are returned in the JSON and in the GET request line, but new implementations are strongly encouraged not to rely upon parameters other than the ones currently documented.
Text Message Received
Text message webhooks are sent after a text message is received. Text message webhooks send after a text message is received by one of your tracking numbers. This webhook includes all information about the message, including the ID for the message, as well as the contents of the message.
Text Message Sent
Text message webhooks sent after a text message is sent. Text message sent webhooks send after a text message is sent by one of your tracking numbers. This webhook includes all information about the message, including the ID for the message, as well as the contents of the message
Form Submission
Form Submission webhooks send whenever a form is submitted to your website. To retrieve this information, you should have Form Tracking active. This webhook sends information gathered from the form submission, including all recognized form fields.