Actions20
- Candidates Actions
- Pipeline Templates Actions
- Stage Templates Actions
- Recruitment Campaigns Actions
Overview
This node enables managing stage templates within a recruitment system via the Pulse API. Specifically, the "Delete Stage Template" operation allows users to remove an existing stage template by specifying its unique ID. This is useful for maintaining and cleaning up recruitment workflows by deleting outdated or incorrect stage templates.
Practical examples include:
- Automatically deleting a stage template that is no longer relevant after a recruitment campaign ends.
- Removing test or placeholder stage templates created during setup or testing phases.
Properties
| Name | Meaning |
|---|---|
| Stage Template ID * | The unique identifier of the stage template to delete. This is required to specify which stage template should be removed. |
Output
The output JSON contains the response from the Pulse API after attempting to delete the specified stage template. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Pulse API using a valid API authentication token configured in n8n credentials.
- The node depends on the Pulse API helper utilities bundled with the node implementation to perform API requests.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Stage Template ID will result in an error from the API indicating the resource could not be found.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity problems can prevent the node from reaching the Pulse API.
Error messages:
"The operation "deleteStageTemplate" is not supported for resource "stageTemplate"!"— indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.- API errors related to authorization or resource existence will be returned in the output JSON under an error message field.
To resolve these issues:
- Verify the Stage Template ID is correct and exists.
- Confirm API credentials are properly set up and have necessary permissions.
- Check network connectivity and API endpoint availability.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n documentation on creating custom nodes