Paygee Zapier integrationAutomate Paygee with Zapier.
The Paygee Zapier integration gives you 3 triggers, 2 actions and 1 search. Paygee reports every change of state on customers, loans and sales cases straight away, and a Zap can create leads or approve applicants in return.
Verified Trustpilot reviews · AI, automation & growth agency
What the Paygee Zapier integration actually does
Paygee runs pay-as-you-go sales: products paid off in instalments, with customers, loans and sales cases that move from one state to the next. The integration tells Zapier each time one of them changes state, and lets a Zap add a lead or approve a customer in Paygee.
Three results worth building. A late-payment desk: Loan State Change also reports loans running late, at least once a day while the delay lasts, so a Zap with a filter can call the customer at the exact number of days you choose. A lead inbox: a form or ad tool feeds New Customer, which creates the person in Paygee as a lead, with no retyping by your field agents. A deposit alert: Sales Case State Change flags a paid down payment, so delivery can be scheduled without anyone watching the screen.
Now what Zapier will not do here. It cannot edit a loan, record a payment or move a sales case: the two actions only create a customer or approve one. The single search finds a customer by its ID, not by name or phone. And a Zap only sees changes that happen after you publish it, so the loans already late on day one stay invisible to it.
If you are still choosing your automation tool, read the Make vs Zapier comparison first.
Zapier vocabulary in one minute
Eight words carry this page. Each one in plain English.
- 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. Once the Zap is on, Zapier waits for it. Paygee offers three.
- Action
- What the Zap does once it has started: the step that writes, sends or changes something. Paygee has two, both on customers.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's quota counts those, nothing else.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. No Paygee trigger works like this.
- Instant trigger
- A trigger the app reports itself, calling Zapier the moment the event happens. All three Paygee triggers are instant.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise. Paid plans only.
- Search step
- A step that looks up something already in an app, so the steps after it can use what it found.
What a Paygee Zap really costs
The trigger costs nothing. Tasks start with the first action that succeeds.
- Free plan100 tasks a month, unlimited Zaps
- Zap size on free2 steps: one trigger, one action
- Paygee triggers3 instant, grid does not apply
- Paygee premium?No, available on the free plan
A Paygee trigger never uses a task, and each action that succeeds counts as one, in Paygee or in any other app. A failed action, for example an approval refused because the customer was not in the right state, is not counted. Watch the late-loan case: a loan that stays late reports again at least once a day, and each run that passes your filter spends tasks again. The free plan builds two-step Zaps only. A filter, a second action or the search makes the Zap multi-step, which needs a paid plan. The interval grid below concerns polling triggers; Paygee's three are instant, so it never delays them.
Connect Paygee to Zapier in three steps
- 01
Open the connection dialog
Go to the Apps page of your Zapier account and click + Add connection. A connection is your Paygee account linked once, then reused by every Zap step that works on Paygee.
- 02
Select Paygee
Type Paygee in the search box of the dialog, pick it, and click Add connection. You need an existing Paygee account; this dialog will not create one for you.
- 03
Sign in and allow access
Sign in to Paygee in the tab that opens and grant Zapier access. To create or approve customers from a Zap, the account you connect needs write access to customers.
Your first Zap: alert the team on a late loan
GoalWhen Paygee reports a loan running late, keep only the cases at the delay you chose and post them in the collections channel.
- 01
Pick the trigger
Build a new Zap, choose Paygee as the app and
Loan State Changeas the event, then select the Paygee connection you made earlier. - 02
Test on a real loan
Run the test. Zapier brings back the three most recent loan events of your account, so you set the next steps on a real one.
- 03
Add the filter
Add a Filter step: state equals days_late, then + And days_late equals the delay you want, 5 for example. Use a number rule on the second line, or the filter never passes.
- 04
Add the message
Add the action in your chat app and place the loan details from the trigger in the message. Test the step and read what came back.
- 05
Publish
Publish the Zap to switch it on. The filter makes it multi-step, so it needs a paid plan; the trigger itself fires right away on any plan.
The 3 Paygee triggers
3 events start a Zap when something happens in Paygee, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.
Customer State Change
Instant triggerIn Zapier“Triggers when a customer state changes.”
Starts your Zap whenever a customer in Paygee moves from one state to another, for example from lead to applied or from applied to approved. Each move is its own run, with the new state attached.
Loan State Change
Instant triggerIn Zapier“Triggers when a loan state changes. As well triggers for events that don't change state on server side but could be interesting to set up a custom workflow, e.g. 'days_late' will get triggered at least once a day when the loan has delays in payment. How many days late is included in the payload as field 'days_late'. An example workflow that should be triggered on 5 days late, would filter on state='days_late' AND payload.days_late='5'.”
Fires when a loan changes state, and also on events that are not a state change but matter to collections. The main one is days_late, sent at least once a day while a loan has payment delays, with the number of days late included.
Sales Case State Change
Instant triggerIn Zapier“Triggers when a Sales Case changes state. e.g. 'dp_paid' for down payment paid.”
Reacts when a sales case moves to a new state in Paygee. Paygee's own example is dp_paid, which means the down payment has been paid, the point where a sale becomes real.
The 2 Paygee actions
Paygee gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Approve Customer
ActionIn Zapier“Changes customer state to 'approved'. Returns an error in case customer is not in state 'applied'”
Moves a customer to the approved state. It needs the Customer ID, usually taken from Customer State Change.
New Customer
ActionIn Zapier“Creates a new customer in state 'lead'. Make sure to use a valid international phone number format.”
Creates a customer in Paygee in the lead state. Two fields are required, the customer name and phone number.
The Paygee search
1 search step looks for data that already exists in Paygee, so a later step can use it.
A search step looks up a record that already exists in Paygee and passes it to the next steps. You find it at the bottom of the Action event list, under SEARCH. Adding it makes the Zap multi-step, which needs a paid plan. Three settings decide what happens when the lookup does not go to plan.
Find Customer
SearchIn Zapier“Find a customer by ID”
Looks up one Paygee customer by its Customer ID, which is required, and hands the record to the next steps.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the dependent steps are skipped. Turned on, the Zap keeps going empty-handed.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. Paygee offers no such variant on Zapier, so the box does not appear here.
- If multiple search results are found?Three ways out when several records match: keep the first, which is the default, stop the Zap, or pass them all on at once.
When a Paygee Zap breaks
Zapier documents no Paygee-specific error or rate limit. The trouble comes from the rules of the two actions and from how Zapier behaves in general.
Four cases cover most of it. Anything else, check the Zapier troubleshooting page.
Approval returns an error
Approve Customer only works on a customer in the applied state. Any other state sends the step back with an error, so put a filter on applied in front of it.The new customer is rejected
New Customer needs a name and a phone number in valid international format. A local number without country code does not meet that format.The Zap sets itself off
A Zap on Customer State Change that runs Approve Customer creates the very change it listens to. Without a filter on applied, it runs again on the approved state and the approval comes back with an error.Past events are never picked up
A Zap reacts only to what happens after you publish it. Loans already late and customers already approved before that date never reach it.
Need help automating Paygee with Zapier?
A person reads every message.
