Integration Zadarma (For free) and Okdesk (Okdex)
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 Zadarma
Click on the name of the event to see the available fields.
API documentation — here.
Description
Not
Available fields
| Id | Name |
|---|---|
call_start
|
The start time of the call |
pbx_call_id
|
Call ID |
caller_id
|
Caller's number |
called_did
|
The number that was called |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
call_start
|
The start time of the call |
pbx_call_id
|
Call ID |
caller_id
|
Caller's number |
destination
|
The number that was called |
internal
|
(optional) internal number |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
call_start
|
The start time of the call |
pbx_call_id
|
Call ID |
caller_id
|
Caller's number |
called_did
|
The number that was called |
internal
|
(optional) internal number |
duration
|
Duration in seconds |
disposition
|
The status of the call |
last_internal
|
Internal number, the last participant of the call (after transfer or interception); |
status_code
|
Call status code Q.931 |
is_recorded
|
1 - there is a recording of the call, 0 - there is no recording |
call_id_with_rec
|
The ID of the call with the recording (we recommend downloading the recording file no earlier than 40 seconds after the notification, because it takes time to save the recording file) |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
call_start
|
The start time of the call |
pbx_call_id
|
Call ID |
caller_id
|
Caller's number |
destination
|
The number that was called |
internal
|
(optional) internal number |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
call_start
|
The start time of the call |
pbx_call_id
|
Call ID |
caller_id
|
Caller's number |
destination
|
The number that was called |
internal
|
(optional) internal number |
duration
|
Duration in seconds |
disposition
|
The status of the call |
status_code
|
Call status code Q.931 |
is_recorded
|
1 - there is a recording of the call, 0 - there is no recording |
call_id_with_rec
|
The ID of the call with the recording (we recommend downloading the recording file no earlier than 40 seconds after the notification, because it takes time to save the recording file) |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
call_id_with_rec
|
The unique ID of the call with the recording of the conversation |
pbx_call_id
|
Call ID |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
result.tracker
|
Tracker ID (you can find out on the code installation page) |
result.start
|
The start time of the call |
result.duration
|
The duration of the call in seconds |
result.caller_id
|
Caller's number |
result.caller_did
|
The number that was called |
result.source
|
Name of the user's source |
result.country
|
(optional) The country from which the call was made |
result.ga_id
|
(optional if the Google Analytics Id is specified in the settings) User ID in Google Analytics |
result.metrika_id
|
(optional, if the Yandex.Metrika Id is specified in the settings) the user ID in Yandex.Metrika |
result.url
|
The address of the page from which the call was made |
result.utm_source
|
result.utm_source |
result.utm_medium
|
result.utm_medium |
result.utm_campaign
|
result.utm_campaign |
result.utm_term
|
result.utm_term |
result.utm_content
|
result.utm_content |
result.first_utm
|
(optional) An array with utm tags specified above, which the user used to go to the site for the first time |
+ 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 Okdesk
Click on the name of the action to see the available fields.
API documentation — No.
Request fields
| Id | Name |
|---|---|
issues_id
|
Application ID |
status
|
New status code |
available_current_status
|
Possible current status codes |
control_amount
|
Expected amount in applications |
comment
|
A comment |
Answer fields
| Id | Name |
|---|---|
result
|
Request execution flag |
Integration setup plan Zadarma with Okdesk
| 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
FAQ
How does the app differ from regular bundles?The application is not an alternative to bundles, but simply a preset set of bundles (template) for popular tasks to speed up setup.
Is it possible to change the logic of the created bundles?Yes. The created set of bundles can be customized according to your tasks or left unchanged if everything works as it should.
