WhatsApp automation API: Connect WavesFlo to your CRM, or build on the API.

Get a key, call the API, then subscribe to events. WavesFlo issues API keys per workspace, scoped to it and revocable without affecting anyone else. The API is REST over HTTPS, with JSON both ways and an Idempotency-Key header accepted on sends and other create actions. For webhooks, point a URL at the events you want and verify the signature on each delivery. The full API is included in the plan.

Yes. Beside messaging, the WavesFlo API has 28 endpoints for conversations, tickets, calls, pipelines, opportunities, companies and tasks, under 7 scopes of their own. An integration can list and read conversations with their messages and notes, assign them, mark them done and add internal notes; open, update and comment on tickets; read the call register and its totals; and create and edit opportunities, companies and tasks, including moving an opportunity to won or lost. A key acts for the workspace rather than a person, so it sees every record in it, and history records its changes as made through the API. Deletes, call recordings and exports are not part of the API.

Yes, if the request carries an Idempotency-Key header. Sends and other create actions accept an Idempotency-Key: a retry with the same key within 24 hours returns the first result instead of repeating the action. Reusing a key with a different body is refused, so a timed-out send is safe to retry with the same key.

WavesFlo publishes 49 signed webhook events, in categories that each destination URL subscribes to separately: messaging (message.received, message.sent, message.ack, message.reaction, message.media_stored); engagement (poll.vote); calls (call.received, call.ended, call.placed); groups (group.participant_joined, group.participant_left, group.settings_changed, group.membership_request, group.member_added, group.member_removed, group.updated, group.job_completed); consent (consent.withdrawn, consent.granted); campaigns (campaign.started, campaign.completed, campaign.failed, campaign.approval_required); accounts (account.connected, account.disconnected, account.qr_required, account.send_blocked, account.restricted); support (ticket.created, ticket.updated, ticket.resolved, ticket.sla_breached, message.flagged, message.unflagged); sales (opportunity.created, opportunity.updated, opportunity.stage_changed, opportunity.won, opportunity.lost, opportunity.deleted); companies and tasks (company.created, company.updated, company.deleted, task.created, task.updated, task.completed, task.due); inbox (conversation.assigned, conversation.updated). The message.received and message.sent events carry the id of the connected number the message arrived on or left from.

WavesFlo delivers webhooks at least once. A failed delivery is retried with backoff until the attempt cap, and only to the endpoints that failed, never the ones that already succeeded; every attempt is logged. Order is not guaranteed, so sort by the timestamp each payload carries, and deduplicate on the event identifier, which stays the same across retries. A destination is disabled after 20 consecutive failures, with the reason recorded.

HubSpot and Zoho CRM connect natively. Once a workspace Admin switches syncing on, WavesFlo logs one-to-one WhatsApp messages and opt-out or opt-in changes as notes on the matching CRM contact; group, status and channel messages never reach the CRM. WavesFlo can also import CRM contacts with a usable international phone number, on demand or every six hours, and an import never records consent. Salesforce and other CRMs connect through n8n or Power Automate, using the REST API and the signed message.received webhook. WavesFlo keeps a sales pipeline on its own WhatsApp conversations, with no quotas and no lead scoring; your CRM stays the record for everything else.

Yes. Inside WavesFlo, Workflows (beta) joins a trigger to steps, with templates, Build with AI and HTTP request and webhook steps. Zapier, Make and n8n also have WavesFlo apps (n8n's is the n8n-nodes-wavesflo package), so a workflow can send messages, work tickets and deals, or start from any of the 49 published webhook events; Power Automate connects through a custom connector. Approval requests, campaign results and number alerts can go to Slack or Microsoft Teams, and AI apps such as Claude or Cursor connect over MCP.