1. How integrations behave
Where to find them: Sublyra admin → Settings → Integrations (Klaviyo, Mailchimp, API keys) and Settings → SMS notifications (Twilio).
Every integration call is fire-and-forget from the webhook choke points:
- No keys? The integration quietly does nothing. Subscriptions work normally.
- Bad keys? The error is logged and shown as a red "last sync failed" line on the card — webhook processing is never affected. A broken integration can never break your billing.
- Keys are encrypted at rest and masked in the UI. Once saved, a secret is never shown again — leaving the field blank later means "keep the stored one".
2. Klaviyo
Sublyra pushes subscription lifecycle events into your Klaviyo account so you can build automated flows off them, and keeps a list in step with your subscriber base.
| What syncs | Detail |
|---|---|
| Lifecycle events | Subscription Started, Subscription Cancelled, Subscription Paused, Order Charged, Payment Failed — sent via Klaviyo's Track API, ready to trigger flows |
| Profiles & list | Profile upsert plus list subscribe when a subscription starts; unsubscribe on cancel — gated on the customer's marketing consent |
1 In Klaviyo, create a private API key (starts with pk_) and optionally copy a List ID. The SOP's Klaviyo section shows both screens.
2 Sublyra admin → Settings → Integrations → the Klaviyo card → paste the key (and List ID if you made one).
3 Click Send test event — the key is verified against Klaviyo and a real Sublyra Test Event is sent. A green banner means it worked; look for the event in Klaviyo under Metrics.
4 Tick Activate Klaviyo sync and save. Saved-but-not-activated keeps your settings but sends nothing.
The card shows a last-sync status after each real event, so a red banner there is the first place to look if flows stop firing.
3. Mailchimp
Sublyra keeps your Mailchimp audience (Mailchimp's word for a mailing list) in step with your subscribers — consent-gated, in both directions.
| What syncs | Detail |
|---|---|
| Audience member add | Customers who opted in to marketing are added to your audience when their first subscription contract arrives |
| Unsubscribe on cancel | Cancelling customers are marked unsubscribed automatically |
1 In Mailchimp, create an API key and copy your Audience ID. Copy the whole key including the data-center suffix at the end (-us6, -us21, …) — the app checks for it. The SOP's Mailchimp section shows both screens.
2 Sublyra admin → Settings → Integrations → the Mailchimp card → paste both values.
3 Click Test connection — the app verifies the key and that the audience exists.
4 Tick Activate Mailchimp sync and save. The badge flips to Connected.
4. Twilio SMS
Text messages ride on your own Twilio account — Sublyra writes the messages, Twilio delivers and bills them. Email notifications keep working with or without Twilio.
| Text | When it sends |
|---|---|
| Payment-failure reminders (dunning) | Day 3 and day 7 alongside the retry emails, with the card-update link |
| Order confirmations | When a subscription order is recorded |
1 In the Twilio console, find your Account SID (starts with AC), Auth Token, and buy an SMS-capable from number. The SOP's Twilio section walks through it.
2 Sublyra admin → Settings → SMS notifications → paste all three. The token is stored encrypted and never shown again.
3 Tick Enable SMS notifications — the master switch; off means no SMS is ever sent, whatever the toggles below say.
4 Under Which SMS go out, tick the texts you want, then Send a test message to your own phone to catch typos. Each test costs a little Twilio credit.
5. Shopify Flow
Sublyra emits trigger actions at subscription lifecycle points, so you can build custom automations in Shopify Flow — for example, email a discount code when a subscriber pauses. No keys or setup: if your store has Flow, the triggers are there.
6. Public API keys
The public API gives your own systems read access to your subscription data — a 3PL, a warehouse, an internal tool. API access is on the Growth plan and above (or the API & webhooks add-on).
1 Settings → Integrations → Public API keys → generate a key with a label per system.
2 Copy the plaintext key immediately — it is shown once. Only a SHA-256 hash is stored.
3 Revoke what you no longer use. Revoking is instant — requests with that key get a 401 from then on.
Full endpoint reference: developers.sublyra.com.
7. Integration directory
The directory on the Integrations page shows what's live and what's coming:
| Integration | Status | What it's for |
|---|---|---|
| Shopify Flow | Available | Custom automations at lifecycle points |
| Fast Bundle | Planned | Sell bundles as one subscription box |
| Translate & Adapt | Planned | Multilingual subscription widgets |
| Discounty | Planned | Volume and bulk discounts alongside subscription pricing |
| Givy | Planned | Gift products, gift cards and subscriptions |
Planned integrations are other Shopify apps that need partnership-level access. Want one prioritised? Use the request link on the Integrations page — we read every request.
8. FAQ
Do I need Klaviyo or Mailchimp for Sublyra's own emails?
No. Sublyra's transactional emails — subscription confirmations, failed-payment reminders, win-back offers — are sent by Sublyra itself. Klaviyo and Mailchimp are for your marketing automations on top.
Who pays for SMS?
Twilio bills you directly on your own account. Sublyra adds nothing to the message cost.
My Klaviyo card shows "Last sync failed". What now?
The private API key is wrong or was deleted in Klaviyo. Create a new pk_… key, paste it into the card, click Send test event, then save. More fixes in Troubleshooting.
Does a failed integration delay my webhooks?
No. Integration calls are fire-and-forget: errors are logged and surfaced on the card, but webhook processing — contract creation, order recording, retries — is never affected.
Related guides
- Billing & plans — what each plan includes and how add-ons work
- Developer docs — REST API, outbound webhooks, custom fields
- Troubleshooting — sync errors and test failures