Pulse Recruitment icon

Pulse Recruitment

Recruitment actions from Pulse API

Overview

This node enables managing pipeline templates within a recruitment system via the Pulse API. Specifically, the "Delete Pipeline Template" operation allows users to remove an existing pipeline template by its unique identifier. This is useful for maintaining and cleaning up recruitment workflows by deleting outdated or unused pipeline templates.

Practical examples include:

  • Automatically deleting a pipeline template when it is no longer relevant.
  • Cleaning up templates as part of a recruitment process automation workflow.
  • Managing pipeline templates programmatically without manual intervention in the Pulse UI.

Properties

Name Meaning
Pipeline Template ID * The unique identifier of the pipeline template to delete. This is a required string input.

Output

The node outputs a JSON object representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide details if an error occurred. The exact structure depends on the Pulse API response but generally includes status information about the deleted pipeline template.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Pulse API using an API key credential configured in n8n.
  • The node depends on the Pulse API helper utilities bundled with the node implementation to perform authenticated requests.
  • Proper permissions are needed on the API key to allow deletion of pipeline templates.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Pipeline Template ID will likely cause an error.
    • Insufficient API permissions can lead to authorization errors.
    • Network connectivity problems may prevent communication with the Pulse API.
  • Error messages:

    • "The operation "deletePipelineTemplate" is not supported for resource "pipelineTemplate"!" — indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.
    • Errors returned from the Pulse API typically include descriptive messages; check the node's output for details.
  • Resolution tips:

    • Verify the Pipeline Template ID is correct and exists.
    • Confirm that the API key has the necessary rights to delete pipeline templates.
    • Check network settings and retry if transient errors occur.

Links and References

Discussion