Actions17
- Announcement Actions
- Employee Actions
- Holiday Actions
- Leave Request Actions
- Planning Actions
Overview
This node integrates with the Pulse API to manage office-related data, specifically allowing users to create, update, retrieve, and delete various resources such as employees, announcements, holidays, leave requests, and planning entries. Focusing on the Holiday - Create Holiday operation, this node enables users to add new holiday entries into their organizational system.
Typical use cases include automating the addition of company-wide or department-specific holidays into a calendar system, ensuring that scheduling and planning tools reflect official non-working days. For example, HR teams can automate the creation of public holidays or special organizational holidays without manual entry, improving accuracy and saving time.
Properties
| Name | Meaning |
|---|---|
| Name * | The name of the holiday to be created (e.g., "Christmas Day", "Company Foundation Day"). |
| Date * | The date of the holiday in ISO 8601 format (date and time). |
| Organizational Unit * | The specific organizational unit (department, team, or division) for which the holiday applies. |
* indicates required fields.
Output
The output is a JSON object representing the newly created holiday record as returned by the Pulse API. This typically includes details such as the holiday's unique identifier, name, date, and associated organizational unit.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Pulse API via an API key credential.
- The node depends on the Pulse API helper utilities bundled within the node's codebase to handle API requests.
- Proper configuration of the API authentication credentials in n8n is necessary for successful execution.
Troubleshooting
Common Issues:
- Missing required properties (
name,date, ororganizational_unit) will cause the operation to fail. - Incorrect date format may lead to API rejection; ensure the date is in valid ISO 8601 format.
- Invalid or expired API credentials will result in authentication errors.
- Specifying an organizational unit that does not exist or is not recognized by the Pulse system may cause errors.
- Missing required properties (
Error Messages:
"Unknown operation: "createHoliday" is not supported for resource "holiday"!"— Indicates a mismatch in operation or resource parameters; verify correct selection.- API error messages related to authorization or validation will be passed through; check API key validity and input correctness.
Resolution Tips:
- Double-check all required inputs are provided and correctly formatted.
- Verify API credentials and permissions.
- Consult Pulse API documentation for valid organizational units and date formats.
Links and References
- Pulse API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General information on ISO 8601 Date Format