Actions114
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
- Call Actions
- Label Actions
- OpenAI Actions
- N8N Integration Actions
- EvoAI Actions
- Template Actions
- Business Actions
Instance → Define Behavior
AI-generatedOverview
This node interacts with the Evolution API to define behavior settings for an instance. It allows users to configure various instance-specific options such as rejecting calls, setting call messages, ignoring groups, always being online, reading messages, syncing full history, and reading status. This is useful for automating and customizing instance behavior in communication or workflow automation scenarios.
Use Case Examples
- Automatically reject calls with a custom message when the instance is set to reject calls.
- Configure the instance to always be online and read all incoming messages.
- Sync the full message history for the instance to maintain up-to-date records.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance to configure. |
| Reject Calls | Whether to reject incoming calls or not. |
| Call Message | The message to send if calls are rejected. |
| Ignore Groups | Whether to ignore group mentions or not. |
| Always Online | Whether the instance should always appear online. |
| Read Messages | Whether the instance should read messages automatically. |
| Sync Full History | Whether to sync the full message history. |
| Read Status | Whether to read status updates. |
Output
JSON
instanceName- The name of the configured instance.rejectCall- Indicates if calls are rejected.msgCall- Message sent when calls are rejected.groupsIgnore- Indicates if group mentions are ignored.alwaysOnline- Indicates if the instance is always online.readMessages- Indicates if messages are read automatically.syncFullHistory- Indicates if full message history is synced.readStatus- Indicates if status updates are read.
Dependencies
- Requires an API key credential for Evolution API authentication.
Troubleshooting
- If the node throws an 'Unsupported operation' error, verify that the resource and operation names are correctly set to 'Instance' and 'Define Behavior'.
- Ensure the API key credential is valid and has the necessary permissions to configure instance settings.
- Check network connectivity to the Evolution API endpoint to avoid request failures.
Links
- Evolution API Documentation - Official documentation for the Evolution API, useful for understanding available endpoints and parameters.