Skip to main content

​
What are the Zapier, Make & n8n integrations?

Voxworks doesn’t ship a purpose-built app inside Zapier’s, Make’s, or n8n’s own app directories. Instead, you connect these platforms to Voxworks the same way any external system does — through three general-purpose building blocks:
  • Inbound Webhook triggers — an Automation that starts when Zapier, Make, or n8n posts a JSON payload to a Voxworks URL. Use this to turn a form submission, a new CRM record, or any event in your other tools into a Voxworks contact or an outbound call.
  • Webhook destinations — the Send Webhook tool inside a call script, or a Webhook destination step inside an Automation pipeline — post JSON out to a URL that Zapier, Make, or n8n is listening on. Use this to hand call data to a workflow the moment a call ends (or mid-call).
  • The REST API — authenticated HTTP endpoints your automation platform’s own HTTP or webhook modules can call directly, for full control over contacts, calls, and other records without building a Voxworks Automation in between.
This page maps each of those three mechanisms into concrete recipes for Zapier, Make, and n8n.

​
Before you start: what the Integrations page “Connect” button does

Admin > Integrations lists Zapier, Make, and n8n as cards in the Available Integrations section, each categorised as an automation integration with a description (“Connect to thousands of apps through Zapier”, “Visual automation platform to connect apps and automate workflows”, “Workflow automation tool for technical teams”). Clicking Connect opens a dialog asking for an API Key: “Enter your [name] API key to establish the connection.” Be aware of what this does and doesn’t do:
  • Connecting stores the key you paste (encrypted) against your team. It does not verify the key against Zapier, Make, or n8n at connect time.
  • Opening Integration Settings on a connected card shows “No tools are currently available for this integration” — and the card’s own footer reads “No tools yet”. No script tool or calendar-booking flow currently reads this connection.
In practice, connecting the card by itself does nothing for your call scripts or automations. The working integration surface — the one that actually moves data — is the webhook and API mechanisms described below, which don’t require connecting these cards at all.
Integrations are typically built out for specific clients, so the full functionality of a given third-party application’s interface might not be available. If your team needs additional features from Zapier, Make, n8n, or any other connected application, contact the Voxworks team directly to discuss what can be added.

​
Direction 1: Zapier, Make, or n8n → Voxworks

Use this direction to turn an event in another app (a new form submission, a CRM deal, a support ticket) into a Voxworks contact, a stored value, or an outbound call.

​
Step 1 — Create the Inbound Webhook trigger

  1. In the sidebar under Outbound Calls, open Automations.
  2. Click New Automation. In the Create New Automation dialog, choose the Inbound Webhook trigger option and click Create & Configure.
  3. On the automation’s Pipeline tab, the Trigger Configuration panel shows:
A Copy cURL Command button generates a ready-to-run curl -X POST example against your webhook URL for testing before you touch Zapier, Make, or n8n at all.

​
Step 2 — Point your workflow at the webhook URL

  • Zapier — after your trigger step (Google Sheets, Typeform, a CRM, and so on), add a Webhooks by Zapier action step, choose POST, and paste the Voxworks webhook URL. Map the fields you want to send into the request body.
  • Make — add an HTTP > Make a request module as the next step in your scenario, set the method to POST, paste the Voxworks webhook URL, and build the JSON body from the previous module’s fields.
  • n8n — add an HTTP Request node after your trigger node, set it to POST, paste the Voxworks webhook URL, and set the body to the JSON you want to send.
If you set an HMAC Secret, add the corresponding signature header in the same step, generated by whichever module your platform uses to compute an HMAC (Zapier’s Code step, Make’s built-in hmac function, or n8n’s Crypto node).

​
Step 3 — Turn the payload into a contact, a call, or stored data

Build the rest of the pipeline on the Pipeline tab using the trigger payload as the data source:
  • Upsert Contact — matches an existing contact on Phone Number or Email, then field-maps values from the trigger payload (for example trigger.phone → Phone Number, trigger.name → Full Name) to create or update the contact.
  • Create Call — starts an outbound call. Choose a Script, and set the Phone Number Path to a dot-notation path into the execution context — trigger.phone for the raw webhook field, or contact.phone_number if an Upsert Contact step ran first. From Number is optional and falls back to the script’s default trunk number if left blank.
  • Upsert Custom Variable — writes trigger fields into a custom variable type instead of (or alongside) a contact, for structured data that doesn’t belong on the contact record.
  • Transform and Condition steps sit in between to reshape fields or branch the pipeline (for example, only place a call when a qualified field from the trigger is true).
Example recipe: a Zapier Zap watches a lead-capture form, then POSTs the lead to your Inbound Webhook trigger. The pipeline runs Upsert Contact (matched on Phone Number) followed by Create Call against a “New Lead Qualification” script, so the assistant calls the lead within moments of the form submission.

​
Direction 2: Voxworks → Zapier, Make, or n8n

Use this direction to hand call data, a booking, or an event to a workflow in Zapier, Make, or n8n. There are two places to send it from, depending on when you need the data to move.

​
Mid-call: the Send Webhook tool

Add the Send Webhook tool to a step in a call script when the assistant needs to push data out — or pull a response back — while the call is still in progress. Because it runs synchronously inside the call, keep the endpoint fast: the request times out after 10 seconds with no retry, so a slow Zapier/Make/n8n workflow can introduce a noticeable pause for the caller. Variables this tool writes The tool’s output routes true on a 2xx response and false otherwise — route the failure path deliberately if the workflow’s result matters to the rest of the call.

​
After a call or on other events: the Webhook destination step

For anything that doesn’t need to happen mid-call, build an Automation instead. Automations can start from Call Completed, Call Scheduled, or Notification Created (currently in beta, available to selected invites only; the Integration Event trigger’s configuration screen isn’t available yet — it shows “will be available in a future update”). Add a Destination step, set its Destination Type to Webhook, and configure: Example recipe: an Automation triggers on Call Completed, filtered to your outbound sales scripts, and its Destination step POSTs the call summary and outcome to a Make Custom webhook trigger URL — which then updates a spreadsheet and posts a Slack message, entirely inside Make. Check outcomes for both destinations in the automation’s Execution Log tab — see Execution Log & Monitoring.

​
Direction 3: Full control with the REST API

For workflows that need to reach further than a single pipeline run — polling call status, reading back a transcript, or driving Voxworks from a scheduled Zapier/Make/n8n job rather than a webhook — point your platform’s native HTTP or webhook module at the Voxworks REST API directly, using an API key generated under Settings > API Keys.
  • Zapier — the built-in Webhooks by Zapier action (or a Code step) can call any Voxworks endpoint with the API key in the Authorization header.
  • Make — the HTTP > Make a request module handles authenticated requests the same way.
  • n8n — the HTTP Request node, with header authentication configured against your Voxworks key.
Typical uses include creating or updating a contact and scheduling a call from outside a webhook-driven pipeline. See API Keys & Authentication for generating and scoping a key, API Quickstart for a first end-to-end request, and REST Endpoints for the full reference.

​
Choosing a direction

​
Next Steps

  • Automations — triggers, pipeline steps, and how a pipeline runs end to end.
  • Automation Triggers — full detail on the Inbound Webhook trigger, including signature verification.
  • Send Webhook — the full field-by-field reference for the mid-call webhook tool.
  • Integrations Overview — how connections, connection statuses, and tool gating work across your team.