HAP icon

HAP

Interact with HAP (Hyper Application Platform) API

Actions31

Workflow → Trigger

AI-generated

Overview

This node allows you to trigger a workflow execution on the Hyper Application Platform (HAP) by specifying the workflow process ID and optional input parameters. It is useful when you want to programmatically start workflows in HAP from within an n8n automation, passing custom data to influence the workflow's behavior.

Common scenarios:

  • Automating business processes by triggering workflows based on external events.
  • Integrating HAP workflows with other systems via n8n.
  • Passing dynamic input parameters to customize workflow runs.

Example: Trigger a workflow that processes customer orders by providing the order ID and customer details as input parameters.

Properties

Name Meaning
Process ID The unique identifier of the workflow process to trigger.
Input Parameters JSON object containing key-value pairs to pass as input parameters to the triggered workflow.

Output

The node outputs the response from the HAP API after triggering the workflow. The output is structured as JSON data representing the result of the trigger operation, which may include status information or identifiers related to the triggered workflow instance.

If the workflow trigger returns any binary data, it would be included accordingly, but typically this node deals with JSON responses only.

Dependencies

  • Requires an API key credential for authenticating with the HAP API.
  • The node uses HTTP requests with JSON content type to communicate with the HAP platform.
  • Ensure the API key credential is configured properly in n8n before using this node.

Troubleshooting

  • Invalid Process ID: If the provided workflow process ID does not exist or is incorrect, the API will likely return an error. Verify the process ID is correct.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Confirm the API key credential is set up and valid.
  • Malformed Input Parameters: Input parameters must be valid JSON. Invalid JSON syntax will cause errors. Use proper JSON formatting.
  • API Connectivity Issues: Network problems or incorrect endpoint configuration can prevent triggering workflows. Check network connectivity and API endpoint settings.

Links and References

Discussion