דלג לתוכן הראשי
Evolution API 2.3.7

Evolution API

WhatsApp automation through Evolution API running on your own server. The same 70 operations are available in both Make and n8n, because both are generated from a single table.

70
operations
10
groups
2
platforms

Full reference Install

Connecting

The connection asks for two things. The server field takes only a subdomain and the full URL is built from it, so nothing outside cigcrm.com is reachable.

FieldExampleNotes
Server subdomainevolution-srv1Just the subdomain. The app builds https://evolution-srv1.cigcrm.com for you.
API key571d…Sent as the apikey header. This is not a Bearer token.

Choosing an instance

Almost every operation starts with an instance dropdown — one instance is one connected WhatsApp number. The list loads from your server and shows exactly what your key can reach. It belongs to the operation rather than the connection, so one connection can drive many numbers and the instance can come from an earlier step.

What is inside

GroupOpsWhat it covers
Instance5Operate your connected number — pair it with a QR code, check the connection state, set presence, restart or log out.
Send Message13Every outbound message type: text, media, audio, stickers, locations, contacts, reactions, polls, lists, buttons and Business templates.
Call1Ring a contact with a call offer.
Chat23Read and act on conversations — find chats, contacts and messages, mark as read, archive, block, and manage the profile.
Business2Read a WhatsApp Business product catalog and its collections.
Group16Create groups and administer them: participants, invites, subject and picture, and disappearing messages.
Template4WhatsApp Business message templates — create, edit, delete and list.
Setting2Instance behaviour — call rejection, read receipts, group handling and history sync.
Proxy2Route an instance through an HTTP proxy.
Label2List the chat labels on the account, and attach or detach them.

Replying to a message

Every send operation has a Quoted section. Fill in the message ID and the remote JID of the message you are answering — both come straight out of a previous find or send step — and the reply threads under it in WhatsApp.

{
  "number": "972500000000",
  "text": "Sure, sending it now",
  "quoted": {
    "key": { "id": "3EB0…", "remoteJid": "972500000000@s.whatsapp.net", "fromMe": false },
    "message": { "conversation": "Can you send the invoice?" }
  }
}
The API wants a nested structure. The form is flat, and the assembly is done for you.
בואו נתחיל