Twenty CRM icon

Twenty CRM

Connect with Twenty CRM API

Opportunity → Create

AI-generated

Overview

This node integrates with the Twenty CRM API to manage CRM data programmatically within n8n workflows. Specifically, for the Opportunity - Create operation, it allows users to create new sales opportunities in their Twenty CRM account. This is useful for automating lead and deal management processes, such as adding new potential sales deals from form submissions, marketing campaigns, or other automated triggers.

Practical examples include:

  • Automatically creating an opportunity when a new lead fills out a web form.
  • Adding opportunities based on events in other systems like email marketing platforms or customer support tools.
  • Integrating with sales pipelines to keep opportunity data synchronized across multiple tools.

Properties

Name Meaning
Opportunity Name The name/title of the opportunity being created. (Required)
Amount The monetary value associated with the opportunity.
Stage The current stage of the opportunity in the sales pipeline. Options: New, Qualified, Proposal, Negotiation, Won, Lost
Probability The likelihood (percentage 0-100) that the opportunity will close successfully.
Close Date The expected closing date/time for the opportunity.

Output

The node outputs JSON data representing the newly created opportunity record as returned by the Twenty CRM API. This typically includes all fields of the opportunity such as its unique ID, name, amount, stage, probability, close date, and any other metadata provided by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Twenty CRM API via an API key credential configured in n8n.
  • The node uses HTTP requests authenticated with this credential to communicate with the Twenty CRM REST API endpoint.
  • The base URL for the API is dynamically obtained from the credential configuration.

Troubleshooting

  • Invalid JSON in Fields: If using custom fields (not applicable here but relevant for custom resource operations), ensure the JSON string is valid. Malformed JSON will cause errors.
  • Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions to create opportunities.
  • Required Fields Missing: The "Opportunity Name" is mandatory; omitting it will result in an error.
  • API Rate Limits or Network Issues: Temporary failures may occur due to network problems or API rate limiting; retrying after some time can help.
  • Date Format Issues: The "Close Date" must be in a valid ISO 8601 datetime format; invalid formats may cause request failures.

Links and References

Discussion