Arivo CRM icon

Arivo CRM

Create and edit data in Arivo CRM

Actions68

Overview

The node allows updating an existing deal in Arivo CRM by specifying the deal's unique identifier and the fields to update. This operation is useful for managing sales pipelines, tracking deal progress, and maintaining accurate records of client interactions.

Common scenarios include:

  • Changing the status of a deal (e.g., from "Open" to "Won" or "Lost").
  • Updating financial details such as estimated value or close dates.
  • Assigning deals to different users or teams.
  • Adding or modifying custom fields specific to business needs.

Practical example: Automatically update a deal's status to "Won" and set the closed date when a payment is received, ensuring the CRM reflects the latest sales information.

Properties

Name Meaning
Deal ID The unique identifier of the deal to update.
Update Fields A collection of fields that can be updated on the deal:
- Deal Name The name/title of the deal (e.g., "Software License Deal").
- Description Text description providing details about the deal (e.g., "Annual software license renewal for 100 users").
- Value Estimated monetary value of the deal.
- Company ID Identifier of the client company associated with this deal.
- Contact ID Identifier of the main contact person for this deal.
- Status Current status of the deal. Options: "Open", "Won", "Lost".
- Temperature Indicates the probability of success. Options: "Cold", "Warm", "Hot".
- Opened At Date/time when the deal was opened, in ISO-8601 format.
- Estimated Close Date Expected date/time when the deal will close, in ISO-8601 format.
- Closed At Date/time when the deal was closed, in ISO-8601 format.
- Pipeline Step Name or ID The pipeline step to which the deal should be moved. Can be selected from a list or specified via expression.
- Tags Comma-separated tags associated with the deal.
- User Name or ID The user assigned to manage this deal. Selectable from a list or via expression.
- Team Name or ID The team responsible for this deal. Selectable from a list or via expression.
- Custom Fields Multiple custom fields can be added or updated. Each custom field requires a field name or ID and its corresponding value.

Output

The node outputs JSON data representing the updated deal object as returned by the Arivo CRM API. This typically includes all current properties of the deal after the update, such as IDs, names, statuses, dates, values, assigned users/teams, tags, and any custom fields.

No binary data output is involved.

Dependencies

  • Requires an active connection to Arivo CRM via an API key credential configured in n8n.
  • The node depends on Arivo CRM's API endpoints for deals.
  • Some property options (like pipeline steps, users, teams, and custom fields) are dynamically loaded using internal methods that query Arivo CRM.

Troubleshooting

  • Invalid Deal ID: If the provided Deal ID does not exist, the API may return an error indicating the deal was not found. Verify the ID is correct.
  • Permission Errors: Insufficient permissions or invalid API credentials can cause authorization errors. Ensure the API key has appropriate access rights.
  • Invalid Field Values: Providing incorrect formats (e.g., non-ISO dates) or unsupported values for fields like status or temperature may result in validation errors.
  • Empty Update Fields: Attempting to update without specifying any fields may lead to no changes or errors. Always provide at least one field to update.
  • API Rate Limits: Frequent updates might hit rate limits imposed by Arivo CRM; handle such errors by retrying after some delay.

Links and References

Discussion