Outseta

Interact with Outseta CRM API to manage people, accounts, and deals

Actions16

Overview

The node integrates with the Outseta CRM API to update an existing account's details. It allows users to modify the account's name and stage by specifying the unique identifier (UID) of the account they want to update. This operation is useful in scenarios where account information changes over time, such as updating the status of a customer account or correcting account details.

Practical examples include:

Changing an account's name after a company rebranding.
Updating the account stage to reflect its current lifecycle status, e.g., moving from "Trialing" to "Subscribing".
Correcting data entry errors in account records.

Properties

Name	Meaning
Account UID	The unique identifier of the account to update (required).
Account Name	The new name for the account.
Additional Fields	Optional additional fields to update on the account. Currently supports: - Account Stage: One of Demo, Trialing, Subscribing, Cancelling, Expired, Trial Expired, Past Due

Output

The node outputs JSON data representing the updated account object returned by the Outseta CRM API. This typically includes all the account's properties after the update has been applied, such as UID, name, stage, and any other relevant metadata.

No binary data output is involved in this operation.

Dependencies

Requires an API key credential for authenticating with the Outseta CRM API.
The node uses the base URL constructed from the user's configured domain credential.
The HTTP method used is PUT, targeting the endpoint /crm/accounts/{accountUid}.

Troubleshooting

Missing or invalid Account UID: The update operation requires a valid account UID. If omitted or incorrect, the API will likely return an error indicating the resource was not found.
Invalid field values: Providing unsupported values for fields like Account Stage may cause validation errors.
Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
Network issues: Connectivity problems can prevent successful API calls; verify network access to the Outseta API endpoint.

Common error messages might include:

404 Not Found if the account UID does not exist.
400 Bad Request if the request body contains invalid data.
401 Unauthorized if authentication fails.

Resolving these usually involves verifying input parameters, credentials, and network connectivity.