Actions31
- Option Set Actions
- Public Query Actions
- Record Actions
- Role Actions
- Workflow Actions
- Worksheet Actions
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 remotely or integrate HAP workflows into larger automation pipelines.
Typical use cases include:
- Starting a predefined workflow in HAP based on external events.
- Passing dynamic input parameters to customize workflow runs.
- Integrating HAP workflows with other systems via n8n.
For example, you can trigger a workflow that processes customer orders by providing the order ID and related data as input parameters.
Properties
| Name | Meaning |
|---|---|
| Process ID | The unique identifier of the workflow process you want to trigger. |
| Input Parameters | JSON object containing key-value pairs to pass as input parameters to the workflow run. |
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, execution IDs, or any returned data from the workflow trigger endpoint.
If the workflow produces binary data as part of its response, it would be included accordingly, but this node primarily handles JSON responses related to workflow execution triggers.
Dependencies
- Requires an API key credential for authenticating with the HAP API.
- The node depends on the HAP API being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
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: Ensure the API key credential is valid and has sufficient permissions to trigger workflows.
- Malformed Input Parameters: Input parameters must be valid JSON. Invalid JSON syntax will cause errors.
- Network Issues: Connectivity problems to the HAP API endpoint will prevent triggering workflows.
- API Rate Limits: Excessive triggering requests might hit rate limits imposed by the HAP API.
To resolve errors, check the error messages returned by the node, verify credentials, validate input JSON, and confirm network connectivity.
Links and References
- Hyper Application Platform (HAP) API Documentation (example placeholder link)
- n8n Documentation - Creating Custom Nodes