Actions11
Overview
This node integrates with the Pulse API to manage recruitment-related actions, specifically focusing on candidates and quiz sessions. For the Create Candidate operation under the Candidates resource, it allows users to either create a new candidate profile or associate an existing person as a candidate within the recruitment system.
Typical use cases include:
- Adding new candidates to the recruitment pipeline by providing their personal details.
- Linking existing persons in the system as candidates without duplicating data.
- Automating candidate creation workflows when receiving applications or referrals.
For example, a recruiter can automate adding new applicants by inputting their names and organizational unit, or link a previously created person record as a candidate for a specific job opening.
Properties
Name | Meaning |
---|---|
New Person | Whether to create a new person record (true ) or use an existing one (false ). |
Person ID * | The unique identifier of an existing person to be used as the candidate (required if New Person is false ). |
First Name * | The first name of the new person (required if New Person is true ). |
Middle Name | The middle name of the new person (optional). |
Last Name * | The last name of the new person (required if New Person is true ). |
Organizational Unit * | The organizational unit associated with the new person (required if New Person is true ). |
Picture URL | URL pointing to the picture of the new person (optional). |
*Fields marked with * are required depending on the choice of creating a new person or using an existing one.
Output
The node outputs a JSON object representing the created candidate's data as returned by the Pulse API. This typically includes identifiers, personal details, and any metadata related to the candidate record.
No binary data output is involved in this operation.
Dependencies
- Requires 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 API calls.
- Proper network access to the Pulse API endpoint is necessary.
Troubleshooting
Common Issues:
- Missing required fields when creating a new person (e.g., first name, last name, organizational unit) will cause errors.
- Providing an invalid or non-existent Person ID when not creating a new person will result in failure.
- Network or authentication issues with the Pulse API may prevent successful candidate creation.
Error Messages:
"The operation "createCandidate" is not supported for resource "candidates"!"
— indicates a misconfiguration of the operation or resource parameters.- Errors from the API such as validation failures will be returned in the node output; ensure all required fields are correctly set.
Resolution Tips:
- Double-check that all required properties are provided according to whether you are creating a new person or using an existing one.
- Verify API credentials and network connectivity.
- Use the node’s “Continue On Fail” option to handle errors gracefully during batch processing.
Links and References
- Pulse API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General best practices for API Authentication