Capability matrix
Connected does not mean unlimited control.
Every integration starts unavailable, becomes observable after a connection test, and becomes recoverable only when the provider, plan, project policy, and exact action all permit it.
| Platform | Liulum can observe | Eligible recovery | Never implied |
|---|---|---|---|
| Shopify | Storefront, approved journeys, webhooks, connected apps, downstream outcomes | Eligible connected customer-owned apps and workflows | No control over Shopify-managed checkout, payments, or infrastructure |
| WooCommerce | Store, WordPress, hosting, journeys, webhooks, workflows | Pre-approved hosting and application playbooks on eligible projects | No unbacked database, payment, secret, or WordPress-core changes |
| Headless commerce and SaaS | Frontend, APIs, deployments, workers, queues, webhooks, outcomes | Eligible rollback, cache, restart, or idempotent replay actions | No arbitrary code, secrets, payments, or destructive data actions |
| n8n | Signed callbacks, schedules, executions, downstream outcomes | Eligible idempotent retry or resume when the instance exposes it | No repair without provider control, policy, and independent verification |
| Make | Scenario callbacks, schedules, webhook receipts, outcomes | Only provider-supported, customer-approved actions | No implied control over Make infrastructure or unsupported scenario actions |
| Zapier | Configured webhook receipt and downstream outcome | Observation-first; escalation when no safe control exists | No promise of autonomous Zap repair or replay |
Test one connection in the Guided Proof.
No credentials are collected in the public request form.