Skip to content
WhatsApp

Autocloz + Sinch WhatsApp

Sinch WhatsApp is listed in Autocloz, but it does not work from the Settings card today. Autocloz's Sinch WhatsApp adapter uses Sinch's Conversation API, which needs a project ID and a Conversation API app ID. The Sinch card asks for a WhatsApp bot ID instead, so the adapter never receives the two IDs and stops with a clear error. Nothing is sent. For WhatsApp now, use the official Meta WhatsApp Cloud API, which connects in one sign-in.

Status: limited today. Measured on 2026-09-28: Sinch WhatsApp configured through Settings fails with "Sinch api_key + extras.project_id + extras.app_id required".

Autocloz and Sinch WhatsApp integration
Bring your own accountWorkspace-scoped, no cross-org leakFree-forever CRM core

What you can do with Sinch WhatsApp

Sinch WhatsApp plugs into the WhatsApp stack — bring your own whatsapp business account, scoped to your workspace.

Values saved

Your Sinch token, region and bot ID are stored encrypted for your workspace.

Conversation API adapter

The adapter posts to {region}.conversation.api.sinch.com with a bearer token once it has a project and app ID.

Visible failure

The missing IDs are named on the failed touch, so it is clear the setup, not the lead, is the problem.

How to connect Sinch WhatsApp

Bring your own WhatsApp Business account — you keep control of the account, the spend and the data boundary.

  1. 1

    Check what Sinch gave you

    The Conversation API needs a project ID and an app ID from the Sinch dashboard.

  2. 2

    Save the Sinch card

    Settings → Integrations → WhatsApp → Sinch. The card has no project ID or app ID fields.

  3. 3

    Expect the error

    A test WhatsApp send fails with the required-fields message.

  4. 4

    Use Meta for WhatsApp

    Connect with Meta under WhatsApp → Numbers for working WhatsApp messaging.

Planning around the gap

WhatsApp steps on a Sinch sender will keep failing until the mapping is fixed. Move them to a Meta sender, or remove them from the sequence. Email, LinkedIn, SMS and call steps are not affected.

How to confirm nothing went out

Each attempt shows on the lead as a failed WhatsApp touch with the adapter's message, and campaign analytics count it as failed. The check runs before any request, so Sinch is not contacted. After you connect Meta and move the WhatsApp step to a Meta sender, you can retry the failed leads.

WhatsApp rules Autocloz applies on every provider

Free-form messages only inside 24 hours of the contact's last message, approved templates otherwise, and the DNC list checked on every send. WhatsApp senders have no quiet-hours window by default because messages are opt-in. Templates are limited to 1,024 characters for body and footer together. Background: WhatsApp Business API.

The field mismatch in plain terms

Sinch used to offer WhatsApp through an older API that identified senders by a bot ID, which is what the card collects. Autocloz's adapter targets the newer Conversation API, which identifies the sender by project and app. The two do not meet, so the adapter refuses to send. Sinch SMS on the same card is unaffected; see Sinch SMS.

WhatsApp through Meta instead

The Meta Cloud API path is native in Autocloz: Connect with Meta, templates created and tracked in-app, delivered and read receipts, and replies in the Unibox without a relay. If your WhatsApp number is currently hosted by Sinch, it would need to move to your own WhatsApp Business Account on Meta, which Meta supports. See the WhatsApp channel.

What Sinch WhatsApp does not do in Autocloz

  • No working Sinch WhatsApp sends from the card.
  • No Sinch WhatsApp inbound.
  • No template sync from Sinch.

Troubleshooting Sinch WhatsApp

"Sinch api_key + extras.project_id + extras.app_id required".
Known mapping gap. Use Meta Cloud API for WhatsApp.

Part of the WhatsApp stack

Sinch WhatsApp is one of the providers behind the WhatsApp channel. All providers share the same template gating, opt-in enforcement and unified-inbox threading.

Explore the WhatsApp feature

Related integrations

Frequently asked

Does the WhatsApp bot ID field do anything?

It is stored, but the current adapter does not use it.

Is Sinch SMS affected too?

No. Sinch SMS works from the card with the service plan ID and API token.

How long does moving to Meta take?

Connect with Meta takes a few minutes if you have a Meta business account. Template approval by Meta can take longer and is out of Autocloz's control.

Can I keep my WhatsApp number?

Meta supports moving a number between providers. Check with Sinch and Meta about migrating it to your own WhatsApp Business Account.

Run Sinch WhatsApp inside Autocloz

Bring your own account, plug it into the WhatsApp channel, and keep a free-forever CRM for 3 users.