Actions8
- People Actions
- Person Identity Document Actions
Overview
The "Pulse People" node interacts with the People resource of the Pulse API. It allows users to retrieve and update information about people stored in the Pulse system. Specifically, for the "Show Person details info" operation, the node fetches detailed information about a single person by their unique ID. This is useful in scenarios where you need to display or process detailed user data, such as in CRM integrations, HR systems, or customer support workflows.
Practical examples:
- Fetching a person's profile details to display in a dashboard.
- Retrieving related account information linked to a person.
- Using person details to trigger further automation based on attributes like status or role.
Properties
| Name | Meaning |
|---|---|
| Person ID * | The unique identifier of the person whose details you want to retrieve or update. |
| Include Related Resources | Optional related resources to include in the response. Currently supports: Account. |
Output
The node outputs a JSON object containing the detailed information of the requested person. This includes all standard fields provided by the Pulse API for a person, such as name, contact details, and any other metadata. If the "Include Related Resources" property is used, the output will also contain nested objects representing those related entities (e.g., Account).
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Pulse API via an API key credential configured in n8n.
- The node depends on the Pulse API service being available and accessible.
- No additional external dependencies are required beyond the API authentication.
Troubleshooting
Common issues:
- Invalid or missing Person ID: The node requires a valid person identifier; ensure the ID exists in the Pulse system.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network or service downtime: The Pulse API must be reachable; check network connectivity and API status.
Error messages:
"The operation "getPersonById" is not supported for resource "people"!"— This indicates a misconfiguration of the operation or resource; verify the selected options.- Errors returned from the API (e.g., 404 Not Found) typically mean the person ID does not exist.
- Authentication errors suggest invalid or expired credentials; reconfigure the API key.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n documentation on creating custom nodes
- General API error handling best practices