Actions32
- Talent Actions
- Skill Actions
- Language Actions
- Education Actions
- Certification Actions
- Experience Actions
- Talent Quizz Sessions Actions
Overview
This node interacts with the "Experience" resource of the Pulse API, specifically supporting operations to manage experience entries related to talent profiles. The "Delete Experience" operation allows users to remove a specific experience entry by its ID. This is useful in scenarios where outdated or incorrect experience records need to be cleaned up from a talent's profile.
Practical examples include:
- Automatically deleting an experience entry when it no longer applies (e.g., a contract ended).
- Cleaning up test or placeholder data during automated workflows.
- Managing talent profiles by removing redundant or duplicate experience entries.
Properties
| Name | Meaning |
|---|---|
| Experience ID * | The unique identifier of the experience entry to delete. This is required for deletion. |
Output
The output JSON contains the response from the Pulse API after attempting to delete the specified experience entry. Typically, this will confirm whether the deletion was successful or provide error details if it 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 are necessary to delete experience entries.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Experience ID will likely result in an error from the API indicating that the resource could not be found.
- Insufficient API permissions may cause authorization errors.
- Network connectivity problems can prevent the node from reaching the Pulse API.
Error messages and resolutions:
"The operation "deleteExperience" is not supported for resource "experience"!"— This indicates a misconfiguration; ensure the operation and resource names are correct.- API error messages about missing or invalid Experience ID — Verify that the Experience ID provided exists and is correctly formatted.
- Authorization errors — Check that the API key credential has the necessary scopes/permissions.
Links and References
- Pulse API Documentation (hypothetical link)
- n8n documentation on creating custom nodes