Actions8
- Organizations Actions
- People Directories Actions
Overview
This node allows you to manage People Directories via the Pulse API, specifically supporting operations such as creating, updating, deleting, retrieving by ID, and listing people directories. The "Delete People Directory" operation removes a specified people directory entry from the system.
Common scenarios for this node include automating the maintenance of organizational contact lists or employee directories, cleaning up outdated entries, or integrating directory management into broader workflows.
For example, you might use this node to automatically delete a people directory entry when an employee leaves the company or when a directory is no longer relevant.
Properties
| Name | Meaning |
|---|---|
| People Directory ID * | The unique identifier of the people directory entry to delete. This is a required field. |
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 entry. The exact structure depends on the Pulse API response but generally includes status information.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Pulse API.
- Requires an API authentication token credential configured in n8n to authorize requests.
- The node depends on the bundled PulseApiFactory helper to interact with the Pulse API endpoints.
Troubleshooting
Common issues:
- Invalid or missing People Directory ID will cause the operation to fail.
- Authentication errors if the API key or token is invalid or expired.
- Network connectivity problems can prevent communication with the Pulse API.
Error messages:
"The operation "deletePeopleDirectory" is not supported for resource "peopleDirectories"!"indicates a misconfiguration of the operation or resource parameters.- Errors returned from the API (e.g., "Not Found" if the ID does not exist) will be passed through; ensure the ID is correct.
Resolutions:
- Verify that the People Directory ID is correct and exists.
- Check that the API credentials are valid and have sufficient permissions.
- Ensure network access to the Pulse API endpoint.
Links and References
- Pulse API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes