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
N8N Integration → Update Workflow
AI-generatedOverview
This node interacts with the Evolution API to update an n8n workflow based on user-defined parameters. It is useful for automating the management of workflows in n8n instances, such as updating workflow triggers, session settings, and webhook URLs. For example, it can be used to programmatically update a workflow to trigger on specific keywords or to maintain session state for a chatbot integration.
Use Case Examples
- Updating a workflow to trigger only on certain keywords.
- Setting debounce time and session timeout for workflow triggers.
- Configuring a workflow to listen to group messages or broadcasts.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the n8n instance where the workflow is hosted. |
| Webhook URL | The URL of the n8n webhook that triggers the workflow. |
| Trigger Type | Defines when the workflow should be triggered, either on all messages or specific keywords. |
| Trigger Keywords | Comma-separated keywords that trigger the workflow when the Trigger Type is set to 'Keyword'. |
| Additional Options | Optional settings to customize workflow behavior, including debounce time, session management, and message listening preferences. |
| Workflow ID | The unique identifier of the workflow to update. |
Output
JSON
workflowUpdateResponse- The response from the Evolution API after updating the workflow, typically containing status and updated workflow details.
Dependencies
- Requires an API key credential for the Evolution API to authenticate requests.
Troubleshooting
- Ensure all required parameters like Instance Name, Webhook URL, and Workflow ID are provided to avoid validation errors.
- If the API returns an unsupported operation error, verify that the selected resource and operation are correct and supported by the node.
- Network or authentication errors may occur if the API key credential is missing or invalid; ensure proper credential configuration.
Links
- Evolution API Documentation - Official documentation for the Evolution API used by this node.