Steps

Documentation Index

Fetch the complete documentation index at: https://docs.voxworks.ai/llms.txt

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

​

Overview

Steps execute in order from top to bottom. Each step reads from and writes to a shared context object that carries data through the pipeline. You can add up to 20 steps per automation. To add a step, click + Add step in the pipeline builder and select the step type.

---

​

Step Types

​

Transform

Reshape and map data from one format to another. Transforms are typically used to:

• Map incoming webhook fields to contact fields before an Upsert Contact step
• Map call results to CRM column identifiers before a Destination step

Configuration: Add one or more field mappings. Each mapping has: Example — mapping webhook fields for a contact: Transform results are written to mapped.* in the context and are available to all subsequent steps.

---

​

Upsert Contact

Create a new contact in Voxworks or update an existing one. The step matches on either phone number or email to determine whether to create or update. Configuration: After this step runs, contact.* is available in the context for all subsequent steps. Example: Match on phone_number, with mappings: If a contact with that phone number already exists, their name fields are updated. If not, a new contact is created.

---

​

Upsert Object

Create or update a typed data object and optionally link it to the contact. Objects store CRM identifiers and external data that your automation needs to reference later — for example, a Monday.com item ID or a HubSpot deal ID. Configuration: After this step runs, the object’s data is available at objects.{type_name}.*. Example: Object type: monday_item, match on CRM_ID = trigger.crm_id, link to contact: yes.

---

​

Create Call

Trigger an outbound call using a specific Script. This step creates a call record and schedules it for immediate execution (or at a specified time). Configuration: Important: Pipeline split. Any steps placed after Create Call become post-call steps. They do not execute until the call finishes and the AI has generated the summary and structured data. The pipeline builder shows a visual divider: “after call completes”. After the call completes, call.* is populated with the full call record including summary, transcript, structured data, and objectives.

---

​

Destination

Push data to an external system. There are four destination types:

​

Integration Sync

Sync data to a connected CRM (e.g., Monday.com). Uses field mappings to map call outputs and object data to integration-specific column identifiers. The target field names correspond to column IDs in your CRM. You’ll find these in your CRM’s column settings.

​

Email

Send an email to the contact, your team members, or a specific address. Email subjects and bodies support {{variable}} interpolation.

​

SMS

Send a text message to the contact or to team members.

​

Webhook

Send an HTTP request to any URL. Useful for integrating with systems that don’t have a native integration.

---

​

Condition

Branch the pipeline based on a field value. If the condition is true, the on_true steps run. If false, the optional on_false steps run (or the condition is skipped). Configuration: Example — notify team on low rating:

• Field: call.structured_data.rating
• Operator: lt
• Value: 3
• On true: SMS to team — “Low rating call: {{contact.full_name}}”
• On false: (skip)

Conditions can be nested up to 2 levels deep.

---

​

Source

Fetch data from an external API or connected integration. The response is written to source.* in the context. Configuration (HTTP): Configuration (Integration Fetch): The fetched data is resolved at runtime using object identifiers from the context (e.g., the contact’s linked CRM item ID).

---

​

Limits