Resources · Zapier integration

PartnerStack Zapier integrationAutomate PartnerStack with Zapier.

The PartnerStack Zapier integration gives you 9 triggers, 10 actions and 3 searches to keep partners, leads, deals, customers and rewards in step with the rest of your tools. All nine triggers are instant, and the app runs on the free plan.

See the 22 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the PartnerStack Zapier integration actually does

It links your PartnerStack account to Zapier. Anything that happens in your partner program, an application, a lead, a deal, a reward, can start work in another app, and data from other apps can land in PartnerStack already attributed to the right partner, without anyone retyping it.

Three results teams usually build first. Customers credited to the partner who sent them: New Lead Event starts the Zap, a filter keeps the event you care about, and Create Customer files the customer under that partner. Revenue that reaches the partner: your billing tool hands over a payment and Create Transaction records it against the customer. A partner team that never misses a message: New Message Event forwards every partner message to the tool your team already watches.

What Zapier does not do here. There is no delete action: a wrong customer or deal gets cleaned up inside PartnerStack. The triggers group several events under one name, so telling a creation from an update is up to a filter. And nothing reaches back into the past: a Zap only sees what happens after you switch it on.

If Zapier is new to you, the Zapier training is a sensible first step, and Make vs Zapier helps if you are still choosing a tool.

Vocabulary

Zapier words, in plain English

Eight words come back on every line of this page. Here is what each one means for you.

Zap
The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something on your behalf.
Task
What Zapier bills you for: one action that your Zap completes successfully. Your plan counts these and only these.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, so nothing waits for a check.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it quietly otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can reuse what it found.
Connection
Your PartnerStack account linked to Zapier once, then reused by every step of every Zap that touches the app.
Cost

What it really costs in tasks

PartnerStack is not a premium app, so it runs on the free plan. The trigger never costs a task; each action that succeeds costs one, and a failed one costs nothing.

  • TriggerFree, never counted
  • Successful action1 task each
  • Free plan100 tasks a month, two-step Zaps only
  • Filter or searchMakes the Zap multi-step, paid plan

The free plan gives you 100 tasks a month but only two-step Zaps: one trigger, one action. Because each PartnerStack trigger bundles several events, most useful Zaps need a filter, and a filter makes the Zap multi-step, which means a paid plan. Same for a search or a second action. The interval grid below only concerns polling triggers; all nine here are instant. What you budget for is tasks, nothing else.

Connect

Connect your PartnerStack account

  1. 01

    Open your connections

    In your Zapier account, go to the Apps page and click + Add connection. You need a PartnerStack account, plus access to whatever you do not own yourself and want the Zap to change.

  2. 02

    Pick PartnerStack

    Type the name of the app in the dialog, select it, then click Add connection. Zapier opens a separate tab where PartnerStack asks you to sign in to your account.

  3. 03

    Sign in and allow access

    Log in with the PartnerStack account the Zaps should act as, then grant Zapier access. The connection appears on your Apps page and every later PartnerStack step reuses it.

First Zap

Your first Zap: turn approved leads into customers

GoalWhen a partner's lead is approved in PartnerStack, create the customer under that same partner.

  1. 01

    Build the trigger

    Pick PartnerStack and New Lead Event, then your connection. The filter in this Zap makes it multi-step, so it needs a paid plan.

  2. 02

    Test on a real lead

    Run the trigger test. Zapier brings back the three most recent items of your account, so you map the next steps on a real lead rather than on empty fields.

  3. 03

    Keep approvals only

    From the plus icon, add a Filter step. The trigger covers creations, updates, closings, approvals and declines; the filter lets only the approval through.

  4. 04

    Create the customer

    Add Create Customer. Map the Partner Key and the email from the lead, and use the email as Customer Key if you have no internal reference.

  5. 05

    Test, then publish

    Use Configure & test on each step and read what came back. When the customer shows up under the right partner, click Publish.

Triggers

PartnerStack triggers

9 events start a Zap when something happens in PartnerStack, and 9 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Application Event

Instant trigger

In Zapier“Triggers when a new Application event occurs. (eg. Application Created, Updated, Approved, Declined).”

Follows the applications people send to join your program: a new one, an edit, an approval or a decline all start the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your partner manager wants each new application posted in the team chat, or each approval logged in the CRM.
Watch out
one trigger, four kinds of event, so a declined applicant and an approved one land in the same Zap. Filter on the event type.
2

New Customer Event

Instant trigger

In Zapier“Triggers when a customer event occurs (eg. Customer Created, Updated, Deleted).”

Reacts whenever a customer is created, updated or deleted in PartnerStack, and hands the customer record to the next steps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your finance or support tool should know which partner referred each new customer, without an export.
Watch out
a deletion fires it too; filter on the event type before you copy anything, or a removed customer could come back to life elsewhere.
3

New Deal Event

Instant trigger

In Zapier“Triggers when a deal event occurs (eg. Deal Created, Updated, Stage Updated, Close Date Updated, Amount Updated) Note: Meta fields are set in Groups > Deal Registration.”

Tracks deals that partners register, from creation through changes of stage, close date or amount, so the Zap sees a deal move as it moves.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
sales needs partner-sourced deals mirrored in the CRM, with the stage kept up to date.
Watch out
the extra deal fields come from Groups > Deal Registration in PartnerStack; a field missing there will be missing in the Zap too.
4

New Lead Event

Instant trigger

In Zapier“Triggers when a lead event occurs (eg. Lead Created, Updated, Closed, Approved, Declined).”

Starts the Zap whenever one of your partners' leads is created, updated, closed, approved or declined. It is the natural starting point for anything that follows a referral.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an approved lead should become a customer, or a declined one should trigger a note to the partner.
Watch out
never pair it with Update Lead on the same lead, or each run starts the Zap again.
5

New Message Event

Instant trigger

In Zapier“Triggers whenever a partner sends a message through the Messages Tab (https://app.growsumo.com/messages).”

Fires each time a partner writes to you through the Messages tab of PartnerStack. The message reaches the Zap, ready to be passed on.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your partner team lives in a shared inbox or a chat tool and should not have to log in to PartnerStack to see questions.
Watch out
only messages that partners send count here, so this is not a full copy of the conversation.
6

New Offer Event

Instant trigger

In Zapier“Triggers when an offer event occurs (eg. Offer Created, Updated, Deleted).”

Watches the offers you publish to partners: creating, editing or deleting one starts the Zap with the details of that offer.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
marketing keeps a list of current partner offers in a sheet or a wiki and wants it updated without anyone copying it.
Watch out
a deleted offer fires the same trigger, so a filter decides whether to add, change or remove the line.
7

New Partnership Event

Instant trigger

In Zapier“Triggers when a partnership event occurs (eg. Partnership Created, Updated, Deleted).”

Covers the partners themselves: a partnership created, updated or deleted starts the Zap with that partner's record.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
each new partner should get a contact in your CRM or a seat in your onboarding sequence, from the day the partnership exists.
Watch out
an update fires it too; pair it with a step that updates an existing record rather than creating a new one each time.
8

New Reward Event

Instant trigger

In Zapier“Triggers when a reward event occurs (eg. Reward Created, Declined, Restored, Updated).”

Follows the rewards your partners earn, whether a reward is created, declined, restored or updated.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your accounting team wants every partner reward in its own tracking sheet, or a partner manager wants to congratulate the partner who just earned one.
Watch out
a declined reward and a restored one go through the same trigger; filter on the event type before you send any message to the partner.
9

New Transaction Event

Instant trigger

In Zapier“Triggers when a transaction event occurs (eg. Transaction Created, Deleted).”

Fires when a transaction is created or deleted, the payments that feed partner commissions in PartnerStack.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you report partner-driven revenue in a spreadsheet or a dashboard tool and want each payment there on its own.
Watch out
a deletion arrives through the same trigger, so a Zap that adds a row on every event also adds one for a payment that was removed.
Actions

PartnerStack actions

PartnerStack gives you 10 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Action

Action

In Zapier“Logs an action that a partner or customer has performed. If a reward is set for the action, it will be created. (e.g. partner posted in forum).”

Logs something a partner or a customer did, such as posting in your forum. If that action is tied to a reward, the reward is created along with it.

When to use it
you reward partners for activity that happens in another tool.
Watch out
the name follows a noun_verb pattern and, for a rewarded event, must match exactly what was set up with PartnerStack's Customer Success team.
2

Create Deal

Action

In Zapier“Creates a new Deal attributed to the partner that owns it.”

Opens a deal in PartnerStack and credits it to the partner who owns it.

When to use it
partners register opportunities in your CRM or a form, and you want PartnerStack to know.
Watch out
eight fields are required, the amount is in cents, and the stage must already exist in the deal stage list of your Group Settings.
3

Create Lead

Action

In Zapier“Creates a new Lead attributed to the partner that drove it.”

Adds a lead and attributes it to the partner who brought it in.

When to use it
partner referrals arrive through a form or an inbox rather than through PartnerStack itself.
Watch out
on creation the status can only be new or qualified; anything else has to wait for Update Lead.
4

Create Partner

Action

In Zapier“Creates a new partner.”

Creates a new partner in PartnerStack. The only field it insists on is the email.

When to use it
partner sign-ups are collected in another tool, such as a form or an event registration, and should become partners without manual entry.
Watch out
run Find Partner first if the same person can sign up twice.
5

Create Transaction

Action

In Zapier“Creates a new Transaction attributed to a partner.”

Records a payment against a customer, which is what lets PartnerStack credit the partner behind it.

When to use it
your billing tool confirms a payment and the partner commission should follow.
Watch out
the amount is in cents, so 2000 means 20.00, and the Customer Key is what ties the payment to the right customer.
6

Create Customer

Action

In Zapier“Creates a new customer.”

Records a customer and links it to the partner who referred it, using that partner's key.

When to use it
a referred lead signs up in your product and PartnerStack must know which partner gets the credit.
Watch out
two customers cannot share a Customer Key; a second run with the same key ends in an error. Without an internal ID, use the customer's email.
7

Update Customer

Action

In Zapier“Updates an existing customer. You can use this to connect a customer to a provider key.”

Changes a customer that already exists. It can also attach the customer to a provider key.

When to use it
a customer's details change in your product and PartnerStack should stay accurate.
Watch out
it finds the customer by Customer Key only; use Find Customer first if all you have is an email.
8

Update Deal

Action

In Zapier“Updates a Deal.”

Edits a deal that a partner already registered, its stage for instance.

When to use it
your CRM moves an opportunity forward and the partner should see the same stage in PartnerStack.
Watch out
it needs the Deal Key you set when the deal was created, so keep that key somewhere your CRM can return it.
9

Update Lead

Action

In Zapier“Updates a Lead.”

Changes an existing lead, for example to move it past the status it had on creation.

When to use it
sales qualifies or closes a referral in another tool and PartnerStack should reflect it.
Watch out
it needs the lead's key; Find Lead can return it from an email.
10

Update Partnership

Action

In Zapier“Update a partnership.”

Edits a partner's record, found by its current partner key or email.

When to use it
a partner's details change in your CRM and PartnerStack should carry the same information.
Watch out
if the step changes the email, the old email is the one to supply as the identifier.
Searches

PartnerStack searches

3 search steps look for data that already exists in PartnerStack, so a later step can use it.

A search step fetches one existing customer, lead or partner so the next step can use it. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Each of the three PartnerStack searches also shows up as a Find or Create line: same search, create box ticked. Three settings decide what happens when the result surprises you.

1

Find Customer

SearchFind or create

In Zapier“Finds a customer by email address or customer key.”

Looks up a customer from either its Customer Key or its email, entered in a single box.

When to use it
before Update Customer or Create Transaction, when the starting step only knows the email.
Watch out
Find or Create Customer is this same search with the create box ticked, and it then asks for what Create Customer needs.
2

Find Lead

SearchFind or create

In Zapier“Find lead by email.”

Finds a lead from its email, and nothing else: there is no other way to search here.

When to use it
just before Update Lead, to get the key that action requires.
Watch out
Find or Create Lead is not another operation, only this search with the create box ticked; it then wants the fields of Create Lead, Partner Key included.
3

Find Partner

SearchFind or create

In Zapier“Finds a partner by email address or partner key.”

Returns a partner from its partner key or its email, typed into one field.

When to use it
before Create Partner, so the same person is never added twice, or before Update Partnership.
Watch out
the Find or Create Partner line in the editor is this search with creation switched on, not a separate step.

The three settings every search exposes

  1. Successful if no search results are found?
    Left as it is, a search that finds nothing stops the Zap and the steps that needed its result are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: the setting above disappears and the step asks for what it needs to create the missing item.
  3. If multiple search results are found?
    When several items match, keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When a PartnerStack Zap breaks

Zapier attaches no help article to this app, and no app-specific rate limit is documented. What goes wrong comes from how Zaps work in general, plus a few rules found in the fields of PartnerStack itself.

These cases cover most of the surprises. If a run still fails, the Zapier troubleshooting page is the next stop.

  • Past leads and deals are ignored

    A Zap only reacts to what happens after you publish it. Partners, leads and deals already in PartnerStack stay put; moving that history is a separate job.

  • Create Customer fails on a known key

    PartnerStack refuses two customers with the same Customer Key. Put Find Customer in front, or use Find or Create Customer, so a repeat run does not end in an error.

  • A deal stage is rejected

    Create Deal only accepts a stage that already exists in the deal stage list of your Group Settings. A stage name coming from your CRM must match it exactly.

  • A lead event loops on itself

    If the Zap starts on New Lead Event and runs Update Lead on that same lead, each update starts the Zap again and burns through your tasks.

  • A deletion gets copied as news

    Customer, offer, partnership and transaction triggers also fire on deletions. Without a filter, a removed item can create a fresh row or record elsewhere.

  • A bulk import gets held back

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back instead of firing them all.
Need help

Need help automating PartnerStack with Zapier?

A person reads every message.

FAQ

PartnerStack Zapier integration: questions

01Is the PartnerStack Zapier integration free?
Yes, it works on the free Zapier plan, because PartnerStack is not a premium app. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. That is the real limit with PartnerStack, because each trigger bundles several events and you usually want a filter to keep just one of them. A filter, a search or a second action makes the Zap multi-step, and multi-step Zaps need a paid plan. No price is given here, since Zapier changes its grids often.
02How many tasks does a PartnerStack Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that starts on New Lead Event and runs Create Customer costs one task each time a customer is created. A filter placed before the action stops unwanted events without spending a task, which matters here because every trigger fires on several kinds of event. An action that fails is not counted. Watch the Zaps that write back into PartnerStack: a loop between a lead trigger and Update Lead can empty a monthly allowance quickly.
03Is the PartnerStack integration real time?
Yes. All nine triggers are instant: PartnerStack tells Zapier when the event happens, and the Zap starts right away. The plan interval, 15 minutes on Free and down to 1 minute on Team or Enterprise, only applies to polling triggers, and this app has none. In the editor, a Zap built on an instant trigger shows a lightning bolt. The type is set by the app and cannot be changed from Zapier, so there is nothing to tune on your side.
04What does it take to connect PartnerStack to Zapier?
A PartnerStack account and a Zapier account. On the Apps page in Zapier, click + Add connection, search for PartnerStack, then Add connection; sign in to PartnerStack in the tab that opens and grant access. You also need read or write access to anything you do not own and want the Zap to change. Before building, gather the Partner Keys of the partners involved, since Create Lead, Create Deal and Create Customer all require one, and it often sits at the end of the partner's referral link.
05Why does Create Customer return an error for some customers?
Most often because a customer with the same Customer Key already exists, and PartnerStack does not allow two. This happens when a Zap runs twice for the same person, or when the key you map is not unique. The fix is to put Find Customer in front of the action, or to use Find or Create Customer, which only creates the customer when the search comes back empty. If your product has no internal reference for customers, using their email as the Customer Key keeps things unique and readable.
06What if the PartnerStack operation you need is not listed?
Then the integration cannot do it, and no hidden setting will unlock it. The 22 operations on this page are everything Zapier offers for PartnerStack today: 9 triggers, 10 actions and 3 searches. There is no delete action, for example, and no way to find a deal by search. The usual workaround is to combine what exists, such as a Find search followed by an Update action. If that still does not cover the case, the step stays manual in PartnerStack.
07Zapier, Make or n8n for PartnerStack?
Decide on criteria, not on brand. On Zapier, PartnerStack offers 9 instant triggers, 10 actions and 3 searches, and works on the free plan as long as a Zap stays at two steps, which a filter breaks. On any platform you compare, check whether the actions you need exist, Create Transaction or Create Action for instance, whether triggers arrive instantly, and how a run that goes through a filter is billed. Then build the same scenario on both and keep the one your team can maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations