Actions2
Overview
This node provides integration with the n8n Mobile App, allowing users to retrieve workflow or execution data and to set workflow statuses via API calls. It supports fetching workflows or execution logs either automatically from webhook query parameters or manually via node parameters. It also allows enabling or disabling workflows by setting their status. This node is useful for monitoring and managing workflows remotely, such as fetching execution logs for analysis or toggling workflow activation states programmatically.
Use Case Examples
- Automatically fetch workflows or executions based on webhook query parameters for dynamic monitoring.
- Manually retrieve a list of workflows including disabled ones for administrative overview.
- Get execution logs filtered by status and limited in number for performance analysis.
- Enable or disable a specific workflow by setting its status manually.
Properties
| Name | Meaning |
|---|---|
| Parameter Source | Determines whether parameters are obtained automatically from webhook query or set manually in the node. |
| Data Type | Specifies the type of data to retrieve when parameters are set manually. |
| Workflow ID | The ID of the workflow to get details for or to get executions for, depending on the data type. |
| Include Disabled | Whether to include disabled workflows in the results when retrieving workflows manually. |
| Limit | Maximum number of executions to return when retrieving execution logs manually. |
| Status | Filter executions by their status when retrieving execution logs manually. |
Output
JSON
success- Indicates whether the operation was successful.operation- The operation performed, e.g., 'getData' or 'setStatus'.message- Descriptive message about the operation result or error.data- The retrieved data such as workflows or execution logs, or response data from status update.total- Total number of items returned in the data array.timestamp- Timestamp of when the operation was performed.workflowId- The ID of the workflow affected or queried.status- The status of the workflow or execution, e.g., enabled/disabled or execution status.error- Error message if the operation failed.
Dependencies
- Requires an API key credential for the n8n API to authenticate requests.
- Uses environment variables or node credentials to determine the base URL and API key for the n8n instance.
Troubleshooting
- Ensure a valid n8n API key is configured either in environment variables or node credentials; otherwise, the node will throw an error about missing API key.
- If the API endpoint returns non-JSON responses or errors, the node logs the issue and returns a failure message in the output.
- When fetching executions, a workflow ID is required; missing this parameter will cause an error.
- Network or permission issues with the n8n API server can cause fetch failures; verify connectivity and API permissions.
Links
- n8n Mobile App Integration Documentation - Official documentation for the Mobile App Integration node in n8n.