Integrations

Connect your stack. Your bill stays the same.

Store orders, payment events, CRM stages and form submissions become triggers for email that arrives when someone did something — not when you remembered to send. And because Bluey bills on emails sent, syncing a 200,000-customer store costs nothing extra.

No credit card to start · Cancel any time · Import your list in one click

₹0 extraConnecting a store never raises your bill — billing is on sends
8–15%Industry benchmark for cart recovery once the Shopify flow is live
5–15 minTypical setup, per integration. No developer for the native ones
$4/moEntry price for API and webhook access, 15,000 emails included

E-commerce

The events that make abandoned cart, browse abandonment and post-purchase flows possible.

Content & payments

Where subscribers are captured, and where money actually changes hands.

CRM

Keep the CRM your sales team lives in. Move the email off the per-contact meter.

Automation & developers

For the long tail of tools, and for everything that needs to be faster than middleware.

Native integration, middleware, or the API?

Use a native integration when one exists. It handles historical backfill, respects consent flags, keeps unsubscribes aligned in both directions and fires in real time. Nothing else does all four.

Use Zapier or Make for the long tail. A webinar platform, a booking tool, a spreadsheet your team maintains — middleware connects them in about five minutes each. The caveats worth knowing up front: polling triggers can run on a delay of up to fifteen minutes on lower Zapier plans, and there is no historical backfill, so import existing records by CSV separately.

Use the API when volume or latency rules the others out. Above a few thousand events a month, per-task middleware pricing starts to exceed the cost of writing the call. And for anything time-critical — abandoned cart, password resets — a fifteen-minute delay is the difference between a flow that works and one that does not. The API and webhooks page covers the endpoints, the event types and the plan limits.

Not sure which integration to start with?
If you have a store, connect it and turn on abandoned cart — it is reliably the highest-return flow. If you sell subscriptions, connect Stripe and build failed-payment recovery first.
Read the automation guide

Questions people ask before switching

Does connecting a large store or CRM increase my bill?

No, and this is the single most useful thing to understand about the pricing model. Bluey bills on emails sent, not contacts stored, so importing 200,000 Shopify customers or a decade of Salesforce records costs nothing extra until you email them. On per-contact platforms, connecting a large store is precisely the moment your invoice jumps a tier — which is why teams on those platforms end up doing database hygiene for billing reasons rather than deliverability ones.

What if the tool I use is not listed here?

Two routes. Zapier and Make connect Bluey to thousands of apps without waiting for a native integration, which covers most cases at low volume. Above a few thousand events a month, or where latency matters, the REST API and webhooks are faster and cheaper than paying per task. If you are choosing between them, the practical dividing line is volume: middleware for hundreds of events, API for thousands.

Do I need a developer?

Not for Shopify, Stripe, WordPress, HubSpot or Salesforce — those connect through OAuth or a plugin and a key. WooCommerce needs a plugin installed and an API key pair generated, which is standard WordPress admin work. Only the direct API genuinely requires a developer, and even then SMTP is available if you would rather not change your send code.

Will my customers' marketing consent be respected?

Yes. Consent flags carry across from the source system, and contacts who have not opted in import as suppressed rather than mailable. Unsubscribes propagate in both directions on the two-way CRM syncs. This matters legally under GDPR, CASL, the Australian Spam Act, Singapore's PDPA and India's DPDP Act — and practically, because mailing people who did not opt in is the fastest way to breach Gmail's 0.3% complaint threshold.

Can I run a new integration alongside my existing email tool?

Yes, and it is the sensible way to migrate. Split the audience — Bluey flows on one segment, your existing tool on the rest — compare recovered revenue over a week or two, then cut over. What you must not do is run both against the same contacts at once, because they will receive everything twice.

Free · 7 days

Connect it, and see what one flow recovers.

Seven days of full access, no credit card. Connect your store or your payment processor, turn on a single flow, and judge it on your own numbers.