Keep your calling workflows in n8n.
Import lead intake and signed outcome workflows for Slack, Teams, or Sheets.
Imports are inactive. Set credentials and the production webhook URL before activation.
- Source event or saved call outcome
- n8n validates and routes the request
- Queue lead or destination update
What you need.
Importable workflows and signed webhook
- An n8n instance where you can import workflows and configure credentials.
- For intake, a Redialler workspace key, queue ID, and authenticated source webhook.
- For signed outcomes, customer-owned self-hosted n8n with crypto Code-node access and protected signing-secret environment access.
Set up n8n.
Open n8n setup in Redialler Settings and download the relevant workflow JSON. Imports are inactive.
For intake, set the Redialler origin and queue ID in Prepare Request. Select separate Header Auth credentials for the source webhook and Redialler API request.
Map a real phone, stable source lead ID, and separate source event ID. Keep accepted, duplicate, and blocked results visible.
For outcomes, configure the signing secret and the chosen Slack, Teams, or Google Sheets credentials on your self-hosted instance.
Use the production Webhook URL in a Redialler outbound connection. Review node versions and credentials before activation.
Confirm provider access and delivery in your account before rollout.
Data and permissions.
- Intake passes mapped lead fields and supplied consent evidence to Redialler.
- Outcome workflows verify the signature over the exact raw request body before destination work.
- Sheets outcomes match rows by event ID and write values as-is, without parsing. Notification workflows send outcome metadata, with no recordings, transcripts, or notes.
Current limits.
- n8n Cloud is not assumed to support the required module and environment access for signed outcome workflows.
- Intake makes at most three HTTP attempts. A Retry-After above the five-minute wait limit becomes repair work.
- Confirm workflow import, node compatibility, and destination delivery on your n8n instance before rollout.
- Destination sends can repeat after an uncertain response. Serialize Sheets executions and keep identity columns unchanged.
Provider documentation
Questions about n8n.
Are imported workflows active immediately?
No. Imports are inactive. Configure credentials, placeholders, and the correct production Webhook URL before activation.
Can I use the test Webhook URL?
Use it only while n8n is listening during your own validation. A persistent Redialler connection needs the production Webhook URL.
Why does the outcome workflow need the raw body?
The signature covers the timestamp and exact JSON bytes. Parsing and re-serializing the body can change those bytes and invalidate verification.
Set up n8n for your workspace.
Sign in to open this tool in Settings. An organisation admin connects it for your workspace.