Skip to main content
A follow-up can be a task for a person, a CRM update, or another customer interaction. First choose the event that makes it appropriate, then configure the action.

​
Choose the mechanism

Receive the analysis webhook. Use the result and extracted data to choose the next step in your backend, n8n, or Make.

​
Recipe: create a task after a call

1

Define the follow-up decision field

In Post-call, add a boolean analysis field such as requires_follow_up. Explain when it should be true. Its value arrives at data.call.call_analysis.custom_analysis_data.requires_follow_up.
2

Configure the receiver and mapping

Publish the agent’s outgoing webhook URL. Keep data.call.call_id and, when present, data.contact.contact_id. Persist the event before acknowledging receipt, then process the task through a queue or recoverable workflow.
3

Check conditions before acting

Allow only the expected call types, exclude tests, and check for a contact. If the analysis field is absent, send the case for review or query the call; do not treat absence as false.
4

Create the task once

Use your own unique key such as call_id + create_follow_up_task. Store action state and result durably. Do not rely on temporary memory or mark completion before creating the task.Create it in your CRM or use Create task. That endpoint requires details, brief, type, and created_by. Include the contact reference in details: contact_id currently does not create a persisted association through that operation.

​
Map the data

​
Choose the next step

To call again, use Call a contact with schedule. Store the relationship between original and new attempts. Do not connect every no_answer to an immediate call: that would create an unlimited loop.

​
Recipe: send conversation data to your CRM

In an inbox rule, choose a trigger such as Conversation Closed, add AI Conversation Analysis if you need extraction, then Send Webhook. Define a Body template using the editor’s available variables. ai.* variables only exist after the analysis step. Inspect Run History → Trigger Payload and each step’s Output. Replay executes actions again; the receiver must also recognize duplicates.
A test can start calls, send messages, or create real tasks. Use a controlled contact and verify one complete execution before enabling the workflow for everyone.

​
If the next step is WhatsApp

The voice webhook does not automatically provide channel_id or thread_id. Get the channel through List channels and choose the correct conversation. When initiating contact or using a template, see Send template and Templates. A call webhook does not itself open a WhatsApp conversation window.

​
Frequently asked questions

The creation response identifies the request. Wait for analysis delivery or query the record before making a result-based decision.
The retry only delivers data again. Your automation could still make another call if it does not deduplicate actions.
Before executing a pending action, recheck the customer’s response, opportunity state, and attempt limits in your system.

​
Continue with

Call types

Separate tests, campaigns, and production.

Webhook types

Choose the right trigger.