Twenty CRMInstall

Overview

This node integrates with the Twenty CRM API to manage various CRM resources such as companies, people, opportunities, tasks, notes, and more. Specifically, for the Task resource with the Get operation, it retrieves a single task record by its unique ID.

Common scenarios where this node is useful include:

• Fetching detailed information about a specific task in your CRM workflow.
• Automating workflows that require task data retrieval for further processing or decision-making.
• Integrating task details into other systems or reports.

For example, you might use this node to get the status, due date, and description of a task before sending a reminder email or updating another system.

Properties

Output

The node outputs the retrieved task data as JSON. The structure corresponds to the task object returned by the Twenty CRM API, typically including fields like:

• id: Task unique identifier
• title: Title of the task
• bodyV2: Task description in markdown format
• status: Current status of the task (e.g., To Do, In Progress, Done)
• dueAt: Due date/time of the task
• Other metadata fields related to the task

If the node is configured to fetch multiple records (Get Many), it returns an array of such task objects. For the Get operation, it returns a single task object wrapped in an array for n8n compatibility.

The node does not output binary data.

Dependencies

• Requires an API key credential for authenticating with the Twenty CRM API.
• The node expects the API base URL and authentication to be configured via this credential.
• No additional external dependencies are needed beyond the Twenty CRM API access.

Troubleshooting

• Invalid ID error: If the provided task ID does not exist or is malformed, the API will return an error. Ensure the ID is correct and exists in your Twenty CRM account.
• Authentication errors: If the API key credential is missing or invalid, requests will fail. Verify that the credential is properly set up and has necessary permissions.
• JSON parsing errors: When using custom JSON fields (not applicable for Get operation), invalid JSON input can cause errors.
• API rate limits or connectivity issues: Network problems or API limits may cause request failures. Check network connectivity and API usage quotas.

If the node encounters an error during execution, it either throws an error or, if "Continue On Fail" is enabled, returns an error object in the output for that item.

Links and References

• Twenty CRM API Documentation (for detailed API endpoints and data structures)
• n8n Documentation (for general node usage and credential setup)