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 CRM and business platform, specifically enabling the creation of new activities within Bitrix24. Activities in Bitrix24 represent various types of interactions or tasks such as calls, emails, meetings, or tasks associated with CRM entities like contacts, companies, deals, or leads.
Common scenarios for this node include automating the logging of communications or scheduling follow-ups directly from workflows, ensuring that all relevant activity data is captured in Bitrix24 without manual entry. For example, after a lead is qualified in an automation, this node can create a "Call" activity assigned to a sales representative to initiate contact.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook URL, or API Key. |
| Type | Type of activity to create. Options: Call, Email, Meeting, Task. |
| Owner Type | Type of entity that owns the activity. Options: Company, Contact, Deal, Lead. |
| Owner ID | ID of the specific entity (e.g., contact or deal) that owns the activity. |
| Subject | Subject or title of the activity. |
| Responsible ID | ID of the user responsible for the activity (optional). |
| Start Time | Start time of the activity (optional). |
| End Time | End time of the activity (optional). |
Output
The node outputs an array of items where each item contains a json object representing the created activity's details as returned by the Bitrix24 API. This typically includes identifiers and metadata confirming the successful creation of the activity.
If an error occurs and the node is configured to continue on failure, the output will contain an error message along with the resource name and a timestamp.
The node does not output binary data.
Dependencies
- Requires access to a Bitrix24 account with appropriate permissions to create activities.
- Requires one of the following authentication methods configured in n8n:
- OAuth2 credentials for Bitrix24
- Bitrix24 webhook URL
- Bitrix24 API key authentication
- The node uses Bitrix24 API endpoints internally to perform operations.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured and valid. OAuth2 tokens may expire and require refreshing.
- Invalid Owner ID or Owner Type: The specified owner entity must exist in Bitrix24; otherwise, the API call will fail. Verify IDs correspond to existing CRM entities.
- Missing required fields: The properties
Type,Owner Type,Owner ID, andSubjectare mandatory. Omitting these will cause errors. - API rate limits or connectivity issues: Network problems or Bitrix24 API limits may cause failures. Check network connectivity and Bitrix24 service status.
- Error messages: If the node throws an error, it usually includes the API error message. Use this to diagnose issues such as permission problems or invalid parameters.