Actions9
Overview
The 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.
This node is useful in scenarios where you need to programmatically manage user accounts within the Pulse system, for example:
- Updating a user's email address after they change it.
- Changing the type of an account (e.g., from personal to service).
- Setting or modifying the expiration date of an account to control access duration.
Practical example: Automatically update user account details when syncing with an external HR system or after a user submits a profile update form.
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 expiration date of the account (date only). |
* indicates required fields.
Output
The node outputs a JSON object representing the updated user account data returned by the Pulse API. This typically includes the updated fields such as account ID, email, account type, expiration date, and possibly other metadata about the account.
No binary data output is involved.
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 perform authenticated requests.
Troubleshooting
Common issues:
- Invalid or missing Account ID will cause the update to fail.
- Providing an invalid email format may result in API validation errors.
- Attempting to update an account that does not exist will return an error.
- Missing or incorrect API credentials will prevent successful communication with the Pulse API.
Error messages:
"The operation "updateAccount" is not supported for resource "account"!":Indicates a misconfiguration of the operation name.- API errors returned from Pulse will be passed through; check the message for details like invalid parameters or authentication failures.
Resolutions:
- Ensure all required fields are provided and valid.
- Verify API credentials and permissions.
- Confirm the account ID exists before attempting updates.
Links and References
- Pulse API Documentation (replace with actual URL if available)
- n8n documentation on Creating Custom Nodes