Ghost + Zapier: Manual Workflow for Non-Stripe Payments (and Its Limits)
Zapier is often the first suggestion when Ghost publishers ask about non-Stripe payment support. Here is an honest look at how the workflow is set up, where it breaks down, and what it actually costs.
Zapier is often the first suggestion when Ghost publishers ask about non-Stripe payment support. Here is an honest look at how the workflow is set up, where it breaks down, and what it actually costs.
What Zapier can do for Ghost
Zapier has a Ghost integration that allows you to create or update members. Combined with a trigger from a payment provider, you can build a flow: "when a purchase happens in Polar, create or update the member in Ghost." In theory, this solves the non-Stripe problem without writing any code.
In practice, the workflow requires more setup than a single Zap and has meaningful limitations around reliability, cost, and security.
Setting up the Zap
The basic flow looks like this:
- Trigger: "New order" or "New subscription" in your payment provider (Polar, PayPal, etc.)
- Action: "Create or update member" in Ghost, passing the customer email and setting the appropriate membership tier
- Optional: a second Zap for cancellations that revokes the tier
Each subscription lifecycle event (creation, renewal, upgrade, cancellation, refund) typically needs its own Zap or a complex filter and path setup within one Zap.
The real limitations
No signature verification
Zapier's webhook trigger accepts any POST request. There is no built-in signature verification. A fake event from any source would trigger your Zap and potentially grant membership access to the wrong person.
Per-task billing, and the free plan barely works for this
The free plan gives you 100 tasks per month, but it limits you to two-step Zaps (one trigger, one action) and polls every 15 minutes. That alone rules out membership sync: you typically need more than one action per event (update Ghost, log it, maybe notify yourself), and no branching between subscribe/cancel/renew paths. Once you go past 500 new members per month on a paid plan, you are paying for 500 to 2000+ tasks depending on how many steps your Zap has. Tasks are finite and costs grow with your audience.
No dead-letter queue
If a Zap run fails, Zapier logs the error in the task history. There is no automatic retry or manual replay. You need to find the failed task, understand why it failed, and re-trigger it manually.
Polling delay
On the free plan, Zapier polls for new events every 15 minutes. Paid plans poll faster, down to about 1 minute, but app-based polling triggers are never truly instant unless the provider supports a native webhook trigger. A customer who just purchased may still wait minutes before their Ghost access is granted.
What it actually costs
Zapier pricing is based on tasks per month, and the free plan is really just a sandbox for membership sync: 100 tasks, two-step Zaps only, 15-minute polling. To get multi-step Zaps (which membership sync needs for subscribe/cancel/renew branches), you need the Professional plan, which starts around 20 USD per month billed annually (about 30 USD billed monthly) for 750 tasks. The Team plan, with 2000 tasks, runs around 69 to 103 USD per month depending on billing cycle. These costs are on top of whatever you pay for Ghost and your payment provider.
For a growing membership site, Zapier costs can scale faster than membership revenue at early stages.
When Zapier is the right choice
Zapier works well if you have very low volume (under 50 events per month), you need to connect Ghost to services that have no other integration path, and you are comfortable accepting the reliability limitations.
For membership sync specifically, a purpose-built relay gives you signature verification, instant delivery, automatic retry, and predictable flat pricing. That is a meaningful difference when real member access is on the line.
