Resources · Zapier integration

Passion.io Zapier integrationAutomate Passion.io with Zapier.

The Passion.io Zapier integration gives you 7 triggers, 4 actions and 0 searches. All 7 triggers are instant: sign-ups, purchases, cancellations, lessons, comments, chat messages and check-ins reach your Zap without waiting, free plan included.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Passion.io Zapier integration does for you

The Passion.io Zapier integration links the app where you sell your courses and coaching to the rest of your tools, without code. Something happens in Passion.io (a member signs up, buys a plan, finishes a lesson) and Zapier carries it elsewhere. It also works the other way: an outside event makes Passion.io record an order or post a message.

Three results people build first. A buyer list that keeps itself current: Plan Purchased and Subscription Cancelled feed your spreadsheet or CRM, so who pays and who left gets written down without anyone copying it by hand. A community that greets newcomers: Account Created followed by Send Channel Message posts a welcome in the channel you pick. Sales made elsewhere that land in Passion.io: a payment recorded in another tool runs Create Order, tied to the plan IDs you choose.

What Zapier does not do here. This app has no search step, so a Zap cannot look up an existing member or plan before it acts: it works with what the trigger brought, or with what you type. There is no action to edit a member, a lesson or a post. And nothing that happened before the Zap was switched on gets picked up, so plan the import of past members on its own. Still choosing a platform? See the Zapier review, then Make vs Zapier and n8n vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here they are in plain English, once.

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, like a new Passion.io member. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes, sends or records something for you in an app.
Task
The unit Zapier bills: one action your Zap completed successfully. The number on your plan counts those, nothing else.
Instant vs polling trigger
An instant trigger is reported by the app the moment the event happens. A polling one is checked by Zapier on a timer set by your plan.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it quietly otherwise.
Connection
Your Passion.io account linked to Zapier once, then reused by every step of every Zap that touches Passion.io.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
Cost

What Passion.io on Zapier really costs

Zapier bills in tasks, and only for actions that work. Triggers never cost a thing, and since every Passion.io trigger is instant, your plan's check interval plays no part here.

  • Tasks on the free plan100 per month
  • Steps on the free plan2: one trigger, one action
  • Premium appNo
  • Instant triggers7 of 7

Each successful action counts one task, so a Zap with two actions counts two per run. A failed action is not counted. The free plan gives 100 tasks a month and Zaps of two steps only. A filter or a second action turns the Zap multi-step, which means a paid plan. Watching for new Passion.io events costs nothing, however busy your community gets. Passion.io is not a premium app: it runs on the free plan.

Connect

Connect Passion.io to Zapier in 3 steps

  1. 01

    Open Apps and add a connection

    In your Zapier account, open the Apps page and click + Add connection. A dialog opens with a search box: type Passion.io and pick it from the results.

  2. 02

    Sign in to Passion.io

    Click Add connection. Passion.io opens in a separate tab: sign in with the account behind the app you sell. If someone else owns it, ask them first for read or write access to what the Zap will touch.

  3. 03

    Grant access and reuse it

    Approve the access Zapier asks for. The connection now sits on your Apps page, and every Zap step that uses Passion.io picks it up, so you sign in once, not once per Zap.

First Zap

Your first Zap: celebrate a finished lesson in your community

GoalWhen a member completes the lesson you choose, Passion.io posts a message in one of your community channels.

  1. 01

    Build: pick the trigger

    Create a Zap, choose Passion.io as the app that starts it and Lesson Completed as the event. Select the connection you made earlier.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent completions from your account. Pick one, so the rest of the setup is mapped on a real member and a real lesson.

  3. 03

    Add a filter

    From the plus icon, add Filter. Choose the field that names the lesson, a text rule, and the lesson title as value. A text rule only works on text. This step makes the Zap multi-step: paid plan.

  4. 04

    Add the action

    Add Passion.io again with Send Channel Message. Type the Community ID and the Channel ID (Post ID), then write the message, mixing your own words with the member data from the trigger.

  5. 05

    Test, then publish

    Test the action once and check the post really landed in the right channel. Then Publish: the Zap is on and reacts to the next completion, not to past ones.

Triggers

The 7 Passion.io triggers

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

1

Account Created

Instant trigger

In Zapier“New user appeared in the users list”

Starts your Zap each time someone new joins your Passion.io app. It is the entry point for anything that should happen to a newcomer: a welcome, a contact in your CRM, a line in your onboarding tracker.

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 want every new member greeted or logged, whether they paid or simply downloaded the app.
Watch out
members who joined before the Zap was published are never picked up, so import the backlog separately.
2

Comment Created

Instant trigger

In Zapier“A user commented on a post”

Fires when a user comments on a post in your Passion.io community. That makes it a listening post: you see what members say without opening the app all day long, and you can route a question to whoever answers it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a coach wants every new comment copied to a team chat so nobody waits for an answer.
Watch out
if a Zap of yours posts into the community too, test whether its own posts come back as new items before switching both on.
3

Lesson Completed

Instant trigger

In Zapier“User completed a lesson”

Reacts when a user finishes a lesson. Progress becomes something you can act on: congratulate, unlock the next step in another tool, or record where each student stands in a course you sell.

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 run a cohort and want a certificate request or a coaching call booked once the final lesson is done.
Watch out
it fires for every lesson; to react to one in particular, add a filter, which needs a paid plan.
4

New Chat Message

Instant trigger

In Zapier“A user sent a message”

Picks up each message a user sends in the app's chat. Support questions and sales conversations no longer sit unread inside Passion.io: they can reach the inbox or the help desk your team already watches.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
members write to you in the app, but your team answers from somewhere else.
Watch out
a Zap that replies with Send DM could wake this trigger again; check on a test account that your own messages do not loop back.
5

Plan Purchased

Instant trigger

In Zapier“Triggers when a user subscribes to a plan.”

Goes off the moment someone buys one of your plans. This is the moment money comes in, so it usually feeds accounting, a sales sheet or a thank-you sequence handled by your email tool.

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 want each new subscriber added to a customer list and tagged with the plan they bought.
Watch out
each run that completes an action costs a task, so a busy launch week eats your monthly allowance faster than a quiet one.
6

Subscription Cancelled

Instant trigger

In Zapier“A user canceled their subscription”

Each subscription a user cancels starts the Zap. Churn stops being a number you discover at the end of the month: each departure becomes an event you can answer, log or hand to someone who will call the member back.

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 want a short exit survey sent, or a CRM record moved to a former-customer stage.
Watch out
cancellations made before the Zap went live are not replayed, so your lost-customer list starts on the day you publish.
7

New Tracking Check-In

Instant trigger

In Zapier“A user created a new check-in”

Starts the Zap when a user creates a new check-in in the app's tracking feature. For fitness or habit programs, every check-in is a sign of engagement worth keeping somewhere you can sort and chart.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a trainer wants every client check-in added as a row in a sheet reviewed before each session.
Watch out
active members check in often, and each completed action is a task; keep the free plan's 100 in mind.
Actions

The 4 Passion.io actions

Passion.io gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Cancel Subscription

Action

In Zapier“Cancels one ore more user subscriptions based on Plan IDs”

Cancels one or more subscriptions of a user, found by email address, for the plan IDs you list.

When to use it
a refund or a failed payment handled in another tool must also cut access in Passion.io.
Watch out
it acts on every plan ID you give it, so double-check the list before you publish.
2

Create Order

Action

In Zapier“Creates an Order”

Records an order in Passion.io for a buyer, identified by email address, with the country, the plan IDs bought and the sale amount.

When to use it
you sell through another checkout and want the sale to show up in Passion.io too.
Watch out
the amount field expects the sales price in cents, not in units, so convert it before mapping.
3

Send Channel Message

Action

In Zapier“Sends a Message to a Channel”

Posts your message in a given channel of a given community. You type both IDs once, and the text can blend fixed words with data from the trigger.

When to use it
announcements, welcomes or wins you want the whole community to see.
Watch out
the Channel ID is the ID of the post, so copy the right one or the message lands elsewhere.
4

Send DM

Action

In Zapier“Sends a DM to a user”

Sends a private message to one user of your app. It needs that user's ID and the text to send, nothing more.

When to use it
a personal nudge after a purchase or a missed lesson, without writing it yourself each time.
Watch out
without a search step, the User ID must come from an earlier step; a Zap started in another tool may not have it.
When it breaks

When a Passion.io Zap breaks

Zapier links no help article to Passion.io, so the traps below are the general ones, read through this app.

Four cases cover what goes wrong. If a Zap still misbehaves after that, the Zapier troubleshooting page is the next stop.

  • Old members, buyers and lessons are ignored

    A Zap only reacts to what happens after you publish it. Users, orders and completions that existed before are never picked up: moving that history is a separate job.

  • A Zap that keeps setting itself off

    When a Zap writes where its own trigger watches, say a reply DM on a chat message, it can start itself again and again and burn your tasks fast.

  • A sudden flood is held back

    If a bulk import or a migration makes a trigger return a huge batch at once, Zapier's flood protection can hold those runs back instead of firing them all.

  • An action fails on a missing ID

    All four actions require fields such as Plan IDs, a Community ID or a User ID. If the earlier steps do not supply one, the action fails and costs no task.
Need help

Need help automating Passion.io with Zapier?

A person reads every message.

FAQ

Passion.io Zapier integration: frequent questions

01Is the Passion.io Zapier integration free?
Yes, on simple Zaps. Passion.io is not a premium app, so it works on the free Zapier plan, which gives 100 tasks a month. The catch is the shape of the Zap: the free plan allows two steps, one trigger and one action. The moment you add a filter, a second action or any other step, the Zap becomes multi-step and needs a paid plan. A Zap that turns a new purchase into a welcome post fits in the free plan; a Zap that filters on one lesson does not.
02How many tasks does a Passion.io Zap use?
One task per action that completes successfully, and nothing for the trigger. A Zap with Plan Purchased and Create Order spends one task each time a plan is bought. Add a Send DM after it and the same event costs two. An action that fails is not counted against your plan. Watching for new events costs nothing either, however often members sign up or post. So the bill grows with the number of actions per run multiplied by the number of runs, not with the number of Zaps you keep switched on.
03Are Passion.io triggers real time?
Yes. All seven are instant triggers: Passion.io tells Zapier when the event happens, and the Zap starts straight away. That holds on every plan, including the free one, which on polling triggers would mean checking for news only every 15 minutes. In the editor, a Zap built on an instant trigger shows a lightning bolt. The type comes from the app itself and cannot be changed from Zapier, so there is no setting to look for. What can still hold runs back is a sudden flood of events, which Zapier's flood protection may pause.
04What do you need to connect a Passion.io account?
A Passion.io account, and access to the app and community the Zap will act on. On Zapier, you open the Apps page, click + Add connection, pick Passion.io, sign in in the tab that opens and grant access. If the Passion.io app belongs to someone else, they need to give you read or write access first. Then, for the actions, keep the IDs at hand: Plan IDs, a Community ID and a Channel ID, or a User ID. Without them, the actions cannot be filled in.
05Why does Send DM fail when the Zap starts in another app?
Because Send DM needs the User ID of the member, and Passion.io has no search step on Zapier to look it up from an email address. When the Zap starts on a Passion.io trigger, the test shows what the event carries, so you can check whether an ID is there to map. When the Zap starts in a payment tool or a form, nothing guarantees that ID is part of the data, and if it is missing the action fails for want of a required field. Test with a real item before publishing.
06What if the Passion.io operation you want does not exist on Zapier?
Then the Zap cannot do it directly. The integration offers 7 triggers and 4 actions, with no search and no action to edit a member, a lesson or a post. Two ways out. Rework the scenario around what exists: record an order with Create Order, or cut access with Cancel Subscription. Or do the step in another tool your Zap already reaches. Check the operations listed on this page before you build, so the scenario starts from what really exists.
07Zapier, Make or n8n for Passion.io?
It depends on the shape of your scenarios, not on a ranking. On Zapier, Passion.io brings 7 instant triggers and 4 actions, works on the free plan, and connecting the account only takes a sign-in. The limits are clear too: two steps on the free plan, no search step, billing per successful action. If your Zaps stay simple, that fits well. If you need filters, several actions or lookups on every run, compare what the other platform offers for Passion.io and how it bills a run before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations