- Home
- Resources
- Integrations
- Partnero
Partnero Zapier integrationAutomate Partnero with Zapier.
The Partnero Zapier integration gives you 20 triggers, 14 actions and 2 searches. All 20 triggers are instant and the app runs on the free plan. Here is what each operation does, what it costs in tasks, and where a Zap built on it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the Partnero Zapier integration is for
The Partnero Zapier integration links your partner program to the rest of your tools, without code. When something moves in Partnero (a partner approved, a lead converted, a transaction recorded), another app reacts. It also works the other way: another app can create, update or delete records in Partnero.
Three setups show what the pairing is for. A welcome for every new partner: Partner Approved starts the Zap and your email tool sends the onboarding note. Sales recorded where rewards are worked out: Create a New Transaction pushes the full purchase amount into Partnero, which calculates the partner's reward from your program settings. A lead pipeline nobody updates by hand: Lead Submitted, Lead Converted and Lead Rejected each feed the CRM or sheet your sales side already reads.
What Zapier does not do for Partnero matters just as much. There is no action on leads, so a Zap can watch a lead but never create or change one. The two searches cover customers and partners only, nothing for subscribers or transactions, and neither offers to create a missing record. Every trigger is instant, so there is no polling interval to tune either.
If you are still choosing a platform, the same app exists on Make: Partnero Make integration.
Zapier words in one minute
Eight terms you will meet on this page and in the editor, in plain words.
- 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, here a Partnero event such as Partner Approved. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like Create a New Customer.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and the count on your plan is a count of those.
- Instant vs polling
- An instant trigger is reported by the app itself when the event happens. A polling trigger is checked by Zapier on a timer. Partnero only has instant ones.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
- Search step
- A step that looks up something that already exists in an app, a Partnero partner for example, so the next steps can use it.
- Connection
- Your Partnero account linked to Zapier once, then reused by every step of every Zap that touches Partnero.
What a Partnero Zap really costs
Triggers are free: Zapier bills a task only when an action completes successfully, and an action that fails is not counted.
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, works on the free plan
- Instant triggers20 out of 20
- BilledEach action that succeeds
Partnero is not a premium app, so it runs on the free plan: 100 tasks a month and unlimited Zaps, but two steps per Zap, one trigger and one action. Add a second action, a filter or a search and the Zap turns multi-step, which needs a paid plan. The interval grid only applies to polling triggers, and all 20 Partnero triggers are instant. A Zap built on Partner Approved plus one email step therefore stays free.
Connect Partnero to Zapier in three steps
- 01
Open the Apps page
In Zapier, go to the Apps page of your account and click + Add connection. You need a Partnero account, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick Partnero
Type Partnero in the search box of the dialog, select it, then click Add connection. A new tab opens on the Partnero side for the sign-in, so keep your Partnero login at hand.
- 03
Sign in and grant access
Sign in to Partnero in that tab and grant Zapier access to the account. The connection is saved, and every Partnero step of every Zap reuses it from then on.
Your first Partnero Zap
GoalLog every new Partnero transaction in a sheet and tell the team in Slack.
- 01
Pick the trigger
Build the Zap: choose Partnero as the app that starts it, Transaction Created as the event, then select the connection made above.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent transactions of the connected account, so you map from a real one instead of guessing.
- 03
Add the sheet row
Add Google Sheets as the first action and map the Partnero values into your columns. Test the step once and read what came back before going further.
- 04
Add the team message
Add Slack as a second action and build the message from the same values. Two actions make this a multi-step Zap, so it needs a paid plan.
- 05
Publish
Publish the Zap to switch it on. Each new transaction then runs both actions, and each one that succeeds counts as a task: two per transaction.
The 20 Partnero triggers
20 events start a Zap when something happens in Partnero, and 20 of them are instant: the app calls Zapier straight away, whatever your plan.
Customer Created
Instant triggerIn Zapier“Triggers when Customer is created.”
Starts your Zap each time a new customer record is added to Partnero, and hands that customer to the steps that follow.
Customer Credited
Instant triggerIn Zapier“Triggers when Customer is Credited.”
Fires when a customer's balance in Partnero receives a credit, so a reward landing on an account can set something off elsewhere.
Customer Deleted
Instant triggerIn Zapier“Triggers when Customer is deleted.”
Reacts to a customer being removed from Partnero. The deletion becomes the starting point, so the other tools holding that person can follow suit.
Customer Updated
Instant triggerIn Zapier“Triggers when Customer is updated.”
Any change saved on an existing Partnero customer starts the Zap, which receives that customer to pass along.
Lead Converted
Instant triggerIn Zapier“Triggers when Lead is converted.”
Picks up the moment a lead in Partnero is marked as converted: the referral turned into business, and the partner behind it is owed credit.
Lead Rejected
Instant triggerIn Zapier“Triggers when Lead is rejected.”
Covers the opposite outcome: a lead that gets rejected in Partnero. The Zap carries that refusal to wherever your team follows up.
Lead Submitted
Instant triggerIn Zapier“Triggers when Lead is submitted.”
The first lead event of the three: a lead is submitted in Partnero and the Zap starts with it in hand.
Partner Approved
Instant triggerIn Zapier“Triggers when Partner is approved.”
Runs when you approve a partner in Partnero, so the onboarding that happens outside the app can start without anyone remembering it.
Partner Archived
Instant triggerIn Zapier“Triggers when Partner is archived.”
Archiving a partner in Partnero sets this one off, which lets your other tools catch up with that change.
Partner Created
Instant triggerIn Zapier“Triggers when Partner is created.”
A new partner record created in Partnero starts this Zap, before any approval decision is involved.
Partner Deleted
Instant triggerIn Zapier“Triggers when Partner is deleted.”
Removing a partner from Partnero for good triggers the Zap and passes that partner on.
Partner Rejected
Instant triggerIn Zapier“Triggers when Partner is rejected.”
When an applicant is turned down in Partnero, this trigger hands that partner to the Zap.
Partner Updated
Instant triggerIn Zapier“Triggers when Partner is updated.”
Edits to an existing partner start the Zap, so a change made in Partnero can travel to every other copy of that partner.
Referred Subscriber Created
Instant triggerIn Zapier“Triggers when Referred Subscriber is created.”
Made for referral programs: it fires when a subscriber who came through a referral is created in Partnero.
Subscriber Created
Instant triggerIn Zapier“Triggers when Subscriber is created.”
Every new subscriber added to Partnero starts this Zap, and the subscriber is handed to the steps after it.
Subscriber Deleted
Instant triggerIn Zapier“Triggers when Subscriber is deleted.”
Deleting a subscriber in Partnero hands that removal to the Zap, so the person disappears elsewhere too.
Subscriber Rewarded
Instant triggerIn Zapier“Triggers when Subscriber is rewarded.”
Signals that a subscriber has been rewarded in Partnero, which is the natural moment to say thanks.
Subscriber Updated
Instant triggerIn Zapier“Triggers when Subscriber is updated.”
Changes saved on a subscriber in Partnero start the Zap with the updated subscriber attached.
Transaction Created
Instant triggerIn Zapier“Triggers when Transaction is created.”
A transaction recorded in Partnero, the purchase the partner's reward is calculated from, starts this Zap.
Transaction Deleted
Instant triggerIn Zapier“Triggers when Transaction is deleted.”
Whatever the reason, removing a transaction from Partnero sets this trigger off and passes the removed entry on.
The 14 Partnero actions
Partnero gives you 14 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
- Create a New Customer
- Create a New Partner
- Create a New Referred Customer
- Create a New Referring Customer
- Create a New Subscriber
- Create a New Transaction
- Credit Customer Balance
- Delete Existing Customer
- Delete Existing Partner
- Delete Existing Subscriber
- Delete Existing Transaction
- Update Existing Customer
- Update Existing Partner
- Update Existing Subscriber
Create a New Customer
ActionIn Zapier“Creates new Customer in the system.”
Adds a customer to Partnero from another app. Only the name is required.
Create a New Partner
ActionIn Zapier“Creates new Partner in the system.”
Opens a partner account in Partnero. A name and an email address are required, and the email must be unique.
Create a New Referred Customer
ActionIn Zapier“Creates new referred Customer in the system.”
Records a customer who arrived through a referral. The name is the one required field.
Create a New Referring Customer
ActionIn Zapier“Creates new Referring Customer in the system.”
Creates the other side of a referral: the customer who refers others. This one asks for an email address.
Create a New Subscriber
ActionIn Zapier“Creates new Subscriber in the system.”
Adds a subscriber to Partnero. The email is required and must be unique; optional TOS, Marketing Consent and Approved fields record what the person agreed to and their status.
Create a New Transaction
ActionIn Zapier“Creates new Transaction in the system.”
Records a purchase in Partnero, which then calculates the partner's reward from your program settings. Customer Key, Transaction Amount (the full purchase amount) and Transaction Action, a free label shown in the program, are required.
Credit Customer Balance
ActionIn Zapier“Credit specific Customer balance.”
Adds credit to a given customer's balance. Amount, Is Currency and Amount Units are all required.
Delete Existing Customer
ActionIn Zapier“Deletes existing Customer in the system.”
Removes a customer from Partnero, identified by its Key, the one required field.
Delete Existing Partner
ActionIn Zapier“Deletes existing Partner in the system.”
Takes a partner out of Partnero for good, straight from another app.
Delete Existing Subscriber
ActionIn Zapier“Deletes existing Subscriber in the system.”
Deletes a subscriber from Partnero when another tool says so.
Delete Existing Transaction
ActionIn Zapier“Deletes existing Transaction in the system.”
Removes a transaction from Partnero, picked by its Key, which is required.
Update Existing Customer
ActionIn Zapier“Updates existing Customer in the system.”
Changes an existing Partnero customer with values coming from another app, without anyone editing the record by hand in Partnero.
Update Existing Partner
ActionIn Zapier“Updates existing Partner in the system.”
Edits a partner already in Partnero, so a change made elsewhere reaches the program.
Update Existing Subscriber
ActionIn Zapier“Updates existing Subscriber in the system.”
Edits a Partnero subscriber, including Updated TOS, Updated Approved and Updated Marketing Consent.
The 2 Partnero searches
2 search steps look for data that already exists in Partnero, so a later step can use it.
Both searches sit at the bottom of the Action event list, under the SEARCH heading. A search makes the Zap multi-step, so it needs a paid plan. Three settings decide what happens when the result is not the one you expected.
Find Customer
SearchIn Zapier“Finds & get Customer details for given Id in the system.”
Looks up an existing Partnero customer from its Key, the one required field, and passes the details to the next steps.
Find Partner
SearchIn Zapier“Finds & get Partner details for given Id in the system.”
Retrieves a partner's details from Partnero by its Id, which is required, so later steps can use them.
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 and the steps that depend on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. Neither Partnero search offers that variant, so a missing customer or partner is never created here.
- If multiple search results are found?Three ways out: keep the first match (the default), stop the Zap, or hand all of them on at once.
When a Partnero Zap breaks
Zapier attaches no help article to Partnero, and no app-specific limit is documented. What breaks is the general behavior of Zaps, applied to this app.
Four cases come up with an app whose triggers and actions touch the same records. When a Zap acts strangely, the Zapier troubleshooting page is the next stop.
Nothing from before the Zap
A Zap only reacts to what happens after it is switched on. Partners, leads or transactions that already existed are not picked up; moving that backlog is a separate job.The Zap that sets itself off
Customer Updated plus Update Existing Customer, or Transaction Created plus Create a New Transaction: the Zap writes where its trigger watches, fires again and burns tasks.A bulk import held back
After a migration or a bulk import into Partnero, a sudden wave of events can be held back by Zapier's flood protection instead of running every step.A required field left empty
Key on Delete Existing Customer, Id on Find Partner, unique email on Create a New Partner: if the earlier step does not carry the value, the step cannot do its job.
Need help automating Partnero with Zapier?
A person reads every message.



