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 |
---|---|
quiz.id
|
The ID of the quiz survey |
quiz.name
|
The name of the quiz survey |
project.id
|
The ID of the quiz survey project |
project.name
|
The name of the quiz survey project |
company.id
|
The company ID of the quiz survey |
company.name
|
The name of the quiz survey company |
lead.id
|
Lead ID |
lead.title
|
The name of the lead (formed from the name of the quiz) |
lead.created_at
|
date of creation |
CardExpDate
|
The validity period of the card in MM/YY format |
lead.contact.name
|
Name of lida |
lead.contact.phone
|
Lida's phone number |
lead.contact.email
|
Email lida |
lead.contact.messenger
|
Lida Messenger |
lead.contact.contact_messenger
|
Contact of the lida messenger |
lead.utm.source
|
utm_source |
lead.utm.medium
|
utm_medium |
lead.utm.campaign
|
utm_campaign |
lead.utm.content
|
utm_content |
lead.utm.term
|
utm_term |
lead.answers
|
Answers to questions |
lead.answers2
|
Answers to questions (version 2) |
lead.roistat_visit
|
Roystat visit |
lead.comagic_session_id
|
The session ID of the comagic service |
lead.y_client_id
|
Yandex Client ID |
lead.g_client_id
|
Google Client ID |
lead.yclid
|
The click ID in Yandex Direct |
lead.gclid
|
Click ID in Google Ads |
lead.fbclid
|
The click ID on Facebook |
lead.fbc
|
The value of the _fbc cookie from Facebook Pixel |
lead.fbp
|
The value of the _fbp cookie from Facebook Pixel |
lead.custom_fields
|
The value of additional fields |
+ 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 |
---|---|
CashboxUniqueNumber
|
KKM factory/Serial Number |
PaymentType
|
Payment type |
TaxType
|
Type of tax |
TaxPercent
|
The percentage of the tax. The default is 12 |
payment
|
The payment array from the Tilde |
Change
|
Change. If this field is not filled in, the deposit is calculated on the Webkassa side |
RoundType
|
Type of rounding |
ExternalCheckNumber
|
The receipt number of the source system. Restrictions: not unicode. By default: OrderID from the payment array |
ExternalOrderNumber
|
Order number |
CustomerEmail
|
Buyer's email address |
CustomerPhone
|
Buyer's phone number |
CustomerXin
|
Buyer's IIN/BIN |
Id | Name |
---|---|
CheckNumber
|
Fiscal feature/offline code |
DateTime
|
Date and time of the transaction (receipt) |
OfflineMode
|
Offline Mode: True/False |
CashboxOfflineMode
|
Offline Mode: True/False |
Cashbox.UniqueNumber
|
KKM factory/Serial Number |
Cashbox.RegistrationNumber
|
The registration number of the KKM in the tax service |
Cashbox.IdentityNumber
|
The identification number of the KKM in the OFD |
Cashbox.Address
|
Address of the place of use of the cash register |
Cashbox.Ofd.Name
|
Name of the OFD |
Cashbox.Ofd.Host
|
OFD address |
Cashbox.Ofd.Code
|
OFD code |
CheckOrderNumber
|
The serial number of the receipt within the shift |
ShiftNumber
|
ShiftNumber |
TicketUrl
|
Link to the receipt |
TicketPrintUrl
|
Link to the receipt for printing |
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