Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Opportunity → Update
AI-generatedOverview
This node integrates with the Twenty CRM API to manage Opportunity records. Specifically, the Update operation allows users to modify existing opportunities by specifying their ID and updating fields such as opportunity name, amount, stage, probability, and close date.
Typical use cases include:
- Adjusting the details of a sales opportunity as it progresses through different stages.
- Updating financial figures or expected close dates based on new information.
- Automating CRM updates from other systems or workflows to keep opportunity data current.
For example, you might use this node in an automation that updates an opportunity’s stage to "Won" and sets the close date when a deal is finalized.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the opportunity record to update (required). |
| Opportunity Name | The name/title of the opportunity (required). |
| Amount | The monetary value associated with the opportunity. |
| Stage | The current phase of the opportunity in the sales process. Options: New, Qualified, Proposal, Negotiation, Won, Lost. |
| Probability | The likelihood (percentage 0-100) that the opportunity will close successfully. |
| Close Date | The expected or actual closing date of the opportunity (date-time format). |
Output
The node outputs JSON data representing the updated opportunity record as returned by the Twenty CRM API. This typically includes all fields of the opportunity after the update has been applied.
If multiple input items are processed, the output is an array of such JSON objects, each corresponding to one updated opportunity.
No binary data output is produced by this node.
Dependencies
- Requires connection credentials for the Twenty CRM API, including an API URL and an authentication token.
- The node uses HTTP PATCH requests to update opportunity records via the Twenty CRM REST API endpoint.
- Proper configuration of the API credential in n8n is necessary for successful communication.
Troubleshooting
- Invalid JSON in Fields: If custom fields JSON is malformed (not applicable here but relevant for custom resource updates), the node throws an error. Ensure JSON syntax correctness.
- Missing Required Fields: The node requires the
IDandOpportunity Namefields for update operations. Omitting these will cause errors. - API Authentication Errors: If credentials are incorrect or expired, the node will fail to authenticate. Verify API key/token validity.
- HTTP Errors: Network issues or invalid IDs may result in HTTP errors. Check the ID exists and the API endpoint is reachable.
- Stage Value Restrictions: The
Stageproperty must be one of the predefined options; invalid values will cause request failures.
Links and References
- Twenty CRM API Documentation (general reference for API endpoints and data models)
- n8n Documentation - Creating Custom Nodes (for understanding node development concepts)
If you need further details about other operations or resources, feel free to ask!