Call initiation failed
A telephony call failed to start. Requires an agent connected to a supported telephony provider.
→
Ready-made Workflow
Alert Slack when an ElevenLabs call fails to start
Connect your own ElevenLabs key with ElevenAgents Write and Webhooks Access, then choose a dedicated agent without an existing agent or inherited workspace post-call webhook. FastHook manages the signed subscription. Only new matching events after activation are processed; historical conversations are not imported. When the final consumer stops, FastHook removes its owned webhook during the next 15-minute reconciliation cycle. The selected agent must use supported telephony, such as Twilio or SIP, for a real call-initiation failure. Connect Slack and choose the alerts channel. Send the conversation ID, agent ID, provider failure reason and event time, without phone numbers, raw carrier metadata, transcript or credentials. A provider may report an unknown reason; inspect the native call history for details. Plain-text messages have link and media previews disabled. This recipe only reports failures: it does not place calls or retry them. Manual workflow reruns can send another alert.
Use this templateCreates a new Draft · no credentials copied
What gets copied
The working graph, not another user's secrets
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Send call initiation failure alert
Send text, Block Kit content, attachments, or a thread reply to a channel.
Before activation
Connect your accounts in the Draft
ElevenLabs
Connect your own ElevenLabs account and review the provider settings used by this Workflow.
Slack
Connect your own Slack account and review the provider settings used by this Workflow.
Explore connected apps
Related Workflow templates
ElevenLabs · Slack
Notify Slack when an ElevenLabs conversation completes
Connect your own ElevenLabs key with ElevenAgents Write and Webhooks Access, then choose a dedicated agent without an existing agent or inherited workspace post-call webhook. FastHook manages the signed subscription. Only new matching events after activation are processed; historical conversations are not imported. When the final consumer stops, FastHook removes its owned webhook during the next 15-minute reconciliation cycle. Connect Slack and select the destination channel. Send the conversation ID, agent ID, duration and analysis outcome after post-call processing, rather than immediately at hangup. The full transcript, generated free-text summary, phone numbers and raw metadata are not sent. Conversation completed and Transcript ready are two views of the same native post_call_transcription event; enabling both recipes intentionally produces both outputs. Messages use plain text with previews disabled. Manual workflow reruns can send another notification.
- 1. ElevenLabs · Conversation completed
- 2. Slack · Send conversation completion details
Questions
Template FAQ
Does the template copy someone else's credentials?
No. FastHook creates a disconnected Draft. Connect your own ElevenLabs, Slack accounts before activation.
Can I change the Steps and mappings?
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
What is copied into my workspace?
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
When does the Workflow start running?
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.