Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Instance → Set Behavior
AI-generatedOverview
This node operation allows users to configure behavior settings for an instance in the Zapin EVO system. It is useful for managing how the instance handles calls, message reading, online status, and history synchronization. For example, users can set the instance to reject calls with a custom message, decide whether the instance should always appear online, or enable full history synchronization.
Use Case Examples
- Setting the instance to reject incoming calls with a specific message.
- Configuring the instance to always appear online regardless of actual status.
- Enabling the instance to read messages and statuses automatically.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance to configure, required to identify which instance's behavior is being set. |
| Reject Calls | Boolean flag to determine whether the instance should reject incoming calls. |
| Call Message | The message sent when calls are rejected, providing a custom response to callers. |
| Ignore Groups | Boolean flag indicating whether to mention all group members or not. |
| Always Online | Boolean flag to set the instance to always appear online. |
| Read Messages | Boolean flag to enable the instance to read messages. |
| Sync Full History | Boolean flag to enable synchronization of the full message history. |
| Read Status | Boolean flag to enable the instance to read status updates. |
Output
JSON
instanceName- The name of the instance configured.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.syncFullHistory- Indicates if full history synchronization is enabled.readStatus- Indicates if status reading is enabled.
Dependencies
- An API key credential for authenticating with the Zapin EVO API
Troubleshooting
- If the node throws an 'Unsupported operation' error, verify that the resource and operation names are correctly set to 'Instance' and 'Set Behavior'.
- Ensure the API credentials are valid and have the necessary permissions to modify instance settings.
- If the instance name is incorrect or does not exist, the operation may fail; verify the instance name input.