Skip to main content

​
What are Post-call Flows?

A post-call flow is a workflow that runs automatically when a call ends. It receives everything that happened on the call — transcript, duration, contact info, dynamic variables — and uses it to update your systems without anyone lifting a finger. This is where the follow-up work after a conversation happens:
  • Log the call and its outcome to your CRM
  • Email a summary to your team
  • Create a support ticket with the transcript attached
  • Push structured data to a spreadsheet and notify a Slack channel
  • Branch on the result — for example, escalate only when the call ended unresolved
Post-call flows are the opposite end of the call from pre-call flows. A post-call flow runs after the call ends; a pre-call flow runs before the agent greets.

​
How it works

1

The call ends

The caller hangs up or the agent ends the call.
2

The flow fires

Diga sends the full call data to every post-call flow assigned to the agent.
3

Your actions run

The flow runs its steps — logging, notifying, updating — using any of the call’s data.
Post-call flows run in the background after the call is already over, so they never add delay to the conversation and the caller never notices them.

​
Build a Post-call Flow

1

Create a workflow

From the Workflows section, create a new workflow (from scratch or a template). See Creating Workflows.
2

Select the Call Finished trigger

Choose the Diga piece and select the Call Finished trigger. This runs the flow automatically every time an assigned agent’s call ends.
3

Test the trigger

Click Test trigger to pull in sample call data. You’ll use this data to configure the fields in your following steps.
4

Add your actions

Add the steps you need, using the call data wherever you want:
  • Google Sheets → Add row (log the call)
  • Gmail → Send email (the transcript as a summary)
  • Slack → Send message (notify your team)
  • HTTP → Make request (update any system)
5

Publish and enable

Publish the workflow and make sure it’s enabled. Then assign it to an agent (see below).

​
Data available to the flow

When the call ends, the flow receives the complete call record — including the status, duration, end_reason, the contact’s phone_number, the call’s dynamic_variables, and the full messages array (the transcript). See the Call Finished trigger for the full field reference.
Use any of these fields in your actions. For example, insert the full transcript into an email, or send the call duration and outcome to a spreadsheet.

​
Assign Post-call Flows to an Agent

Open the agent and go to its Workflows section. Add the post-call flow there. Each flow shows a Post-call badge so you can tell them apart.You can assign multiple post-call flows to the same agent — all of them run when the call ends.
Like other flows, post-call flows are assigned per agent version. The flow must be published and enabled before it will run.

​
Common use cases

Send the transcript to your team by email or Slack, with the duration and outcome, so everyone stays in the loop without listening to the recording.
Find or create the contact in your CRM, log the call, and create a follow-up task — all from the call data.
Add a row to a spreadsheet or a record to your database for every call, so you can report on volumes, reasons, and outcomes.
Branch on the call result and only create a ticket or alert a human when the call ended without resolution.

​
Next Steps

The Diga piece

Full reference for the Call Finished trigger and the data it provides.

During-call flows

Run a workflow mid-conversation, as a tool the agent can call.

Assign to agents

Connect your workflows with agents so they execute.

Creating workflows

Build the flow step by step in the visual builder.