Sign in to SALT

Zapier integration guide

Zapier connects SALT to thousands of other tools via no-code workflows. SALT exposes triggers (new Submission, contact created, Form progress events) and actions (fetch a Submission). Connect via Zapier's SALT app and authorize.

Verified • For agency admin

In short: Authorize SALT in Zapier, build a Zap that uses one of SALT’s triggers, and pipe data wherever you want. Zapier handles the connection logic.

Connecting SALT and Zapier — part 1
Connecting SALT and Zapier — part 2

What Zapier enables

Zapier is a workflow automation platform. With SALT in Zapier, you can:

  • Push new Submissions to a tool that doesn’t have a native SALT integration (Slack, Google Sheets, Notion, etc.)
  • Send Submissions to your own internal database or CRM via webhook
  • Create complex multi-step workflows (“on new Submission, post to Slack AND add a row to Google Sheets AND send a Mailchimp email”)
  • Bridge SALT to systems you can’t justify a direct integration for

Zapier is best for glue work — when you need to connect SALT to something specific without building it yourself.

SALT triggers in Zapier

Common SALT events that fire Zaps:

  • New Submission — fires when a Submission completes
  • Submission updated — fires on subsequent edits
  • Contact created — fires when a new Insured is captured
  • Form progress — fires on milestone events during incomplete sessions

Each trigger comes with a payload of Submission data Zapier can use in subsequent steps.

SALT actions in Zapier

Zapier can also pull data from SALT on demand:

  • Get Submission — fetch a specific Submission’s details by token

Use actions when a non-SALT trigger needs SALT data — e.g. “when a new Stripe payment lands, fetch the related SALT Submission.”

Connect Zapier

  1. 1

    In Zapier, search for “SALT” and pick the SALT app.

  2. 2

    Click to connect a new SALT account.

  3. 3

    Authorize via SALT’s OAuth flow — sign in to SALT and approve.

  4. 4

    Build your Zap. Pick a SALT trigger or action; configure subsequent steps; turn the Zap on.

You can have multiple Zaps connected from a single Zapier authorization. Each Zap is independent.

What Zapier sends

The Submission payload available in Zapier includes:

  • Submission ID and status
  • Insured and contact info (subject to standard PII handling)
  • Vehicles, properties, drivers (where applicable)
  • Custom Question answers (where exposed)
  • Tags, status, assignee
  • Form and Link metadata (which Form, which Link, when created)

Custom Question answers are included in the payload and delivered directly to the endpoint you connect — there is no separate per-field consent step for integrations. Review what your Custom Questions collect before you enable one.

Disconnect

To stop Zapier:

  • Per Zap — turn off the specific Zap in Zapier’s dashboard
  • Per connection — remove SALT from your Zapier connected accounts (this disables all Zaps using it)
  • Per SALT side — see Connecting and disconnecting integrations

Common questions

Are Zaps per-account? Yes — each agency has its own Zapier connection.

Can I use Zapier to import data INTO SALT? Limited — SALT’s primary direction is outbound (SALT events trigger Zaps). For automated inbound creation of Submissions, Webhooks or direct integrations are better fits.

Does Zapier consume Data Credits? No. Zapier doesn’t trigger paid lookups; it just routes the data SALT already has.

Can my Custom Questions show up in Zapier? Yes — published Custom Questions appear in Zapier’s payload. All answers are included directly; there is no per-field consent gate for integration payloads.