Pathway Zapier integrationAutomate Pathway with Zapier.
The Pathway Zapier integration gives you 3 triggers and 4 actions to move new clients, new policies and renewals between Pathway and your other tools, and to create clients, policies, abeyances or flow contacts in Pathway, starting on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Pathway Zapier integration does for an agency
Pathway builds marketing automation for insurance agencies and brokerages. The Zapier integration connects it to the rest of the agency's tools: new clients, policies and renewals in Pathway can start work elsewhere, and clients or policies captured elsewhere can be created in Pathway without retyping.
Three results cover most needs. An automatic welcome: New Client starts the Zap and Add Contact to Flow puts that person into a Pathway flow, so the follow-up starts without anyone remembering it. A renewal watch: New Renewal reports policies being renewed, which can feed a producer's task list or a team chat. A single entry point: a quote form or a web lead becomes a client with Create New Client, or a full policy with Create New Policy, instead of being typed in twice.
Now what the integration does not do. There is no search step, so a Zap cannot check whether a client already exists before creating one. Nothing edits or deletes a client or a policy either; the actions only create. The three triggers are checked on a timer, so nothing reaches your tools the second it happens in Pathway. And the create actions ask for many agency codes, which have to come from somewhere in the Zap.
If you are weighing Zapier itself, there is an Zapier review, and a page on n8n vs Zapier.
Zapier words in plain English
Seven words are enough to read this page. Each one is explained once here, then used without a reminder.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap, such as a new client in Pathway. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: the step that creates, sends or adds something for you, like a new policy in Pathway.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer; an instant one is reported by the app itself. All three Pathway triggers are polling.
- Filter
- A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it otherwise.
- Connection
- Your Pathway account linked to Zapier once, then reused by every step that talks to Pathway.
What a Pathway Zap costs
Zapier bills tasks, and a task is an action that worked. Nothing else counts.
- Free plan100 tasks a month
- Steps on the free plan1 trigger + 1 action
- Premium appNo
- Trigger type3 polling, 0 instant
The trigger is free, however often Zapier checks Pathway for new clients, policies or renewals. Each action that succeeds counts once: a Zap that adds every new client to a flow uses one task per client. Failed actions are not counted. Pathway is not a premium app, so it runs on the free plan, which gives 100 tasks a month and Zaps of two steps, one trigger and one action. Add a second action or a filter and the Zap becomes multi-step, which needs a paid plan. How quickly a trigger is checked depends on the plan, as below.
Connect your Pathway account in three steps
- 01
Open your connections
On the Apps page of your Zapier account, click + Add connection. You need a Pathway account, plus access to any clients or policies you do not own but want a Zap to work on.
- 02
Select Pathway
Search for Pathway in the dialog, pick it from the results and click Add connection. A new tab opens on Pathway, where you sign in to the agency's account.
- 03
Sign in and grant access
Log in to Pathway in that tab and allow Zapier to reach the agency account. The connection is then saved, and every Pathway step in every Zap can reuse it.
Your first Pathway Zap
GoalEach new client in Pathway is added to a welcome flow, then gets an abeyance for the producer who owns the account.
- 01
Build: pick the trigger
Create a Zap, choose Pathway as the starting app and New Client as the event, select your connection, then fill in the required Created From date.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent clients of the account, so the next steps are mapped on a real client, not on a blank record.
- 03
Add the client to a flow
Add Add Contact to Flow. Enter the Flow ID of the welcome flow and map the client that came from the trigger into the required Contact ccode field.
- 04
Add the abeyance
Add Create New Abeyance as a second action. This makes a multi-step Zap, so it needs a paid plan; on the free plan, stop after the flow step.
- 05
Test each step, then publish
Test every step and read what came back before going further. When both actions look right, publish the Zap to switch it on.
Pathway triggers
3 events start a Zap when something happens in Pathway. Zapier checks for them at the interval your plan allows.
New Policy
Polling triggerIn Zapier“Triggers when a new policy is created.”
Starts your Zap when a policy is created in Pathway. It is the right starting point for anything that should follow a sale: telling the account manager, adding a row to a production report, or starting a client communication outside Pathway.
New Renewal
Polling triggerIn Zapier“Triggers when a policy is renewed.”
Reacts when a policy is renewed in Pathway. Renewals are where a brokerage keeps or loses a client, so this trigger suits Zaps that put the right person in front of the account at the right moment.
New Client
Polling triggerIn Zapier“Triggers when a new client is created.”
Fires when a client is created in Pathway. This is the trigger for onboarding: a welcome sequence, a record in another CRM, or a note to the team that will look after the new account.
Pathway actions
Pathway gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create New Abeyance
ActionIn Zapier“Creates new abeyance in our system”
Creates an abeyance in Pathway for a contact, with an activity owner, a time and the agency and branch codes, and an option to make it visible to the client.
Create New Client
ActionIn Zapier“Creates new client in our system”
Adds a client to Pathway from data captured elsewhere: name, email, phone and the agency's codes for branch, broker and type of business, plus whether the client is personal.
Add Contact to Flow
ActionIn Zapier“Adds Contact to the Flow”
Puts an existing Pathway contact into one of your flows, using the flow's ID and the contact's ccode.
Create New Policy
ActionIn Zapier“Creates new Policy on our system”
Writes a full policy into Pathway, together with the client it belongs to, from effective and expiration dates down to the department and profit center codes.
When a Pathway Zap breaks
Zapier lists no help article or rate limit specific to Pathway. What goes wrong comes from how every Zap behaves, and four cases explain most of it.
None of them shows as an error inside Pathway, which is why they surprise people. The Zapier troubleshooting page helps with anything beyond this list.
Existing clients are not picked up
A Zap only reacts to what happens after you publish it. Clients and policies already in Pathway never start it; move that backlog as a separate job.New Client plus Create New Client loops
A Zap that creates clients in Pathway while starting from New Client sets itself off again and again, and burns through your monthly tasks quickly.A bulk import held back
When a trigger suddenly returns a large batch, after importing a book of business for example, Zapier's flood protection can hold those items back.The same policy never runs twice
On a polling trigger, Zapier remembers what it has already seen, so a given client, policy or renewal starts the Zap only once.
Need help automating Pathway with Zapier?
A person reads every message.
