Install
Both platforms connect to the same server the same way: a subdomain and a key.
Before you start
You need a running Evolution API server on a cigcrm.com domain, and an API key for it.
A quick check that the server is alive and the key is valid:
curl -H "apikey: YOUR_KEY" \
https://evolution-srv1.cigcrm.com/instance/fetchInstancesMake
The app is published and installs from an invite link. Once Make completes its review it will also appear in the regular app search.
- Open the install link and pick the organization to install into.
- In a new scenario, search for the app name and pick an operation.
- Creating the connection asks for the subdomain and the API key.
- Pick an instance from the dropdown — if it fills, the connection works.
n8n
The node installs as a community package on self-hosted n8n.
The package is not on the public npm registry yet. Until it is, we can send it to you directly — email support@cig.chat.
Community packages are self-hosted only. On n8n Cloud, use the HTTP Request node against the same server.
Domain lock
The server field takes a subdomain, not a URL. The address is built from it after stripping every character that is not a letter, digit or hyphen, so a full URL pasted into the field cannot redirect the integration somewhere else.
evolution-srv1 → https://evolution-srv1.cigcrm.com
https://evil.example.com → https://httpsevilexamplecom.cigcrm.comCommon problems
| Symptom | Cause |
|---|---|
| 401 Unauthorized | Wrong key, or a key belonging to a different server. |
| Instance list is empty | The key is valid but sees no instances. An instance key only sees its own. |
| 400 when sending | A required field is empty. Optional fields left blank are not sent. |
| No connection on the operation | The connection was not selected on the operation itself. |
Evolution API 2.3.7 · support@cig.chat