# Ported Twilio Numbers and Make .com **URL:** \ **Category:** Support Help\ **Tags:** telephony\ **Created:** [May 22, 2026, 9:08pm UTC](https://community.retellai.com/t/ported-twilio-numbers-and-make-com/2840 "2026-05-22T21:08:03Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![ernestadamsrei](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/ernestadamsrei/32/1984_2.png) [@ernestadamsrei](https://community.retellai.com/u/ernestadamsrei)\ **Post date:** [May 22, 2026, 9:08pm UTC](https://community.retellai.com/t/ported-twilio-numbers-and-make-com/2840/1 "2026-05-22T21:08:03Z")
I am not receiving the call\_analyzed packet when I call from the ported number. Logs show that Retell is receiving a 404 error from [Make.com](http://Make.com). When I call from the web within Retell it works fine. Please help, thanks! ---
**Author:** ![andrew5](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/andrew5/32/1986_2.png) [@andrew5](https://community.retellai.com/u/andrew5)\ **Post date:** [May 23, 2026, 12:28am UTC](https://community.retellai.com/t/ported-twilio-numbers-and-make-com/2840/2 "2026-05-23T00:28:09Z")
Hey! This is a classic difference between how Retell sends the `call_analyzed` webhook for web calls vs. phone calls — the payload structure is slightly different and that’s likely what’s tripping up your [Make.com](http://Make.com) scenario. **First, a few things to check:** 1. **Are you using the same agent for both the web call and the ported number?** It’s worth confirming — if they’re separate agents, one may have the webhook configured and the other may not. 2. **Where is your webhook configured — workspace level or agent level?** Go to your Retell dashboard and check both: 3. - _Workspace-level:_ Settings → Webhooks - - _Agent-level:_ Open the agent → Webhook Settings - If it’s only set at one level, calls from a different context may not be triggering it. - Do you have the Webhook Events setup for call analyzed events on? - **The most likely culprit — payload differences:** 4. Open your Make scenario and look at the raw data coming into your webhook trigger. Compare what the payload looks like for a **web call** vs. a **phone call**. The key fields that differ are things like `call_type` (`"web_call”` vs `"phone_call”`), and the presence/absence of fields like `from_number`, `to_number`, etc. If you have conditional routing in your Make scenario (e.g., a Router or a filter on a specific field), it’s very likely that the phone call payload is not matching the condition — so the route that handles `call_analyzed` never gets triggered, and Make returns a 404 back to Retell. **Quick debug steps:** - Temporarily remove any filters/conditions on your webhook trigger in Make and run a test phone call — does the data arrive? - - Check the Make scenario execution history and look at what payload came in — share it here if you can (redact any sensitive info) and we can help identify what’s different. - Let us know what you find! ---
**Author:** ![mark1](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/mark1/32/2524_2.png) [@mark1](https://community.retellai.com/u/mark1)\ **Post date:** [May 23, 2026, 8:17pm UTC](https://community.retellai.com/t/ported-twilio-numbers-and-make-com/2840/3 "2026-05-23T20:17:32Z")
Hello @ernestadamsrei The 404 from [Make.com](http://Make.com) means Retell is hitting an endpoint that doesn’t exist at [Make.com](http://Make.com)’s side. The key insight: when calling from the web (Retell), the agent uses your account-level or agent-level webhook. When calling from the ported number, it likely uses an agent assigned to that phone number which may have a different (or stale/invalid) `webhook_url` set — pointing to a [Make.com](http://Make.com) scenario URL that no longer exists or is inactive. Things to check: 1. The agent bound to the ported number — verify its `webhook_url` field. Agent-level webhooks override account-level ones. 2. Make sure the [Make.com](http://Make.com) scenario is turned on (inactive scenarios return 404). 3. Confirm the [Make.com](http://Make.com) webhook URL hasn’t been regenerated. Thank You ---
**Author:** ![ernestadamsrei](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/ernestadamsrei/32/1984_2.png) [@ernestadamsrei](https://community.retellai.com/u/ernestadamsrei)\ **Post date:** [May 23, 2026, 8:51pm UTC](https://community.retellai.com/t/ported-twilio-numbers-and-make-com/2840/4 "2026-05-23T20:51:47Z")
Hi Andrew, thanks for your help! 🙂 The first snip is what I get when calling from the port number, the second is what I get when testing from the web. I have the same Web Hook in the agent and the phone number. The call\_analyzed payload only comes when I test it. I have other agents that use the native Retell AI phone number that do not have this problem. ![image](https://canada1.discourse-cdn.com/flex008/uploads/retell1/original/2X/4/4052375a79324c1db2ac696208c3aafb977d13fc.png) ---
**Author:** ![ernestadamsrei](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/ernestadamsrei/32/1984_2.png) [@ernestadamsrei](https://community.retellai.com/u/ernestadamsrei)\ **Post date:** [May 23, 2026, 8:52pm UTC](https://community.retellai.com/t/ported-twilio-numbers-and-make-com/2840/5 "2026-05-23T20:52:24Z")
![image](https://canada1.discourse-cdn.com/flex008/uploads/retell1/original/2X/3/3bec2fb45325aaaf56df038ee0fad4b0f1af8519.png)