Why WordPress Categories Break in Zapier Automations (and How to Fix It)
Posts arriving broken in WordPress from Airtable via Zapier? The culprit is usually custom taxonomy formatting. Here's why it happens and three ways to fix it.
Fix the Zapier + Stripe 'New Subscription' Trigger Timing Problem
The Zapier 'New Subscription' Stripe trigger fires before payment is confirmed. Here's how to fix it by switching to the 'New Charge' trigger — and the filter gotcha to avoid.
TABLE OF CONTENTS
If you're using Zapier's New Subscription trigger with Stripe to grant access after a purchase, there's a timing problem you need to know about — and a straightforward fix.
The Problem: "New Subscription" Fires Before Payment Clears
The Stripe → New Subscription trigger in Zapier fires as soon as Stripe creates a subscription object. That happens before the first payment is confirmed.
This means your Zap — which might send a welcome email, create a user account, or unlock a course — runs even when the card fails or the payment is still processing.
The result: users get access before they've paid. In some cases, they never pay at all.
The Fix: Switch to "New Charge"
Instead of using the New Subscription trigger, use the New Charge trigger in Stripe. This trigger only fires once a charge is successfully captured — meaning Stripe has confirmed the payment went through.
Here's how to update your Zap:
- Open the Zap in Zapier and click on the trigger step.
- Change the trigger from New Subscription to New Charge.
- In the trigger filters, set Status = succeeded to ensure you're only catching confirmed payments.
- Map your existing action fields to the new charge data (the field names are slightly different).
- Test with a real payment before going live.
The Filter Gotcha: Avoid Exact-Match on Status
When filtering on the charge status, be careful with exact-match filters. If Stripe returns an unexpected string value (like an error code or a localized variant), an exact-match filter will silently fail and let the Zap through anyway.
Instead of:
Status = "succeeded"Use:
Status contains "succeeded" or Status starts with "succeeded"This makes your filter resilient to minor variations in the returned value without breaking your logic.
Handling Subscription Context in the Charge Data
One thing you lose when switching to New Charge is the subscription ID as a top-level field. You may need it to look up the plan, billing interval, or customer record downstream.
Here's how to handle it:
- The charge object includes a
invoicefield. The invoice links back to the subscription.
- Add a Zapier Formatter step or a Webhooks by Zapier lookup to retrieve the subscription object using the invoice ID if you need subscription-level data (plan name, interval, trial status).
- Alternatively, use the customer ID from the charge data to look up the customer's active subscriptions via a Stripe API call.
Using the Description Field for Dynamic Pricing
If you're selling multiple plans and need to route users differently based on what they bought, the charge's description field is your friend.
Stripe populates the description with the product or plan name when a charge is created from a subscription. You can use this in Zapier filter steps to branch your workflow:
Description contains "Pro"→ route to pro onboarding flow
Description contains "Starter"→ route to starter onboarding flow
This avoids the need to look up the subscription object for simple routing decisions.
Ongoing Subscription Failures vs. Initial Payment Failures
Keep in mind that the New Charge trigger handles both:
- Initial payments — first charge when a new customer subscribes
- Renewal charges — subsequent monthly/annual charges
You probably don't want your welcome email or account creation flow to re-run on every renewal. Add a filter step to exclude charges where the
invoice → attempt_count is greater than 1, which identifies renewal charges rather than initial ones.For ongoing failures (a card that expires mid-subscription), consider a separate Zap using the Payment Failed trigger — this keeps your success and failure handling cleanly separated.
Quick Reference: New Subscription vs. New Charge
ㅤ | New Subscription | New Charge |
When it fires | Subscription object created | Payment successfully captured |
Payment confirmed? | ❌ No | ✅ Yes |
Best for | Metadata/setup tasks | Granting access, sending receipts |
Subscription data | Direct | Via invoice lookup |
Get Your Zapier + Stripe Integration Right the First Time
Payment workflow bugs are high-stakes — they either give away your product for free or block customers who've already paid. If you want an expert to review your setup, book a free discovery call.
As certified Zapier Premier Partners, Connex has helped hundreds of teams build reliable payment, onboarding, and subscription automation workflows.
Related Posts
Notion Custom Agent Credits: How to Cut Costs Before the Paid Era Begins
Notion custom agents switch to paid credits May 4, 2026. Learn how to audit your usage, narrow triggers, and optimize agent workflows before the meter starts.
How to Build a Notion Custom Agent for Daily Team Briefings
Learn how to build a Notion custom agent that delivers personalized daily briefings to your team — pulling calendar events, tasks, and meeting context automatically.
