After-call workflows

After-call workflows run ordered actions on a saved business connection after a call completes. They can create contacts, log a call, add notes or perform other actions explicitly marked for automation by that provider.

Configure a workflow

1. Connect and test the provider in Integrations.
2. Enable writes if a step creates or changes records.
3. Add up to eight ordered steps. Choose only actions available for after-call automation.
4. Use a read step to find an existing record before an update. Map returned identifiers into later steps rather than asking the model to invent them.
5. Save and test with a new authorized call. Changes apply to calls beginning at or after the workflow save; queued historical calls are skipped.
6. Inspect both the action receipts and the vendor records before enabling wider production use.

Map variables

• {{call.id}} is the completed call identifier.
• {{analysis.summary}} uses the latest completed analysis summary, with a basic call-status summary as fallback.
• {{call.metadata.firstName}} reads a value already present in call metadata.
• {{steps.0.id}} reads an identifier returned by the first step. Some providers use a nested path such as {{steps.0.data.id}}; inspect the actual result.

An exact placeholder preserves its JSON value. Missing paths become an empty string and can fail required-field validation. Use the selected action’s schema rather than assuming all CRMs accept the same field names.

Recovery behavior

Successful recorded steps are reused during job recovery. Failed or uncertain writes stop for inspection. Editing a workflow does not create permission to repeat an already processed write for the same call; changed arguments are held for review.

Appointment changes, outbound calling and SMS are not automatically enabled by a CRM connection. Keep caller-confirmed scheduling in its authorized booking flow, and configure separate outreach permissions where needed.