Paigo Zapier integrationAutomate Paigo with Zapier.
The Paigo Zapier integration gives you 5 triggers, 5 actions and 3 searches. All five triggers are instant, so invoices, payments and usage alerts reach your other tools right away, and Zapier can feed Paigo with customers, offerings and metered usage in return.
Verified Trustpilot reviews · AI, automation & growth agency
What the Paigo Zapier integration actually does
Paigo is a usage-based billing tool: it measures what each customer consumes, turns that into invoices, helps you read your costs and charges customers through their own channel. On Zapier, it reports customers, invoices and usage thresholds the moment they happen, and it accepts usage records, customers, offerings and credits from other apps.
Three outcomes teams build with it. Usage metered from anywhere: an event in your product or another tool runs Measure Usage, and the line ends up on the customer's next invoice without a developer writing anything. Finance kept in the loop: Invoice Created, Invoice Sent and Invoice Paid push each step of the invoice life into your accounting tool, a spreadsheet or a team channel. Customers warned before they hit the wall: Entitlement Threshold Reached fires a warning at 80% of an allowance and an alarm at 100, so customer success can call before the customer notices.
Now what Zapier does not do here. There is no action to edit or delete a customer, an invoice or an offering: every action creates or adds. The searches read only. And several actions need identifiers you copy from the Paigo dashboard first, because the Zap cannot invent them.
If you are still comparing tools, the Zapier review and Make vs Zapier are good places to start.
Zapier vocabulary, in plain words
Eight words come back on every Zapier page. Read them once here and the rest follows.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it. Paigo offers five.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. None of Paigo's triggers work this way.
- Instant trigger
- A trigger the app reports itself: it calls Zapier the moment the event happens. All five Paigo triggers are instant.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Search step
- A step that looks up something that already exists in an app, so the steps after it can use what it found.
What a Paigo Zap really costs
Paigo is not reserved for paid plans: it runs on the free Zapier plan, and its triggers are all instant, so the free plan's slower checking never delays them.
- Paigo triggerNever costs a task
- Successful actionCounted as a task
- Failed actionNot counted
- Free plan allowance100 tasks per month
- Search, filter or second actionPaid plan required
The trigger never costs a task. Each action that succeeds counts as one, whether it is Measure Usage in Paigo or a message in your team chat; a failed action is not counted. The free plan gives you 100 tasks a month and builds two-step Zaps only: one trigger, one action. Add a filter, a second action or one of Paigo's three searches, and the Zap becomes multi-step, which needs a paid plan. Measure Usage on every product event can eat an allowance fast, so size it before you publish.
Connect Paigo to Zapier in three steps
- 01
Open your connections
Go to the Apps page of your Zapier account. A connection is your Paigo account linked to Zapier once, then reused by every step that uses Paigo, so you only set it up a single time.
- 02
Add Paigo
Click + Add connection, search for Paigo in the dialog and pick it, then click Add connection. A new browser tab then opens where Paigo asks you to sign in.
- 03
Sign in and grant access
Sign in to Paigo in that tab and grant Zapier access to the account. If the billing account belongs to someone else, make sure you have write access to it first, since most actions create records.
Your first Paigo Zap: warn the team before a customer runs out
GoalWhen a customer on a given offering reaches the alarm level of its allowance, the team gets a message in its chat; the earlier warning is ignored.
- 01
Pick the trigger
Create a Zap, choose Paigo and the event Entitlement Threshold Reached, then enter the offering to monitor. Every customer on that offering is then checked against its allowances.
- 02
Test on real data
Run the test. Zapier brings back the three most recent items from the connected account, so you map fields on a real threshold event instead of an empty example.
- 03
Add a filter
From the plus icon, add a filter: field, rule, value. Keep only the alarm, issued at 100, and drop the warning at 80%. This step makes the Zap multi-step, so it needs a paid plan.
- 04
Add the message
Add the action of your chat tool and map the customer details from the Paigo step into the message. Test it once and check that it really landed in the right channel.
- 05
Publish
Click Publish to switch the Zap on. Because the trigger is instant, each alarm reaches the channel right away, whatever plan you are on.
Paigo triggers on Zapier
5 events start a Zap when something happens in Paigo, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.
Customer Created
Instant triggerIn Zapier“Triggers when a new customer is created.”
Starts the Zap each time a new customer is created in Paigo, by hand in the dashboard or through Onboard Customer. It is the natural entry point for anything that has to happen once per new account, from a welcome message to a row in your CRM.
Entitlement Threshold Reached
Instant triggerIn Zapier“Triggers when a customers usage using the associated offering reaches a threshold warning is issued at 80% and an Alarm is issued at 100.”
Fires when a customer's usage on a given offering reaches a threshold: a warning at 80% of the allowance, then an alarm at 100. You pick the offering to monitor, and every customer attached to it is checked against its entitlement dimensions.
Invoice Created
Instant triggerIn Zapier“Triggers when an invoice is generated inside of Paigo.”
Runs the Zap when Paigo generates an invoice, before it is approved or sent. That early moment is handy for checks: someone can review the amount, or a spreadsheet can log the new invoice, while there is still time to act.
Invoice Paid
Instant triggerIn Zapier“Triggers when an invoice has been paid.”
Kicks off the Zap once an invoice has been paid. It closes the loop on billing: whatever you hold back until payment, access, a thank-you or a reconciliation line, can follow from here without anyone checking the dashboard.
Invoice Sent
Instant triggerIn Zapier“Triggers when an invoice is approved and sent.”
Fires when an invoice is approved and sent to the customer. It marks the moment the customer can actually see the amount, which makes it the right signal for anything that talks to the customer about that bill.
Paigo actions on Zapier
Paigo gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Add Credits
ActionIn Zapier“Add Credits for a customer”
Gives a customer credits, set in the currency assigned to them and in USD by default.
Create Dimension
ActionIn Zapier“Creates a Dimension inside of Paigo”
Adds a dimension, the unit Paigo meters and bills: its name as shown on invoices, what is consumed, its unit and the minimum increment.
Create Offering
ActionIn Zapier“Creates and Offering in Paigo.”
Creates an offering in Paigo, the plan your customers are attached to. You give it a name, a type and an environment, sandbox or production.
Measure Usage
ActionIn Zapier“Measure any usage associated with a customer. Can be emails sent, api calls, cpu hours consumed, paigo accepts any type of usage. Before metering, define the usage as a dimension at dashboard.paigo.tech Dimensions”
Records a quantity consumed by a customer on a dimension: emails sent, calls made, processor hours. If a user sent 110 emails in the last hour, the value is 110.
Onboard Customer
ActionIn Zapier“Create a customer and assign them an offering in paigo. You must have created an offering already at dashboard.paigo.tech”
Creates a customer and assigns them an offering in one step, with a name and the email used at sign-up.
Paigo searches on Zapier
3 search steps look for data that already exists in Paigo, so a later step can use it.
A search step reads Paigo without changing anything, and hands what it found to the steps that follow. In the editor, Paigo's searches sit at the bottom of the action list, under SEARCH. Using one makes the Zap multi-step, so it needs a paid plan.
Get Customers
SearchIn Zapier“Find all customers associated with your paigo account”
Brings back the customers tied to your Paigo account, so a later step can work with them.
Get Invoice
SearchIn Zapier“Get more detailed information about an invoice”
Fetches the detail of one invoice, from its Invoice Id, for the steps that come after.
Get Offerings
SearchIn Zapier“Find all of the offerings in your Paigo account.”
Lists the offerings in your Paigo account, which is how a Zap finds an offering to hand on.
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 steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this box turns a search into find-or-create. Paigo offers no find-or-create variant, so its searches only ever read.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a Paigo Zap breaks
Zapier links no help article and no rate limit to Paigo. What breaks is general Zapier behavior, plus the identifiers Paigo actions depend on.
Four cases to know before you publish. When a Zap stops and you need a method, see Zapier troubleshooting.
Past invoices and customers never come through
A Zap only reacts to what happens after it is switched on. Invoices and customers that already exist in Paigo are not replayed; moving that backlog is a separate job.The Zap feeds itself
Customer Created followed by Onboard Customer on the same account: each customer the action creates fires the trigger again, and the task count burns fast.A usage burst gets held back
A sudden huge batch, after a bulk import or a migration, can be held back by Zapier's flood protection instead of running all at once.A missing identifier stops the step
Onboard Customer, Measure Usage and Add Credits all rely on an Id from Paigo. A wrong or empty one and the action fails, which at least costs no task.
Need help automating Paigo with Zapier?
A person reads every message.
