Message orchestration
Design routing and retries without custom backend code
WhatsApp Connector
Build in-app, customer-facing messaging and notification flows using the WhatsApp Business Platform. Embed send and receive capabilities, media handling and webhook-driven events into your SaaS product for richer customer engagement.
Customer engagement
Trigger templates for marketing and transactional journeys
Operational scale
Centralize credentials, monitoring and error handling
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
WhatsApp Connector overview
The WhatsApp connector lets SaaS teams integrate Meta’s WhatsApp Business Platform into multi-tenant products. Use Cyclr to map data, orchestrate message workflows, surface incoming events and expose governed MCP tools to customers. Ideal for notifications, two-way support and marketing conversations that require templates and phone number registration.
PRODUCT USE CASES
Top Use Cases for WhatsApp Integrations
Use Cyclr’s embedded integration tools to deliver two-way support, automated notifications, marketing campaigns and transactional messaging via WhatsApp. Build, test and deploy integrations without shipping custom point-to-point code for every customer.
In-app two-way support
Route incoming WhatsApp messages to support workflows, keep message history and trigger agent notifications.
Transactional alerts and reminders
Send payment confirmations, delivery updates and appointment reminders via WhatsApp templates.
Template-based campaigns
Run approved template campaigns and orchestrate follow-ups based on webhook events and quality signals.
ORCHESTRATION
How WhatsApp works with Cyclr
Cyclr sits between your SaaS product and WhatsApp to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
WhatsApp
WhatsApp processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore WhatsApp methods you can orchestrate through Cyclr.
Templates1
List Templates
ActionList all templates.
Business2
List Business Phone Numbers
ActionList all business phone numbers.
Get Business
ActionGet a business.
Webhooks3
Stop Promotions Message
WebhookReceives opt out messages.
Failed Message
WebhookReceives failed messages.
General Message
WebhookReceives messages that are not failed or stop promotion. You may have to map your own request fields as these change on message type.
Messages2
Send Canned Text Message (Template)
ActionSend a canned text message with no variable parameters or header.
Send Text Message
ActionSend a text message.
Internal1
Test - Do not use.
WebhookTemplate Messages1
Send Text Message (Template)
ActionSend a templated text message.
TECHNICAL DETAILS
WhatsApp integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing WhatsApp integrations in Cyclr.
API and authentication
- API host
https://graph.facebook.com- Authentication
- OAuth / Graph API access token
- Credentials
Access token, Phone Number ID, WhatsApp Business Account ID, App secret or system user token
- Method categories
Send messages, receive webhooks, manage media, templates, phone numbers and history
Pagination and rate limits
Pagination
Method-specific behavior should be confirmed before implementation.
Rate limits
Meta enforces throughput, pair-rate and tiered conversation limits; exceed limits returns 429 errors and specific rate-limit error codes.
IMPLEMENTATION
Authentication at a glance
Uses Meta Graph API access tokens. Applications typically use temporary or system-user tokens with relevant WhatsApp permissions and business verification.
- Authentication method
- OAuth / Graph API access token
- Credential required
Access token, Phone Number ID, WhatsApp Business Account ID, App secret or system user token
Before you begin:
View setup guideRequires phone number registration and Meta business verification for production use.
COMMON QUESTIONS
Frequently asked questions
Yes. Production use requires a registered WhatsApp Business Account and a phone number provisioned for the WhatsApp Business Platform.
The connector uses Meta Graph API access tokens. You can use temporary tokens for development and system user or app tokens for production with required permissions.
Yes. WhatsApp supports webhooks for message and status events; Cyclr workflows can consume and act on those events in real time.
Meta enforces throughput and conversation-tier limits. Exceeding those limits returns 429 or platform-specific error codes. Implement throttling and backoff in workflows.
KEEP EXPLORING
Related resources and connectors
Product
CRM Integrations you should be using
Read more →ProductMCP PaaS
Read more →Related connectordotdigital
Related Marketing connector for customer-facing integration workflows.
Related connectorHighLevel
Related Sms connector for customer-facing integration workflows.
Related connectorLinkedIn Marketing
Related Marketing connector for customer-facing integration workflows.