RecurX Integrations: What Connects to Your Shopify Subscriptions

Every integration at a glance

You connect each one from Settings → Integrations in the RecurX admin. Most take an API key; none require a developer.

Email and SMS marketing: Klaviyo, Mailchimp, Omnisend, Postscript

All four work the same way: RecurX pushes subscription lifecycle events into the tool, and you build the flows there. Data moves one way, from RecurX to the marketing tool. The lifecycle events are subscription started, renewed, cancelled, paused, resumed, skipped and expired, payment failed and recovered, win-back sent, and card expiring.

• Klaviyo. Each event updates the customer profile (subscription status, plan, total spent, last payment amount) and adds the profile to the list you chose. RecurX also records metrics you can trigger flows from, named like "RecurX Subscription Started", "RecurX Payment Failed" and "RecurX Card Expiring". A thirteenth signal, "RecurX Order Upcoming", carries the next order date, the items, the subtotal and signed links the subscriber can use to skip, delay or manage that order. Existing subscribers are synced as profiles when you connect.
• Mailchimp. RecurX upserts the member in your audience, tags them with their status (recurx_active, recurx_paused, recurx_cancelled, recurx_payment_failed) and plan, and records member events such as recurx_subscription_started and recurx_payment_failed. Existing subscribers are synced with their tags when you connect.
• Omnisend. RecurX upserts the contact, tags it recurx_subscriber plus the plan, and sends custom events such as recurx_subscription_started, recurx_payment_recovered and recurx_order_upcoming, with plan, status, amount and currency attached.
• Postscript. RecurX sends custom events such as recurx_subscription_created, recurx_payment_failed and recurx_order_upcoming, keyed by the subscriber’s phone number or email, for you to use as SMS automation triggers. It does not create Postscript subscribers or collect SMS consent; that stays in Postscript.

Marketing consent is never invented. RecurX only marks someone as subscribed to email marketing when they start a subscription and Shopify already holds their consent. Everyone else is synced for transactional use only.

Messaging: Twilio SMS and WhatsApp

These two are different from the marketing tools: RecurX itself sends the message, using your account, on every plan.

• Twilio. Connect an account SID, auth token and sending number. RecurX sends payment-recovery (dunning) texts, win-back texts, renewal reminders and customer-portal login codes. Delivery status comes back from Twilio, and STOP and START replies are honoured.
• WhatsApp. Connect the Meta WhatsApp Cloud API with a phone number ID and access token, then map your approved templates. RecurX sends payment recovery, win-back, renewal reminder, card expiry and subscription status messages (created, renewed, paused, resumed, cancelled, payment failed, payment recovered). A message is only sent when you have mapped an approved template for it and the subscriber has opted in to WhatsApp.

Shopify Flow: 9 triggers and 6 actions

RecurX appears in Shopify Flow as soon as it is installed, on both plans. Triggers start a workflow when something happens to a subscription; actions let a workflow change a subscription.

The six actions are Pause subscription, Resume subscription, Skip next subscription order, Change next billing date, Add subscriber tag and Discount next subscription order. There is no cancel action: a workflow cannot cancel a subscription.

Automation: Zapier, n8n and outbound webhooks

All three deliver the same JSON event to a URL you provide. Pick the one that matches where your automation lives.

• Zapier. Paste a Zapier Catch Hook URL and tick the events you want. This is a webhook connection into your Zaps, not a listed Zapier app, and it is one way: Zaps receive RecurX events.
• n8n. Paste the production webhook URL of an n8n workflow, with an optional auth header.
• Outbound webhooks. Add any HTTPS endpoint. Each delivery is signed with an HMAC SHA-256 signature, retried on failure with increasing delays, and kept in a 30-day delivery history you can replay from. A test event can be sent from the admin.

The events you can subscribe to are subscription.created, subscription.cancelled, subscription.paused, subscription.resumed, subscription.expired, subscription.skipped, subscription.updated, subscription.next_date_changed, subscription.frequency_changed, subscription.address_updated, subscription.product_added, subscription.product_removed, payment.succeeded, payment.failed, order.upcoming, order.shipped, order.delivered, winback.sent and card.expiring.

Support: Gorgias

Connecting Gorgias gives your agents two things inside a ticket. A read-only card shows the customer’s subscriptions (status, plan, frequency, next order, items and price) and recent orders. A macro lets an agent cancel a subscription without leaving the ticket; RecurX cancels the Shopify contract and records the agent and the reason. Cancel is the only action available from Gorgias. Pausing or skipping is done in the RecurX admin or by the customer in the portal.

For developers: public API and MCP server

Create an API key under Settings → API keys and choose its scopes. The REST API lists and reads subscriptions, customers and plans, returns an analytics summary, and can pause, resume, skip, reschedule, swap a product, change frequency, apply a discount or cancel a subscription. An OpenAPI description is published with the API.

The same key connects an AI assistant through the RecurX MCP server at app.recurx.app/mcp. An assistant can look up subscriptions and customers and pause, resume, skip, reschedule, swap or discount them. It cannot cancel a subscription.

Moving in from another subscription app

Importing subscribers from Recharge, Stripe, another app or a CSV file is covered in the migration guide, including the part that matters most: saved cards do not carry over automatically.