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
Event → Kafka
AI-generatedOverview
This node interacts with the Evolution API specifically for managing Kafka event configurations. It allows users to either set Kafka integration settings or check the current Kafka configuration for a given instance. This is useful for automating the management of Kafka event handling within the Evolution API environment, such as enabling or disabling Kafka integration and selecting specific Kafka events to monitor or handle.
Use Case Examples
- Setting Kafka integration for an instance by enabling it and selecting specific Kafka events like CALL or SEND_MESSAGE.
- Checking the current Kafka configuration status for an instance to verify if Kafka integration is enabled and which events are configured.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance for which Kafka settings are being managed. |
| Action | Choose between setting Kafka configuration or checking the Kafka configuration status. |
| Enable Kafka | Boolean flag to enable or disable Kafka integration (only applicable when setting Kafka). |
| Events | Select multiple Kafka event types to be enabled or monitored (only applicable when setting Kafka). |
Output
JSON
status- The status of the Kafka configuration operation or check.enabled- Indicates whether Kafka integration is enabled.events- List of Kafka events configured or returned by the check operation.
Dependencies
- Requires an API key credential for the Evolution API to authenticate requests.
Troubleshooting
- Common issues include unsupported operations if the action selected is not implemented, which results in an error message 'Unsupported operation.'
- Errors may occur if required parameters like 'Instance Name' are missing or invalid.
- Network or authentication errors can happen if the API key credential is incorrect or the Evolution API service is unreachable.