TwentyDEV icon

TwentyDEV

Consume the Twenty API

Actions252

Overview

This node allows you to delete a specific workflow run by its unique identifier. It is useful in scenarios where you need to programmatically remove workflow execution records, for example, to clean up old or erroneous runs, manage storage, or maintain data hygiene within your automation environment.

A practical example would be deleting a failed workflow run after troubleshooting is complete, ensuring that only relevant and successful runs remain visible in your system.

Properties

Name Meaning
Id The unique identifier of the workflow run to delete. This is a required string value representing the object id of the workflow run.

Output

The node outputs JSON data representing the result of the deletion operation. Typically, this will confirm whether the workflow run was successfully deleted or provide error information if the deletion failed.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential to authenticate requests against the external service managing workflow runs.
  • The node depends on a configured base URL (domain) provided via credentials to target the correct API endpoint.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent workflow run ID will cause the deletion to fail.
    • Missing or incorrect API authentication credentials will prevent the node from executing successfully.
    • Network connectivity problems can also cause request failures.
  • Error messages:

    • "Workflow run not found" indicates the specified ID does not exist; verify the ID before retrying.
    • Authentication errors suggest invalid or missing API keys; ensure credentials are correctly set up.
    • Timeout or connection errors require checking network access and API availability.

Links and References

  • Refer to the API documentation of the service managing workflow runs for detailed information on the delete operation and error codes.
  • Consult n8n's official documentation on setting up API credentials and handling HTTP request nodes for additional context.

Discussion