Integrations
List Integration Capabilities
Describe what each integration provider syncs, emits, and supports
GET
List Integration Capabilities
Describe what Sequenzy’s integration providers do, whether or not they are connected. Use this to decide what to connect, to compare providers, or to check that an event a sequence needs actually exists for a given provider.
Coverage differs sharply between providers. Only Shopify has storefront browse tracking, and only Stripe and Chargebee cover the full trial lifecycle - so check here rather than assuming a provider emits an event.
Request
string
Return only this provider, such as
stripe or shopify. Returns 404 for an
unknown provider.string
Filter by category:
payments, ecommerce, auth, analytics, ads,
affiliate, cms, or developer.Response fields
string
available, beta, or coming_soon. A coming_soon provider appears in the
dashboard picker but has no webhook handler yet, so it emits nothing.string
How the provider is connected:
oauth, api_key, app_install, plugin, or
webhook. OAuth and app installs always need a person in the dashboard.string[]
What the integration keeps in sync, such as
customers, orders, or
products. Empty when the provider only pushes events as they happen.object[]
Every event the provider can produce. Each entry has
event (the name a
sequence triggers on) and when (the real-world moment that produces it). An
empty array means the provider never triggers automations.object[]
Subscriber attributes the provider writes, each with a
key and
description. Use these in segment filters.string[]
Actions supported on a connected integration:
enable_sync, disable_sync,
sync_now, or sync_products.string[]
Caveats worth knowing before building on the provider, such as which events it
does not emit.
Responses
List Integration Capabilities