Tenant-scoped credentials
Connections belong to one tenant. Provider credentials are validated before storage and are not returned by the public API.
Integrations
Start with implemented Shopify, Meta WhatsApp, Meta Facebook & Instagram, Twilio voice, webhooks, and REST API paths. Use a custom connection when a native connector is not available.
Available paths
Native connectors, channel onboarding, telephony, event delivery, and custom API paths are different integration types.
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 setupUse the Meta Tech Provider onboarding flow to connect customer-owned WhatsApp Business assets, manage numbers and templates, and deploy messaging experiences.
Explore WhatsAppConnect a Facebook Page and Instagram business account through the same Meta platform flow as WhatsApp. Read and reply to DMs and comments, and publish AI-drafted posts, from one workspace.
Ask about Meta setupConnect a voice-capable Twilio number, verify tenant credentials, and route signed inbound call webhooks into the CallMissed voice pipeline.
Read Twilio setupSubscribe a tenant endpoint to supported CallMissed events. Native JSON deliveries include a signing secret and retry history.
Read webhook guideUse scoped CallMissed API keys to connect application logic to inference, conversations, contacts, knowledge, bots, integrations, and other documented resources.
Explore Developer APIStore a bearer token, API key, or approved header set in the tenant integration vault and use it from configured HTTP tools.
Open developer hubIntegration foundations
The details below come from the current connector, webhook, WhatsApp, and Twilio implementations.
Connections belong to one tenant. Provider credentials are validated before storage and are not returned by the public API.
Meta, Shopify, and Twilio inbound handlers verify provider signatures. Configured outbound webhooks include CallMissed signing data.
Use service and resource permissions to keep integration keys limited to the APIs each workflow needs.
The implemented Shopify connector validates store access and supports commerce data in configured agent and automation workflows.
Webhook delivery records track attempts and outcomes so failed deliveries can be inspected and replayed by an authorized operator.
Use REST APIs, outbound webhooks, or a manual authenticated connector when a dedicated native connector is not available.
Example workflow
Authorize Shopify or validate store-domain and Admin API credentials.
Register supported Shopify webhooks when verification credentials are configured.
Allow configured tools to query the store during an agent or automation workflow.
Use WhatsApp, voice, or another customer channel to deliver the resulting experience.
FAQ
The current connector registry includes Shopify and a manual authenticated connector. CallMissed also has implemented Meta WhatsApp onboarding, Meta Facebook Page and Instagram messaging and post publishing, Twilio inbound voice, outbound webhooks, and scoped REST APIs through dedicated product surfaces.
Yes. Use outbound webhooks to receive supported CallMissed events, the REST APIs to read or change documented resources, or a manual connector for credentials used by an approved HTTP tool. Contact sales if the workflow needs a dedicated connector.
CallMissed supports Shopify OAuth and validated Admin API credentials. The connector verifies the store, stores the credential for the tenant, and can register supported webhooks when the app secret needed for verification is available.
CallMissed uses Meta's Tech Provider onboarding flow for WhatsApp Business assets. The WhatsApp product page and documentation describe onboarding, numbers, templates, messaging, bots, and calling-related workflows.
Yes. Connect a Facebook Page and an Instagram business account through the same Meta platform flow used for WhatsApp, and read, reply to, and publish across all three from one workspace.
The documented Twilio integration is for inbound voice calls. A public API for initiating outbound Twilio calls is not currently documented as available.
Provider webhooks use their documented signature checks. CallMissed outbound JSON webhooks include an HMAC signature, validate destination URLs, and record delivery attempts for inspection and replay.
Start with an implemented path, or describe the system and actions your custom integration needs.