Integration Leadback (Leadback) and FreshOffice (Fresh office)
Connection in 5 minutes, 30 days on tests, try.
Accepted webhooks
Done actions
New clients
Free Turnkey setting, Instructions.
What data can be transmitted from: from_Service to: to_Service
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 Leadback
Click on the name of the event to see the available fields.
API documentation — here.
Description
Not
Available fields
| Id | Name |
|---|---|
event_type
|
Type of event |
data.id_call
|
Call ID |
data.user_id
|
Client ID |
data.widget_id
|
Widget ID |
data.date_create
|
Date and time when the call request was created |
data.date_update
|
Date and time of the last update of the call information |
data.callback_phone
|
The phone number of the person who ordered the callback |
data.operator_phone
|
The phone number of the employee who received the call |
data.site
|
The domain of the site where the callback was ordered |
data.user_tariff
|
The client's tariff |
data.tariffed_minutes
|
Minutes spent in connection with the account balance |
data.duration
|
The duration of the conversation in seconds |
data.record_url
|
Link to the conversation recording |
data.callback_answer
|
The person who ordered the call answered it (no - no, yes - yes) |
data.visit_uuid
|
User ID |
data.visit_id
|
Session ID |
data.visit_ip
|
IP address of the person who ordered the callback |
data.visit_source
|
The source of the call |
data.delayed_time
|
The date and time to which the call was rescheduled (if the call was ordered outside business hours) |
data.status
|
Call status (complete - accepted, failed - missed) |
data.call_time
|
The date and time when the call took place |
data.visit_data
|
Full information about the source of the call |
data.visit_profile
|
User data if filled in in the online chat form (name, email and phone number) |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
event_type
|
Type of event |
data.id_call
|
Call ID |
data.user_id
|
Client ID |
data.widget_id
|
Widget ID |
data.date_create
|
Date and time when the call request was created |
data.date_update
|
Date and time of the last update of the call information |
data.callback_phone
|
The phone number of the person who ordered the callback |
data.operator_phone
|
The phone number of the employee who received the call |
data.site
|
The domain of the site where the callback was ordered |
data.user_tariff
|
The client's tariff |
data.tariffed_minutes
|
Minutes spent in connection with the account balance |
data.duration
|
The duration of the conversation in seconds |
data.record_url
|
Link to the conversation recording |
data.callback_answer
|
The person who ordered the call answered it (no - no, yes - yes) |
data.visit_uuid
|
User ID |
data.visit_id
|
Session ID |
data.visit_ip
|
IP address of the person who ordered the callback |
data.visit_source
|
The source of the call |
data.delayed_time
|
The date and time to which the call was rescheduled (if the call was ordered outside business hours) |
data.status
|
Call status (complete - accepted, failed - missed) |
data.call_time
|
The date and time when the call took place |
data.visit_data
|
Full information about the source of the call |
data.visit_profile
|
User data if filled in in the online chat form (name, email and phone number) |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
event_type
|
Type of event |
data.widget_id
|
Widget ID |
data.user_id
|
Client ID |
data.dialog_id
|
Dialog ID |
data.chat_log
|
Messages of the user's correspondence with the operator |
data.operator.id_operator
|
Operator ID |
data.operator.operator_jid
|
Operator's login |
data.operator.operator_name
|
Operator's name |
data.operator.avatar_type
|
Avatar type (custom, standart) |
data.operator.avatar_url
|
The address to the operator's avatar |
data.visit_data
|
Full information about the source of the visitor's visit |
data.visit_profile
|
User data if filled in in the online chat form (name, email and phone number) |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
event_type
|
Type of event |
data.widget_id
|
Widget ID |
data.user_id
|
Client ID |
data.dialog_id
|
Dialog ID |
data.chat_log
|
Messages of the user's correspondence with the operator |
data.visit_data
|
Full information about the source of the visitor's visit |
data.visit_profile
|
User data if filled in in the online chat form (name, email and phone number) |
+ 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 FreshOffice
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.
Integration setup plan Leadback with FreshOffice
| 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
Whatsapp Tracker for Yandex.Metrica
Uploading conversions to Yandex.Metrica on the first message from Whatsapp
Is free