WhatsApp CRM integration with QuackAPI

QuackAPI has no CRM-specific app. It is a REST API plus webhooks, and every major CRM can call a URL when a record changes. That is enough to send WhatsApp messages from a CRM and to push replies back into it.

How it fits together

  • CRM to WhatsApp: a workflow, flow or automation in the CRM calls POST https://quackapi.com/v1/messages/chat when a deal, lead or ticket changes.
  • WhatsApp to CRM: set your device's webhook URL. QuackAPI posts message.received to it, and your endpoint or automation tool writes the reply to the contact in the CRM.
  • Match people by phone number. Store numbers in international format with the country code, digits only, so the CRM record and the WhatsApp sender line up.

The one request every CRM sends

Whatever the CRM, the call is the same: a POST with the x-api-key header and a small JSON body.

Body
{
  "deviceId": 1,
  "to": "923001234567",
  "body": "Hi Sara, thanks for your interest. Is 3pm tomorrow good for a call?"
}

If the CRM cannot set a custom header

Some webhook actions only let you set the URL and body. In that case put n8n, Make or Zapier in the middle: the CRM calls the tool, and the tool makes the HTTP request with the x-api-key header. Our guides for each are linked below. This is also the easiest route if you prefer no code.

HubSpot

  • Create a deal or contact workflow with a trigger such as deal stage changed.
  • Use the Send a webhook action (available on some paid HubSpot tiers, so check your plan) or send it through n8n, Make or Zapier.
  • Map the contact's phone property and a message into the body. Keep the message tied to what the contact asked for.

Zoho CRM

  • Create a workflow rule on Leads, Contacts or Deals and add a webhook or a custom function as the action.
  • In a custom function, Deluge's invokeurl task can make the POST with the header and the JSON body.
  • Use the Mobile field after normalising it to digits with the country code.

Salesforce

  • Record-triggered Flow can make an HTTP callout, using a Named Credential or External Credential to hold the API key.
  • Or call the API from Apex in an asynchronous (future or queueable) method, because callouts are not allowed from a synchronous trigger.
  • Add the endpoint to Remote Site Settings if your setup needs it.

Pipedrive

  • Pipedrive webhooks and automations send events to a URL you choose but do not let you set arbitrary headers, so point them at n8n, Make or Zapier.
  • From there, call the QuackAPI endpoint with the x-api-key header using the person's phone field.
  • The same tool can also add a note to the deal when a reply arrives.

Receive replies and log them

Set the device webhook to your own endpoint. It gets message.received with the sender number and text. Look the contact up by phone, then write the message to the CRM with its API (a note, activity or timeline entry). The example below receives the webhook and leaves the CRM call for you to fill in with your CRM's own API.

Node.js (Express)
import express from 'express';
const app = express();
app.use(express.json());

async function sendWhatsApp(to, body) {
  const res = await fetch('https://quackapi.com/v1/messages/chat', {
    method: 'POST',
    headers: { 'x-api-key': process.env.QUACKAPI_KEY, 'Content-Type': 'application/json' },
    body: JSON.stringify({ deviceId: 1, to, body }),
  });
  return res.json();
}

app.post('/whatsapp-webhook', async (req, res) => {
  res.sendStatus(200); // answer fast, work after
  const { event, from, content, messageId } = req.body;
  if (event !== 'message.received') return;
  // 1. Find the contact by phone: `from` is digits with country code.
  // 2. Add `content` as a note or activity with your CRM's API.
  // 3. Optional: auto-reply.
  await sendWhatsApp(from, 'Thanks, we got your message and will reply soon.');
});

app.listen(3000);

ERP systems

ERPs such as Odoo, ERPNext, SAP Business One, Microsoft Dynamics and NetSuite follow the same pattern. Each can call a URL from a workflow, automated action or script, and each exposes an API you can call from the webhook receiver above. Typical uses: invoice created, payment received, delivery dispatched, low-stock alert for a supplier. Pick the event in the ERP, make the HTTP call, and keep the message short and useful.

Keep in mind

QuackAPI connects through WhatsApp's linked-devices feature. It is not Meta's official WhatsApp Business Cloud API, so WhatsApp's own rules and enforcement apply to the number you connect. Read the acceptable use page before sending at volume.

Only message contacts who gave you their number for that purpose and respect requests to stop. CRM tools have their own pricing, limits and terms, which are theirs and not ours. Pause between bulk sends, and test with your own number first.

FAQ

Is there a native QuackAPI app in the HubSpot, Zoho, Salesforce or Pipedrive marketplace?

No. QuackAPI works through each CRM's standard webhook, HTTP and workflow features, so there is nothing to install from a marketplace.

Can it send template messages like the official WhatsApp Business API?

No. QuackAPI sends normal messages from the number you link, with no template approval. It is not Meta's official Cloud API, so read the risk policy before you build on it.

How are incoming replies matched to CRM records?

The webhook gives you the sender's phone number in international format. Look up the contact by that number in your CRM, then add the reply as a note or activity.

Related

Last reviewed 2026-11-09. QuackAPI is an unofficial linked-device service. Acceptable use