Twenty CRMInstall

Overview

This node integrates with the Twenty CRM API to manage various CRM resources such as workflows, companies, people, opportunities, tasks, notes, calendar events, messages, attachments, and custom resources. Specifically for the Workflow resource with the Get operation, it retrieves a single workflow record by its unique ID.

Common scenarios where this node is beneficial include:

• Fetching detailed information about a specific workflow in your CRM to use in automation or reporting.
• Integrating workflow data into other systems or processes within an n8n workflow.
• Triggering actions based on the properties of a particular workflow.

Example: You want to retrieve a workflow by its ID to check its status or details before proceeding with further automation steps.

Properties

Output

The node outputs the retrieved workflow record as JSON data. The output structure corresponds directly to the workflow object returned by the Twenty CRM API, containing all available fields and their values for that workflow.

If multiple items are processed, each item's output will be an individual JSON object representing the respective workflow.

No binary data output is produced by this node.

Dependencies

• Requires an API key credential for authenticating with the Twenty CRM API.
• The node uses the base API URL configured in the credentials.
• No additional external dependencies beyond the Twenty CRM API and n8n's HTTP request helper.

Troubleshooting

• Invalid or missing ID: 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 workflow.
• Authentication errors: If the API key credential is invalid or expired, requests will fail. Verify the credential configuration.
• API rate limits or connectivity issues: Network problems or API limits may cause failures. Check network connectivity and API usage quotas.
• JSON parsing errors: Although unlikely for the Get operation, if any JSON input is malformed (in other operations), errors will be thrown.

Error messages from the node typically include the API response message. To resolve, verify inputs, credentials, and API availability.

Links and References

• Twenty CRM API Documentation (general reference for API endpoints and data structures)
• n8n HTTP Request Node Documentation (for understanding HTTP request handling in n8n)

This summary focuses on the Workflow resource with the Get operation as requested. Other resources and operations are supported but not detailed here.