Skip to main content

​
What are Automations?

Automations are configurable pipelines that move data between Voxworks and your external systems. Each automation starts with a trigger — an event that kicks off the pipeline — and flows through a sequence of steps that fetch data, create contacts, place calls, sync results, and send notifications.
ComponentWhat It Does
TriggerThe event that starts the automation (webhook, call completed, integration event)
StepsThe actions to perform — transform data, create contacts, place calls, sync to CRM, send emails or SMS
ContextA shared data object that flows through the pipeline, carrying trigger data, contact info, call results, and more
Automations are standalone entities with their own page, editor, and execution log. They reference Scripts (via a Create Call step or trigger filter) but are not embedded inside Scripts.

​
When to Use Automations

Automations are the right tool when you need to connect a voice call to something outside of Voxworks:
  • Inbound CRM triggers — A new lead appears in Monday.com, and you want Voxworks to call them automatically
  • Post-call CRM sync — After a call completes, push the summary, structured data, and outcomes back to your CRM
  • Notifications — Send an email to the contact after the call, or alert your team via SMS when a call gets a low rating
  • Webhook integrations — Receive data from any system via webhook, create a contact, and trigger an outbound call
  • Data enrichment — Fetch live CRM data at the moment a call starts so your assistant has up-to-date context

​
How Automations Work

An automation runs as a linear pipeline. Steps execute in order, and each step can read from and write to a shared context: 
Trigger fires
  -> Step 1: Transform (map incoming fields)
  -> Step 2: Upsert Contact
  -> Step 3: Create Call
     [call executes with your Script]
  -> Step 4: Transform (map call results)
  -> Step 5: Sync to CRM
  -> Step 6: Send email to contact
  -> Step 7: Condition — if rating < 3, alert team via SMS
When a Create Call step is present, the pipeline splits automatically:
  • Pre-call steps (before Create Call) execute immediately when the trigger fires
  • Post-call steps (after Create Call) execute after the call completes and the summary is generated
This split is handled for you — just arrange your steps in order and Voxworks takes care of the timing.

​
Next Steps