Connection in 5 minutes, 30 days on tests, try.
Free Turnkey setting, Instructions.
Click on the name of the event to see the available fields.
API documentation — here.
Not
Id | Name |
---|---|
callDetails.companyID
|
Company number in the Binotel virtual PBX |
callDetails.generalCallID
|
The call ID |
callDetails.startTime
|
The start time of the call in Unix time format |
callDetails.callType
|
Call type: incoming - 0, outgoing - 1 |
callDetails.internalNumber
|
The internal number of the employee/group in the virtual PBX (if the call was not received) |
callDetails.internalAdditionalData
|
The group number in the virtual PBX (if the call was received) |
callDetails.externalNumber
|
Customer's phone number |
callDetails.waitsec
|
Waiting until connection |
callDetails.billsec
|
The duration of the conversation |
callDetails.disposition
|
The status of the call |
callDetails.isNewCall
|
Incoming call is new - 1, previously called - 0 |
callDetails.customerData.name
|
Client's name |
callDetails.customerData.email
|
Client's email address |
callDetails.employeeData.name
|
Employee's name |
callDetails.employeeData.email
|
Employee's email address |
callDetails.pbxNumberData.number
|
The phone number to which the call came or from which the call was made |
callDetails.pbxNumberData.name
|
Name of the phone number |
callDetails.historyData
|
Call history details |
+ You can add your fields that are in webhuk.
If you haven't found the right event, but the service has the right webhook, then use the universal connector "Including webhuk". It will be possible to tie the logic of bundles to any field that comes in the webhook.
Click on the name of the action to see the available fields.
API documentation — No.
Id | Name |
---|---|
email
|
|
phone
|
Telephone |
name
|
Name |
amount
|
The amount of the transaction |
yandex_client_id
|
Yandex client id (_ym_uid) |
google_client_id
|
Google client id (_ga) |
facebook_client_id
|
Facebook client id (_fbp) |
utm_source
|
Utm source |
utm_medium
|
Utm medium |
utm_campaign
|
Utm campaign |
utm_content
|
Utm content |
utm_term
|
Utm term |
url
|
The URL where the request was left |
content
|
Transcript of the call/chat |
external_lead_id
|
Lead ID/transactions from an external CRM |
Id | Name |
---|---|
id
|
Lead ID |
Id | Name |
---|---|
email
|
|
phone
|
Telephone |
domain
|
Application domain |
route
|
The URL of the application page without parameters |
url
|
Url of the application page |
external_lead_id
|
Lead ID/transactions from an external CRM |
Id | Name |
---|---|
id
|
Lead ID |
email
|
|
phone
|
Telephone |
name
|
Name |
amount
|
The amount of the transaction |
yandex_client_id
|
Yandex client id (_ym_uid) |
google_client_id
|
Google client id (_ga) |
facebook_client_id
|
Facebook client id (_fbp) |
utm_source
|
Utm source |
utm_medium
|
Utm medium |
utm_campaign
|
Utm campaign |
utm_content
|
Utm content |
utm_term
|
Utm term |
1 | Configure the connection for: Service in Apimonster. |
2 | Configure Webhuk in: Service, indicating the link from Apimonster. |
3 | Configure the connection for: Service in Apimonster, indicating the login/password/token for access to the API. |
4 | Create a bunch. |
5 | Indicate as a data source: Service. |
6 | Create the required action for: to_Service, indicating in which fields: to_Service to transmit field values from: from_Service. |
7 | Configure filters for each step if necessary. |
8 | Test the bundles and make sure that they work according to the TOR. |
Or go through the full well on ApiMonster.
Ready-made customized bundles for popular business tasks