Introduction to Workflows

Documentation Index

Fetch the complete documentation index at: https://docs.diga.io/llms.txt

Use this file to discover all available pages before exploring further.

​

What are Workflows?

Workflows are multi-step automations that connect your agent calls with external services through a visual builder. Where an integration handles a single API call, a workflow lets you chain multiple steps together across different services, with logic and conditions in between. For example, when a call ends a workflow can extract the key points from the transcript, create a deal in HubSpot, add a row to a Google Sheet, and notify your team on Slack, all as a single automated sequence.

​

Workflows vs Integrations

Both tools connect your agents with external services, but they serve different purposes: Use an integration when your agent needs to hit one endpoint and return the result to the conversation. For example, checking order status in your database or creating a ticket in your CRM. Use a workflow when you need more than that: multiple services involved, post-call processing, outbound call campaigns, or any logic that goes beyond a single request.

​

Types of Workflows

​

Post-call

Post-call workflows activate automatically when a call ends. The workflow receives all call data: transcript, duration, contact information, dynamic variables, and the full message history. Common use cases:

• Summarize the call and send it by email
• Update a record in your CRM (HubSpot, Salesforce, etc.) and create a follow-up task
• Create a support ticket and attach the transcript
• Log structured data to Google Sheets and trigger a Slack notification
• Run conditional logic, for example to escalate to a human only if the call ended without resolution

​

During call

During-call workflows act as tools the agent can invoke while speaking with the user. The agent detects when it needs external information, executes the workflow, and uses the response to continue the conversation. Use a workflow here (instead of an integration) when you need to do more than one thing: for example, look up a customer’s account, then check their open orders, then format the combined data before returning it to the agent. Common use cases:

• Query multiple systems and merge the results
• Look up data and conditionally branch based on the response
• Transform or enrich data before returning it to the agent
• Perform a booking that requires calling several APIs in sequence

​

Pre-call

Pre-call workflows use the Make Call action from the Diga piece to initiate outbound calls. They can be triggered by any external event: a CRM record change, a form submission, a scheduled time, or a webhook. Common use cases:

• Call leads automatically after they complete a form
• Scheduled follow-up campaigns
• Confirmation calls after a booking
• Appointment reminders triggered by your calendar system

​

Key Concepts

​

Pieces

Pieces are connectors that provide triggers and actions for specific services. There are over 200 pieces available: Google Sheets, Slack, HubSpot, Gmail, Stripe, and many more. The Diga piece is the one that connects workflows with your calls.

​

Triggers

A trigger is the event that starts a workflow. Each workflow has exactly one. The Diga piece provides two call-specific triggers:

• Call Finished: fires when a call ends
• Function Call: fires mid-call when the agent needs to run an action

​

Actions

Actions are the steps that execute after the trigger. Each action receives data from all previous steps, so information flows through the chain. You can pass the transcript from step 1 into the email in step 4, for example.

​

Connections

Connections are the credentials pieces use to access external services (API keys, OAuth tokens). You authorize them once and reuse them across all workflows. See Connections for details.

​

Next Steps