Tenant-scoped credentials
Connections belong to one tenant. Provider credentials are validated before storage and are not returned by the public API.
Integrations
Connect CallMissed to the systems you actually use
Start with implemented Shopify, Meta WhatsApp, Twilio voice, webhooks, and REST API paths. Use a custom connection when a native connector is not available.
- Shopify connector with OAuth and validated Admin API access
- Meta WhatsApp Tech Provider onboarding and business messaging
- Signed Twilio inbound-voice webhooks
- Scoped REST APIs and outbound event webhooks
Connection paths
NativeShopify
ChannelMeta WhatsApp
TelephonyTwilio inbound voice
EventsSigned webhooks
CustomREST API + credentials
Available paths
Implemented connections, clearly labeled
Native connectors, channel onboarding, telephony, event delivery, and custom API paths are different integration types.
Native connector
Shopify
Connect a Shopify store through OAuth or validated Admin API credentials. CallMissed can register verified store webhooks when the required app secret is configured.
Ask about Shopify setup →Verified platform flow
Meta WhatsApp
Use the Meta Tech Provider onboarding flow to connect customer-owned WhatsApp Business assets, manage numbers and templates, and deploy messaging experiences.
Explore WhatsApp →Inbound voice
Twilio Voice
Connect a voice-capable Twilio number, verify tenant credentials, and route signed inbound call webhooks into the CallMissed voice pipeline.
Read Twilio setup →Event delivery
Outbound webhooks
Subscribe a tenant endpoint to supported CallMissed events. Native JSON deliveries include a signing secret and retry history.
Read webhook guide →Developer surface
REST APIs
Use scoped CallMissed API keys to connect application logic to inference, conversations, contacts, knowledge, bots, integrations, and other documented resources.
Explore Developer API →Manual connector
Custom authenticated tools
Store a bearer token, API key, or approved header set in the tenant integration vault and use it from configured HTTP tools.
Open developer hub →Integration foundations
What the implemented connection layer provides
The details below come from the current connector, webhook, WhatsApp, and Twilio implementations.
Signed inbound and outbound events
Meta, Shopify, and Twilio inbound handlers verify provider signatures. Configured outbound webhooks include CallMissed signing data.
Scoped automation access
Use service and resource permissions to keep integration keys limited to the APIs each workflow needs.
Shopify commerce context
The implemented Shopify connector validates store access and supports commerce data in configured agent and automation workflows.
Observable delivery history
Webhook delivery records track attempts and outcomes so failed deliveries can be inspected and replayed by an authorized operator.
A path for unlisted systems
Use REST APIs, outbound webhooks, or a manual authenticated connector when a dedicated native connector is not available.
Example workflow
Connect Shopify to a customer conversation
Connect the store
Authorize Shopify or validate store-domain and Admin API credentials.
Receive store events
Register supported Shopify webhooks when verification credentials are configured.
Use commerce context
Allow configured tools to query the store during an agent or automation workflow.
Keep channels separate
Use WhatsApp, voice, or another customer channel to deliver the resulting experience.
FAQ
Integration questions, answered
The current connector registry includes Shopify and a manual authenticated connector. CallMissed also has implemented Meta WhatsApp onboarding, Twilio inbound voice, outbound webhooks, and scoped REST APIs through dedicated product surfaces.
Connect a verified workflow
Start with an implemented path, or describe the system and actions your custom integration needs.