Actions9
Overview
This node interacts with the Pulse API to perform various account-related actions. Specifically, for the Account resource and the Get Current User operation, it retrieves information about the currently authenticated user. This is useful in workflows where you need to obtain details about the user running the workflow or verify user identity and permissions.
Practical examples include:
- Fetching the current user's profile data to personalize subsequent workflow steps.
- Retrieving related resources such as the user's associated person record or roles to control access or trigger role-based logic.
- Using the current user’s account information to audit or log activity within a workflow.
Properties
| Name | Meaning |
|---|---|
| Include Related Resources | Select one or more related resources to include in the response. Options: Person, Roles. |
- Include Related Resources: Allows including additional related data in the response, such as the linked person entity or the roles assigned to the user.
Output
The output is a JSON object containing the current user's account information as returned by the Pulse API. If related resources are requested via the "Include Related Resources" property, those will be included in the response as nested objects.
The structure typically includes fields like user ID, username, email, status, and optionally embedded related entities (person details, roles).
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Pulse API.
- The node depends on the Pulse API service being accessible and the provided credentials having permission to retrieve user account information.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Requesting unsupported related resources may result in errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
"The operation "getCurrentUser" is not supported for resource "account"!"— indicates a misconfiguration of the operation name."The resource "account" is not supported!"— indicates an invalid resource selection.- API errors from Pulse (e.g., unauthorized, forbidden) should be checked by verifying credentials and permissions.
To resolve errors, ensure that:
- The correct resource ("Account") and operation ("Get Current User") are selected.
- Valid API credentials are configured.
- The Pulse API service is reachable.
Links and References
- Pulse API Documentation (hypothetical link)
- n8n documentation on creating custom nodes