Actions46
- Company Actions
- Person Actions
- Opportunity Actions
- Task Actions
- Note Actions
- Calendar Event Actions
- Message Actions
- Attachment Actions
- Workflow Actions
- Custom Actions
Workflow → Delete
AI-generatedOverview
This node integrates with the Twenty CRM API to manage various CRM resources, including workflows. Specifically, for the Workflow resource and the Delete operation, it deletes a workflow record identified by its ID. This is useful in scenarios where you want to programmatically remove obsolete or incorrect workflows from your CRM system.
Practical examples:
- Automatically deleting workflows that are no longer needed after a project completion.
- Cleaning up test or temporary workflows created during automation testing.
- Removing workflows based on certain conditions detected in upstream nodes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the workflow record to delete. This is required to specify which workflow should be removed. |
Output
The node outputs JSON data representing the response from the Twenty CRM API after attempting to delete the workflow. Typically, this will confirm successful deletion or provide error details if the operation failed.
If the node encounters an error and "Continue On Fail" is enabled, the output JSON will include an error field describing the issue along with the resource and operation names.
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 perform CRUD operations on CRM resources.
- The base URL for the API is obtained from the credential configuration (
apiUrl).
Troubleshooting
- Invalid ID: If the provided workflow 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 missing, invalid, or expired, requests will fail. Verify the credential setup in n8n.
- API rate limits or connectivity issues: Network problems or API throttling can cause failures. Check network connectivity and API usage limits.
- JSON parsing errors: Although not typical for delete, other operations involving JSON input may throw errors if the JSON is malformed.
- To handle errors gracefully, enable "Continue On Fail" in the node settings to capture error messages in the output instead of stopping execution.
Links and References
- Twenty CRM API Documentation (general reference for API endpoints and authentication)
- n8n Documentation - Creating Custom Nodes (for understanding node development and usage)
This summary focuses on the Workflow resource's Delete operation as requested, based on static analysis of the provided source code and property definitions.