Actions9
Overview
This node interacts with the Pulse API to perform various actions related to accounts and account roles. Specifically, for the "Get Account Role Details" operation under the "Account Role" resource, it retrieves detailed information about a specific account role by its ID. This is useful in scenarios where you need to fetch role-specific data such as permissions or metadata associated with an account role within your system.
Practical examples include:
- Fetching role details to display in an admin dashboard.
- Validating role information before assigning it to users.
- Integrating role data into workflows that manage user access or permissions.
Properties
| Name | Meaning |
|---|---|
| Account Role ID * | The unique identifier of the account role to retrieve details for. |
| Include Related Resources | Optional list of related resources to include in the response. Currently supports: Account |
Output
The output contains a JSON object representing the details of the requested account role. This includes all relevant fields returned by the Pulse API for that role, potentially enriched with related resources if specified (e.g., the associated account).
If the "Include Related Resources" property is used with "Account," the output JSON will also contain embedded information about the related account linked to the role.
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:
- Providing an invalid or non-existent Account Role ID will likely result in an error from the API indicating the role was not found.
- Missing or incorrect API credentials will cause authentication failures.
- Requesting unsupported related resources in the "Include Related Resources" field will have no effect or may cause errors depending on API behavior.
Error messages:
"The operation "getAccountRoleById" is not supported for resource "accountRole"!"— indicates a misconfiguration of the operation name.- API errors related to authorization or resource not found will be passed through; ensure the provided Account Role ID exists and credentials are valid.
To resolve these issues:
- Double-check the Account Role ID input.
- Verify API credentials are correctly set up and have sufficient permissions.
- Use only supported options in the "Include Related Resources" property.
Links and References
- Pulse API Documentation (general reference for account roles and related endpoints)
- n8n documentation on creating and configuring API credential nodes