The INVOX integration with Zapier allows you to automatically trigger workflows whenever INVOX tracks a new phone call or form submission.

INVOX provides two Zapier triggers:

Each trigger sends the available tracking and attribution data to Zapier. You can then map this information to other applications available on Zapier, such as Salesforce, HubSpot, Shopify, Facebook Conversions, Google Ads, Anthropic (Claude), and many others.

A typical workflow looks like this:

New Call or Form in INVOX → Zapier Trigger → Send data to another application

For example, you can use Zapier to create or update CRM leads, send conversions to advertising platforms, enrich customer records, trigger follow-up workflows, or send call and form data to AI applications for additional processing.

The New Call trigger is activated when a new phone call is generated and tracked by INVOX.

Depending on the tracking configuration and the data available for that particular visitor and call, INVOX can send the following fields to Zapier.

key - Internal identifier associated with the event.

id - Internal INVOX record identifier.

call_id - The unique ID of the call in INVOX.

account - The INVOX account associated with the call.

date - Date and time of the call.

duration - Call duration.

status - Call status. Depending on the call, values may include Answered, No answer, User busy, Call Rejected, Voice Mail, Calling, or Unallocated (unassigned) number.

caller - The caller's phone number.

receivingnumber - The INVOX tracking number called by the customer.

destinationnumber - The destination phone number to which INVOX forwarded the call.

recording_uri - URL to the call recording player in the INVOX platform, when call recording is enabled and available.

source - The marketing source or channel attributed to the call by INVOX.

Examples may include paid search, organic search, social, newsletter, referral, outdoor, print, or other configured sources.

keyword - The PPC keyword associated with the visitor, when available.

referrer - The webpage that referred the visitor to the website.

page - The last page viewed by the visitor before making the call.

medium - The marketing medium associated with the visitor.

campaign - The marketing campaign associated with the visitor.

When available, INVOX can send the following UTM parameters:

utm_id - UTM campaign identifier.

utm_source - UTM source.

utm_term - UTM term.

utm_content - UTM content.

When available, the following Google Ads and ValueTrack information can be sent:

campaignid - Google Ads campaign ID.

adgroupid - Google Ads ad group ID.

network - The Google Ads network associated with the click.

matchtype - Keyword match type.

creative - Google Ads creative ID.

adposition - Ad position information.

device - The device used by the visitor.

gclid - Google Click ID.

gacid - Google Analytics Client ID.

gbraid - Google GBRAID identifier.

wbraid - Google WBRAID identifier.

fbclid - Meta/Facebook Click ID.

ttclid - TikTok Click ID.

These identifiers can be used in Zapier workflows to connect phone calls with advertising, analytics, CRM, or conversion data.

When the corresponding INVOX features are enabled and the information is available, the following AI-generated data can also be sent:

reason - A brief description of the reason for the call.

summary - AI-generated summary of the conversation.

client_sentiment - The customer's sentiment during the call, such as positive, neutral, or negative.

operator_sentiment - The operator's sentiment during the call, such as positive, neutral, or negative.

The New Form trigger is activated when INVOX Form Tracking detects a new form submission.

This allows form leads and their associated marketing attribution data to be automatically sent to other applications through Zapier.

Form Tracking data is divided into general submission information, normalized mapped data, and the original raw tracking data.

key - Internal identifier associated with the event.

id - Internal INVOX record identifier.

call_id - INVOX identifier associated with the tracked interaction.

form_id - The unique identifier of the form submission.

date - Date and time when the form was submitted.

account - The INVOX account associated with the form submission.

receiving_number - Receiving phone number associated with the tracked form, when available.

receiving_email - Receiving email address associated with the form, when available.

The mapped object contains normalized form and attribution data that can be easily mapped to fields in your destination application.

name - Name submitted through the form.

email - Email address submitted through the form.

phone - Phone number submitted through the form.

message - Message or other main text content submitted through the form.

referer - The referring URL associated with the visitor.

referer_domain - Domain of the referring website.

original_referer - The visitor's original referrer.

traffic_source - The traffic source attributed to the current visit.

first_traffic_source - The visitor's first recorded traffic source.

organic_source - Organic traffic source, when applicable.

organic_source_alt - Alternative organic source information.

remote_url - URL from which the form was submitted.

remote_url_base - Base URL associated with the form submission.

remote_form_id - Identifier of the form on the originating website.

landing_page - The visitor's landing page.

landing_page_base - Base URL of the landing page.

user_ip - IP address associated with the form submission.

user_agent - Browser/device User-Agent associated with the visitor.

utm_source - Current UTM source.

utm_medium - Current UTM medium.

utm_term - Current UTM term.

utm_content - Current UTM content.

utm_campaign - Current UTM campaign.

INVOX can also provide the first recorded UTM attribution associated with the visitor:

first_utm_source - First recorded UTM source.

first_utm_medium - First recorded UTM medium.

first_utm_term - First recorded UTM term.

first_utm_content - First recorded UTM content.

first_utm_campaign - First recorded UTM campaign.

This makes it possible to use both current-session attribution and first-touch attribution in your Zapier workflows.

fbclid - Meta/Facebook Click ID.

msclkid - Microsoft Advertising Click ID.

gclid - Google Click ID.

wbraid - Google WBRAID identifier.

gbraid - Google GBRAID identifier.

gaclientid - Google Analytics Client ID.

fbc - Meta _fbc identifier.

fbp - Meta _fbp identifier.

INVOX can also expose additional form values using:

extra_field_1 through extra_field_10

These fields can be used for additional information submitted through the form that does not correspond to one of the standard mapped fields.

In addition to normalized mapped data, the raw object can contain the original tracking values collected with the form submission.

Depending on the implementation, these may include:

handl_handl_original_ref
​handl_handl_landing_page
​handl_handl_landing_page_base
​handl_handl_ip
​handl_handl_ref
​handl_handl_url
​handl_handl_ref_domain
​handl_handl_url_base
​handl_organic_source
​handl_organic_source_str
​handl_user_agent
​handl_traffic_source
​handl_first_traffic_source
​handl_handlID
​handl__fbp

The raw object is primarily intended for advanced integrations or situations where the original tracking values are required.

For most Zapier integrations, we recommend using the normalized fields available in the mapped object.

By combining INVOX Call Tracking and Form Tracking with Zapier, you can build automated workflows around both major types of inbound leads: phone calls and website forms.

For example:

INVOX → Salesforce
Create or update leads and send call or form data together with marketing attribution information.

INVOX → HubSpot
Create or update contacts and associate inbound phone calls or form submissions with CRM records.

INVOX → Shopify
Use phone numbers, email addresses, or other customer information to connect INVOX interactions with e-commerce workflows.

INVOX → Facebook Conversions
Use qualified phone calls or form submissions as part of workflows for sending conversion information to Meta.

INVOX → Google Ads
Build conversion workflows using tracked calls or forms together with available Google advertising identifiers such as gclid, gbraid, or wbraid.

INVOX → Anthropic (Claude)
Send call summaries, call reasons, sentiment, form messages, or other lead information to Claude for additional classification, analysis, enrichment, or automated processing.

These are only examples. INVOX data can be connected to other applications and actions available through Zapier.

A visitor clicks a Google Ads campaign, visits your website, and calls an INVOX dynamic tracking number.

INVOX attributes the phone call to the visitor's marketing journey and can collect information such as:

Google Ads → Campaign → Ad Group → Keyword → Landing Page → Phone Call

The New Call trigger then makes the available call and attribution data available in Zapier.

You can use this information to create a lead in your CRM, update an existing customer, trigger a sales workflow, or send conversion information to another platform.

A visitor clicks an advertising campaign, lands on your website, and submits a contact form tracked by INVOX.

INVOX can capture both the submitted lead information and the visitor's marketing attribution:

Traffic Source → Campaign → Landing Page → Form Submission

The New Form trigger sends the available information to Zapier, including fields such as the visitor's name, email, phone number, message, UTM parameters, advertising click IDs, landing page, traffic source, and first-touch attribution.

Zapier can then automatically create or update the lead in your CRM or trigger another workflow.

Not every field will contain a value for every call or form submission.

The data available depends on the tracking method, visitor journey, marketing source, advertising platform, tracking parameters present during the session, website configuration, and INVOX features enabled for the account.

For example, a gclid will normally only be available when a Google advertising click identifier was captured, while AI-generated call information such as summary, reason, or sentiment requires the corresponding INVOX functionality to be enabled.

When a particular value is not available, the corresponding field may be empty.

To create an INVOX integration in Zapier:

Once the Zap is active, new calls or form submissions tracked by INVOX can automatically trigger the workflow you configured.