Actions68
- Email Actions
- File Actions
- Note Actions
- Product Category Actions
- Task Actions
- Address Actions
- Company Actions
- Custom Record Actions
- Deal Actions
- Deal Item Actions
- Person Actions
- Phone Actions
- Product Actions
Overview
The "Create or Update Deal" operation in this node allows users to either create a new deal or update an existing one within the Arivo CRM system. This is particularly useful for sales and business development teams who want to automate managing their sales pipeline by programmatically adding new deals or updating details of ongoing deals based on matching criteria (such as the deal name).
Typical scenarios include:
- Automatically creating a new sales deal when a lead reaches a certain stage.
- Updating an existing deal's status, value, or other attributes when new information becomes available.
- Synchronizing deals from external systems into Arivo CRM without duplicating entries.
For example, you could use this node to create a deal named "Software License Deal" with an estimated value and assign it to a specific sales pipeline and user. If a deal with the same name already exists, it will be updated instead of creating a duplicate.
Properties
| Name | Meaning |
|---|---|
| Deal Name | The name of the deal used to identify and match existing deals. Required field. Example: "Software License Deal". |
| Additional Fields | A collection of optional fields to provide more details about the deal: |
| - Description | Text description of the deal, e.g., "Annual software license renewal for 100 users". |
| - Value | Estimated monetary value of the deal (number). |
| - Company ID | Identifier of the client company associated with the deal. |
| - Contact ID | Identifier of the main contact person for the deal. |
| - Status | Current status of the deal. Options: "Open", "Won", "Lost". Default is "Open". |
| - Temperature | Indicates the probability of success. Options: "Cold", "Warm", "Hot". Default is "Warm". |
| - Opened At | Date/time when the deal was opened, in ISO-8601 format. |
| - Estimated Close Date | Expected closing date of the deal, in ISO-8601 format. |
| - Pipeline Name or ID | Sales pipeline to which the deal belongs. Can be selected from a list or specified by ID using expressions. |
| - Tags | Comma-separated tags associated with the deal. |
| - User Name or ID | User assigned to the deal. Selectable from a list or specified by ID using expressions. |
| - Team Name or ID | Team assigned to the deal. Selectable from a list or specified by ID using expressions. |
| - Custom Fields | Allows adding multiple custom fields by specifying field names or IDs and their corresponding values. Useful for extending deal data with organization-specific attributes. |
Output
The node outputs JSON objects representing the created or updated deal(s). Each output item corresponds to one input item processed.
The JSON structure typically includes all standard and custom fields of the deal as stored in Arivo CRM, such as:
- Deal identifiers
- Name
- Description
- Value
- Status
- Temperature
- Associated company and contact IDs
- Pipeline and user/team assignments
- Dates (opened at, estimated close)
- Tags
- Custom fields and their values
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate with the Arivo CRM API.
- The node depends on Arivo CRM's REST API endpoints for deals.
- Some properties load options dynamically (e.g., pipelines, users, teams, custom fields), so network connectivity and proper API permissions are necessary.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication errors.
- Providing an invalid or non-existent pipeline, user, team, or custom field ID may result in API errors.
- Incorrect date formats for "Opened At" or "Estimated Close Date" can cause validation failures.
- Attempting to update a deal that does not exist (when relying on matching by deal name) might create duplicates if matching fails.
Error messages:
- Authentication errors: Check that the API key credential is correctly set up and has sufficient permissions.
- Validation errors: Verify that required fields are provided and that dates follow ISO-8601 format.
- Not found errors: Ensure referenced entities like companies, contacts, pipelines, users, and teams exist in Arivo CRM.
To resolve issues, verify input data correctness, ensure API credentials are valid, and check network connectivity.
Links and References
- Arivo CRM API Documentation (hypothetical link as no direct link provided)
- n8n Expressions Documentation
- ISO 8601 Date Format