Developments
Click on the name of the event to see available fields.
API documentation — No.
Description
Notification of a new application within 1-2 minutes after its creation in utmstat
Available fields
| Id | Name |
|---|---|
event_name
|
Event code |
id
|
Application ID |
project_id
|
Project ID |
status_id
|
Status code |
status_name
|
Status |
amount
|
Sum |
type.id
|
The code of the client's contact method |
type.name
|
The name of the client's contact method |
contact.id
|
Contact ID |
contact.phone
|
Telephone |
contact.email
|
|
contact.name
|
Name |
fields.order_price.value
|
Potential revenue by application |
source.first_click.utm.utm_source
|
Utm source in the "First Click" attribution |
source.first_click.utm.utm_medium
|
Utm medium in the "First Click" attribution |
source.first_click.utm.utm_campaign
|
Utm campaign in the "First Click" attribution |
source.first_click.utm.utm_content
|
Utm content in the "First Click" attribution |
source.first_click.utm.utm_term
|
Utm term in the "First Click" attribution |
source.first_click.ppc.campaign_id
|
The campaign ID in the "First click" attribution |
source.first_click.ppc.group_id
|
The ID of the group in the "First click" attribution |
source.first_click.ppc.ad_id
|
The ad ID in the "First click" attribution |
source.first_click.ppc.phrase_id
|
The ID of the phrase in the "First click" attribution |
source.first_click.ppc.keyword
|
The keyword in the attribution is "First click" |
source.first_click.device.device_type_id
|
The device type code in the "First click" attribution |
source.first_click.device.device_type_name
|
The name of the device type in the "First click" attribution |
source.first_click.device.device_id
|
The device code in the "First click" attribution |
source.first_click.device.device_name
|
The name of the device in the "First click" attribution |
source.first_click.device.screen_resolution
|
Screen resolution in the "First click" attribution |
source.first_click.site.domain
|
Domain in the "First click" attribution |
source.first_click.site.url
|
Url in the "First click" attribution |
source.first_click.site.url_path
|
Url without parameters in the "First click" attribution |
source.first_click.geo.country_id
|
Country code by SxGeo in the "First click" attribution |
source.first_click.geo.country_name
|
Country name by SxGeo in the "First click" attribution |
source.first_click.geo.region_id
|
The SxGeo region code in the "First Click" attribution |
source.first_click.geo.region_name
|
The name of the region according to SxGeo in the "First click" attribution |
source.first_click.geo.city_id
|
The SxGeo area code in the "First Click" attribution |
source.first_click.geo.city_name
|
The name of the city according to SxGeo in the "First click" attribution |
source.first_click.clients_id.utmstat_client_id
|
Client id for utmstat in the "First click" attribution |
source.first_click.clients_id.google_client_id
|
Client id for google analytics in the "First click" attribution |
source.first_click.clients_id.yandex_client_id
|
Client id for yandex. metrica in the "First click" attribution |
source.first_click.clients_id.facebook_client_id
|
Client id for Facebook in the "First click" attribution |
source.first_click.date.created_at
|
The date the click was created in the "First click" attribution |
source.first_click.date.timestamp
|
Timestamp of creating a click in the "First click" attribution |
source.last_significant_click.utm.utm_source
|
Utm source in the "Last significant Click" attribution |
source.last_significant_click.utm.utm_medium
|
Utm medium in the "Last significant Click" attribution |
source.last_significant_click.utm.utm_campaign
|
Utm campaign in the "Last Significant Click" attribution |
source.last_significant_click.utm.utm_content
|
Utm content in the "Last significant Click" attribution |
source.last_significant_click.utm.utm_term
|
Utm term in the "Last significant Click" attribution |
source.last_significant_click.ppc.campaign_id
|
The campaign ID in the "Last significant Click" attribution |
source.last_significant_click.ppc.group_id
|
The ID of the group in the "Last significant click" attribution |
source.last_significant_click.ppc.ad_id
|
The ad ID in the "Last significant click" attribution |
source.last_significant_click.ppc.phrase_id
|
The ID of the phrase in the "Last significant click" attribution |
source.last_significant_click.ppc.keyword
|
The keyword in the attribution is "Last significant click" |
source.last_significant_click.device.device_type_id
|
The device type code in the "Last significant click" attribution |
source.last_significant_click.device.device_type_name
|
The name of the device type in the "Last significant click" attribution |
source.last_significant_click.device.device_id
|
The device code in the "Last significant click" attribution |
source.last_significant_click.device.device_name
|
The name of the device in the "Last significant click" attribution |
source.last_significant_click.device.screen_resolution
|
The screen resolution in the "Last significant click" attribution |
source.last_significant_click.site.domain
|
The domain in the "Last significant click" attribution |
source.last_significant_click.site.url
|
Url in the "Last significant click" attribution |
source.last_significant_click.site.url_path
|
Url without parameters in the "Last significant click" attribution |
source.last_significant_click.geo.country_id
|
The country code according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.geo.country_name
|
The name of the country according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.geo.region_id
|
The SxGeo region code in the "Last significant Click" attribution |
source.last_significant_click.geo.region_name
|
The name of the region according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.geo.city_id
|
The SxGeo area code in the "Last significant Click" attribution |
source.last_significant_click.geo.city_name
|
The name of the city according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.clients_id.utmstat_client_id
|
Client id for utmstat in the "Last significant click" attribution |
source.last_significant_click.clients_id.google_client_id
|
Client id for google analytics in the "Last significant Click" attribution |
source.last_significant_click.clients_id.yandex_client_id
|
Client id for yandex.metrica in the "Last significant click" attribution |
source.last_significant_click.clients_id.facebook_client_id
|
Client id for Facebook in the "Last significant Click" attribution |
source.last_significant_click.date.created_at
|
The date the click was created in the "Last significant click" attribution |
source.last_significant_click.date.timestamp
|
Timestamp of click creation in the "Last significant Click" attribution |
+ You can add your fields that are in webhuk.
Description
Notification of a new application within 1-2 minutes after its creation in utmstat
Available fields
| Id | Name |
|---|---|
event_name
|
Event code |
id
|
Application ID |
project_id
|
Project ID |
status_id
|
Status code |
status_name
|
Status |
amount
|
Sum |
type.id
|
The code of the client's contact method |
type.name
|
The name of the client's contact method |
contact.id
|
Contact ID |
contact.phone
|
Telephone |
contact.email
|
|
contact.name
|
Name |
fields.order_price.value
|
Potential revenue by application |
source.first_click.utm.utm_source
|
Utm source in the "First Click" attribution |
source.first_click.utm.utm_medium
|
Utm medium in the "First Click" attribution |
source.first_click.utm.utm_campaign
|
Utm campaign in the "First Click" attribution |
source.first_click.utm.utm_content
|
Utm content in the "First Click" attribution |
source.first_click.utm.utm_term
|
Utm term in the "First Click" attribution |
source.first_click.ppc.campaign_id
|
The campaign ID in the "First click" attribution |
source.first_click.ppc.group_id
|
The ID of the group in the "First click" attribution |
source.first_click.ppc.ad_id
|
The ad ID in the "First click" attribution |
source.first_click.ppc.phrase_id
|
The ID of the phrase in the "First click" attribution |
source.first_click.ppc.keyword
|
The keyword in the attribution is "First click" |
source.first_click.device.device_type_id
|
The device type code in the "First click" attribution |
source.first_click.device.device_type_name
|
The name of the device type in the "First click" attribution |
source.first_click.device.device_id
|
The device code in the "First click" attribution |
source.first_click.device.device_name
|
The name of the device in the "First click" attribution |
source.first_click.device.screen_resolution
|
Screen resolution in the "First click" attribution |
source.first_click.site.domain
|
Domain in the "First click" attribution |
source.first_click.site.url
|
Url in the "First click" attribution |
source.first_click.site.url_path
|
Url without parameters in the "First click" attribution |
source.first_click.geo.country_id
|
Country code by SxGeo in the "First click" attribution |
source.first_click.geo.country_name
|
Country name by SxGeo in the "First click" attribution |
source.first_click.geo.region_id
|
The SxGeo region code in the "First Click" attribution |
source.first_click.geo.region_name
|
The name of the region according to SxGeo in the "First click" attribution |
source.first_click.geo.city_id
|
The SxGeo area code in the "First Click" attribution |
source.first_click.geo.city_name
|
The name of the city according to SxGeo in the "First click" attribution |
source.first_click.clients_id.utmstat_client_id
|
Client id for utmstat in the "First click" attribution |
source.first_click.clients_id.google_client_id
|
Client id for google analytics in the "First click" attribution |
source.first_click.clients_id.yandex_client_id
|
Client id for yandex. metrica in the "First click" attribution |
source.first_click.clients_id.facebook_client_id
|
Client id for Facebook in the "First click" attribution |
source.first_click.date.created_at
|
The date the click was created in the "First click" attribution |
source.first_click.date.timestamp
|
Timestamp of creating a click in the "First click" attribution |
source.last_significant_click.utm.utm_source
|
Utm source in the "Last significant Click" attribution |
source.last_significant_click.utm.utm_medium
|
Utm medium in the "Last significant Click" attribution |
source.last_significant_click.utm.utm_campaign
|
Utm campaign in the "Last Significant Click" attribution |
source.last_significant_click.utm.utm_content
|
Utm content in the "Last significant Click" attribution |
source.last_significant_click.utm.utm_term
|
Utm term in the "Last significant Click" attribution |
source.last_significant_click.ppc.campaign_id
|
The campaign ID in the "Last significant Click" attribution |
source.last_significant_click.ppc.group_id
|
The ID of the group in the "Last significant click" attribution |
source.last_significant_click.ppc.ad_id
|
The ad ID in the "Last significant click" attribution |
source.last_significant_click.ppc.phrase_id
|
The ID of the phrase in the "Last significant click" attribution |
source.last_significant_click.ppc.keyword
|
The keyword in the attribution is "Last significant click" |
source.last_significant_click.device.device_type_id
|
The device type code in the "Last significant click" attribution |
source.last_significant_click.device.device_type_name
|
The name of the device type in the "Last significant click" attribution |
source.last_significant_click.device.device_id
|
The device code in the "Last significant click" attribution |
source.last_significant_click.device.device_name
|
The name of the device in the "Last significant click" attribution |
source.last_significant_click.device.screen_resolution
|
The screen resolution in the "Last significant click" attribution |
source.last_significant_click.site.domain
|
The domain in the "Last significant click" attribution |
source.last_significant_click.site.url
|
Url in the "Last significant click" attribution |
source.last_significant_click.site.url_path
|
Url without parameters in the "Last significant click" attribution |
source.last_significant_click.geo.country_id
|
The country code according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.geo.country_name
|
The name of the country according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.geo.region_id
|
The SxGeo region code in the "Last significant Click" attribution |
source.last_significant_click.geo.region_name
|
The name of the region according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.geo.city_id
|
The SxGeo area code in the "Last significant Click" attribution |
source.last_significant_click.geo.city_name
|
The name of the city according to SxGeo in the "Last significant click" attribution |
source.last_significant_click.clients_id.utmstat_client_id
|
Client id for utmstat in the "Last significant click" attribution |
source.last_significant_click.clients_id.google_client_id
|
Client id for google analytics in the "Last significant Click" attribution |
source.last_significant_click.clients_id.yandex_client_id
|
Client id for yandex.metrica in the "Last significant click" attribution |
source.last_significant_click.clients_id.facebook_client_id
|
Client id for Facebook in the "Last significant Click" attribution |
source.last_significant_click.date.created_at
|
The date the click was created in the "Last significant click" attribution |
source.last_significant_click.date.timestamp
|
Timestamp of click creation in the "Last significant Click" attribution |
+ You can add your fields that are in webhuk.
Description
Once a day, utmstat analyzes all applications for the last 14 days and evaluates the contracts in them in terms of readiness for purchase and the status of processing the last application by the manager. It is useful for automating basic control over the processing of applications by managers, for example, to create tasks if applications with a large receipt have not been processed.
Available fields
| Id | Name |
|---|---|
event_name
|
Event code |
scoring.rmf_rate
|
RFM Analysis result Code |
scoring.interest_rate
|
Interest rating from 0 to 100 |
scoring.recommendation
|
Recommendation for the manager |
contact.id
|
Contact ID |
contact.name
|
Name |
contact.email
|
|
contact.phone
|
Telephone |
geo.sx_geo_country_id
|
Country code by SxGeo |
geo.sx_geo_country_name
|
Country name by SxGeo |
geo.sx_region_id
|
The region code according to Sx Geo |
geo.sx_region_name
|
The name of the region according to SxGeo |
geo.sx_geo_city_id
|
The area code according to SxGeo |
geo.sx_geo_city_name
|
The name of the city according to SxGeo |
visit.last_visited_at
|
Date of the last visit |
visit.last_visited_days_ago
|
How many days have passed since the last visit |
visit.is_visit_after_last_lead
|
Was there a visit after the last request |
visit.last_7_days_visited_count
|
How many consecutive days has the client visited the site in the last 7 days |
crm.leads.last_lead_created_at
|
Date of the last application |
crm.leads.last_lead_created_days_ago
|
How many days have passed since the last request |
crm.leads.last_lead_updated_at
|
The date of the last update of the application |
crm.leads.last_lead_updated_days_ago
|
How many days have passed since the last update of the application |
crm.leads.last_lead_status_id
|
The status code of the last application |
crm.leads.last_lead_status_name
|
Name of the status of the last application |
crm.leads.last_lead_source_id
|
Code of the application receipt method (call/chat/form) |
crm.leads.last_lead_source_name
|
Name of the application receipt method (call/chat/form) |
crm.leads.last_lead_amount
|
Potential revenue from the application |
crm.leads.last_lead_url
|
The URL of the site where the client left the last request |
crm.leads.last_lead_external_manager_id
|
Manager code from an external CRM (amoCRM/Bitrix24) |
crm.leads.last_lead_external_manager_name
|
The name of the manager from the external CRM (amoCRM/Bitrix24) |
crm.leads.last_lead_external_manager_email
|
Email of the manager from an external CRM (amoCRM/Bitrix24) |
crm.leads.last_lead_external_crm_entity_id.Bitrix24
|
Application ID in Bitrix24 |
crm.leads.last_lead_external_crm_entity_id.AmoCRM
|
Application ID in amoCRM |
crm.leads.last_lead_external_crm_entity_id.RetailCRM
|
Application ID in retailCRM |
crm.leads.last_lead_external_crm_entity_type_id
|
The loyalty code in the external CRM (lead/transaction) |
crm.leads.last_lead_external_crm_entity_type_name
|
The name of the entity in the external CRM (lead/transaction) |
crm.leads.leads_count
|
Total customer requests |
crm.sales.last_sale_created_at
|
The date of creation of the last application that was closed for sale |
crm.sales.last_sale_created_days_ago
|
How many days have passed since the last order closed for sale |
crm.sales.last_sale_amount
|
Revenue from the last sale |
crm.sales.sales_count
|
Total sales by customer |
crm.sales.ltv
|
The client's LTV |
+ 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
Click on the name of the action to see the available fields.
API documentation — No.
Request fields
| Id | Name |
|---|---|
name
|
Name |
phone
|
Telephone |
email
|
|
comment
|
Comments |
price
|
Price |
prime_cost
|
Cost price |
status_id
|
Status |
tags
|
Tags |
traffic_source
|
Advertising source |
gclid
|
Google client id |
yclid
|
Yandex client id |
fclid
|
Facebook client id |
uclid
|
Utmstat client id |
external_id
|
Lead ID/deals from CRM |
campaign_id
|
The ID of the advertising campaign |
group_id
|
The ID of the advertising group |
ad_id
|
The ad ID |
Answer fields
| Id | Name |
|---|
Request fields
| Id | Name |
|---|---|
id
|
Application ID in UTMSTAT |
external_id
|
Lead ID/deals from CRM |
price
|
Price |
prime_cost
|
Cost price |
status_id
|
Status |
Answer fields
| Id | Name |
|---|
Request fields
| Id | Name |
|---|---|
email
|
|
phone
|
Telephone |
Answer fields
| Id | Name |
|---|---|
data.id
|
Client ID |
data.email
|
|
data.phone
|
Telephone |
data.last_click_data.yandex_client_id
|
Yandex client id (_ym_uid) |
data.last_click_data.google_client_id
|
Google client id (_ga) |
data.last_click_data.facebook_client_id
|
Facebook client id (fbp) |
data.last_click_data.utm_source
|
Utm Source |
data.last_click_data.utm_medium
|
Utm Medium |
data.last_click_data.utm_content
|
Utm Content |
data.last_click_data.utm_campaign
|
Utm Campaign |
data.last_click_data.utm_term
|
Utm Term |
data.last_click_data.campaign_id
|
The ID of the advertising campaign |
data.last_click_data.group_id
|
The ID of the advertising group |
data.last_click_data.ad_id
|
The ad ID |
data.last_click_data.phrase_id
|
Phrase ID |
data.last_click_data.keyword
|
Phrase |
Request fields
| Id | Name |
|---|---|
projectId
|
projectId |
telephony_name
|
The name of the telephony |
call_id
|
Call ID |
call_start
|
Start date of the call |
caller_id
|
Caller's number (caller_id) |
called_did
|
The number where the call is going (called_did) |
manager_id
|
Manager's ID |
Answer fields
| Id | Name |
|---|
Request fields
| Id | Name |
|---|---|
projectId
|
projectId |
call_id
|
Call ID |
call_start
|
Start date of the call |
caller_id
|
Caller ID |
called_did
|
Start date of the call |
manager_id
|
Manager's ID |
duration
|
Duration of the call |
disposition
|
Call status |
Answer fields
| Id | Name |
|---|
Request fields
| Id | Name |
|---|---|
projectId
|
projectId |
call_id
|
Call ID |
record_url
|
The URL of the conversation recording |
Answer fields
| Id | Name |
|---|
Check out other ApiMonster features
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
Not enough opportunities?
Please fill in the brief and we will try to add new functionality in the coming week.
You can also write to us at Chat in telegram.
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.
Check out the possibilities of integrating Utmstat with other services
Click on the service to see how it works in conjunction with Utmstat.