Connection in 5 minutes, 30 days on tests, try.
Free Turnkey setting, Instructions.
Click on the name of the event to see the available fields.
API documentation — No.
There are no events, try Change to replace the services.
If you haven't found the right event, but the service has the right webhook, then use the universal connector "Including webhuk". It will be possible to tie the logic of bundles to any field that comes in the webhook.
Click on the name of the action to see the available fields.
API documentation — No.
Id | Name |
---|---|
channelId
|
The channel ID (UUID) through which the message should be sent |
chatType
|
Channel Type |
chatId
|
Chat ID (the contact's account in the messenger) |
text
|
The text of the message. Required if contentUri is not specified |
contentUri
|
The link to the file to send. Required if no text is specified |
refMessageId
|
The ID of the message to quote |
crmUserId
|
The CRM user ID specified using CRUD users |
crmMessageId
|
The ID of the message on the CRM side |
username
|
The username of the contact in Telegram, without the "@" at the beginning. It can be used if the chatId is not known |
phone
|
The contact's phone number is in international format, without "+" and other symbols, only numbers. It can be used if the chatId is not known |
clearUnanswered
|
Whether to reset the unanswered counter. To prevent the message from resetting the counter, specify false |
templateId
|
WABA Template Code |
templateValues
|
The values to fill in the variables in the template |
buttonsObject.buttons.0.text
|
For the WABA template: Button text 1, maximum 20 characters |
buttonsObject.buttons.1.text
|
For the WABA template: Button text 2, maximum 20 characters |
buttonsObject.buttons.3.text
|
For the WABA template: 3 button text, maximum 20 characters |
buttonsObject.buttons.4.text
|
For the WABA template: 4 button text, maximum 20 characters |
buttonsObject.id
|
For the WABA template: ID for the buttons |
buttonsObject.payload
|
For the WABA template: Payload from the template message buttons |
Id | Name |
---|---|
messageId
|
Message ID |
1 | Configure the connection for: Service in Apimonster. |
2 | Configure Webhuk in: Service, indicating the link from Apimonster. |
3 | Configure the connection for: Service in Apimonster, indicating the login/password/token for access to the API. |
4 | Create a bunch. |
5 | Indicate as a data source: Service. |
6 | Create the required action for: to_Service, indicating in which fields: to_Service to transmit field values from: from_Service. |
7 | Configure filters for each step if necessary. |
8 | Test the bundles and make sure that they work according to the TOR. |
Or go through the full well on ApiMonster.
Ready-made customized bundles for popular business tasks
Sending orders to sdek, receiving a tracking number
Is free
Communicate in Avito through your trained ChatGPT assistant
$99
Uploading conversions to Yandex.Metrica on the first message from Whatsapp
Is free
The store is in the process of filling up. If you are solving the same field problem in different projects, then it probably has the point is to design it as a template and add it to the store. Write to us.
If you are a developer and want to sell your no-code solutions (with nodejs support) - write to us.