I recently upgraded to a paid Twilio account and I’m trying to build an automation that checks if phone numbers are working. My current setup successfully sends outbound calls using Twilio through Zapier, which works great.
The issue I’m running into is with capturing call responses. Zapier has a trigger called “New Call” that should catch call data and use it to start other automations. However, this trigger only seems to fire when I receive incoming calls to my Twilio number. When I make outgoing calls, the trigger doesn’t activate at all.
Has anyone managed to get Zapier to detect outbound call events from Twilio? Am I missing some configuration step in either platform? I need to know when my outbound calls connect or fail so I can validate phone numbers automatically.
yea, i got the same prob. zapier only picks up inbound calls from twilio. i managed to fix it using their status callback webhooks tho. just specify where twilio should send the call status updates when you make an outbound call. it’s a lil more work but worth it!
Had this same issue six months back while building a lead validation workflow. Skip Zapier’s native trigger - it’s a pain. Instead, I created a custom webhook endpoint in Zapier, then set up my Twilio outbound calls to hit that webhook URL using the StatusCallback parameter. Pro tip: your webhook needs to handle multiple events per call since Twilio fires updates for ringing, answered, completed, etc. Way more reliable than fighting Zapier’s inbound-only nonsense. Takes longer to set up but it’s been bulletproof for automated phone validation.
You’re encountering a common limitation with Zapier and Twilio. The ‘New Call’ trigger is designed for inbound calls only, which means it won’t activate for outbound calls. I dealt with a similar challenge while creating a phone validation system. Instead of relying on Zapier’s built-in trigger, consider using Twilio webhooks. By setting a StatusCallback URL when you make outbound calls, you can direct Twilio to send updates to a Zapier webhook. You’ll receive call status updates like ‘answered,’ ‘busy,’ or ‘failed’ as the call progresses. Just include the StatusCallback parameter with your Zapier webhook URL in your API call and define the StatusCallbackEvent for the events you wish to track. This method offers better control and effectiveness for monitoring outbound calls.
Hey Guys,
I encounter a problem described in this topic. While my area of expertise is far away from knowledge served here i would like to ask for a bit assistance if possible.
I try to build a solution for fellow engineers being on duty after working hours. Idea is to trigger a call via twilio and based on StatusCallback trigger next steps like re-call on “busy” or “failed” and after few unsuccessful tries switch to 2nd on-duty person and then big loop after call is answered.
I use mailbox that if recieve mail will trigger the call to pointer number. Via Zapier it is 2-step process and it just works. I stuck on getting StatusCallback value to build on it.
I try to use “Weebhooks by Zapier” block with event GET (i’ve set zapier webhook https in Twilio StatusCallback field in TwiML app). In “configure” section i’ve tried to set 'Query String Params" with 'CallStatus" “StatusCallback” “StatusCallbackEvent” but in test i am anly recieving Status value “queued” (among other data) and nothing more specific.
I am still looking for some tips in countless topics but as a hardware engineer it is a whole new world for me and i am probably not able to understand all i read and can’t connect dots ;[.
Any chance you guys have a spare time to push me in the right direction?
Thanks in advance.