Mobile App Integration icon

Mobile App Integration

Provides API endpoints for NextFlow App - workflow monitoring and management
Join our community

Actions2

Overview

This node provides integration with the NextFlow Mobile App, allowing users to manage workflows and retrieve workflow or execution data via API endpoints. Specifically, the 'Set Workflow' operation enables users to enable or disable a workflow either by automatically extracting parameters from a webhook request or by manually specifying parameters. This is useful for remotely controlling workflow activation status, for example, enabling a workflow after deployment or disabling it during maintenance.

Use Case Examples

  1. Automatically enable a workflow when triggered by a webhook with parameters specifying the workflow ID and desired status.
  2. Manually disable a workflow by specifying its ID and setting the status to disabled within the node configuration.

Properties

Name Meaning
Parameter Source Determines where the parameters for the operation are obtained from, either automatically from webhook query/body or manually set in the node.
Operation Type Specifies the type of operation to perform on the workflow, currently only 'Set Status' is supported.
Workflow ID The unique identifier of the workflow to update.
Status The new status to set for the workflow, either enable or disable.

Output

JSON

  • success - Indicates if the operation was successful.
  • workflowId - The ID of the workflow that was updated.
  • operation - The type of operation performed, e.g., 'setStatus'.
  • status - The resulting status of the workflow after the operation ('enabled' or 'disabled').
  • message - A message describing the result of the operation.
  • data - Additional data returned from the API about the workflow status change.
  • 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 obtain the base URL and API key for the n8n instance.

Troubleshooting

  • Common issues include missing or invalid API key configuration, which will cause authentication errors.
  • Errors may occur if required parameters like 'workflowId' or 'operationType' are missing when using automatic parameter source.
  • API call failures due to network issues or incorrect base URL configuration can cause the node to return error messages with HTTP status codes.
  • JSON parsing errors may occur if the API response is not valid JSON, which the node handles and reports.

Links

Discussion