Twenty CRMInstall

Overview

This node integrates with the Twenty CRM API to manage various CRM resources such as workflows, companies, people, opportunities, tasks, notes, and more. Specifically for the Workflow - Update operation, it allows updating an existing workflow record by its ID. This is useful when you need to modify details of a workflow already stored in Twenty CRM without creating a new one.

Common scenarios include:

• Updating workflow metadata or status after changes in your business process.
• Synchronizing workflow information from other systems into Twenty CRM.
• Automating updates to workflows based on triggers or events in n8n.

Example: You have a workflow in Twenty CRM that tracks customer onboarding steps. When a step completes, you use this node to update the workflow’s status or add notes programmatically.

Properties

Note: The provided properties JSON only includes the ID property relevant for the update operation on the Workflow resource.

Output

The node outputs the updated workflow record as JSON data. The structure corresponds to the response from the Twenty CRM API's workflow endpoint after a successful PATCH request. It typically contains fields representing the workflow's current state and attributes.

If multiple input items are processed, the output is an array of JSON objects, each corresponding to the updated workflow for each input item.

No binary data output is produced by this node.

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 perform operations on the Twenty CRM REST API.
• No additional external dependencies beyond the Twenty CRM API and n8n credentials system.

Troubleshooting

• Invalid JSON in Fields: If updating custom resources or fields (not applicable here since only Workflow update is requested), malformed JSON in the "Fields JSON" property will cause errors. Ensure valid JSON syntax.
• Missing or Incorrect ID: The update operation requires a valid workflow ID. Providing an empty or incorrect ID will result in API errors indicating the record was not found.
• API Authentication Errors: If the API key credential is missing, invalid, or expired, authentication errors will occur. Verify the credential configuration in n8n.
• HTTP Request Failures: Network issues or API downtime can cause request failures. Check connectivity and Twenty CRM service status.
• Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output JSON.

Links and References

• Twenty CRM API Documentation (general reference for API endpoints and data structures)
• n8n Documentation (for configuring credentials and using HTTP Request nodes)

This summary focuses on the Workflow resource's Update operation as requested, describing the input, output, and behavior based on static analysis of the provided source code.