Actions24
- Talent Actions
- Skill Actions
- Language Actions
- Education Actions
- Certification Actions
- Experience 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 duplicate or erroneous experience entries.
Properties
| Name | Meaning |
|---|---|
| Experience ID * | The unique identifier of the experience entry to delete. This is required for deletion. |
Output
The output of the node is a JSON object representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide details about the deleted experience entry. The exact structure depends on the Pulse API response but generally includes status information and possibly metadata about the deleted record.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Pulse API.
- The node depends on the Pulse API helper utilities bundled within the node's codebase.
- Proper configuration of the API credentials in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Experience ID will likely cause an error.
- Missing or incorrect API authentication credentials will prevent the node from connecting to the Pulse API.
- Network connectivity issues can cause timeouts or failures.
Error messages and resolutions:
"The operation "deleteExperience" is not supported for resource "experience"!"— This indicates a misconfiguration; ensure the operation and resource are correctly set.- Errors related to authentication usually indicate missing or invalid API keys; verify credentials in n8n.
- If the node returns an error stating the Experience ID is invalid, double-check the ID value being passed.
Links and References
- Pulse API Documentation (Replace with actual URL if available)
- n8n documentation on Creating Custom Nodes