Pulse Account Action icon

Pulse Account Action

Account actions from Pulse API

Actions9

Overview

This node enables managing account roles within the Pulse API by performing various actions such as adding, retrieving, updating, and deleting account roles. Specifically, the "Delete Account Role" operation allows users to remove an existing account role by specifying its unique identifier. This is useful in scenarios where roles are no longer needed or must be cleaned up to maintain proper access control.

Practical examples include:

  • Removing obsolete or deprecated roles from an account.
  • Automating cleanup of roles during account lifecycle management.
  • Integrating with workflows that manage user permissions dynamically.

Properties

Name Meaning
Account Role ID * The unique identifier of the account role to delete. This is a required string input.

Output

The output of this operation is a JSON object representing the result of the deletion request. Typically, it will contain confirmation of the deletion or relevant status information returned by the Pulse API. There is no binary data output for this operation.

Example output structure (conceptual):

{
  "success": true,
  "message": "Account role deleted successfully",
  "deletedRoleId": "string"
}

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 within the node's codebase to perform authenticated requests.
  • Proper permissions on the API key are necessary to delete account roles.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Account Role ID will likely cause an error.
    • Insufficient API permissions can lead to authorization errors.
    • Network connectivity problems may prevent successful API calls.

  • Error messages:

    • "The operation "deleteAccountRole" is not supported for resource "accountRole"!" — indicates a misconfiguration of the operation name.
    • API errors returned from Pulse API (e.g., 404 Not Found if the role ID does not exist).

  • Resolutions:

    • Verify the Account Role ID is correct and exists.
    • Ensure the API key has the necessary permissions to delete roles.
    • Check network connectivity and API endpoint accessibility.
    • Confirm the node’s Resource is set to "Account Role" and Operation to "Delete Account Role".

Links and References

Discussion