Outseta icon

Outseta

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

Overview

This node interacts with the Outseta CRM API to update an existing deal record. It allows users to modify details of a deal such as its name, amount, pipeline stage, and associated account by specifying the unique identifier (UID) of the deal they want to update.

Common scenarios:

  • Updating the status or stage of a sales deal in your CRM.
  • Changing the deal amount after negotiation.
  • Associating a deal with a different account.
  • Renaming a deal to reflect updated contract terms.

Practical example:
You have a deal identified by UID abc123 that you want to rename to "Enterprise Contract" and update its amount to $50,000 while moving it to a new pipeline stage. This node lets you send those updates directly to Outseta CRM via its API.


Properties

Name Meaning
Deal UID The unique identifier of the deal to update (required).
Deal Name The new name for the deal.
Additional Fields Optional extra fields to update on the deal:
- Amount Numeric value representing the deal amount in dollars.
- Deal Pipeline Stage UID Unique identifier of the deal's pipeline stage to assign.
- Account UID Unique identifier of the account associated with the deal.

Output

The node outputs the JSON response from the Outseta CRM API after updating the deal. This typically includes the updated deal object with all its properties reflecting the changes made.

No binary data output is involved.


Dependencies

  • Requires an API key credential for authenticating with the Outseta CRM API.
  • Needs the domain URL of the Outseta instance configured in credentials.
  • The node sends HTTP PUT requests to the endpoint /crm/deals/{dealUid}.

Troubleshooting

  • Missing or invalid Deal UID: The update operation requires a valid deal UID. Ensure this is provided and correctly references an existing deal.
  • Authentication errors: Verify that the API key credential and domain are correctly set up and have sufficient permissions.
  • Invalid field values: For example, providing a non-numeric value for the amount or an invalid UID for pipeline stage/account may cause API errors.
  • Network issues: Check connectivity to the Outseta API endpoint.
  • API rate limits: If many updates are performed rapidly, you might hit rate limits imposed by Outseta.

Error messages returned by the API will usually indicate the specific problem, such as "Deal not found" or "Invalid field value," which should guide corrective actions.


Links and References

Discussion