WhatsApp Integration
Connect WhatsApp messaging to Firetip and use the Firetip dispatch infrastructure to manage messaging, templates, recipients, delivery events and automation.
Overview
Firetip's WhatsApp integration provides a structured messaging layer for businesses that need WhatsApp communication alongside their existing email, SMS and API infrastructure.
WhatsApp Dispatch
Send WhatsApp messages through your configured WhatsApp business infrastructure.
Unified Audience
Use Firetip audiences and contact data across multiple communication channels.
Automation
Connect WhatsApp events to Firetip campaigns, workflows and webhook-driven processes.
Requirements
Before connecting WhatsApp to Firetip, make sure the required WhatsApp Business infrastructure has been provisioned and that you have access to the relevant credentials.
Important: WhatsApp messaging is subject to Meta's WhatsApp Business policies, template requirements, conversation rules and recipient opt-in requirements.
- Active WhatsApp Business infrastructure.
- Verified business identity where required.
- Configured WhatsApp sender / phone number.
- Required API credentials.
- Approved message templates where applicable.
- A Firetip account with integration access.
Setup
The integration is configured from the Firetip integrations area. The exact fields displayed may vary depending on the WhatsApp infrastructure connected to your account.
Open Integrations
Sign in to Firetip and open the Integrations section of the dashboard.
Select WhatsApp
Select WhatsApp from the available communication integrations.
Enter Credentials
Enter the credentials supplied by your WhatsApp Business infrastructure and save the integration.
Configure Sender
Select the WhatsApp business sender and configure the identity that Firetip should use for dispatch.
Configure Webhooks
Configure inbound and delivery-event webhooks if your integration requires event synchronisation with Firetip.
Run a Test
Send a controlled test message to confirm credentials, sender configuration and delivery events are operating correctly.
Configuration
Firetip stores the integration configuration required to communicate with the connected WhatsApp service. Credentials should be treated as sensitive system configuration.
| Configuration | Purpose | Status |
|---|---|---|
Provider |
Identifies the WhatsApp messaging provider. | Required |
Business Account |
Associates the integration with the WhatsApp business account. | Required |
Sender |
Identifies the WhatsApp number used for dispatch. | Required |
Access Token |
Authenticates API requests to the connected service. | Required |
Webhook |
Receives delivery and messaging events. | Optional |
Message Types
WhatsApp messaging can be used for different types of customer communication. Firetip should distinguish between transactional communication, approved template messages and conversational messaging.
Template Messages
Pre-approved WhatsApp message templates used when required by WhatsApp conversation rules.
Conversation
Customer conversations and responses handled through the connected messaging infrastructure.
Notifications
Operational and transactional notifications delivered to opted-in recipients.
API Dispatch
Applications can trigger WhatsApp dispatch through the Firetip API once the integration has been configured.
{
"channel": "whatsapp",
"recipient": "+447700000000",
"template": "example_template",
"variables": {
"name": "Customer"
}
}
API endpoint paths, authentication headers and provider-specific parameters should be taken from the current Firetip API documentation associated with your account.
Audience & Recipients
WhatsApp can operate as another communication channel within the Firetip audience layer. Contacts should only receive WhatsApp communication where the required consent and messaging permissions exist.
- Maintain a valid recipient phone number.
- Store the appropriate country code.
- Maintain consent / opt-in state where applicable.
- Respect opt-out and suppression states.
- Do not send unsolicited communications.
Webhooks & Events
Webhooks allow WhatsApp events to be returned to Firetip or your application so that delivery, engagement and workflow state can be updated.
| Event | Description |
|---|---|
sent |
Message accepted for dispatch. |
delivered |
Message delivery confirmed. |
read |
Message read event received where available. |
failed |
Message could not be delivered. |
inbound |
Inbound recipient message received. |
Automation
WhatsApp can form part of a wider Firetip automation sequence. For example, a workflow can use an audience event to trigger email, WhatsApp or SMS communication depending on the configured journey.
Audience Event
A contact enters or changes state within the Firetip audience layer.
Automation Rule
Firetip evaluates the configured workflow conditions.
WhatsApp Dispatch
The configured WhatsApp message is submitted for dispatch.
Event Feedback
Delivery or inbound events can update the workflow state through the configured webhook layer.
Security
WhatsApp credentials should be treated as production secrets. Do not place access tokens directly into frontend JavaScript, public HTML or client-side applications.
Recommended: Keep provider credentials server-side and allow Firetip's backend/API layer to perform authenticated dispatch operations.
Troubleshooting
Messages are not sending
Check that the WhatsApp integration is active, the configured sender is valid and the required credentials have not expired or been revoked.
Template rejected
Confirm that the template exists, is approved and that the variables supplied by the Firetip campaign match the template definition.
Recipient cannot be reached
Confirm the phone number is correctly formatted with its international country code and that the recipient is eligible to receive the message.
Webhook events are missing
Verify the webhook URL, authentication configuration and provider-side webhook subscription.
Next Steps
Once WhatsApp is connected, continue with the rest of the Firetip communication stack.