Pulse Account Action icon

Pulse Account Action

Account actions from Pulse API

Actions9

Overview

This node provides actions related to user accounts via the Pulse API. Specifically, for the Account resource and the Update User Account operation, it allows updating details of an existing user account such as email, account type, and expiration date.

Typical use cases include:

  • Modifying user account information in a system integrated with Pulse API.
  • Automating updates to user profiles based on external triggers or workflows.
  • Managing account lifecycle by setting expiration dates or changing account types programmatically.

For example, you could update a user's email address and change their account type from "Personal Account" to "Service Account" automatically when certain conditions are met in your workflow.

Properties

Name Meaning
Account ID * The unique identifier of the account to update.
Email * The new email address to assign to the user account.
Account type * The type of account to set. Options: Personal Account, Service Account, Local Account.
Expired At (Optional) The expiration date of the account, specified as a date only (no time).

* indicates required fields.

Output

The node outputs a JSON object representing the updated user account data returned from the Pulse API after the update operation completes successfully.

The exact structure depends on the API response but typically includes fields such as:

  • Account ID
  • Email
  • Account type
  • Expiration date
  • Other metadata related to the user account

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

Troubleshooting

  • Common issues:

    • Invalid or missing Account ID will cause the update to fail.
    • Providing an improperly formatted email or unsupported account type may result in API errors.
    • Expired or insufficient API credentials will prevent successful communication with the Pulse API.

  • Error messages:

    • "The operation "updateAccount" is not supported for resource "account"!" — This indicates a misconfiguration of the operation name; ensure "updateAccount" is selected.
    • API error messages returned in the error field if continueOnFail is enabled, which can help diagnose issues like invalid input or permission problems.

  • Resolution tips:

    • Double-check all required fields are provided and correctly formatted.
    • Verify API credentials and permissions.
    • Use the node’s error output to identify specific API error messages.

Links and References

Discussion