Why use Hookfire with Twilio?

Instant push notifications

Get notified on your phone the moment a Twilio webhook fires. No more checking dashboards.

Subscribe to what matters

Choose exactly which Twilio events trigger notifications. Filter out the noise.

Team-wide delivery

Control who on your team gets notified and how: push notifications, record only, or both.

Setup in under 2 minutes

Copy a webhook URL, paste it in Twilio, and you're done. No code required.

Supported events

Event	Sample notification
Incoming message `message.received` 💬 Text from +14017122661 Hi, is the shop open on Sunday?	💬 Text from +14017122661 Hi, is the shop open on Sunday?
Call not answered `no-answer` 📵 Missed call from +14017122661 Nobody picked up on +15558675310	📵 Missed call from +14017122661 Nobody picked up on +15558675310
Call got a busy signal `busy` 📵 Missed call from +14017122661 +15558675310 was busy	📵 Missed call from +14017122661 +15558675310 was busy
Caller hung up first `canceled` 📵 +14017122661 hung up The call to +15558675310 ended before anyone answered	📵 +14017122661 hung up The call to +15558675310 ended before anyone answered
Call failed `failed` 📵 Call from +14017122661 failed Twilio could not connect the call to +15558675310	📵 Call from +14017122661 failed Twilio could not connect the call to +15558675310
Call completed `completed` 📞 Call from +14017122661 ended Call to +15558675310 ended	📞 Call from +14017122661 ended Call to +15558675310 ended

How to connect Twilio

Hookfire can tell you about texts to a Twilio number and about calls nobody answered. See Twilio’s webhook docs.

Step 1: Create an Integration

Go to your organization’s Integrations page.
Click Add Integration and select Twilio.
You’ll receive a unique Webhook URL. Copy it.

Step 2: Point Your Number at Hookfire

In the Twilio Console, open Phone Numbers, pick your number, and:

Incoming texts: set the webhook for A message comes in to your Hookfire URL, method HTTP POST. Hookfire answers with an empty reply, so the sender gets nothing back. This replaces any other app handling texts to that number.
Calls: set the Call status changes callback to your Hookfire URL. Leave the voice webhook that answers calls as it is: pointing that at Hookfire would stop your number answering.

If your calls are forwarded with <Dial>, set Hookfire as the action URL of the <Dial>. It is told whether the forwarded call was answered, which is the reliable way to learn about a missed call. Hookfire replies with an empty response, which ends the call, so only use it where your TwiML has nothing to do after the <Dial>.

Use either the Call status changes callback or the <Dial> action for a number, not both. With both, a forwarded call nobody picked up would also arrive as a completed call, since your number itself answered it.

Step 3: Signing Secret

Copy your Auth Token from the Twilio Console’s account dashboard.
Paste it into the Signing Secret field on your Hookfire integration page.

Twilio signs every request with the X-Twilio-Signature header, made from your Auth Token, the URL and the parameters. Hookfire refuses anything that does not match. The Auth Token is a powerful credential: consider using a subaccount for the number. If you rotate the token, update it here.

Step 4: Subscribe to Events

On your Hookfire integration page, toggle on the events you want to receive push notifications for.

Step 5: Test

Text your Twilio number, or click Send test next to an event on your Hookfire integration page.

Supported Events

Event	Description
`message.received`	A text arrived at your number
`no-answer`	A call rang out without being answered
`busy`	A call got a busy signal
`canceled`	The caller hung up before anyone answered
`failed`	The call could not be connected
`completed`	A call ended after being answered

Twilio