Actions46
- Company Actions
- Note Actions
- Note Relation Actions
- Opportunity Actions
- Person Actions
- Pipeline Actions
- Task Actions
- Task Relation Actions
Opportunity → Update
AI-generatedOverview
This node updates an existing Opportunity record in the Dalil AI system. It allows users to specify the Opportunity by its UUID and update various fields such as name, amount, close date, company association, currency code, custom properties, owner, point of contact, and stage. The node supports specifying the depth of nested related objects to include in the response. This is useful for workflows that need to modify opportunity details dynamically, such as updating sales pipeline stages or financial amounts based on external triggers or data.
Use Case Examples
- Updating the amount and close date of a specific opportunity identified by its UUID.
- Changing the stage of an opportunity to 'CLOSED_WON' after a successful deal closure.
- Modifying custom properties of an opportunity to reflect new business insights or client feedback.
Properties
| Name | Meaning |
|---|---|
| Opportunity Name or ID | UUID string of the opportunity to update. Choose from the list or specify an ID using an expression. |
| Update Fields | Collection of fields to update on the opportunity, including amount, close date, company, currency code, custom properties, name, owner, point of contact, and stage. |
| Depth Name or ID | Level of nested related objects to include in the response: 0 (opportunity only), 1 (opportunity + direct relations), 2 (opportunity + relations + their relations). |
Output
JSON
json- The updated opportunity object returned from the Dalil AI API, including any nested related objects as specified by the depth parameter.
Dependencies
- Dalil AI API
- an API key credential for authentication
Troubleshooting
- Ensure the opportunityId is a valid UUID and exists in the Dalil AI system to avoid 'not found' errors.
- Verify that the custom properties provided match the expected data types and formats to prevent validation errors.
- Check API authentication credentials if requests fail due to authorization issues.
- If the depth parameter is set too high, the response might be large and slow; adjust accordingly.