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 integrates with the Bitrix24 platform, specifically enabling telephony-related operations. The "Add Voximplant SIP Line" operation allows users to add a new SIP line configured for Voximplant within their Bitrix24 telephony setup. This is useful for organizations that want to connect external SIP lines (using Voximplant) to their Bitrix24 telephony system, enabling calls through SIP infrastructure.
Practical scenarios include:
- Adding a new SIP line to route calls via Voximplant.
- Automating telephony configuration in Bitrix24 during deployment or scaling.
- Managing multiple SIP lines programmatically without manual UI interaction.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key authentication. |
| Line Name | The name assigned to the SIP line being added. |
| Line Number | The phone number associated with the SIP line. |
| SIP Server | The address of the SIP server to connect to (e.g., Voximplant SIP server). |
| SIP Login | The login username for the SIP account. |
| SIP Password | The password for the SIP account (input is masked for security). |
Output
The node outputs JSON data representing the result of the SIP line addition operation. This typically includes confirmation details from Bitrix24 about the newly created SIP line or error information if the operation failed.
No binary data output is involved.
Dependencies
- Requires valid authentication credentials for Bitrix24, which can be provided as an OAuth2 token, webhook URL, or API key.
- Access to the Bitrix24 telephony API with permissions to manage SIP lines.
- Network connectivity to Bitrix24 services and the specified SIP server.
Troubleshooting
- Authentication errors: Ensure the selected authentication method is correctly configured with valid credentials. OAuth2 is recommended for production use.
- Invalid SIP credentials: Verify the SIP server address, login, and password are correct and active.
- API call failures: Check network connectivity and Bitrix24 API availability.
- Permission issues: Confirm the authenticated user has rights to add SIP lines in Bitrix24.
- Error messages returned by the node will include the error message from Bitrix24's API. Use these messages to diagnose issues such as invalid parameters or quota limits.