Pulse Account Action icon

Pulse Account Action

Account actions from Pulse API

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 scenarios where you want to fetch details about the user who is currently logged in or connected via the API key, such as displaying user profile data, verifying user identity, or customizing workflows based on user attributes.

Practical examples include:

  • Automatically fetching the current user's profile details to personalize subsequent workflow steps.
  • Retrieving related user roles or person details to control access or permissions within a workflow.
  • Using the current user’s account information to log activity or audit changes.

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 associated person entity or the roles assigned to the user. This can enrich the returned user data with contextual information.

Output

The output of this operation is a JSON object representing the current user's account information as returned by the Pulse API. The structure typically includes user identifiers, contact details, status, and optionally related entities if requested.

If "Include Related Resources" is used, the output JSON will also contain nested objects or arrays for those related resources (e.g., person details or roles).

No binary data output is produced by this node.

Example output JSON snippet (simplified):

{
  "id": "user_123",
  "email": "user@example.com",
  "status": "active",
  "person": {
    "id": "person_456",
    "name": "John Doe"
  },
  "roles": [
    {
      "id": "role_789",
      "name": "Administrator"
    }
  ]
}

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.
  • No additional environment variables are required beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Requesting related resources without proper permissions may result in partial or empty related data.
    • 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 or resource parameters.
    • API errors from Pulse (e.g., 401 Unauthorized) usually mean invalid credentials or insufficient permissions.

  • Resolutions:

    • Verify that the API key credential is correctly configured and has necessary scopes.
    • Ensure the selected resource and operation match the intended action.
    • Check network connectivity and Pulse API service status.

Links and References

Discussion