Integrations
The Integrations tab in Curobi’s top navigation, between Data & API and Settings, is where you send subscription events to the other apps your store runs. A cancellation can start a win-back series in Klaviyo, tag the customer through Shopify Flow, or land in your own systems through a webhook, without you exporting anything.
Subscription metrics and profile fields in your own Klaviyo account, for flows and segments. Business plan and up.
KlaviyoSubscription triggers for Shopify’s own automation app. Every plan, including Free.
Shopify FlowSigned webhooks, API keys and exports for your own ERP, 3PL or warehouse. Pro plan.
Webhooks & APIWhich plan you need
| Integration | Plan | Development stores |
|---|---|---|
| Shopify Flow | Every plan, including Free | Yes |
| Klaviyo | Business and Pro. Not part of the Free plan’s 14-day trial | Yes |
| Webhooks and the developer API | Pro | No, until the store is on a paid Shopify plan |
Klaviyo is a Business feature even though Shopify’s plan selection page and Curobi’s Plan & billing page don’t list it: those show each plan’s top features only.
Development stores get Klaviyo, but not webhooks. A Klaviyo connection can only ever talk to Klaviyo. A webhook can point at any address, and a store that will never be billed could otherwise aim it at production systems. So an agency can build and test Klaviyo flows on a development store before a store launches, while webhooks wait for a paid store. See Development stores.
Which one to use
- You want subscription emails built in Klaviyo, next to the rest of your marketing: use Klaviyo. You can also hand Curobi’s own lifecycle emails to a Klaviyo flow so customers don’t get two.
- You want something to happen in Shopify (tag a customer, alert your team, add a row to a sheet): use Shopify Flow. Flow already connects to many other apps, so it covers a lot of tools Curobi has no direct integration for.
- You want the data in your own systems: use webhooks and the Admin API.
You can use more than one at the same time.
When an integration stops working
An integration that fails quietly is worse than none, because your flows look fine and simply stop running. So when Curobi has to switch a connection off itself (a Klaviyo key that was deleted, or a webhook endpoint that keeps failing), it shows a banner on that integration’s page and raises an Integrations item in the Risk Center. Switching one off yourself raises nothing.