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 |
---|---|
id
|
The unique identifier of the call in Calltouch. |
ctCallerId
|
Unique client ID in Calltouch |
callerphone
|
The phone number of the client from whom he makes the call |
phonenumber
|
The tracked number that the customer is calling |
subPoolName
|
The name of the subpool that the advertising number is associated with |
redirectNumber
|
The forwarding number to which the customer's call was directed |
duration
|
The duration of a telephone conversation in seconds |
waiting_time
|
Waiting time (beeps before the operator picks up the handset) in seconds |
calltime
|
Date and time of the call the start of the call |
timestamp
|
Date and time of the start of the call in Unix Time Stamp format in seconds |
status
|
Call status (successful - successful call, unsuccessful - unsuccessful call) |
statusDetails
|
Call status details |
unique
|
The flag of the uniqueness of the call. true - unique, false - repeated |
targetcall
|
The flag of the target call. target - target, non-target - non-target call |
uniqtargetcall
|
The flag of a uniquely targeted call. uniqtarget - unique-target call, non-uniqtarget - not unique-target call |
callback
|
Callback or not. callback - callback, non-callback - direct call |
worktime
|
The working or non-working time at which the call came in. worktime - working, non-worktime - non-working |
pool
|
The type of pool the number is assigned to |
rating
|
The rating assigned to the call or request (0 - not assigned, 1-5 - from 1 to 5) |
comment
|
A comment |
tags_auto_pr
|
Calltouch Predict Tags |
tags_auto_af
|
Calltouch Anti-fraud Tags |
tags_auto_gr
|
Tags by client's gender |
tags_auto_ct
|
Tags by extension |
tags_auto_pn
|
Tags by numbers |
tags_manual
|
Manually inserted tags |
tags_api
|
Tags set using the API |
attribution
|
Attribution model. 1 is the last indirect, 0 is the last interaction |
source
|
A source |
medium
|
Channel |
utm_source
|
utm_source tag |
utm_medium
|
utm_medium label |
utm_campaign
|
utm_campaign label |
utm_content
|
The utm_content label |
utm_term
|
utm_term label |
gcid
|
Google Client ID |
yaClientId
|
Yandex Client ID |
sessionId
|
Calltouch session ID |
hostname
|
The monitored site |
url
|
The site login page |
attrs
|
Third-party cookies |
callUrl
|
The call page |
callback_request_id
|
The ID of the callback request |
callback_final_attempt
|
The flag for the end of the call chain |
ref
|
The source of the referral link |
city
|
City |
browser
|
Browser |
os
|
The operating system |
device
|
Device |
ip
|
IP address |
sip_call_id
|
SIP Session ID |
callReferenceNumber
|
The ID of the call from the PBX |
reclink
|
Recording a conversation |
orderId
|
Transaction ID |
siteId
|
Site ID |
siteName
|
The name of the site |
userAgent
|
User agent |
sendingTimestamp
|
Date and time of sending the webhook in Unix Time Stamp format |
text
|
Transcript of the call to text |
manager
|
Call or Request Manager |
spam
|
The spam flag. true - the call is marked as, false - the call is unmarked |
callback_custom_fields
|
Custom fields of Callback widgets |
callback_request_facebook_lead_id
|
Facebook Lead ID |
+ 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.
There are no actions, try Change to replace the services.
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
Sending orders to sdek, receiving a tracking number
Is free
Communicate in Avito through your trained ChatGPT assistant
$99
Uploading conversions to Yandex.Metrica on the first message from Whatsapp
Is free
The store is in the process of filling up. If you are solving the same field problem in different projects, then it probably has the point is to design it as a template and add it to the store. Write to us.
If you are a developer and want to sell your no-code solutions (with nodejs support) - write to us.