Actions17
- Announcement Actions
- Employee Actions
- Holiday Actions
- Leave Request Actions
- Planning Actions
Overview
This node interacts with the Pulse API to manage office-related data, specifically here focusing on managing holidays. The "Delete Holiday" operation allows users to remove a holiday entry from the system by specifying its unique identifier. This is useful in scenarios where a previously scheduled holiday is canceled or no longer applicable.
Practical examples include:
- Removing outdated or incorrect holiday entries.
- Automating cleanup of holiday records based on external triggers or business rules.
- Integrating holiday management into broader HR or planning workflows.
Properties
| Name | Meaning |
|---|---|
| Holiday ID * | The unique identifier of the holiday to delete. This is required to specify which holiday record should be removed. |
Output
The output of this operation is a JSON object representing the result of the deletion request. Typically, it will confirm whether the holiday was successfully deleted or provide error details if the operation failed.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Pulse API via an API key credential configured in n8n.
- The node depends on the Pulse API helper utilities bundled within the node's codebase to perform authenticated requests.
- Proper permissions on the Pulse API side are necessary to delete holiday records.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Holiday ID will likely cause the operation to fail.
- Insufficient API permissions can prevent deletion.
- Network or authentication errors may interrupt communication with the Pulse API.
Error messages and resolutions:
"Unknown operation"error: Ensure that the operation name is correctly set to "deleteHoliday" for the Holiday resource."The resource ... is not supported!": Verify that the resource is set to "holiday".- API errors indicating missing or invalid credentials: Check that the API key credential is properly configured and has the necessary access rights.
- Errors about the Holiday ID: Confirm that the Holiday ID provided exists and is correct.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n documentation on creating custom nodes