Integration Call-Tracking.by and RetailCrm (Retail Cpm)
Connection in 5 minutes, 30 days on tests, try.
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 Call-Tracking.by
Click on the name of the event to see the available fields.
API documentation — here.
Description
Not
Available fields
| Id | Name |
|---|---|
time
|
Time in iso8601 format |
call_status
|
The current event (status). Possible values: start, answer, end, busy, abandon |
pbx_id
|
The unique identifier of the call |
campaign_id
|
Campaign ID |
campaign_name
|
Campaign Name |
stat_source
|
The normalized source of the call. It is formed based on utm tags, referral and the name of the tracked source |
duration
|
The duration of the call. For the call start and response event, the duration of the call is zero |
caller_number
|
Caller's number |
ads_number
|
The number that was shown and/or placed in the advertisement |
answer_number
|
The number that answered the call. An empty line if the call is not answered |
audio_path
|
Link to the conversation recording. Present if recording is enabled. The record is stored according to the user's settings |
utm_keyword
|
Keywords in case the call was made for a dynamic advertising campaign |
utm_campaign
|
Contextual advertising campaign if the call was made on a dynamic advertising campaign |
utm_medium
|
The type of traffic source (cpc, banner, newsletter) if the call was made for a dynamic advertising campaign |
utm_source
|
Traffic source |
utm_content
|
Defines different versions of the ad, if the call was made for a dynamic advertising campaign |
roistat_id
|
Unique RoiStat identifier (available only for dynamic call tracking, if there is a RoiStat script) |
google_analytics_id
|
Unique Google Analytics identifier (available only for dynamic call tracking, if there is a Google Analytics script) |
yandex_metrica_id
|
Unique Yandex.Metrica identifier (available only for dynamic call tracking, if there is a Yandex.Metrica script) |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
time
|
Time in iso8601 format |
call_status
|
The current event (status). Possible values: start, answer, end, busy, abandon |
pbx_id
|
The unique identifier of the call |
campaign_id
|
Campaign ID |
campaign_name
|
Campaign Name |
stat_source
|
The normalized source of the call. It is formed based on utm tags, referral and the name of the tracked source |
duration
|
The duration of the call. For the call start and response event, the duration of the call is zero |
caller_number
|
Caller's number |
ads_number
|
The number that was shown and/or placed in the advertisement |
answer_number
|
The number that answered the call. An empty line if the call is not answered |
audio_path
|
Link to the conversation recording. Present if recording is enabled. The record is stored according to the user's settings |
utm_keyword
|
Keywords in case the call was made for a dynamic advertising campaign |
utm_campaign
|
Contextual advertising campaign if the call was made on a dynamic advertising campaign |
utm_medium
|
The type of traffic source (cpc, banner, newsletter) if the call was made for a dynamic advertising campaign |
utm_source
|
Traffic source |
utm_content
|
Defines different versions of the ad, if the call was made for a dynamic advertising campaign |
roistat_id
|
Unique RoiStat identifier (available only for dynamic call tracking, if there is a RoiStat script) |
google_analytics_id
|
Unique Google Analytics identifier (available only for dynamic call tracking, if there is a Google Analytics script) |
yandex_metrica_id
|
Unique Yandex.Metrica identifier (available only for dynamic call tracking, if there is a Yandex.Metrica script) |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
time
|
Time in iso8601 format |
call_status
|
The current event (status). Possible values: start, answer, end, busy, abandon |
pbx_id
|
The unique identifier of the call |
campaign_id
|
Campaign ID |
campaign_name
|
Campaign Name |
stat_source
|
The normalized source of the call. It is formed based on utm tags, referral and the name of the tracked source |
duration
|
The duration of the call. For the call start and response event, the duration of the call is zero |
caller_number
|
Caller's number |
ads_number
|
The number that was shown and/or placed in the advertisement |
answer_number
|
The number that answered the call. An empty line if the call is not answered |
audio_path
|
Link to the conversation recording. Present if recording is enabled. The record is stored according to the user's settings |
utm_keyword
|
Keywords in case the call was made for a dynamic advertising campaign |
utm_campaign
|
Contextual advertising campaign if the call was made on a dynamic advertising campaign |
utm_medium
|
The type of traffic source (cpc, banner, newsletter) if the call was made for a dynamic advertising campaign |
utm_source
|
Traffic source |
utm_content
|
Defines different versions of the ad, if the call was made for a dynamic advertising campaign |
roistat_id
|
Unique RoiStat identifier (available only for dynamic call tracking, if there is a RoiStat script) |
google_analytics_id
|
Unique Google Analytics identifier (available only for dynamic call tracking, if there is a Google Analytics script) |
yandex_metrica_id
|
Unique Yandex.Metrica identifier (available only for dynamic call tracking, if there is a Yandex.Metrica script) |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
time
|
Time in iso8601 format |
call_status
|
The current event (status). Possible values: start, answer, end, busy, abandon |
pbx_id
|
The unique identifier of the call |
campaign_id
|
Campaign ID |
campaign_name
|
Campaign Name |
stat_source
|
The normalized source of the call. It is formed based on utm tags, referral and the name of the tracked source |
duration
|
The duration of the call. For the call start and response event, the duration of the call is zero |
caller_number
|
Caller's number |
ads_number
|
The number that was shown and/or placed in the advertisement |
answer_number
|
The number that answered the call. An empty line if the call is not answered |
audio_path
|
Link to the conversation recording. Present if recording is enabled. The record is stored according to the user's settings |
utm_keyword
|
Keywords in case the call was made for a dynamic advertising campaign |
utm_campaign
|
Contextual advertising campaign if the call was made on a dynamic advertising campaign |
utm_medium
|
The type of traffic source (cpc, banner, newsletter) if the call was made for a dynamic advertising campaign |
utm_source
|
Traffic source |
utm_content
|
Defines different versions of the ad, if the call was made for a dynamic advertising campaign |
roistat_id
|
Unique RoiStat identifier (available only for dynamic call tracking, if there is a RoiStat script) |
google_analytics_id
|
Unique Google Analytics identifier (available only for dynamic call tracking, if there is a Google Analytics script) |
yandex_metrica_id
|
Unique Yandex.Metrica identifier (available only for dynamic call tracking, if there is a Yandex.Metrica script) |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
time
|
Time in iso8601 format |
call_status
|
The current event (status). Possible values: start, answer, end, busy, abandon |
pbx_id
|
The unique identifier of the call |
campaign_id
|
Campaign ID |
campaign_name
|
Campaign Name |
stat_source
|
The normalized source of the call. It is formed based on utm tags, referral and the name of the tracked source |
duration
|
The duration of the call. For the call start and response event, the duration of the call is zero |
caller_number
|
Caller's number |
ads_number
|
The number that was shown and/or placed in the advertisement |
answer_number
|
The number that answered the call. An empty line if the call is not answered |
audio_path
|
Link to the conversation recording. Present if recording is enabled. The record is stored according to the user's settings |
utm_keyword
|
Keywords in case the call was made for a dynamic advertising campaign |
utm_campaign
|
Contextual advertising campaign if the call was made on a dynamic advertising campaign |
utm_medium
|
The type of traffic source (cpc, banner, newsletter) if the call was made for a dynamic advertising campaign |
utm_source
|
Traffic source |
utm_content
|
Defines different versions of the ad, if the call was made for a dynamic advertising campaign |
roistat_id
|
Unique RoiStat identifier (available only for dynamic call tracking, if there is a RoiStat script) |
google_analytics_id
|
Unique Google Analytics identifier (available only for dynamic call tracking, if there is a Google Analytics script) |
yandex_metrica_id
|
Unique Yandex.Metrica identifier (available only for dynamic call tracking, if there is a Yandex.Metrica script) |
+ 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 RetailCrm
Click on the name of the action to see the available fields.
API documentation — here.
Request fields
| Id | Name |
|---|---|
lastName
|
Surname |
firstName
|
Name |
patronymic
|
Middle name |
phone
|
Telephone |
email
|
|
customerComment
|
Customer's comment |
managerComment
|
Operator's comment |
orderMethod
|
The method of registration |
number
|
Order number |
externalId
|
External Order ID |
privilegeType
|
Type of privilege |
countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
createdAt
|
The date of the order |
discountManualAmount
|
Cash discount for the entire order |
discountManualPercent
|
Percentage discount on the entire order |
mark
|
Order evaluation |
markDatetime
|
Date and time of receipt of the assessment from the buyer |
additionalPhone
|
Additional phone number |
call
|
You need to make a call |
expired
|
Expired |
contragent.contragentType
|
Type of counterparty |
contragent.legalName
|
Full name |
contragent.legalAddress
|
Registration address |
contragent.INN
|
INN |
contragent.OKPO
|
OKPO |
contragent.KPP
|
CHECKPOINT |
contragent.OGRN
|
OGRN |
contragent.OGRNIP
|
OGRNIP |
contragent.certificateNumber
|
Certificate number |
contragent.certificateDate
|
Date of the certificate |
contragent.BIK
|
BIC |
contragent.bank
|
Bank |
contragent.bankAddress
|
Bank address |
contragent.corrAccount
|
Correspondent account |
contragent.bankAccount
|
Payment account |
statusComment
|
Comment on the last status change |
weight
|
Weight |
length
|
Length |
width
|
Width |
height
|
Height |
shipped
|
The order has been shipped |
dialogId
|
ID of the chat dialog |
customFields
|
Associative array of user fields |
orderType
|
Order Type |
customer.id
|
Internal Client ID |
customer.externalId
|
External Client ID |
customer.browserId
|
Device ID in Collector |
customer.site
|
The store's code is required when transferring the externalId |
customer.type
|
Type of client |
customer.nickName
|
Name of the corporate client |
contact.id
|
Internal Client ID |
contact.externalId
|
External Client ID |
contact.browserId
|
Device ID in Collector |
contact.site
|
The store's code is required when transferring the externalId |
company.id
|
Company ID |
company.externalId
|
External Company ID |
company.site
|
Website |
managerId
|
The manager attached to the order |
status
|
Order status |
items.0.markingCodes
|
Marking codes |
items.0.id
|
Item ID in the order |
items.0.initialPrice
|
Product price/SKU |
items.0.discountManualAmount
|
Cash discount per unit of product |
items.0.discountManualPercent
|
Percentage discount per unit of product |
items.0.vatRate
|
VAT rate |
items.0.createdAt
|
The date the position was created in the system |
items.0.quantity
|
Quantity |
items.0.comment
|
Comment on the item in the order |
items.0.purchasePrice
|
Purchase price |
items.0.offer.id
|
The ID of the trade offer |
items.0.offer.externalId
|
External ID of the trade offer |
items.0.offer.xmlId
|
The ID of the trade offer in the warehouse system |
items.0.productName
|
Product Name |
items.0.status
|
The status of the item in the order |
items.0.priceType.code
|
Price type code |
items.0.externalIds.0.code
|
The code |
items.0.externalIds.0.value
|
Meaning |
delivery.code
|
Delivery type code |
delivery.data.externalId
|
ID in the delivery service |
delivery.data.locked
|
Do not synchronize with the delivery service |
delivery.data.tariff
|
Tariff code |
delivery.data.pickuppointId
|
ID of the pick-up point |
delivery.data.payerType
|
The payer for the delivery |
delivery.data.shipmentpointId
|
ID of the shipping terminal |
delivery.data.packages.0.packageId
|
Package ID |
delivery.data.packages.0.weight
|
Weight g. |
delivery.data.packages.0.length
|
Length mm. |
delivery.data.packages.0.width
|
Width mm. |
delivery.data.packages.0.height
|
Height mm. |
delivery.data.packages.0.items.0.orderProduct.id
|
Item ID in the order |
delivery.data.packages.0.items.0.orderProduct.externalId
|
deprecated External item ID in the order |
delivery.data.packages.0.items.0.orderProduct.externalIds.0.code
|
The code |
delivery.data.packages.0.items.0.orderProduct.externalIds.0.value
|
Meaning |
delivery.data.packages.0.items.0.quantity
|
The quantity of the product in the package |
delivery.service.name
|
Name |
delivery.service.code
|
Character code |
delivery.service.active
|
Activity status |
delivery.service.deliveryType
|
Type of delivery |
delivery.cost
|
The cost of delivery |
delivery.netCost
|
Cost of delivery |
delivery.date
|
Delivery date |
delivery.time.from
|
Time "c" |
delivery.time.to
|
Time "before" |
delivery.time.custom
|
Free-form time range |
delivery.address.index
|
The index of the delivery address |
delivery.address.countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
delivery.address.region
|
The region of the delivery address |
delivery.address.regionId
|
The region ID in Geohelper |
delivery.address.city
|
City of the delivery address |
delivery.address.cityId
|
The city ID in Geohelper |
delivery.address.cityType
|
Type of settlement |
delivery.address.street
|
Street of the delivery address |
delivery.address.streetId
|
Street ID in Geohelper |
delivery.address.streetType
|
Street type of delivery address |
delivery.address.building
|
Home of the delivery address |
delivery.address.flat
|
Apartment/Office number |
delivery.address.floor
|
Floor |
delivery.address.block
|
Entrance |
delivery.address.house
|
Building |
delivery.address.housing
|
Body |
delivery.address.metro
|
Metro |
delivery.address.notes
|
Notes to the address |
delivery.address.text
|
The address in text form |
delivery.vatRate
|
VAT rate |
source.source
|
A source |
source.medium
|
Channel |
source.campaign
|
The campaign |
source.keyword
|
The key word |
source.content
|
Campaign content |
shipmentStore
|
Shipping Warehouse |
payments.0.externalId
|
External payment ID |
payments.0.amount
|
Payment amount |
payments.0.paidAt
|
Date of payment |
payments.0.comment
|
A comment |
payments.0.type
|
Payment type |
payments.0.status
|
Payment status |
loyaltyEventDiscountId
|
ID of the discount for the loyalty program event |
shipmentDate
|
Date of shipment |
Answer fields
| Id | Name |
|---|---|
success
|
Query result (successful/unsuccessful) |
bonusesCreditTotal
|
The number of accrued bonuses |
bonusesChargeTotal
|
The number of bonuses written off |
summ
|
The amount of the goods |
id
|
Order ID |
number
|
Order number |
externalId
|
External Order ID |
orderType
|
Order Type |
orderMethod
|
The method of registration |
privilegeType
|
Type of privilege |
countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
createdAt
|
The date of the order |
statusUpdatedAt
|
Date of the last status change |
totalSumm
|
The total amount including the discount |
prepaySum
|
The amount paid |
purchaseSumm
|
Total purchase price |
personalDiscountPercent
|
Personal discount on the order |
loyaltyLevel
|
The level of participation in the loyalty program |
mark
|
Order evaluation |
markDatetime
|
Date and time of receipt of the assessment from the buyer |
lastName
|
Surname |
firstName
|
Name |
patronymic
|
Middle name |
phone
|
Telephone |
additionalPhone
|
Additional phone number |
email
|
|
call
|
You need to make a call |
expired
|
Expired |
customerComment
|
Customer's comment |
managerComment
|
Operator's comment |
managerId
|
The manager attached to the order |
customer.type
|
Type of client |
customer.id
|
Client ID |
customer.externalId
|
External Client ID |
customer.isContact
|
The client is a contact person (created as a contact person and there are no orders placed for him) |
customer.createdAt
|
Date of creation of the client |
customer.managerId
|
The client's manager |
customer.vip
|
An important client |
customer.bad
|
A bad customer |
customer.site
|
The store the customer came from |
customer.tags
|
Customer Tags |
customer.avgMarginSumm
|
Average gross profit on customer orders |
customer.marginSumm
|
LTV |
customer.totalSumm
|
Total amount of orders |
customer.averageSumm
|
Average order amount |
customer.ordersCount
|
Number of orders |
customer.costSumm
|
The amount of expenses |
customer.customFields
|
Associative array of user fields |
customer.personalDiscount
|
Personal discount |
customer.discountCardNumber
|
Discount card number |
customer.firstClientId
|
The first tag of the Google Analytics client |
customer.lastClientId
|
The latest Google Analytics client tag |
customer.address.id
|
Address ID |
customer.address.index
|
Index |
customer.address.countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
customer.address.region
|
Region |
customer.address.regionId
|
The region ID in Geohelper |
customer.address.city
|
City |
customer.address.cityId
|
The city ID in Geohelper |
customer.address.cityType
|
Type of settlement |
customer.address.street
|
Street |
customer.address.streetId
|
Street ID in Geohelper |
customer.address.streetType
|
Street type |
customer.address.building
|
House |
customer.address.flat
|
Apartment/Office number |
customer.address.floor
|
Floor |
customer.address.block
|
Entrance |
customer.address.house
|
Building |
customer.address.housing
|
Body |
customer.address.metro
|
Metro |
customer.address.notes
|
Notes to the address |
customer.address.text
|
The address in text form |
customer.address.externalId
|
External ID |
customer.address.name
|
Changing the address |
customer.segments
|
[array] Segments |
customer.maturationTime
|
"Maturation" time, in seconds |
customer.firstName
|
Name |
customer.lastName
|
Surname |
customer.patronymic
|
Middle name |
customer.sex
|
Paul |
customer.presumableSex
|
Assumed gender based on full name |
customer.email
|
|
customer.emailMarketingUnsubscribedAt
|
Date of unsubscription from email newsletters |
customer.phones
|
Phones |
customer.birthday
|
Birthday |
customer.source.source
|
A source |
customer.source.medium
|
Channel |
customer.source.campaign
|
The campaign |
customer.source.keyword
|
The key word |
customer.source.content
|
Campaign content |
customer.photoUrl
|
Photo URL |
contact.type
|
The type of the client's contact person |
contact.id
|
Client ID |
contact.isContact
|
The client is a contact person (created as a contact person and there are no orders placed for him) |
contact.createdAt
|
Created |
contact.managerId
|
The client's manager |
contact.vip
|
An important client |
contact.bad
|
A bad customer |
contact.site
|
The store the customer came from |
contact.tags
|
Customer Tags |
contact.avgMarginSumm
|
Average gross profit on customer orders |
contact.marginSumm
|
LTV |
contact.totalSumm
|
Total amount of orders |
contact.averageSumm
|
Average order amount |
contact.ordersCount
|
Number of orders |
contact.costSumm
|
The amount of expenses |
contact.customFields
|
Associative array of user fields |
contact.personalDiscount
|
Personal discount |
contact.discountCardNumber
|
Discount card number |
contact.firstClientId
|
The first tag of the Google Analytics client |
contact.lastClientId
|
The latest Google Analytics client tag |
contact.address.id
|
Address ID |
contact.address.index
|
Index |
contact.address.countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
contact.address.region
|
Region |
contact.address.regionId
|
The region ID in Geohelper |
contact.address.city
|
City |
contact.address.cityId
|
The city ID in Geohelper |
contact.address.cityType
|
Type of settlement |
contact.address.street
|
Street |
contact.address.streetId
|
Street ID in Geohelper |
contact.address.streetType
|
Street type |
contact.address.building
|
House |
contact.address.flat
|
Apartment/Office number |
contact.address.floor
|
Floor |
contact.address.block
|
Entrance |
contact.address.house
|
Building |
contact.address.housing
|
Body |
contact.address.metro
|
Metro |
contact.address.notes
|
Notes to the address |
contact.address.text
|
The address in text form |
contact.address.externalId
|
External ID |
contact.address.name
|
Changing the address |
contact.segments
|
[array] Segments |
contact.maturationTime
|
"Maturation" time, in seconds |
contact.firstName
|
Name |
contact.lastName
|
Surname |
contact.patronymic
|
Middle name |
contact.sex
|
Paul |
contact.presumableSex
|
Assumed gender based on full name |
contact.email
|
|
contact.emailMarketingUnsubscribedAt
|
Date of unsubscription from email newsletters |
contact.phones
|
Phones |
contact.birthday
|
Birthday |
contact.source.source
|
A source |
contact.source.medium
|
Channel |
contact.source.campaign
|
The campaign |
contact.source.keyword
|
The key word |
contact.source.content
|
Campaign content |
contact.photoUrl
|
Photo URL |
company
|
Company |
contragent
|
Requisites |
delivery
|
Shipping Information |
marketplace
|
Marketplace data |
site
|
Shop |
status
|
Order status |
statusComment
|
Comment on the last status change |
source
|
Order Source |
items
|
Items in the order |
fullPaidAt
|
Date of full payment |
payments
|
Payments |
fromApi
|
The order was received via the API |
weight
|
Weight |
length
|
Length |
width
|
Width |
height
|
Height |
shipmentStore
|
Shipping Warehouse |
shipped
|
The order has been shipped |
customFields
|
Associative array of user fields |
clientId
|
Google Analytics Customer Tag |
shipmentDate
|
Date of shipment |
Request fields
| Id | Name |
|---|---|
site
|
Shop |
orderType
|
Order Type |
lastName
|
Surname |
firstName
|
Name |
patronymic
|
Middle name |
phone
|
Telephone |
email
|
|
customerComment
|
Customer's comment |
managerComment
|
Operator's comment |
orderMethod
|
The method of registration |
number
|
Order number |
externalId
|
External Order ID |
company.site
|
Website |
contragent.contragentType
|
Type of counterparty |
countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
delivery.date
|
Delivery date |
delivery.code
|
Delivery type code |
shipmentStore
|
Shipping Warehouse |
shipmentDate
|
Date of shipment |
article_field
|
The field with the article |
products
|
An array with Ozon products |
Answer fields
| Id | Name |
|---|---|
success
|
Query result (successful/unsuccessful) |
id
|
ID of the created order |
Request fields
| Id | Name |
|---|---|
site
|
Shop |
orderType
|
Order Type |
lastName
|
Surname |
firstName
|
Name |
patronymic
|
Middle name |
phone
|
Telephone |
email
|
|
customerComment
|
Customer's comment |
managerComment
|
Operator's comment |
orderMethod
|
The method of registration |
number
|
Order number |
externalId
|
External Order ID |
company.site
|
Website |
contragent.contragentType
|
Type of counterparty |
countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
delivery.date
|
Delivery date |
delivery.code
|
Delivery type code |
shipmentStore
|
Shipping Warehouse |
shipmentDate
|
Date of shipment |
article_field
|
The field with the article |
price_field
|
Price field |
items
|
Array with Yandex Market products |
Answer fields
| Id | Name |
|---|---|
success
|
Query result (successful/unsuccessful) |
id
|
ID of the created order |
Request fields
| Id | Name |
|---|---|
site
|
Shop |
orderType
|
Order Type |
status
|
Order status |
payment.type
|
Payment type |
lastName
|
Surname |
firstName
|
Name |
patronymic
|
Middle name |
phone
|
Telephone |
email
|
|
customerComment
|
Customer's comment |
managerComment
|
Operator's comment |
orderMethod
|
The method of registration |
number
|
Order number |
externalId
|
External Order ID |
company.site
|
Website |
contragent.contragentType
|
Type of counterparty |
countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
delivery.date
|
Delivery date |
delivery.code
|
Delivery type code |
delivery.address.index
|
Index |
delivery.address.region
|
Region |
delivery.address.regionId
|
Region (geohelper id) |
delivery.address.city
|
City |
delivery.address.cityId
|
City (geohelper id) |
delivery.address.street
|
Street |
delivery.address.streetId
|
Street (geohelper id) |
delivery.address.metro
|
Metro |
delivery.address.house
|
Building |
delivery.address.housing
|
Body |
delivery.address.building
|
House |
delivery.address.flat
|
Apartment/Office number |
delivery.address.block
|
Entrance |
delivery.address.floor
|
Floor |
delivery.address.text
|
The address in text form |
delivery.address.notes
|
Notes to the address |
shipmentStore
|
Shipping Warehouse |
shipmentDate
|
Date of shipment |
article_field
|
The field with the article |
price_field
|
Price field |
entries
|
Array with Kaspi products |
Answer fields
| Id | Name |
|---|---|
success
|
Query result (successful/unsuccessful) |
id
|
ID of the created order |
Request fields
| Id | Name |
|---|---|
site
|
Shop |
orderType
|
Order Type |
lastName
|
Surname |
firstName
|
Name |
patronymic
|
Middle name |
phone
|
Telephone |
email
|
|
customerComment
|
Customer's comment |
managerComment
|
Operator's comment |
orderMethod
|
The method of registration |
number
|
Order number |
externalId
|
External Order ID |
company.site
|
Website |
contragent.contragentType
|
Type of counterparty |
countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
delivery.date
|
Delivery date |
delivery.code
|
Delivery type code |
delivery.address.index
|
Index |
delivery.address.region
|
Region |
delivery.address.regionId
|
Region (geohelper id) |
delivery.address.city
|
City |
delivery.address.cityId
|
City (geohelper id) |
delivery.address.street
|
Street |
delivery.address.streetId
|
Street (geohelper id) |
delivery.address.metro
|
Metro |
delivery.address.house
|
Building |
delivery.address.housing
|
Body |
delivery.address.building
|
House |
delivery.address.flat
|
Apartment/Office number |
delivery.address.block
|
Entrance |
delivery.address.floor
|
Floor |
delivery.address.text
|
The address in text form |
delivery.address.notes
|
Notes to the address |
shipmentStore
|
Shipping Warehouse |
shipmentDate
|
Date of shipment |
webhook
|
A webhook with a product from Wildberries |
Answer fields
| Id | Name |
|---|---|
success
|
Query result (successful/unsuccessful) |
id
|
ID of the created order |
Request fields
| Id | Name |
|---|---|
site
|
Shop |
orderType
|
Order Type |
lastName
|
Surname |
firstName
|
Name |
patronymic
|
Middle name |
phone
|
Telephone |
email
|
|
customerComment
|
Customer's comment |
managerComment
|
Operator's comment |
orderMethod
|
The method of registration |
number
|
Order number |
externalId
|
External Order ID |
company.site
|
Website |
contragent.contragentType
|
Type of counterparty |
countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
delivery.date
|
Delivery date |
delivery.code
|
Delivery type code |
shipmentStore
|
Shipping Warehouse |
shipmentDate
|
Date of shipment |
webhook
|
A webhook with a product from Wildberries |
priceField
|
Price field |
Answer fields
| Id | Name |
|---|---|
success
|
Query result (successful/unsuccessful) |
id
|
ID of the created order |
Request fields
| Id | Name |
|---|---|
id
|
Order ID |
lastName
|
Surname |
firstName
|
Name |
patronymic
|
Middle name |
phone
|
Telephone |
email
|
|
customerComment
|
Customer's comment |
managerComment
|
Operator's comment |
orderMethod
|
The method of registration |
number
|
Order number |
externalId
|
External Order ID |
privilegeType
|
Type of privilege |
countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
createdAt
|
The date of the order |
statusUpdatedAt
|
Date of the last status change |
discountManualAmount
|
Cash discount for the entire order |
discountManualPercent
|
Percentage discount on the entire order |
mark
|
Order evaluation |
markDatetime
|
Date and time of receipt of the assessment from the buyer |
additionalPhone
|
Additional phone number |
call
|
You need to make a call |
expired
|
Expired |
contragent.contragentType
|
Type of counterparty |
contragent.legalName
|
Full name |
contragent.legalAddress
|
Registration address |
contragent.INN
|
INN |
contragent.OKPO
|
OKPO |
contragent.KPP
|
CHECKPOINT |
contragent.OGRN
|
OGRN |
contragent.OGRNIP
|
OGRNIP |
contragent.certificateNumber
|
Certificate number |
contragent.certificateDate
|
Date of the certificate |
contragent.BIK
|
BIC |
contragent.bank
|
Bank |
contragent.bankAddress
|
Bank address |
contragent.corrAccount
|
Correspondent account |
contragent.bankAccount
|
Payment account |
statusComment
|
Comment on the last status change |
weight
|
Weight |
length
|
Length |
width
|
Width |
height
|
Height |
shipmentDate
|
Date of shipment |
shipped
|
The order has been shipped |
dialogId
|
ID of the chat dialog |
customFields
|
Associative array of user fields |
orderType
|
Order Type |
customer.id
|
Internal Client ID |
customer.externalId
|
External Client ID |
customer.browserId
|
Device ID in Collector |
customer.site
|
The store's code is required when transferring the externalId |
customer.type
|
Type of client |
customer.nickName
|
Name of the corporate client |
contact.id
|
Internal Client ID |
contact.externalId
|
External Client ID |
contact.browserId
|
Device ID in Collector |
contact.site
|
The store's code is required when transferring the externalId |
company.id
|
Digging ID |
company.site
|
Website |
company.externalId
|
External Company ID |
managerId
|
The manager attached to the order |
items.0.markingCodes
|
Marking codes |
items.0.id
|
Item ID in the order |
items.0.initialPrice
|
Product price/SKU |
items.0.discountManualAmount
|
Cash discount per unit of product |
items.0.discountManualPercent
|
Percentage discount per unit of product |
items.0.vatRate
|
VAT rate |
items.0.createdAt
|
The date the position was created in the system |
items.0.quantity
|
Quantity |
items.0.comment
|
Comment on the item in the order |
items.0.purchasePrice
|
Purchase price |
items.0.offer.id
|
The ID of the trade offer |
items.0.offer.externalId
|
External ID of the trade offer |
items.0.offer.xmlId
|
The ID of the trade offer in the warehouse system |
items.0.productName
|
Product Name |
items.0.status
|
The status of the item in the order |
items.0.priceType.code
|
Price type code |
items.0.externalIds.0.code
|
The code |
items.0.externalIds.0.value
|
Meaning |
delivery.code
|
Delivery type code |
delivery.data.externalId
|
ID in the delivery service |
delivery.data.locked
|
Do not synchronize with the delivery service |
delivery.data.tariff
|
Tariff code |
delivery.data.pickuppointId
|
ID of the pick-up point |
delivery.data.payerType
|
The payer for the delivery |
delivery.data.shipmentpointId
|
ID of the shipping terminal |
delivery.data.packages.0.packageId
|
Package ID |
delivery.data.packages.0.weight
|
Weight g. |
delivery.data.packages.0.length
|
Length mm. |
delivery.data.packages.0.width
|
Width mm. |
delivery.data.packages.0.height
|
Height mm. |
delivery.data.packages.0.items.0.orderProduct.id
|
Item ID in the order |
delivery.data.packages.0.items.0.orderProduct.externalId
|
deprecated External item ID in the order |
delivery.data.packages.0.items.0.orderProduct.externalIds.0.code
|
The code |
delivery.data.packages.0.items.0.orderProduct.externalIds.0.value
|
Meaning |
delivery.data.packages.0.items.0.quantity
|
The quantity of the product in the package |
delivery.service.name
|
Name |
delivery.service.code
|
Character code |
delivery.service.active
|
Activity status |
delivery.service.deliveryType
|
Type of delivery |
delivery.cost
|
The cost of delivery |
delivery.netCost
|
Cost of delivery |
delivery.date
|
Delivery date |
delivery.time.from
|
Time "c" |
delivery.time.to
|
Time "before" |
delivery.time.custom
|
Free-form time range |
delivery.address.index
|
The index of the delivery address |
delivery.address.countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
delivery.address.region
|
The region of the delivery address |
delivery.address.regionId
|
The region ID in Geohelper |
delivery.address.city
|
City of the delivery address |
delivery.address.cityId
|
The city ID in Geohelper |
delivery.address.cityType
|
Type of settlement |
delivery.address.street
|
Street of the delivery address |
delivery.address.streetId
|
Street ID in Geohelper |
delivery.address.streetType
|
Street type of delivery address |
delivery.address.building
|
Home of the delivery address |
delivery.address.flat
|
Apartment/Office number |
delivery.address.floor
|
Floor |
delivery.address.block
|
Entrance |
delivery.address.house
|
Building |
delivery.address.housing
|
Body |
delivery.address.metro
|
Metro |
delivery.address.notes
|
Notes to the address |
delivery.address.text
|
The address in text form |
delivery.vatRate
|
VAT rate |
status
|
Order status |
source.source
|
A source |
source.medium
|
Channel |
source.campaign
|
The campaign |
source.keyword
|
The key word |
source.content
|
Campaign content |
shipmentStore
|
Shipping Warehouse |
payments.0.externalId
|
External payment ID |
payments.0.amount
|
Payment amount |
payments.0.paidAt
|
Date of payment |
payments.0.comment
|
A comment |
payments.0.type
|
Payment type |
payments.0.status
|
Payment status |
loyaltyEventDiscountId
|
ID of the discount for the loyalty program event |
Answer fields
| Id | Name |
|---|---|
success
|
Query result (successful/unsuccessful) |
bonusesCreditTotal
|
The number of accrued bonuses |
bonusesChargeTotal
|
The number of bonuses written off |
summ
|
The amount of the goods |
id
|
Order ID |
number
|
Order number |
externalId
|
External Order ID |
orderType
|
Order Type |
orderMethod
|
The method of registration |
privilegeType
|
Type of privilege |
countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
createdAt
|
The date of the order |
statusUpdatedAt
|
Date of the last status change |
totalSumm
|
The total amount including the discount |
prepaySum
|
The amount paid |
purchaseSumm
|
Total purchase price |
personalDiscountPercent
|
Personal discount on the order |
loyaltyLevel
|
The level of participation in the loyalty program |
mark
|
Order evaluation |
markDatetime
|
Date and time of receipt of the assessment from the buyer |
lastName
|
Surname |
firstName
|
Name |
patronymic
|
Middle name |
phone
|
Telephone |
additionalPhone
|
Additional phone number |
email
|
|
call
|
You need to make a call |
expired
|
Expired |
customerComment
|
Customer's comment |
managerComment
|
Operator's comment |
managerId
|
The manager attached to the order |
customer.type
|
Type of client |
customer.id
|
Client ID |
customer.externalId
|
External Client ID |
customer.isContact
|
The client is a contact person (created as a contact person and there are no orders placed for him) |
customer.createdAt
|
Date of creation of the client |
customer.managerId
|
The client's manager |
customer.vip
|
An important client |
customer.bad
|
A bad customer |
customer.site
|
The store the customer came from |
customer.tags
|
Customer Tags |
customer.avgMarginSumm
|
Average gross profit on customer orders |
customer.marginSumm
|
LTV |
customer.totalSumm
|
Total amount of orders |
customer.averageSumm
|
Average order amount |
customer.ordersCount
|
Number of orders |
customer.costSumm
|
The amount of expenses |
customer.customFields
|
Associative array of user fields |
customer.personalDiscount
|
Personal discount |
customer.discountCardNumber
|
Discount card number |
customer.firstClientId
|
The first tag of the Google Analytics client |
customer.lastClientId
|
The latest Google Analytics client tag |
customer.address.id
|
Address ID |
customer.address.index
|
Index |
customer.address.countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
customer.address.region
|
Region |
customer.address.regionId
|
The region ID in Geohelper |
customer.address.city
|
City |
customer.address.cityId
|
The city ID in Geohelper |
customer.address.cityType
|
Type of settlement |
customer.address.street
|
Street |
customer.address.streetId
|
Street ID in Geohelper |
customer.address.streetType
|
Street type |
customer.address.building
|
House |
customer.address.flat
|
Apartment/Office number |
customer.address.floor
|
Floor |
customer.address.block
|
Entrance |
customer.address.house
|
Building |
customer.address.housing
|
Body |
customer.address.metro
|
Metro |
customer.address.notes
|
Notes to the address |
customer.address.text
|
The address in text form |
customer.address.externalId
|
External ID |
customer.address.name
|
Changing the address |
customer.segments
|
[array] Segments |
customer.maturationTime
|
"Maturation" time, in seconds |
customer.firstName
|
Name |
customer.lastName
|
Surname |
customer.patronymic
|
Middle name |
customer.sex
|
Paul |
customer.presumableSex
|
Assumed gender based on full name |
customer.email
|
|
customer.emailMarketingUnsubscribedAt
|
Date of unsubscription from email newsletters |
customer.phones
|
Phones |
customer.birthday
|
Birthday |
customer.source.source
|
A source |
customer.source.medium
|
Channel |
customer.source.campaign
|
The campaign |
customer.source.keyword
|
The key word |
customer.source.content
|
Campaign content |
customer.photoUrl
|
Photo URL |
contact.type
|
The type of the client's contact person |
contact.id
|
Client ID |
contact.isContact
|
The client is a contact person (created as a contact person and there are no orders placed for him) |
contact.createdAt
|
Created |
contact.managerId
|
The client's manager |
contact.vip
|
An important client |
contact.bad
|
A bad customer |
contact.site
|
The store the customer came from |
contact.tags
|
Customer Tags |
contact.avgMarginSumm
|
Average gross profit on customer orders |
contact.marginSumm
|
LTV |
contact.totalSumm
|
Total amount of orders |
contact.averageSumm
|
Average order amount |
contact.ordersCount
|
Number of orders |
contact.costSumm
|
The amount of expenses |
contact.customFields
|
Associative array of user fields |
contact.personalDiscount
|
Personal discount |
contact.discountCardNumber
|
Discount card number |
contact.firstClientId
|
The first tag of the Google Analytics client |
contact.lastClientId
|
The latest Google Analytics client tag |
contact.address.id
|
Address ID |
contact.address.index
|
Index |
contact.address.countryIso
|
ISO country code (ISO 3166-1 alpha-2) |
contact.address.region
|
Region |
contact.address.regionId
|
The region ID in Geohelper |
contact.address.city
|
City |
contact.address.cityId
|
The city ID in Geohelper |
contact.address.cityType
|
Type of settlement |
contact.address.street
|
Street |
contact.address.streetId
|
Street ID in Geohelper |
contact.address.streetType
|
Street type |
contact.address.building
|
House |
contact.address.flat
|
Apartment/Office number |
contact.address.floor
|
Floor |
contact.address.block
|
Entrance |
contact.address.house
|
Building |
contact.address.housing
|
Body |
contact.address.metro
|
Metro |
contact.address.notes
|
Notes to the address |
contact.address.text
|
The address in text form |
contact.address.externalId
|
External ID |
contact.address.name
|
Changing the address |
contact.segments
|
[array] Segments |
contact.maturationTime
|
"Maturation" time, in seconds |
contact.firstName
|
Name |
contact.lastName
|
Surname |
contact.patronymic
|
Middle name |
contact.sex
|
Paul |
contact.presumableSex
|
Assumed gender based on full name |
contact.email
|
|
contact.emailMarketingUnsubscribedAt
|
Date of unsubscription from email newsletters |
contact.phones
|
Phones |
contact.birthday
|
Birthday |
contact.source.source
|
A source |
contact.source.medium
|
Channel |
contact.source.campaign
|
The campaign |
contact.source.keyword
|
The key word |
contact.source.content
|
Campaign content |
contact.photoUrl
|
Photo URL |
company
|
Company |
contragent
|
Requisites |
delivery
|
Shipping Information |
marketplace
|
Marketplace data |
site
|
Shop |
status
|
Order status |
statusComment
|
Comment on the last status change |
source
|
Order Source |
items
|
Items in the order |
fullPaidAt
|
Date of full payment |
payments
|
Payments |
fromApi
|
The order was received via the API |
weight
|
Weight |
length
|
Length |
width
|
Width |
height
|
Height |
shipmentStore
|
Shipping Warehouse |
shipmentDate
|
Date of shipment |
shipped
|
The order has been shipped |
customFields
|
Associative array of user fields |
clientId
|
Google Analytics Customer Tag |
Request fields
| Id | Name |
|---|---|
managerId
|
The manager's internal ID |
text
|
The text of the note |
customer.id
|
Internal Client ID |
customer.externalId
|
External Client ID |
Answer fields
| Id | Name |
|---|---|
success
|
Query result (successful/unsuccessful) |
id
|
The internal ID of the created note |
Request fields
| Id | Name |
|---|---|
email
|
|
phone
|
Telephone |
status
|
Status |
Answer fields
| Id | Name |
|---|---|
id
|
Order ID |
Request fields
| Id | Name |
|---|---|
article
|
Item number |
Answer fields
| Id | Name |
|---|---|
id
|
Product ID |
Request fields
| Id | Name |
|---|---|
code
|
Warehouse Code |
Answer fields
| Id | Name |
|---|---|
name
|
Name |
externalId
|
External ID |
xmlId
|
1C identifier |
description
|
Description of the warehouse |
email
|
Email address of the warehouse |
type
|
Type of warehouse |
inventoryType
|
Type of stock remaining |
address
|
Warehouse address |
active
|
Activity status |
phone
|
Warehouse phone number |
workTime
|
Warehouse opening hours |
Request fields
| Id | Name |
|---|---|
id
|
Order ID |
Answer fields
| Id | Name |
|---|---|
packs
|
Equipment |
Integration setup plan Call-Tracking.by with RetailCrm
| 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
You most likely need to
Popular bundles are given. If you haven't found your option - leave a request for consultation, we will suggest a solution.
1. Lead generation
1.1 Widget on the website with links to telegram/whatsapp with the ability to track the source of the application
Multi-button + Callback —
1.2 Widget for requesting contacts from customers who leave the site without a request
Lead Catcher —
2. Sales
2.1 Creating deals in CRM for requests from the site
2.2 Creating deals in CRM for applications from other services
2.3 Notifications of managers in messengers about new applications
Avito —
3. Analytics
3.1 The download and conversion at various stages of transactions in Yandex metric and google analytics with protection against duplicates
3.2 Dynamic call tracking on your numbers
Calltracking —
3.3 Decryption of calls to text from any telephony
Yandex SpeechKit 3.4 Filtering bots and target audience in paid traffic
4. Artificial intelligence
4.1 Analytics of managers' dialogues via ChatGPT (calls/chats) - search for insights and evaluation of the quality of the conversation
Speech analytics via AI/ChatGPT/OpenAI 
Customer data platform (CDP) 5. Marketplaces
5.1 Transferring orders to CRM
Yandex Market —
5.2 Saving on shipping
Post office 6. Payments and billing
6.1 Automation of card payment acceptance
Yookassa —
CloudKassir 6.2 Automation of payment acceptance on the account
Tochka —
6.3 Automation of international payment acceptance
Payselection —
Working with the API
ApiMonster implements most of the popular tasks for interaction between services via the API.
If your task can be solved through ApiMonster, then it is better to solve it through ApiMonster - you will save yourself 95% of time and money. This is especially useful at the product launch stage, when there is no time and desire to do tasks that do not affect sales.
Clickfrod
According to our statistics, 40% of visitors from paid traffic do nothing on the site and are very similar to bots, 50% have average activity and only 10% are clearly interested in the content of the site.
Using ApiMonster you will be able to gather an audience of bots or active visitors for Yandex Metrics, Google Analytics, Facebook for bid adjustments to cut non-target audience, or Vice versa to train advertising campaign for visitors who are interested in the product.
ApiMonster allows you to configure the parameters of who is considered a bot and who is a target visitor by configuring scoring for your project.
An example of analyzing a user's behavior on a website:
Our clients
We have many clients - from microbusiness to enterprise with hundreds of bundles per project.
Context Specialist
ApiMonster allows you to upload conversions to analytics services as transparently as possible. In case of doubt, you can literally use the transaction id or customer contacts to find which conversions have gone where. This cannot be done with normal goal settings.
Popular tasks
- Uploading conversions to Yandex.Metrica from the website, CRM and any service that transmits the client id in the webhook.
- Uploading conversions to Google Analytics from the website, CRM and any service that transmits the client id in the webhook.
- The ability to create goals and record conversions for each stage in CRM for detailed analytics and training of advertising campaigns.
- Unloading expenses of Yandex Direkt in Google Sheets
- Uploading expenses from Vk Ads to Google Sheets
- Anti-clumping
Popular bundles
-
AmoCRM > Yandex Metric
-
Bitrix24 > Yandex Metric
-
The invoice of the forms > Yandex Metric
-
Incoming webhooks > Yandex Metric
-
Tilda > Yandex Metric
-
Marquiz > Yandex Metric
-
AmoCRM > Google Analytics 4
-
Bitrix24 > Google Analytics 4
-
The invoice of the forms > Google Analytics 4
-
Incoming webhooks > Google Analytics 4
-
Marquiz > Google Analytics 4
-
Tilda > Google Analytics 4
-
Yandex Direct > Google Sheets
-
Clickfraud > Yandex Metric
-
Clickfraud > Google Analytics 4
If you haven't found a suitable bundle here, look for your set of services on the form below.
Web Analyst
ApiMonster allows you to upload conversions to analytics services as transparently as possible. In case of doubt, you can literally use the transaction id or customer contacts to find which conversions have gone where. This cannot be done with normal goal settings.
Popular tasks
- Uploading conversions to Yandex.Metrica from the website, CRM and any service that transmits the client id in the webhook.
- Uploading conversions to Google Analytics from the website, CRM and any service that transmits the client id in the webhook.
- The ability to create goals and record conversions for each stage in CRM for detailed analytics and training of advertising campaigns.
- Unloading expenses of Yandex Direkt in Google Sheets
- Uploading expenses from Vk Ads to Google Sheets
Popular bundles
-
AmoCRM > Yandex Metric
-
Bitrix24 > Yandex Metric
-
The invoice of the forms > Yandex Metric
-
Incoming webhooks > Yandex Metric
-
Marquiz > Yandex Metric
-
Tilda > Yandex Metric
-
AmoCRM > Google Analytics 4
-
Bitrix24 > Google Analytics 4
-
The invoice of the forms > Google Analytics 4
-
Incoming webhooks > Google Analytics 4
-
Marquiz > Google Analytics 4
-
Tilda > Google Analytics 4
-
Yandex Direct > Google Sheets
If you haven't found a suitable bundle here, look for your set of services on the form below.
Data Analyst
ApiMonster will save you from having to write data fill scripts.
Popular tasks
- Uploading any data available via the webhook to Google Sheets
- Uploading any data available via the webhook to Clickhouse
- Further data analytics in storage or via Yandex Lens, Power BI, Looker Studio
Popular bundles
-
Incoming webhooks > Google Sheets
-
Incoming webhooks > Clickhouse
-
The invoice of the forms > Google Sheets
-
The invoice of the forms > Clickhouse
-
Yandex Metric > Google Sheets
-
Yandex Metric > Clickhouse
-
Yandex Direct > Google Sheets
-
Yandex Direct > Clickhouse
If you haven't found a suitable bundle here, look for your set of services on the form below.
Tools
-
JavaScript/NodeJs -
you can use JavaScript for complex data processing before sending it to another service
Entrepreneur
ApiMonster will allow you to launch projects as quickly as possible, significantly saving time and money on basic technical tasks related to linking the site with CRM, analytics and other sales automation tasks.
Solving problems through ApiMonster is much cheaper and more stable than when working with programmers. We will not disappear anywhere and guarantee work for the entire period of working with us.
Popular tasks
- Transfer of applications from the website to the CRM
- Transferring requests from the site to analytics services
- Generating receipts for payments from individuals
- Notification of new applications via telegram or email
- Notifying customers about an accepted order on Whatsapp
- Final control of the availability of sites so that sales do not stop
Popular bundles
-
Tilda > AmoCRM
-
The invoice of the forms > AmoCRM
-
Incoming webhooks > AmoCRM
-
The invoice of the forms > Bitrix24
-
Tilda > Bitrix24
-
Incoming webhooks > Bitrix24
-
Tilda > Wazzup 24
-
The invoice of the forms > Wazzup 24
-
Tilda > Telegram
-
The invoice of the forms > Telegram
-
DownDetector > Telegram
If you haven't found a suitable bundle here, look for your set of services on the form below.
SAAS services
Do you want to have integrations with popular services on the market, but do not want to make connectors? Add your service to ApiMonster, learn more here.
Seller on Ozon/WB/Kaspi
Popular tasks
- Transferring applications from Ozon, Wildberries, Kaspi marketplaces to CRM and Google Sheets
- Synchronization of statuses between CRM and Ozon, Wildberries, Kaspi
- Sending orders to Ozon via CDEK
- Notification of new orders in telegram
Popular bundles
-
Ozon > AmoCRM
-
Ozon > MoySklad
-
Ozon > RetailCrm
-
Ozon > CDEK
-
Ozon > Telegram
-
Ozon > Google Sheets
-
Wildberries > AmoCRM
-
Wildberries > MoySklad
-
Wildberries > RetailCrm
-
Wildberries > Telegram
-
Wildberries > Google Sheets
-
Kaspi.kz > AmoCRM
-
Kaspi.kz > MoySklad
-
Kaspi.kz > RetailCrm
-
Kaspi.kz > Telegram
-
Kaspi.kz > Google Sheets
If you haven't found a suitable bundle here, look for your set of services on the form below.
Seller on Avito
Popular tasks
- Creating deals in CRM for new messages on ads
- Creating deals in CRM for orders
- Notifications in telegram
Popular bundles
If you haven't found a suitable bundle here, look for your set of services on the form below.
Online schools
Popular tasks
- Creating deals in CRM based on the fact of orders in GetCourse
- Sending conversions in Yandex Metric and Google Analytics on the fact of orders in GetCourse
- Registration of new users
Popular bundles
-
Getcourse > AmoCRM
-
AmoCRM > Getcourse
-
Tilda > Getcourse
-
Getcourse > Yandex Metric
-
Getcourse > Telegram
If you haven't found a suitable bundle here, look for your set of services on the form below.
Sales Manager
Popular tasks
- Wiretapping and call quality control. ApiMonster is able to recognize calls and make scoring.
Popular bundles
If you haven't found a suitable bundle here, look for your set of services on the form below.
Developer
Do boring, uninteresting tasks on a bundle of services via ApiMonster. There is no need to solve solved problems 101 times.
Popular tasks
- Connecting self-made solutions to CRM, analytics and other popular services
- Receiving webhooks from popular services to your server
Popular bundles
-
The invoice of the forms > AmoCRM
-
Incoming webhooks > AmoCRM
-
The invoice of the forms > Bitrix24
-
Incoming webhooks > Bitrix24
-
The invoice of the forms > Yandex Metric
-
Incoming webhooks > Yandex Metric
-
The invoice of the forms > Google Analytics 4
-
Incoming webhooks > Google Analytics 4
-
The invoice of the forms > Telegram
-
Incoming webhooks > Telegram
-
AmoCRM > Outgoing webhooks (http request)
If you haven't found a suitable bundle here, look for your set of services on the form below.
Tools
-
JavaScript/NodeJs -
you can use JavaScript for complex data processing before sending it to another service
Devops
Monitor the availability of your sites with notification of problems via telegram or email
Popular tasks
- Monitoring the availability of sites
Popular bundles
If you haven't found a suitable bundle here, look for your set of services on the form below.
CRM Integrator
ApiMonster allows you to solve almost all typical tasks of connecting a business to CRM. For particularly difficult tasks, it is possible to write logic in JavaScript.
Popular tasks
- Transfer of applications from the website to the CRM
- Transferring applications from other services to CRM
- Sending conversions in Yandex Metric and Google Analytics at different stages of transactions
- The complex logic of changing data when transferring between services
Popular bundles
-
Tilda > AmoCRM
-
The invoice of the forms > AmoCRM
-
Incoming webhooks > AmoCRM
-
Marquiz > AmoCRM
-
Tilda > Bitrix24
-
The invoice of the forms > Bitrix24
-
Incoming webhooks > Bitrix24
-
Marquiz > Bitrix24
-
The invoice of the forms > RetailCrm
-
Incoming webhooks > RetailCrm
-
The invoice of the forms > MoySklad
-
Incoming webhooks > MoySklad
-
AmoCRM > Google Analytics 4
-
Bitrix24 > Google Analytics 4
-
AmoCRM > Yandex Metric
-
Bitrix24 > Yandex Metric
If you haven't found a suitable bundle here, look for your set of services on the form below.
Tools
-
JavaScript/NodeJs -
you can use JavaScript for complex data processing before sending it to another service
Restaurants
IIKO is a complex service for self-integration, it is better to do it through ApiMonster.
Popular tasks
- Transfer of applications from Tilda to IIKO
- Transfer of applications from IIKO to CRM
Popular bundles
Tilda > Iiko If you haven't found a suitable bundle here, look for your set of services on the form below.
Affiliate Marketing
ApiMonster allows you to accept sales from any service and centrally upload them to CpaMonster to calculate payments to partners.
Popular tasks
- Transfer of sales to calculate payments to partners
Popular bundles
AmoCRM > CPAMonster If you haven't found a suitable bundle here, look for your set of services on the form below.
Admin in Telegram
ApiMonster allows you to set up automatic moderation and ban spam accounts.
Popular tasks
- Ban a member who is engaged in spam.
Popular bundles
If you haven't found a suitable bundle here, look for your set of services on the form below.
For everyone
ApiMonster can work with any services that have webhooks and APIs. If you have not found a ready-made solution for your task, look for your service in the form below.
Turnkey setting
We are ready to help you with solving problems of any complexity, leave a request here.
Free course
If you have a lot of tasks for no-code, figure out how to work with ApiMonster yourself. We did free course on YouTube.
Complex development
If standard tools cannot solve your problem, development is needed and our experience is relevant - leave a request here, let's see how we can help.
Community
Follow the news of the service on telegram channel, ask questions in chat.
Find my services
Enter your services in the form below to see the features.
Customer reviews
Despite my misunderstanding of the connection process, the team helped me figure it out and the integration was set up successfully. Thanks!
Integration was set up quickly and clearly. Everything works like clockwork.
Excellent, the integration of SDEC with Ozone was set up quickly enough.
We quickly set up synchronization between Ozone and SDEC. Operational support.
It was necessary to set up the integration of cyanogen with AMO, the guys coped with the task perfectly! And most importantly, clearly and quickly! Now the leads will not pass by)
There are quite large free (regular) features. It is intuitive how to work and configure data exchange. Additionally, I would like to mention the loyal support service, which even in demo mode provides all possible assistance with tips.
I made the integration of OZONE-SDEK to automatically create shipments according to the RFBS work scheme. Now I save about 4 hours of time, instead of manually creating invoices. Everything works. Thank you very much!
We contacted you promptly and promptly to set up the integration. High-quality service.
The specialists of the Apimonstr company promptly configured all the necessary parameters. The interaction was carried out via WhatsApp chat. The whole process took one day after the bill was paid. So far, as a beginner, everything is clear and accessible to me. The tincture is completed, the system works smoothly, I hope for long-term and fruitful cooperation. Thank you for your work.
Prompt solution of assigned tasks. They will prompt and help you with all your questions. There are also detailed instructions for typical tasks. There are video instructions.
1) Fast connection 2) Intuitive interface 3) Reasonable price of services 4) Active support service
Fast, convenient, good interface
30 days free of charge
Ready connectors and tools
If the desired service is not in the list, then the universal connector "Incoming webhooks" can be used to receive webhooks and further create bundles, and the connector %2 can be used to send outgoing get/post requests%
Connectors
Tools
Widgets for the site
Didn't find the right service?
If the service has an API and webhooks, then it can be connected via universal connectors
Pricing
We give you 30 days for a free test, all the functionality is available.
Tariff plans
There is no discount
Discount 5%
Discount 10%
Discount 25%
Cost calculator for your project and commercial offer in PDF format here.
Tariff 1
$14 / month.
-
1 100 transactions / month.
Approximately 367 of orders/requests
per month, depends on the complexity of the bundles.
-
10 000 webhooks / month.
-
4 days is the storage period for the history of webhooks
-
Before 30 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 5 days.
Tariff 2
$39 / month.
-
5 000 transactions / month.
Approximately 1667 of orders/requests
per month, depends on the complexity of the bundles.
-
50 000 webhooks / month.
-
7 days is the storage period for the history of webhooks
-
Before 50 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 14 days.
Tariff 3
$69 / month.
-
10 000 transactions / month.
Approximately 3333 of orders/requests
per month, depends on the complexity of the bundles.
-
100 000 webhooks / month.
-
10 days is the storage period for the history of webhooks
-
Before 70 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 21 days.
Tariff 4
$99 / month.
-
15 000 transactions / month.
Approximately 5000 of orders/requests
per month, depends on the complexity of the bundles.
-
150 000 webhooks / month.
-
14 days is the storage period for the history of webhooks
-
Before 100 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Free Settings
turnkey -
Constant support in chat
-
-
Ozon Parsing period/Wildberries/Kaspi: 30 days.
FAQ
Why is it profitable to pay for ApiMonster?
An alternative to ApiMonster is to work directly with programmers whose salaries start from 150,000 rubles/month. You will spend significantly more money and time to solve a problem that has already been solved in ApiMonster. Also, working through ApiMonster, you get maximum stability in solving your problem - ApiMonster works offline 24/7, will not disappear, will not get sick.
I'm not sure if the service is suitable for me, does it make sense to test?
The service performs thousands of different actions every day. If your task can be solved through the service, we guarantee that everything will work. If you find it difficult to set up yourself, there is a turnkey setup.
What is a webhook?
Any http request included in ApiMonster get/post. For example, a notification from amoCRM about the creation of a new deal.
What is a transaction?
This is any outgoing webhook (api request): send a conversion, create/find a deal/contact/task, and so on.
How many transactions do you need?
Multiply the number of applications per month by 3-4. For example, if applications are 100, then transactions will be about 300-400 & mdash; Create transactions, send conversions, notifications. For personal calculation of the tariff, use calculator.
How many incoming webhooks do I need per month?
Usually 2-5 times the number of transactions. This restriction was introduced to reduce the load from projects with an abnormal number of webhooks that create unnecessary load. If you don't send 10 webhooks per second, then the limit is probably not relevant for you.
What is the retention period of the webhook history?
The webhook history is needed in case you find errors in the bundle and want to see what came in the webhook for debugging. The content of webhooks can require a lot of storage resources, so a restriction has been introduced. This parameter does not affect the work of the bundles.
1-3 days are enough to set up the bundles.
How many incoming webhuks do you need per second?
Usually incoming webhuk is the creation or update of the application. This event rarely occurs more often than 1 time per second, so there is more than enough limit of 5-30 webhuk per second.
Tariff 5
$159 / month.
-
30 000 transactions / month.
Approximately 10000 of orders/requests
per month, depends on the complexity of the bundles.
-
300 000 webhooks / month.
-
21 days is the storage period for the history of webhooks
-
Before 150 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Free Settings
turnkey -
Constant support in chat
-
-
Ozon Parsing period/Wildberries/Kaspi: 45 days.
Tariff 6
$299 / month.
-
100 000 transactions / month.
Approximately 33333 of orders/requests
per month, depends on the complexity of the bundles.
-
1 000 000 webhooks / month.
-
30 days is the storage period for the history of webhooks
-
Before 200 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Free Settings
turnkey -
Constant support in chat
-
-
Ozon Parsing period/Wildberries/Kaspi: 45 days.
Tariff 7
$399 / month.
-
200 000 transactions / month.
Approximately 66667 of orders/requests
per month, depends on the complexity of the bundles.
-
2 000 000 webhooks / month.
-
30 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Free Settings
turnkey -
Constant support in chat
-
-
Ozon Parsing period/Wildberries/Kaspi: 45 days.
FAQ
Why is it profitable to pay for ApiMonster?
An alternative to ApiMonster is to work directly with programmers whose salaries start from 150,000 rubles/month. You will spend significantly more money and time to solve a problem that has already been solved in ApiMonster. Also, working through ApiMonster, you get maximum stability in solving your problem - ApiMonster works offline 24/7, will not disappear, will not get sick.
I'm not sure if the service is suitable for me, does it make sense to test?
The service performs thousands of different actions every day. If your task can be solved through the service, we guarantee that everything will work. If you find it difficult to set up yourself, there is a turnkey setup.
What is a webhook?
Any http request included in ApiMonster get/post. For example, a notification from amoCRM about the creation of a new deal.
What is a transaction?
This is any outgoing webhook (api request): send a conversion, create/find a deal/contact/task, and so on.
How many transactions do you need?
Multiply the number of applications per month by 3-4. For example, if applications are 100, then transactions will be about 300-400 & mdash; Create transactions, send conversions, notifications. For personal calculation of the tariff, use calculator.
How many incoming webhooks do I need per month?
Usually 2-5 times the number of transactions. This restriction was introduced to reduce the load from projects with an abnormal number of webhooks that create unnecessary load. If you don't send 10 webhooks per second, then the limit is probably not relevant for you.
What is the retention period of the webhook history?
The webhook history is needed in case you find errors in the bundle and want to see what came in the webhook for debugging. The content of webhooks can require a lot of storage resources, so a restriction has been introduced. This parameter does not affect the work of the bundles.
1-3 days are enough to set up the bundles.
How many incoming webhuks do you need per second?
Usually incoming webhuk is the creation or update of the application. This event rarely occurs more often than 1 time per second, so there is more than enough limit of 5-30 webhuk per second.
Tariff 8
$499 / month.
-
300 000 transactions / month.
Approximately 100000 of orders/requests
per month, depends on the complexity of the bundles.
-
3 000 000 webhooks / month.
-
30 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Free Settings
turnkey -
Constant support in chat
-
-
Ozon Parsing period/Wildberries/Kaspi: 45 days.
Tariff 9
$599 / month.
-
400 000 transactions / month.
Approximately 133333 of orders/requests
per month, depends on the complexity of the bundles.
-
4 000 000 webhooks / month.
-
30 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Free Settings
turnkey -
Constant support in chat
-
-
Ozon Parsing period/Wildberries/Kaspi: 45 days.
Tariff 10
$699 / month.
-
500 000 transactions / month.
Approximately 166667 of orders/requests
per month, depends on the complexity of the bundles.
-
5 000 000 webhooks / month.
-
30 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Free Settings
turnkey -
Constant support in chat
-
-
Ozon Parsing period/Wildberries/Kaspi: 45 days.
FAQ
Why is it profitable to pay for ApiMonster?
An alternative to ApiMonster is to work directly with programmers whose salaries start from 150,000 rubles/month. You will spend significantly more money and time to solve a problem that has already been solved in ApiMonster. Also, working through ApiMonster, you get maximum stability in solving your problem - ApiMonster works offline 24/7, will not disappear, will not get sick.
I'm not sure if the service is suitable for me, does it make sense to test?
The service performs thousands of different actions every day. If your task can be solved through the service, we guarantee that everything will work. If you find it difficult to set up yourself, there is a turnkey setup.
What is a webhook?
Any http request included in ApiMonster get/post. For example, a notification from amoCRM about the creation of a new deal.
What is a transaction?
This is any outgoing webhook (api request): send a conversion, create/find a deal/contact/task, and so on.
How many transactions do you need?
Multiply the number of applications per month by 3-4. For example, if applications are 100, then transactions will be about 300-400 & mdash; Create transactions, send conversions, notifications. For personal calculation of the tariff, use calculator.
How many incoming webhooks do I need per month?
Usually 2-5 times the number of transactions. This restriction was introduced to reduce the load from projects with an abnormal number of webhooks that create unnecessary load. If you don't send 10 webhooks per second, then the limit is probably not relevant for you.
What is the retention period of the webhook history?
The webhook history is needed in case you find errors in the bundle and want to see what came in the webhook for debugging. The content of webhooks can require a lot of storage resources, so a restriction has been introduced. This parameter does not affect the work of the bundles.
1-3 days are enough to set up the bundles.
How many incoming webhuks do you need per second?
Usually incoming webhuk is the creation or update of the application. This event rarely occurs more often than 1 time per second, so there is more than enough limit of 5-30 webhuk per second.
Whitelable 1
$600 / month.
-
100 000 transactions / month.
Approximately 33333 of orders/requests
per month, depends on the complexity of the bundles.
-
1 000 000 webhooks / month.
-
2 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Free Settings
turnkey -
Constant support in chat
-
-
Ozon Parsing period/Wildberries/Kaspi: 5 days.
Whitelable 2
$1,200 / month.
-
200 000 transactions / month.
Approximately 66667 of orders/requests
per month, depends on the complexity of the bundles.
-
2 000 000 webhooks / month.
-
2 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Free Settings
turnkey -
Constant support in chat
-
-
Ozon Parsing period/Wildberries/Kaspi: 14 days.
Whitelable 3
$2,400 / month.
-
400 000 transactions / month.
Approximately 133333 of orders/requests
per month, depends on the complexity of the bundles.
-
4 000 000 webhooks / month.
-
2 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Free Settings
turnkey -
Constant support in chat
-
-
Ozon Parsing period/Wildberries/Kaspi: 21 days.
FAQ
Why is it profitable to pay for ApiMonster?
An alternative to ApiMonster is to work directly with programmers whose salaries start from 150,000 rubles/month. You will spend significantly more money and time to solve a problem that has already been solved in ApiMonster. Also, working through ApiMonster, you get maximum stability in solving your problem - ApiMonster works offline 24/7, will not disappear, will not get sick.
I'm not sure if the service is suitable for me, does it make sense to test?
The service performs thousands of different actions every day. If your task can be solved through the service, we guarantee that everything will work. If you find it difficult to set up yourself, there is a turnkey setup.
What is a webhook?
Any http request included in ApiMonster get/post. For example, a notification from amoCRM about the creation of a new deal.
What is a transaction?
This is any outgoing webhook (api request): send a conversion, create/find a deal/contact/task, and so on.
How many transactions do you need?
Multiply the number of applications per month by 3-4. For example, if applications are 100, then transactions will be about 300-400 & mdash; Create transactions, send conversions, notifications. For personal calculation of the tariff, use calculator.
How many incoming webhooks do I need per month?
Usually 2-5 times the number of transactions. This restriction was introduced to reduce the load from projects with an abnormal number of webhooks that create unnecessary load. If you don't send 10 webhooks per second, then the limit is probably not relevant for you.
What is the retention period of the webhook history?
The webhook history is needed in case you find errors in the bundle and want to see what came in the webhook for debugging. The content of webhooks can require a lot of storage resources, so a restriction has been introduced. This parameter does not affect the work of the bundles.
1-3 days are enough to set up the bundles.
How many incoming webhuks do you need per second?
Usually incoming webhuk is the creation or update of the application. This event rarely occurs more often than 1 time per second, so there is more than enough limit of 5-30 webhuk per second.
Check out the possibilities of integrating Call-Tracking.by with other services
Click on the service to see how it works in conjunction with Call-Tracking.by.
Check out the possibilities of integrating RetailCrm with other services
Click on the service to see how it works in conjunction with RetailCrm.