PartnerPortal.io Zapier integrationAutomate PartnerPortal.io with Zapier.
The PartnerPortal.io Zapier integration gives you 4 triggers, 5 actions and 3 searches to move leads and partners between your partner portal and the rest of your tools. All four triggers are instant, and the app works on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the PartnerPortal.io Zapier integration actually does
It links your PartnerPortal.io account to Zapier, so that a lead or a partner changing in your portal can start work in other apps, and the other way round. Your partner program keeps running from the portal; Zapier carries the records in and out, without anyone copying them by hand.
Three results people usually build first. A partner who hears back on every lead: Lead Created starts the Zap and Add Comment to Lead posts an acknowledgment, which the partner and their agent receive by email. Leads that arrive from your own forms: another app hands over the details and Create Lead files them in the portal. Approved partners synced to your other tools: Partner Updated, a filter on the status, then Find Partner User to get the right person.
What Zapier does not do here. There is no delete action, so a lead or a partner created by mistake gets cleaned up in the portal. No trigger watches comments. And nothing reaches back into the past: a Zap only sees what happens after you switch it on. Every search returns a single record, so a Zap cannot work through a whole list of leads in one go.
If Zapier is new to you, the Zapier training is a reasonable place to start before you build anything for your partners.
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 PartnerPortal.io account linked to Zapier once, then reused by every step of every Zap that touches the app.
What it really costs in tasks
PartnerPortal.io is not a premium app, so it runs on the free plan. The trigger itself never costs a task; each action that succeeds costs one.
- 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
An action that fails is not counted. The free plan gives you 100 tasks a month but only two-step Zaps: one trigger, one action. Add a filter, a search or a second action and you are building a multi-step Zap, which needs a paid plan. The interval grid below only matters for polling triggers, and none of this app's triggers poll. Tasks are what you budget for; how often a trigger checks is not your concern here.
Connect your PartnerPortal.io account
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. You need an account on PartnerPortal.io, plus access to whatever you do not own yourself and want the Zap to touch.
- 02
Pick PartnerPortal.io
Type the name of the app in the dialog, select it, then click Add connection. Zapier opens a separate tab where PartnerPortal.io asks you to sign in.
- 03
Sign in and allow access
Log in with the portal account the Zaps should act as, then grant Zapier access. The connection now shows on your Apps page, ready for every PartnerPortal.io step you add later.
Your first Zap: greet approved partners
GoalWhen a partner becomes active, find the right person at that partner and send them a welcome email.
- 01
Build the trigger
Pick PartnerPortal.io as the app and Partner Updated as the event, then choose your connection. This Zap uses a filter and a search, so it needs a paid plan.
- 02
Test it on real data
Run the trigger test. Zapier brings back the three most recent items from your account, so you map the next steps on a real partner, not on placeholders.
- 03
Keep active partners only
From the plus icon, add a Filter step on the status field and set it to active. Partner Updated fires on every edit, and this filter keeps the approvals only.
- 04
Find the person to greet
Add Find Partner User and map the Partner ID coming from the trigger. It returns one active person, the owner by default, whose email feeds the last step.
- 05
Send, test, publish
Add the email step, map the address the search found, then Configure & test each step and read what came back. Click Publish to switch the Zap on.
PartnerPortal.io triggers
4 events start a Zap when something happens in PartnerPortal.io, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.
Lead Created
Instant triggerIn Zapier“Triggers when a lead is created.”
Starts your Zap each time a new lead is added to the portal. The Zap receives that lead and can pass it to any later step.
Lead Updated
Instant triggerIn Zapier“Triggers when a lead is updated.”
This one reacts to changes rather than arrivals: any time an existing lead is edited, the Zap gets the updated version of it. It is the trigger to follow a deal as it moves along.
Partner Created
Instant triggerIn Zapier“Triggers when a partner is created (invited or registered).”
Fires when a partner company appears in your portal, whether you invited it or it registered on its own. The Zap gets the new partner, including the ID that later steps can reuse.
Partner Updated
Instant triggerIn Zapier“Triggers on any change to a partner, including when a partner is approved (status becomes active). It fires on every edit — not only the moment of approval — so add a Filter step on the status field to narrow to active partners. Best paired with an idempotent action (e.g. upserting a CRM record).”
Watches every change made to a partner, approval included, since an approved partner simply becomes active. That makes it the only way to react when a partner goes live.
PartnerPortal.io actions
PartnerPortal.io gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Add Comment to Lead
ActionIn Zapier“Add a comment to a Lead in PartnerPortal.io. The partner and their agent are notified by email, just like a comment left in the portal.”
Posts a comment on an existing lead, exactly as if someone had typed it in the portal. The partner and their agent are told by email.
Create Lead
ActionIn Zapier“Create a Lead in PartnerPortal.io”
Adds a fresh lead to PartnerPortal.io from data that started somewhere else, such as a form, an inbox or a spreadsheet.
Update Lead
ActionIn Zapier“Update an existing Lead in PartnerPortal.io, including its portal phase.”
Changes a lead that already lives in the portal, and can move it to another portal phase while it is at it.
Create Partner
ActionIn Zapier“Create a partner (organization + owner) in PartnerPortal.io. Behaves exactly like inviting a partner from the portal: the partner is activated and the owner is emailed a set-password invite.”
Creates a partner company and its owner in one go. It behaves like an invitation sent from the portal: the partner is active straight away and the owner gets an email to set a password.
Add Partner User
ActionIn Zapier“Add a user to an existing partner in PartnerPortal.io. Behaves exactly like adding a user from the partner's page in the portal: the user is activated and emailed a set-password invite.”
Adds one more person to a partner that already exists, like adding a user from the partner page. That person is activated and invited by email to set a password.
PartnerPortal.io searches
3 search steps look for data that already exists in PartnerPortal.io, so a later step can use it.
A search step never creates anything on its own: it fetches one existing lead, partner or person so the next step can use it. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not the one you expected.
Find Lead
SearchIn Zapier“Find an existing Lead in PartnerPortal.io by email and/or a custom field value. Returns a single lead so you can update it or add a comment.”
Looks up one existing lead by email, by a custom field value, or both, and returns a single result.
Find Partner
SearchFind or createIn Zapier“Find an existing partner in PartnerPortal.io by domain and/or owner email. Returns a single partner — pair it with Create Partner (via a "only continue if" filter or a search-or-create step) to avoid creating duplicates.”
Finds one partner from its domain, its owner email, or both. The editor also lists Find or Create Partner: it is this same search with the create box ticked, not a separate operation.
Find Partner User
SearchIn Zapier“Find an active person at a partner in PartnerPortal.io by Partner ID. Returns one person: the partner's longest-standing active owner, or its longest-standing active user if no owner is active. Pair it with a partner trigger to sync that person to your CRM. Use the User Type or Email filters to pick a different person.”
Starting from a Partner ID, returns one active person at that partner: the oldest active owner, or the oldest active user when no owner is active.
The three settings every search exposes
- 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.
- 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.
- 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 a PartnerPortal.io Zap breaks
Zapier attaches no help article to this app and no app-specific limit is documented. What goes wrong comes from how Zaps behave in general, plus one habit of the Partner Updated trigger.
Four cases cover most of the surprises. When a run fails anyway, the Zapier troubleshooting page is the next stop.
The Zap ignores existing leads
A Zap only reacts to what happens after you publish it. Leads and partners already in the portal stay where they are; moving that backlog is a separate job.Lead Updated loops on itself
If the Zap starts on Lead Updated and then runs Update Lead on that same lead, each run edits the lead and starts the Zap again, eating tasks fast.Partner Updated fires too often
It fires on every edit to a partner, not just the approval. Without a filter on the status, a welcome flow can go out several times to the same partner.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 automating PartnerPortal.io with Zapier?
A person reads every message.
