Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
This node integrates with the Bitrix24 platform, specifically allowing users to add comments to tasks within Bitrix24. It supports multiple authentication methods including OAuth2, webhook URLs, and API keys, making it flexible for different security and deployment scenarios.
A common use case is automating task collaboration by programmatically appending comments to tasks based on external triggers or workflows. For example, when a customer support ticket is updated in another system, this node can add a comment to the corresponding Bitrix24 task to keep all team members informed.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler), or API Key |
| Task ID | The unique identifier of the task to which the comment will be added |
| Comment Text | The text content of the comment to add |
| Options | Additional optional parameters as JSON objects: |
| - Filter | JSON filter criteria (not typically used for adding comments) |
| - Order | JSON sort order (not typically used for adding comments) |
| - Select | JSON array specifying fields to select (not typically used for adding comments) |
| - Group | JSON group criteria (not typically used for adding comments) |
| - Custom Parameters | Additional custom parameters in JSON format |
| - Access Token | Optional access token string for authentication override |
Output
The node outputs an array of items where each item contains a json object representing the response from Bitrix24 after adding the comment. This typically includes confirmation details such as the comment ID or status.
If an error occurs and "Continue On Fail" is enabled, the output will contain an error message along with the resource name and a timestamp.
No binary data output is involved in this operation.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods.
- Needs network access to Bitrix24 API endpoints.
- No additional external services beyond Bitrix24 are required.
- Proper configuration of authentication credentials in n8n is necessary.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect Task ID causing "task not found" errors.
- Malformed JSON in optional parameters causing request failures.
Error Messages:
- Authorization errors: Check that the selected authentication method is correctly configured and tokens are valid.
- Task not found: Verify the Task ID is correct and the task exists in Bitrix24.
- JSON parsing errors: Ensure any JSON input in options is well-formed.
Resolution Tips:
- Refresh or reconfigure authentication credentials if authorization fails.
- Double-check Task ID values.
- Use JSON validators to verify optional parameter inputs.