Connect WhatsApp, email, and SMS to your in-house CRM
One API and one set of webhooks for every channel. Your CRM stays the source of truth. CampaignHQ sends the messages, runs the journeys, and posts every delivery, open, and reply back to your system.
awsPartnercurl -X POST https://api.campaignhq.co/api/v1/whatsapp/send \
-H "Authorization: Bearer $CAMPAIGNHQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"message_type": "template",
"idempotency_key": "lead-1042-site-visit",
"template": {
"template_id": "TEMPLATE_ID",
"language": "en",
"variables": {
"body": [
{ "position": 1, "value": "Asha" },
{ "position": 2, "value": "Saturday, 11 am" }
]
}
},
"to": [{ "phone_number": "+919800000000", "name": "Asha" }]
}'Why connect your CRM
Your CRM knows who to message. CampaignHQ gets it delivered.
Most in-house CRMs are great at tracking leads and poor at talking to them. Connecting CampaignHQ turns every CRM update into a message the customer actually reads.
Reach a lead while they are still interested
The moment a lead, booking, or payment lands in your CRM, the customer gets a WhatsApp message. No one waits for a salesperson to copy a number into a phone.
Developers send events, marketing runs the journeys
Your engineers integrate once. After that, marketing builds segments, journeys, and templates in CampaignHQ without filing a ticket for every new message.
Skip building WhatsApp yourself
Meta onboarding, template submission, and quality alerts are already built. Your team calls one endpoint instead of maintaining its own Meta integration.
One vendor instead of three
WhatsApp, email, and SMS share one API, one contact database, and one set of reports, instead of a WhatsApp provider, an email service, and an SMS gateway stitched together.
Your CRM keeps the full history
Delivery, read, open, click, and reply events flow back by webhook, so sales sees what each lead received and how they responded, right on the CRM record.
Replies reach a person
When a customer writes back on WhatsApp, your team answers in a shared inbox with assignments and mobile apps, not from someone's personal phone.
Every channel
One API for WhatsApp, email, and SMS
Same API key, same contacts, same webhooks. Your CRM picks the channel per message, or hands the lead to a journey that does.
WhatsApp
Approved templates with header, body, and button variables, plus text and interactive messages inside the 24-hour window.
POST /whatsapp/send
Email
Email templates with merge data from the CRM record, attachments, and cc or bcc. Send on managed credits or your own AWS SES.
POST /transactional_emails
SMS
SMS templates with variables for alerts, reminders, and updates, sent to the phone number on the record.
POST /sms/send
How it works
Four calls between your CRM and CampaignHQ
A REST API with an API key, plus webhooks for everything that happens after a message is sent.
- Step 1
Sync contacts
Create or update a contact from your CRM record: name, email, phone, WhatsApp number, company, and your own custom fields.
POST /lists/:list_id/contacts/create_or_update
- Step 2
Send CRM events
Record what happened in your CRM, such as a new lead, a site visit, or a payment due. Events feed segments and start journeys.
POST /tracked_events
- Step 3
Send messages
Send a WhatsApp, email, or SMS template with values from the record, straight from your CRM.
POST /whatsapp/send · /transactional_emails · /sms/send
- Step 4
Get events back
Webhooks post delivery, read, open, click, and reply events to your CRM, so every lead record shows what was sent and what came back.
Webhook subscriptions
Webhooks
Every delivery and reply, back in your CRM
Subscribe a URL per channel and pick the events you need. Each delivery attempt is logged, and your developers can list them through the API.
- message.sent
- message.delivered
- message.read
- message.failed
- message.replied
- message.sent
- message.delivered
- message.opened
- message.clicked
- message.replied
- message.bounced
- message.complained
- message.unsubscribed
- message.failed
SMS
- message.sent
- message.delivered
- message.failed
What teams build
Your CRM decides, CampaignHQ delivers
Lead follow-up
A new lead lands in your CRM and gets a WhatsApp welcome in seconds, with an email and SMS follow-up if there is no reply.
Bookings and reminders
Site visits, stays, classes, or demos booked in your system send confirmations and reminders on WhatsApp, with SMS or email as backup.
Payment and order updates
Fee, EMI, invoice, and order status changes in your back office go out as a WhatsApp utility template, an email with the invoice attached, or an SMS.
Replies back to the owner
WhatsApp and email replies arrive as webhooks, so your CRM can update the lead and alert the right salesperson. The team can also answer WhatsApp in the CampaignHQ shared inbox.
Security and plans
Built for teams with their own systems
The API and webhooks are part of Custom plans, and available on Growth on request. We scope the integration with your developers on a demo call.
API keys you control
Create keys in Settings, then Integrations, then API keys. Revoke a key at any time.
Safe retries
Send requests accept an idempotency key, so a retry from your CRM never sends the same message twice.
SOC 2 Type II, Meta Business Partner, AWS Partner
Official WhatsApp Business API access, with security reviewed by an independent auditor.
Support
Customers rate our support
CampaignHQ is rated 4.6/5 from 16 reviews on G2, and 9 of them mention responsive support.
Outstanding support
“Their team is always responsive and ready to assist, making email marketing and automation smooth and efficient.”
Shantul A.
Founder, review on G2
Authentic platform, excellent service
“Their customer service and authentic platform are very efficient and serve with the best interest of their clients.”
Minmayee M.
Associate Consultant, review on G2
CRM integration questions
Common questions about connecting WhatsApp, email, and SMS to an in-house CRM.
Still have questions?
Yes. Your CRM calls one CampaignHQ REST API to sync contacts, record events, and send WhatsApp, email, and SMS messages. CampaignHQ sends delivery, read, open, click, and reply events back to your CRM through webhooks.
The API and webhooks are part of Custom plans, and available on Growth on request. Book a demo and we will scope the integration with your team.
No. CampaignHQ is an official Meta Business Partner. You connect your WhatsApp Business number to CampaignHQ during onboarding and send through it with your API key.
Yes. Send an approved template and fill its header, body, and button variables with values from your CRM record, such as a name, an order number, or a payment link.
Yes. Send an email template with merge data from the CRM record, attachments, and cc or bcc, or send an SMS template with variables. Email can go out on CampaignHQ-managed credits or your own AWS SES account.
Create a webhook subscription. CampaignHQ posts WhatsApp events (sent, delivered, read, failed, replied), email events (sent, delivered, opened, clicked, replied, bounced, complained, unsubscribed, failed), and SMS events (sent, delivered, failed) to your URL, and you can list each delivery attempt through the API.
CampaignHQ does not have a native app for these CRMs. Teams connect them through the same API and webhooks, usually with a small middleware or an automation tool their team already runs.
Requests use an API key you create and revoke in CampaignHQ. CampaignHQ is SOC 2 Type II compliant and an AWS Partner. Send requests accept an idempotency key, so a retry from your CRM never sends the same message twice.
Make your next customer interaction count.
Connect your channels, automate your follow-ups and build journeys that keep customers coming back.
15-minute walkthrough · 7-day free trial · no credit card required
Manage your WhatsApp team inbox on mobile
