- Home
- Resources
- Integrations
- PayChasers
PayChasers Zapier integrationAutomate PayChasers with Zapier.
The PayChasers Zapier integration offers 4 triggers and 4 actions, all four triggers checked on a timer. A chase that is created, followed up, overdue or paid can start a Zap, and a Zap can create clients and chases, send a follow-up or mark a chase paid.
Verified Trustpilot reviews · AI, automation & growth agency
What the PayChasers Zapier integration does for your cash flow
PayChasers follows up on money you are owed, invoices, rent, deposits or a loan to a friend, by email and messaging. Linking it to Zapier lets each step of a chase start work elsewhere, and lets other tools open or close chases for you. A Zap is the automation you build: one trigger, then the actions that run each time. PayChasers works on the free plan.
Three outcomes cover most needs. A chase opened the minute an invoice exists elsewhere: Create Client and Create Chase turn a bill raised in another tool into a PayChasers chase, with no retyping. An overdue list your team sees: Chase Overdue reports each chase that passes its due date unpaid, so the people who care hear about it outside PayChasers. Books that close themselves: Chase Marked as Paid tells your other tools a debt is settled, and Mark Chase as Paid does the reverse when the payment shows up somewhere else first.
What Zapier does not do here matters too. All four triggers are polling: Zapier checks PayChasers on a timer, so nothing arrives the instant it happens. There is no search step, so a Zap cannot look up an existing client or chase by name; Send Follow-Up and Mark Chase as Paid need the chase handed to them by an earlier step. And chases that existed before the Zap was switched on are never picked up.
For the bigger picture, see our Zapier review and Make vs Zapier.
Zapier words you will meet on this page
Eight terms, one line each, in plain words. After this block they are used without a reminder.
- Zap
- The automation you set up on Zapier: one trigger, followed by one or more actions that run each time the trigger event takes place.
- Trigger
- The event in an app that starts the Zap, such as a chase going overdue. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, like creating a chase or sending a follow-up.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked by Zapier at a fixed interval. An instant trigger is reported by the app itself. All four PayChasers triggers are polling.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it there otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
- Connection
- Your PayChasers account linked to Zapier once, then reused by every step of every Zap that touches PayChasers.
What a PayChasers Zap really costs
Zapier bills tasks, and only completed actions count. The checks Zapier runs on PayChasers cost nothing, however often they happen.
- Trigger and checksNever cost a task
- Successful action1 task each
- Failed actionNot counted
- Free plan100 tasks a month, two-step Zaps only
- PayChasers on free planYes, not reserved for paid plans
Each action that succeeds is one task: a Zap that sends a follow-up and then logs it uses two per overdue chase. A failed action is not counted. The free plan gives 100 tasks a month and only two-step Zaps, so a second action or a filter means a paid plan. Since every PayChasers trigger is polling, the plan also sets how quickly a Zap reacts, as the grid below shows. Note that a few apps and a few actions take more than one task when they complete.
Connect your PayChasers account in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box. You need an existing PayChasers account first; Zapier does not create one.
- 02
Pick PayChasers and sign in
Type PayChasers, select it, then click Add connection. Sign in to PayChasers in the tab that opens, using the account that holds the clients and chases you want to automate.
- 03
Grant access
Allow Zapier to reach the account. If some chases belong to a colleague, check that your login can read and change them, or the Zap will only ever work on your own.
Your first PayChasers Zap: nudge and log every overdue chase
GoalWhen a chase passes its due date unpaid, send one more reminder from PayChasers and add a line to the sheet where you track late payers.
- 01
Create the Zap
Start a new Zap. With two actions it is a multi-step Zap and needs a paid plan; on the free plan, keep only Send Follow-Up to try it out.
- 02
Set the trigger
Choose PayChasers as the app and Chase Overdue as the event, then your connection. On a paid plan you can change how often Zapier checks, or run a check by hand from the editor.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent overdue chases from your account, so you map the next steps on a real chase rather than on blank data.
- 04
Add the follow-up
Add Send Follow-Up and, in its required Chase box, map the chase the trigger returned. That is how the reminder lands on the right debt.
- 05
Log it, test, publish
Add the spreadsheet step, map the values you want to keep, test each step once, then click Publish to switch the Zap on.
PayChasers triggers on Zapier
4 events start a Zap when something happens in PayChasers. Zapier checks for them at the interval your plan allows.
Chase Overdue
Polling triggerIn Zapier“Triggers when a chase passes its due date without being paid.”
A chase reaches its due date and nobody has paid: this trigger hands that chase to your Zap. It is the most useful signal PayChasers sends, because it marks the moment a polite reminder turns into a real problem.
Chase Marked as Paid
Polling triggerIn Zapier“Triggers when a chase is marked as paid.”
Fires when a chase is set to paid in PayChasers, closing the loop on that debt. Your other tools learn the money is in without anyone updating them by hand.
Follow-Up Sent
Polling triggerIn Zapier“Triggers when a follow-up email is sent for a chase.”
Each reminder email PayChasers sends for a chase starts the Zap. That gives you a running record of every nudge a client has received.
New Chase Created
Polling triggerIn Zapier“Triggers when a new chase is created.”
When a chase is created in PayChasers, by hand or by another Zap, this trigger passes it on. It is where you start if other people need to know that money is now being chased.
PayChasers actions on Zapier
PayChasers gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Chase
ActionIn Zapier“Creates a new payment chase.”
Opens a payment chase in PayChasers from data that arrived earlier in the Zap, such as an invoice issued in your billing tool.
Create Client
ActionIn Zapier“Creates a new client.”
Adds a client to PayChasers, with a name and an email, so the person or company you chase exists in the app before the money does.
Mark Chase as Paid
ActionIn Zapier“Marks a chase as paid.”
Closes a chase as paid, which stops further reminders going to a client who has already settled.
Send Follow-Up
ActionIn Zapier“Sends a follow-up reminder for a chase.”
Sends one more reminder on a chase that already exists, so another tool can decide when it is time to ask again.
When a PayChasers Zap breaks
Zapier lists no help article and no rate limit specific to PayChasers. What breaks comes from how every Zap works, and two PayChasers pairs make loops easy.
Four cases to know before you publish. If one of them catches you anyway, our Zapier troubleshooting page is the next stop.
Reminders that set each other off
Follow-Up Sent followed by Send Follow-Up, or New Chase Created followed by Create Chase: the Zap writes what its own trigger watches, restarts again and again, and burns tasks.No catch-up on existing chases
A Zap only reacts to what happens after it is switched on. Chases that were already overdue or paid before then never come through.A delay you did not expect
All four triggers are polling, so a Zap reacts at the next check: every 15 minutes on the free plan, faster on paid plans, where a check can also be run by hand.Bulk imports held back
After a bulk import of clients or chases, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection. Keep Zaps off during the import.
Need help automating PayChasers with Zapier?
A person reads every message.



