Actions9
Overview
This node interacts with the Pulse API to perform various account-related actions. Specifically, for the "Account" resource and the "Get User Account details" operation, it retrieves detailed information about a user account by its ID. It can optionally include related resources such as the associated person or roles in the response.
Common scenarios where this node is useful include:
- Fetching detailed user account information for display or processing within an automation workflow.
- Retrieving related data like the user's roles or personal details alongside the account info to make decisions or trigger further actions.
- Integrating Pulse account data into other systems or reports.
Example: You want to get the full profile of a user account including their assigned roles to verify permissions before proceeding with a task.
Properties
| Name | Meaning |
|---|---|
| Include Related Resources | Select one or more related resources to include in the response. Options: Person, Roles |
| Account ID * | The unique identifier of the account to retrieve details for (required) |
Output
The node outputs a JSON object containing the user account details fetched from the Pulse API. If related resources are included, those will be nested within the output JSON under appropriate keys (e.g., person details, roles).
The structure typically includes fields representing the account's attributes such as ID, status, creation date, and any included related entities.
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 with the node implementation to handle API requests.
Troubleshooting
Common issues:
- Invalid or missing Account ID: The node requires a valid account ID; ensure this is provided and correct.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Unsupported operations or resources: Using an unsupported operation or resource name will throw an error.
Error messages:
"The operation \"getUserAccountById\" is not supported for resource \"account\"!"— This indicates a mismatch in operation or resource names; check property values."The resource \"xyz\" is not supported!"— The specified resource does not exist in the node; verify spelling and available options.- API errors returned from Pulse (e.g., 404 Not Found if account ID does not exist) will be passed through; check the account ID validity.
To resolve errors, confirm input parameters, API credentials, and network connectivity.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n documentation on creating custom nodes