Available
An interface exists and a workspace-scoped connection is verified or live. No integration qualifies today; the tier is present so a passing integration can move here without renaming the system.
Integrations
Four honest status tiers, from connected to roadmap.
Wavy and the Automix platform distinguish an interface that exists in source from a connection that is verified and live. Every integration below is labelled across four tiers: Available (interface present and connected or verified), Configuration required (interface exists but deployment credentials and provider setup are required), Partial (an interface exists for part of the capability but a core piece is missing or incomplete), and Planned or Investigate (research-normalized direction with no promoted code). No integration is presented as connected by default.
4 status tiersAvailable, Configuration required, Partial, and Planned or Investigate — matching the PRD's required four-tier labelling system.
Interface vs. connectedA source path that compiles is not the same as a verified, credentialled, workspace-scoped connection. We keep the two separate.
No self-service vault yetMost provider secrets are server configuration today, not a per-workspace credential vault, so none is presented as connected by default.
Available
Interface present and connected or verified.
An integration qualifies for this tier only when its interface exists in source and a workspace-scoped connection is verified or live. At this stage no integration has passed its feature-specific release gate, so this tier is intentionally empty. Wavy is the only Available product, but product availability does not imply that any provider connection is connected or verified for a workspace.
- No integration is currently Available. The backend contains interface paths for messaging, AI, payments, QR pairing, Airtable sync, subscriber webhooks, bot connectors, and Google sign-in, but each requires deployment credentials, provider setup, and release-gate validation before it can be treated as connected. When an integration passes its gate, it will move into this tier and be labelled here.
Configuration required
Interface exists in source — deployment configuration is required to connect.
These interfaces are present in backend source and degrade gracefully when unconfigured, but current credentials are supplied through the server environment. A self-service per-workspace credential vault and connection flow are not implemented, so none of these is presented as connected. Enabling one requires deployment credentials, provider setup, webhook verification where applicable, and a workspace channel or configuration record.
- WhatsApp Business Cloud API (Meta) — The backend contains a Meta messaging client (send text, send template, list and create templates) and a webhook ingestion path with signature verification. The client exposes a
configuredcheck and returns a dry-run response when credentials are absent, so no real message is sent while unconfigured. Live use requires server credentials, a registered phone-number ID, WABA configuration, webhook verification, and a workspace channel record. Interface exists; not connected or verified by default. - Optional WhatsApp QR bridge — QR start, status, and send endpoints call a separately deployed multi-device bridge. The bridge URL and optional bearer token are server configuration; the service raises a clear unavailable error when the bridge is absent. Interface exists; not connected by default.
- AI replies, summaries, and translation (LLM Copilot) — Copilot paths call an OpenAI-compatible endpoint when a server-side LLM key is configured. The service exposes an
enabledcheck and returns an explicit not-configured or unavailable response without it. Interface exists; not connected or verified by default. - Payment links (UPI / Razorpay / PhonePe / Stripe) — Provider classes exist for UPI intent links, Razorpay, PhonePe, and Stripe. Each exposes a
configuredcheck and refuses to create a link when its keys are absent. No gateway is connected by default, and public purchase remains closed. Interface exists; not connected or verified by default. - Google sign-in (OAuth) — The auth-service verifies Google ID tokens against a configured client ID. The interface exists and the flow is functional for authentication when a client ID is set; without it, the service reports that Google sign-in is not configured. This is an authentication interface, not a business-data integration, and it is not presented as a connected workspace provider.
- Contact sync (Airtable) — Inbound contact and auth-user sync paths can write to one server-configured Airtable base. The path returns immediately when no API key is set. This is not a per-workspace OAuth connection and it does not claim full conversation sync. Interface exists; not connected by default.
Partial
Interface exists for part of the capability — a core piece is missing or incomplete.
A partial integration has real source for a slice of the capability, but a release-blocking gap remains: an incomplete retry path, a stub runtime, missing tenant isolation, or a verification gap. It is neither a clean configuration-required path nor a planned direction.
- Subscriber webhook delivery — Webhook subscription and delivery models exist, subscriptions are workspace-scoped, and a per-subscription signing secret is generated with a reveal-once pattern. The interface exists. However, the delivery retry and dead-letter path is incomplete, and delivery deduplication for retried events is missing. Outbound signed delivery works in part; the retry and cancellation story is not release-ready, so this is partial, not available.
- Bot connector (bring-your-own agent) — A pluggable bot engine framework exists with a builtin FAQ engine, a webhook engine, and an Automix agent engine. The webhook engine calls an external endpoint and falls back to an operator on failure; the builtin engine is zero-config. However, the Automix agent engine is a stub that proxies to an optional runtime, and the outbound webhook carries no signature, so external processing disclosure and signing are incomplete. Interface exists for part of the capability; partial.
- Airtable contact sync (tenant isolation) — Listed under Configuration required for its interface, and called out here as partial because all workspaces sync to a single server-configured base with no per-workspace mapping. The sync interface exists, but multi-tenant isolation is a release-blocking gap, so the capability is partial rather than a complete configuration-required path.
Planned or Investigate
On the roadmap — no code promoted to a workspace, preview, or release gate.
These integrations are research-normalized directions. No backend adapter, OAuth flow, or workspace code has been promoted for any of them. They are listed to show direction, not current capability, and each carries an honest reason it is not yet built.
- Instagram messaging — Planned additional messaging channel, owned by Socie. Socie's repository is pending, so no Meta Instagram Messaging API adapter or webhook exists. Blocked on the Socie repository.
- RCS messaging — Planned additional messaging channel. No RCS Business Messaging API contract, provider, or code path exists. Investigate only; a competitor-normalized capability is not an Automix implementation claim.
- CRM connector (HubSpot / Salesforce / custom) — Investigate. Research identifies sales CRM sync as a direction for Jeet, but no per-workspace CRM OAuth, field mapping, or consent and suppression framework exists. The Airtable path is not a CRM connector.
- Shopify storefront sync — Planned for Kuber, the website and eCommerce specialist. No Shopify Admin API connection or OAuth flow exists. Export-based analysis is the intended first step; Shopify writes remain disabled without merchant scopes and explicit approval.
- Calendar and scheduling providers (Google Calendar / Microsoft Graph) — Planned for Mitra, the virtual assistant. No OAuth flow, least-privilege scope, or calendar write review gate exists. Investigate.
- Email marketing provider (Gmail / Microsoft Graph) — Planned for Patri, the email marketing specialist. No OAuth, scope verification, consent and suppression framework, or email compliance gate exists. Investigate.
- Google Analytics (read-only) — Investigate for Ank and Khoji. No OAuth, read-only scope enforcement, or privacy review exists. Read-only direction only.
- ATS connector (recruitment) — Investigate for Bharti. No ATS provider has been selected and no fairness or privacy review has been completed. No protected-trait inference is permitted.
- Click-to-WhatsApp ads and Conversions API (Meta) — Investigate. No CTWA or Conversions API code exists. Regional eligibility, consent for remarketing, and event deduplication are unresolved evidence gaps.
- Google Sheets sync — Planned. No OAuth flow or sync code is available in any workspace today. When it reaches a configuration-required stage, its status will change here.
- WhatsApp calling and voice — Blocked. No calling code exists. Calling eligibility, regional support, retention, recording, and provider evidence are not verified. Synthetic voice is excluded until legal and privacy approval.
How integrations are labelled
Four honest status tiers.
The four-tier system separates an interface that exists from a connection that is verified, and separates a partial path from a roadmap direction.
Configuration required
A source interface exists and degrades gracefully when unconfigured, but deployment credentials, provider setup, webhook verification, and a workspace record are required to connect. This does not mean the connection is enabled for every workspace.
Partial
A source interface exists for part of the capability, but a release-blocking gap remains — an incomplete retry or dead-letter path, a stub runtime, missing tenant isolation, or a verification gap. Neither clean configuration-required nor roadmap.
Planned or Investigate
Research-normalized direction with no promoted code, OAuth flow, or workspace surface. Listed to show direction, not current capability. Each carries an honest reason it is not yet built.
Questions
Understanding integration status.
What is the difference between Available and Configuration required?
Available means an interface exists and a workspace-scoped connection is verified or live. Configuration required means the interface exists in source but deployment credentials and provider setup are needed to connect it. No integration is Available today because none has passed its feature-specific release gate.
Why is a path labelled Partial instead of Configuration required?
A partial integration has real source for a slice of the capability, but a release-blocking gap remains — for example, webhook delivery retries and dead-letter handling are incomplete, the Automix agent engine is a stub, or Airtable sync lacks per-workspace tenant isolation. It is neither a clean configuration-required path nor a roadmap direction.
What does Planned or Investigate mean?
The capability is a research-normalized direction. No backend adapter, OAuth flow, or workspace code has been promoted for it. It is listed to show direction, not current capability, and each entry carries an honest reason it is not yet built.
Can each workspace connect its own provider account?
Not through a complete self-service credential flow today. Channel records are workspace-scoped, while several provider secrets remain server configuration. A per-workspace credential vault is not implemented. Do not paste provider secrets into chat or ordinary form fields.
Is Google sign-in an available integration?
The Google sign-in interface exists in the auth-service and is functional for authentication when a client ID is configured. It is labelled Configuration required because it is an authentication interface, not a business-data integration, and it is not presented as a connected workspace provider.
What about integrations for specialists other than Wavy?
Wavy is the first product marked Available. Other specialists remain Coming soon or repository pending; their preview pages do not establish active provider integrations. Instagram is blocked on the Socie repository, and CRM, Shopify, calendar, email, analytics, and ATS connectors are investigate-stage directions for their respective owners.
Where can I read technical documentation?
When the backend is deployed, it exposes generated OpenAPI documentation at api.automixai.in/docs. The full documentation site remains a placeholder until maintained product guides are published.
Explore Wavy with provider states visible.
The public experience distinguishes available, configuration-required, partial, and planned paths. Live external connections still require server and provider setup, and no integration is presented as connected by default.