Skip to main content
Workflows automate repeatable work across calls, contacts, and integrations. Start from a trigger, add actions and conditions in the visual builder, and keep contact records, CRMs, and external systems up to date automatically. The steps below use Call ended as the example trigger.

​
Create a workflow

1

Open Workflows

Go to Workflows in the telli dashboard. The list shows your workflows, run counts, triggers, statuses, and last update times.
2

Click Create Workflow

Click Create Workflow to open the creation dialog.
3

Name and describe the workflow

Give the workflow a clear name and optional description. Use a name that describes the result, such as “Send call summary to CRM” or “Update lead status after call”.
4

Select a trigger

Choose the event that should start the workflow. For this guide, select Call ended to evaluate the workflow after a completed call.
5

Configure the trigger

Fill in the settings required by the trigger. For Call ended, select the agent and the call statuses that should start this workflow.
6

Add workflow blocks

Use the + button on the canvas to add action and condition blocks after the trigger.
7

Publish the draft

Click Publish when the trigger and required blocks are configured. Publishing creates the version telli can use for new workflow runs.
8

Enable the workflow

Turn the workflow Enabled. Disabled workflows keep their draft and published versions, but do not run automatically.

​
Choose which ended calls start the workflow

The Call ended trigger uses your selected call statuses as an OR filter. An ended call starts the workflow once when it matches any selected status. After selecting the statuses that may enter the workflow, use Status or Has follow-up in an If / else or Switch block to route them to different actions. Unknown and unfinished calls do not start a call-ended workflow. Failed calls start it only when Failed is selected.

​
Start when a contact is created

Select Contact created as the trigger to run the workflow when a new contact is added to telli, including through CSV imports, the API, or integrations. Use the new contact’s fields and custom properties in subsequent blocks to update contact details, send a webhook, or create a CRM record. Publish and enable the workflow to start automatic runs.

​
Run on a schedule

Select Scheduled as the trigger to run a workflow at regular intervals or at set times. In Schedule, choose a preset or describe the schedule, such as “Every 20 minutes” or “Weekdays at 9:00 AM”, then select the result. Check the displayed time zone and Next 5 execution times before publishing and enabling the workflow.

​
Add workflow blocks

Triggers define when the workflow starts. Action and condition blocks define what happens next. Add them from the canvas and configure each block in the side panel. Use a Delay block to pause before the next step. Set a total duration of at least 10 seconds. Combined delays along any workflow path cannot exceed 30 days. You can leave a delay unconfigured in a draft, but you must set a valid duration before publishing.
Triggers decide when a workflow runs:

​
Fetch CRM data with a custom integration

telli has native integrations for HubSpot and Salesforce. The steps below cover custom CRM integrations that use HTTP requests.
Use an HTTP request block to retrieve records from a CRM API, then use the returned data in later workflow steps. You need the CRM’s API endpoint and credentials that permit access to the required records.
  1. Add an HTTP request block. Enter the CRM’s HTTPS URL and choose the method the endpoint requires, such as GET for a lookup.
  2. Configure authentication and any required query parameters. Use workflow variables for a record ID, phone number, or other search value.
  3. Run the published workflow to capture a sample response. In a later block’s field picker, select the HTTP request block and browse its JSON response, including nested fields.
For example, fetch a contact’s current lead status, check it with If / else, then update a telli contact or send data back to the CRM.

​
Fetch multiple pages

Enable Pagination when the CRM returns records across several pages. Choose Update a parameter for page numbers or cursors, or Response contains next URL to follow a link from the response. Set a Stop condition and Maximum pages to control when fetching ends. Use Output list to choose how to keep the results:
  • Records combines records into one list. Set Items array path to the array in the CRM’s JSON response, such as data.contacts.
  • Page bodies keeps each response page together.
Use the block’s items output for the combined results. The responseJson output contains the final page’s parsed JSON response. You can inspect each fetched page in the workflow run details.
If authentication, pagination, or nested response fields are not visible in your account, contact telli to enable these options.

​
Publish, enable, and edit

Workflow edits are saved as a draft while you work. Publishing turns the current draft into the version telli uses for new runs.
Use the draft while you are building or changing a workflow. If the builder highlights incomplete or broken blocks, configure those blocks before publishing.

​
Test and monitor runs

Run a workflow manually before relying on automatic execution. Manual runs use the published workflow. The steps below test a Call ended workflow against a real completed call.
1

Open the workflow

Open the workflow you want to test.
2

Go to Runs

Select the Runs tab in the workflow builder.
3

Click Run manually

Click Run manually. This action is available after the workflow is published and a trigger agent is selected.
4

Choose a completed call

Select one of the completed calls from the trigger agent.
5

Click Run workflow

Click Run workflow to create the run.
6

Review the trace

Open the run details to see which blocks ran, which branches were used, and where a failure happened if a block did not complete.
The Runs tab groups the history by your local day. The status icon shows whether the workflow completed, failed, or remains in progress. The first line names the trigger event, then shows the Manual or Triggered origin and exact local time. When snapshot context is available, the second line identifies the contact or call with the saved contact name, phone number or email, plus the call duration. The All time metrics include every retained run, including runs not loaded in the current list. The history loads up to 50 runs at a time. Scroll down or click Load more to fetch older runs, then open any row to review its full trace. When a workflow reaches a delay, run details show the completed blocks and mark the delay In progress. Progress updates at the next delay or when the run finishes.

​
Common examples

Use Call ended with an HTTP request block when another system needs call details after a completed conversation.This is useful for CRMs, data warehouses, or automation platforms that should receive call summaries, contact fields, call outcomes, or collected data.To send a recording link, select Call Metadata → Recording URL in a body field, header, or query parameter.
  • Contact Properties - Define the custom fields workflows can update on telli contacts
  • SMS - Send SMS messages from agents and workflows
  • WhatsApp Business - Send WhatsApp template messages from agents and workflows
  • Call Analysis - Learn how telli extracts structured outcomes from completed calls
  • Webhooks - Send completed call data to external systems outside of workflows
  • Salesforce - Connect Salesforce before using Salesforce workflow blocks
  • HubSpot - Connect HubSpot before using HubSpot workflow blocks