Pulse Account Action icon

Pulse Account Action

Account actions from Pulse API

Overview

This node enables interaction with user accounts via the Pulse API, specifically allowing actions such as creating new user accounts, updating existing accounts, retrieving account details, and managing account statuses. It is useful in scenarios where automated workflows need to manage user lifecycle events, such as onboarding new users, updating user information, or deactivating accounts based on business rules.

For example, you can use this node to automatically create a new user account when a form is submitted, specifying the user's email, account type, and associated person ID. Another practical use case is updating an account's expiration date or status as part of a scheduled maintenance workflow.

Properties

Name Meaning
Email * The email address of the new user account.
Account type * The type of account to create. Options: Personal Account, Service Account, Local Account.
Person ID * The ID of the person to associate with this account.
Expired At The expiration date of the account (date only). Optional field to set when the account expires.

Note: Fields marked with * are required for the "Create new User Account" operation.

Output

The node outputs JSON data representing the result of the executed account operation. For the "Create new User Account" operation, the output JSON typically contains details of the newly created user account, including identifiers, email, account type, associated person ID, and any metadata returned by the Pulse API.

No binary data output is produced by this node.

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 configuration of the API authentication credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Missing required fields such as Email, Account type, or Person ID will cause errors.
    • Invalid or expired API credentials will prevent communication with the Pulse API.
    • Providing unsupported operations or resources will throw explicit errors indicating unsupported actions.
  • Error messages:

    • "The operation \"createAccount\" is not supported for resource \"account\"!" indicates a mismatch between selected operation and resource.
    • Errors related to API authentication failures suggest checking the API key credential setup.
    • Validation errors from the API (e.g., invalid email format) should be resolved by correcting input property values.

Links and References

Discussion