Actions290
- Task Actions
- Direct API Actions
- CRM Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Get Entity
- Add Entity
- Update Entity
- Delete Entity
- Get Entity Rights
- Get Entity Sections
- Add Entity Section
- Update Entity Section
- Delete Entity Section
- Get Entity Item
- Add Entity Item
- Update Entity Item
- Delete Entity Item
- Get Entity Item Properties
- Add Entity Item Property
- Update Entity Item Property
- Delete Entity Item Property
- Chat Actions
- User Field Actions
- File Actions
- User Field Config Actions
- Duplicate Actions
- Timeline Actions
- Disk Actions
- Upload File
- Download File
- Delete File
- Get File Info
- List Files
- Create Folder
- Delete Folder
- Get Storage Info
- Get Storages
- Get Storage
- Get Folders
- Get Folder
- Add Folder
- Update Folder
- Copy Folder
- Move Folder
- Rename Folder
- Get Files
- Get File
- Copy File
- Move File
- Rename File
- Share Item
- Get Shared Items
- Get Sharing Rights
- Update Sharing Rights
- Workflow Actions
- Status Actions
- Calendar Actions
- Chatbot Actions
- Events Actions
- Lists Actions
- Product Actions
- Open Lines Actions
- Telephony Actions
- Register External Call
- Finish External Call
- Hide External Call
- Show External Call
- Search CRM Entities
- Attach Call Record
- Get External Line
- Add External Line
- Update External Line
- Delete External Line
- Get Voximplant Statistics
- Get Voximplant Line
- Get Voximplant SIP Connector
- Get Voximplant SIP Line
- Add Voximplant SIP Line
- Update Voximplant SIP Line
- Delete Voximplant SIP Line
- Message Service Actions
- Notify Actions
Overview
This node allows users to create an activity record in Bitrix24 CRM. Activities can be calls, emails, meetings, or tasks associated with various CRM entities such as companies, contacts, deals, or leads. This is useful for automating the logging of interactions and scheduling within Bitrix24, helping sales and support teams keep track of their communications and tasks.
Practical examples:
- Automatically log a call activity after a phone conversation with a contact.
- Schedule a meeting activity linked to a deal when a proposal is sent.
- Create a task activity assigned to a responsible user for follow-up actions.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key |
| Type | Type of activity to create: Call, Email, Meeting, Task |
| Owner Type | Type of entity that owns the activity: Company, Contact, Deal, Lead |
| Owner ID | ID of the entity that owns the activity |
| Subject | Subject or title of the activity |
| Responsible ID | ID of the user responsible for the activity |
| Start Time | Start time of the activity (date and time) |
| End Time | End time of the activity (date and time) |
Output
The node outputs an array of items where each item contains a json object representing the created activity's data returned from Bitrix24. The exact structure depends on Bitrix24's API response but typically includes identifiers, timestamps, and details of the created activity.
If the node encounters an error and "Continue On Fail" is enabled, it outputs an item with an error field describing the issue, along with the resource name and a timestamp.
No binary data output is produced by this node.
Dependencies
- Requires authentication credentials for Bitrix24 via one of these methods:
- OAuth2 token credential
- Webhook URL credential
- API key credential
- The node uses Bitrix24's REST API endpoints to create activities.
- Proper permissions in Bitrix24 are needed to create activities for the specified owner entities.
Troubleshooting
- Common issues:
- Invalid or expired authentication credentials will cause API call failures.
- Incorrect or missing Owner ID or Owner Type may result in errors or failure to associate the activity correctly.
- Missing required fields like Type, Owner ID, or Subject will prevent activity creation.
- Error messages:
- API errors from Bitrix24 will be surfaced in the node's error output if "Continue On Fail" is enabled.
- Errors related to invalid parameters or permissions should be checked against Bitrix24 user roles and API documentation.
- Resolution tips:
- Verify authentication credentials are valid and have necessary scopes.
- Double-check entity IDs and types exist in your Bitrix24 instance.
- Ensure all required properties are provided before execution.