Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

This node integrates with the Bitrix24 platform, specifically allowing users to delete a Task resource. It is useful in automation workflows where tasks need to be programmatically removed from Bitrix24 based on certain conditions or triggers.

Common scenarios include:

  • Automatically cleaning up completed or obsolete tasks.
  • Removing tasks that were created in error.
  • Managing task lifecycle within larger CRM or project management automations.

For example, after a deal is closed, you might want to delete all related tasks automatically using this node.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication.
Task ID The unique identifier of the task to delete. This is required.
Options Additional optional parameters as JSON objects:
- Filter JSON object specifying filter criteria (not typically used for delete operation).
- Order JSON object specifying sort order (not typically used for delete operation).
- Select JSON array specifying which fields to select (not typically used for delete operation).
- Group JSON object specifying group criteria (not typically used for delete operation).
- Custom Parameters JSON object for any additional custom parameters to pass to the API call.

Output

The node outputs an array of items corresponding to the processed requests. Each item contains a json field with the response data from Bitrix24 regarding the deletion operation.

If the deletion is successful, the output typically includes confirmation details from Bitrix24's API.

In case of failure and if "Continue On Fail" is enabled, the output will contain an error object with:

  • error: The error message.
  • resource: The resource name ("task").
  • timestamp: The ISO timestamp when the error occurred.

No binary data output is produced by this node.

Dependencies

  • Requires a valid Bitrix24 authentication method configured in n8n:

    • An OAuth2 credential,
    • Or a webhook URL credential,
    • Or an API key credential.
  • The node uses Bitrix24's REST API endpoints to perform operations.

  • No additional external dependencies beyond standard HTTP API calls.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication credentials will cause API call failures.
    • Providing an incorrect or non-existent Task ID will result in errors indicating the task was not found.
    • Network connectivity issues can prevent communication with Bitrix24 API.
  • Error messages:

    • "Task not found": Verify the Task ID is correct and the task exists.
    • "Authentication failed": Check that the provided credentials are valid and have necessary permissions.
    • "API rate limit exceeded": Wait and retry later or adjust workflow frequency.
  • To handle errors gracefully, enable "Continue On Fail" in the node settings to capture error details without stopping the entire workflow.

Links and References

Discussion