Error Log Recorded
Emit an event when Twilio Event Streams delivers com.twilio.error-logs.error.logged.
Ready-made Workflow
Notify a Slack channel when Twilio records an application error or warning. Connect Twilio and Slack, then browse to the channel used for operational alerts. Each message includes the log level, Twilio product, error code and creation time. Includes its own fictional Hamburg delivery-error example with German characters. The trigger listens for Twilio Error Logs events delivered through Event Streams after the workflow is activated; it does not import older Debugger entries. Request bodies, response bodies, phone numbers, message content, account identifiers and credentials are not copied into Slack. The message uses plain text with link and media previews disabled. Twilio Event Streams provides at-least-once delivery, so a provider replay can post another notification. This template monitors errors and does not send messages, place calls or modify Twilio resources.
What gets copied
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Emit an event when Twilio Event Streams delivers com.twilio.error-logs.error.logged.
Send text, Block Kit content, attachments, or a thread reply to a channel.
Before activation
Connect your own Twilio account and review the provider settings used by this Workflow.
Connect your own Slack account and review the provider settings used by this Workflow.
Questions
No. FastHook creates a disconnected Draft. Connect your own Twilio, Slack accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.