Twenty CRMInstall

Overview

This node integrates with the Twenty CRM API to manage various CRM resources, including Opportunities. Specifically, the "Get" operation for the Opportunity resource retrieves a single opportunity record by its unique ID. This is useful when you want to fetch detailed information about a specific sales opportunity stored in your CRM system.

Common scenarios include:

• Retrieving opportunity details to display or process in workflows.
• Fetching an opportunity before updating or deleting it.
• Using opportunity data to trigger other automation steps based on its status or stage.

Example: You have an opportunity ID from a previous step and want to get all its details (name, amount, stage, probability, close date) to decide if a follow-up email should be sent.

Properties

Output

The output is a JSON object representing the retrieved opportunity record. It contains all fields available in the Twenty CRM opportunity resource, such as:

• name: Opportunity name
• amount: Monetary value associated with the opportunity
• stage: Current sales stage (e.g., New, Qualified, Proposal, Negotiation, Won, Lost)
• probability: Probability percentage of closing the deal
• closeDate: Expected close date of the opportunity

If the node is configured to return multiple records (in "getAll" operation), the output will be an array of such objects. For the "get" operation, the output is a single object wrapped in an array.

The node does not output binary data.

Dependencies

• Requires connection credentials to the Twenty CRM API, specifically an API key or token configured in n8n credentials.
• The node makes HTTP requests to the Twenty CRM REST API endpoint specified in the credentials.
• No additional external dependencies are needed.

Troubleshooting

• Invalid ID error: If the provided ID does not exist or is malformed, the API will return an error. Ensure the ID is correct and corresponds to an existing opportunity.
• Authentication errors: If the API credentials are missing or invalid, requests will fail. Verify that the API key/token is correctly set up in n8n credentials.
• JSON parsing errors: When using custom fields or filters (not applicable here but relevant for other operations), invalid JSON input can cause errors. Make sure JSON inputs are well-formed.
• API rate limits or connectivity issues: Network problems or API limits may cause request failures. Check network connectivity and API usage quotas.

Links and References

• Twenty CRM API Documentation (general reference for API endpoints and data structures)
• n8n Documentation - Creating Custom Nodes