> For the complete documentation index, see [llms.txt](https://docs.itoc360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itoc360.com/integrations/inbound-integrations/workflow-and-automation/twilio-errors-integration.md). # Twilio Errors Integration [Twilio's](https://www.twilio.com/en-us) Debugger webhook notifies you in real time whenever an error or warning occurs in your Twilio account — a failed SMS delivery, an invalid API request, a webhook timeout, or any other issue Twilio detects while processing your traffic. This integration forwards those notifications to ITOC360, opening an alert every time Twilio records a new error or warning event. ### How It Works Twilio fires an HTTP POST request to your configured webhook URL each time a Debugger event occurs. The payload includes the event's severity level (`ERROR` or `WARNING`), a unique event identifier, and a nested JSON object with product-specific details such as the affected resource SID and error code. ITOC360 receives this payload and creates an alert immediately. ### Prerequisites * A Twilio account * Your ITOC360 source token ### In ITOC360 Go to **Sources**, click **Create Source**, and select **Twilio Errors** from the list. Copy the webhook URL that appears — you'll need it in the next step. ### In Twilio #### Step 1 — Open the Debugger Webhook Settings In the Twilio Console, click the **Monitor** tab. In the left sidebar, expand **Logs → Errors**, then click **Webhook**. Paste your ITOC360 webhook URL into the **Webhook URL(**[**https://api.itoc360.app/functions/v1/events?token=\**](https://api.itoc360.app/functions/v1/events?token=)**)** field and click **Save**.
*** ### Alert Behavior | Level | itoc360 Action | Priority | | --------- | -------------- | -------- | | `ERROR` | Opens an alert | HIGH | | `WARNING` | Opens an alert | MEDIUM | Twilio Errors does not send a recovery payload — alerts opened by this integration remain open until you resolve them manually in ITOC360. ### Notes * Every individual error or warning event creates a separate alert. If your account generates high error volumes, consider using **Twilio Alarms** instead — it aggregates errors over a time window and notifies only when a threshold is exceeded, reducing noise. * The `Payload` field in each webhook contains a JSON string with product-specific details like the error code and affected resource SID. This data is visible in the alert metadata inside itoc360. * Twilio recommends migrating to **Twilio Event Streams** for more scalable error monitoring. The Debugger webhook remains fully functional but Event Streams provides more flexibility for high-volume accounts. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.itoc360.com/integrations/inbound-integrations/workflow-and-automation/twilio-errors-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.