Integration Plusofon (Plusophone) and Binotel (Binotel)

Connection in 5 minutes, 30 days on tests, try.

Accepted webhooks
Done actions
New clients

Try 30 days free

Free Turnkey setting, Instructions.

What data can be transmitted from: from_Service to: to_Service

Important: Please note that the presence of events and actions between the two services does not guarantee a solution your task - the available events and actions may not connect with each other in the way you need.

If you cannot independently determine whether these events and actions will be able to solve your problem; contact support or use the Full construction setting.

Events c Plusofon

Click on the name of the event to see the available fields.

API documentation — here.

Description

Not

Available fields
Id Name
call_id The unique identifier of the call
start The sign of the main shoulder (the first in the chain): yes (1) or no (0)
timestamp A timestamp in Unix Timestamp format
from The caller's number
to The number of the called subscriber
account_id The unique identifier of the agreement
authorizing_id The unique identifier of the device that received the call
bridge_id Only for start = 0, the unique identifier (call_id) of the previous call shoulder helps to track call transfers
+ You can add your fields that are in webhuk.

Description

Not

Available fields
Id Name
call_id The unique identifier of the call
start The sign of the main shoulder (the first in the chain): yes (1) or no (0)
timestamp A timestamp in Unix Timestamp format
from The caller's number
to The number of the called subscriber
account_id The unique identifier of the agreement
authorizing_id The unique identifier of the device that received the call
bridge_id Only for start = 0, the unique identifier (call_id) of the previous call shoulder helps to track call transfers
+ You can add your fields that are in webhuk.

Description

Not

Available fields
Id Name
call_id The unique identifier of the call
start The sign of the main shoulder (the first in the chain): yes (1) or no (0)
finish The sign of the final leverage: yes (1) or no (0)
is_success The sign of a successful call: yes (1) or no (0)
duration Duration of the call
timestamp A timestamp in Unix Timestamp format
from The caller's number
to The number of the called subscriber
internal Internal (extension) number of the SIP account
account_id The unique identifier of the agreement
authorizing_id The unique identifier of the device that received the call
bridge_id Only for start = 0, the unique identifier (call_id) of the previous call shoulder helps to track call transfers
+ You can add your fields that are in webhuk.

Description

Not

Available fields
Id Name
call_id The unique identifier of the call
timestamp A timestamp in Unix Timestamp format
from The caller's number
to The number of the called subscriber
account_id The unique identifier of the agreement
authorizing_id The unique identifier of the device from which the call came
+ You can add your fields that are in webhuk.

Description

Not

Available fields
Id Name
call_id The unique identifier of the call
is_success The sign of a successful call: yes (1) or no (0)
duration Duration of the call
timestamp A timestamp in Unix Timestamp format
from The caller's number
to The number of the called subscriber
internal Internal (extension) number of the SIP account
account_id The unique identifier of the agreement
authorizing_id The unique identifier of the device from which the call came
+ You can add your fields that are in webhuk.

Description

Not

Available fields
Id Name
call_id The unique identifier of the call
is_success The sign of a successful call: yes (1) or no (0)
duration Duration of the call
timestamp A timestamp in Unix Timestamp format
from The caller's number
to The number of the called subscriber
internal Internal (extension) number of the SIP account
account_id The unique identifier of the agreement
authorizing_id The unique identifier of the device from which the call came
+ 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.

Actions in Binotel

Click on the name of the action to see the available fields.

API documentation — No.

There are no actions, try Change to replace the services.

Swap Plusofon with Binotel

Refract turnkey

View opportunities Plusofon

View opportunities Binotel

Integration setup plan Plusofon with Binotel

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.

Check out other ApiMonster features

NoCodeStore - a store of ready-made no-code solutions

Ready-made customized bundles for popular business tasks