Actions31
- Option Set Actions
- Public Query Actions
- Record Actions
- Role Actions
- Workflow Actions
- Worksheet Actions
Overview
This node interacts with the Hyper Application Platform (HAP) API to create a new record in a specified worksheet. It is useful when you want to programmatically add data entries into a HAP worksheet as part of an automated workflow. For example, you might use this node to insert form submission data, import external data sources, or log events into a HAP application.
Properties
| Name | Meaning |
|---|---|
| Worksheet ID | The unique identifier of the worksheet where the new record will be created. |
| Fields | An array of objects specifying field IDs and their corresponding values for the record. |
| Trigger Workflow | Boolean flag indicating whether to trigger any associated workflows after creating the record. |
- Fields expects JSON input structured like:
[
{
"ID": "field_id",
"value": "field_value"
}
]
Output
The node outputs JSON data representing the newly created record as returned by the HAP API. This typically includes the record's unique ID, field values, timestamps, and any metadata provided by the platform.
If the node supports binary data output, it would represent attachments or files related to the record, but based on the provided code and properties, the primary output is JSON data about the created record.
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
Common Issues:
- Invalid or missing Worksheet ID can cause the creation to fail.
- Malformed JSON in the Fields property may result in errors.
- Insufficient permissions or invalid API credentials will prevent successful record creation.
- If "Trigger Workflow" is enabled but the workflow configuration is incorrect, triggering may fail silently or cause errors.
Error Messages:
- Authentication errors indicate issues with the API key; verify credentials.
- Validation errors from the API often point to incorrect field IDs or data types; check the Fields array carefully.
- Network or timeout errors suggest connectivity problems with the HAP API endpoint.
Links and References
- Hyper Application Platform (HAP) API Documentation (example placeholder link)
- n8n documentation on Creating Custom Nodes