> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telli.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflows

> Automate actions that fire after every call

Workflows turn what happens on a call into automatic follow-up actions. Pick a trigger like **Call ended**, add the actions you want (send a webhook, update a contact, sync to Salesforce), and telli takes care of the rest after every call.

<Frame>
  <video src="https://migthzpcwvipwgioldfr.supabase.co/storage/v1/object/public/public_assets/changelog/2026-05-04-week-19/workflows.mp4" width="3842" height="2160" controls muted autoPlay loop playsInline className="w-full rounded-xl" />
</Frame>

## What you can automate

| Use case                         | What it does                                                                                                 |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Push call data to your tools** | Send call summaries, outcomes, and collected data to a URL after every call.                                 |
| **Keep contact records current** | Update telli contact fields or custom properties based on what the agent collected.                          |
| **Sync your CRM**                | Create or update Salesforce records straight from a completed call.                                          |
| **Branch on call results**       | Use conditions so only certain calls trigger certain actions (e.g. only qualified leads sync to Salesforce). |

## Available blocks

<Tabs>
  <Tab title="Triggers">
    Triggers decide **when** a workflow runs. Today, workflows run after a completed call:

    | Block          | Use it to                                                          |
    | :------------- | :----------------------------------------------------------------- |
    | **Call ended** | Evaluate the workflow after a completed call from a selected agent |
  </Tab>

  <Tab title="Actions">
    Action blocks perform work outside the workflow branch itself:

    | Block                        | Use it to                                                   |
    | :--------------------------- | :---------------------------------------------------------- |
    | **Webhook**                  | Send call, contact, and workflow data to another system     |
    | **Update contact**           | Update contact fields or custom contact properties in telli |
    | Salesforce **Create record** | Create a Salesforce record when Salesforce is connected     |
    | Salesforce **Update record** | Update a Salesforce record when Salesforce is connected     |
  </Tab>

  <Tab title="Conditions">
    Condition blocks decide which path the workflow should follow:

    | Block         | Use it to                                                       |
    | :------------ | :-------------------------------------------------------------- |
    | **If / else** | Split the workflow into a true branch and a false branch        |
    | **Switch**    | Route the workflow through multiple branches based on one value |
  </Tab>
</Tabs>

## Build your first workflow

<Steps>
  <Step title="Open Workflows and create a new one">
    Go to **Workflows** in the telli dashboard and click **Create Workflow**.
  </Step>

  <Step title="Name and describe the workflow">
    Use a name that describes the result, like *"Send call summary to CRM"* or *"Update lead status after call"*.
  </Step>

  <Step title="Select and configure a trigger">
    Choose **Call ended** as the trigger, then pick the agent whose completed calls should start the workflow.
  </Step>

  <Step title="Add action and condition blocks">
    Use the **+** button on the canvas to add blocks after the trigger. Configure each block in the side panel, and add **If / else** or **Switch** when only some calls should follow a given path.
  </Step>

  <Step title="Publish the draft">
    Click **Publish** once the trigger and required blocks are configured. Publishing creates the version telli uses for new runs.
  </Step>

  <Step title="Enable the workflow">
    Flip the **Enabled** switch to turn on automatic execution. A workflow must be published before it can be enabled.
  </Step>
</Steps>

<Tip>
  Test with a manual run before relying on automatic execution. In the workflow builder, open the **Runs** tab, click **Run manually**, and pick a completed call to step through the workflow against real data.
</Tip>

## Go deeper

<Card title="Workflows reference" icon="diagram-project" href="/platform/workflows">
  Full reference for triggers, blocks, manual runs, version history, and end-to-end examples like logging telli calls back to Salesforce.
</Card>