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.
Not
Id | Name |
---|---|
update_id
|
The ID of the webhook |
channel_post.message_id
|
Message ID |
channel_post.sender_chat.id
|
User ID |
channel_post.sender_chat.title
|
Channel Name |
channel_post.sender_chat.type
|
Chat Type |
channel_post.chat.id
|
User ID |
channel_post.chat.title
|
Channel Name |
channel_post.chat.type
|
Chat Type |
channel_post.date
|
The time of sending the webhook in timestamp format |
channel_post.text
|
Message text |
+ You can add your fields that are in webhuk.
Not
Id | Name |
---|---|
update_id
|
The ID of the webhook |
message.message_id
|
Message ID |
message.from.id
|
User ID |
message.from.is_bot
|
Flag whether the user is a bot |
message.from.first_name
|
Username |
message.from.last_name
|
Last name of the user |
message.from.username
|
User's nickname |
message.from.language_code
|
User's language |
message.from.is_premium
|
The flag for whether the user has a Telegram Premium subscription |
message.chat.id
|
Message ID |
message.chat.title
|
The name of the group |
message.chat.type
|
Type: group |
message.chat.all_members_are_administrators
|
Flag whether all users are administrators |
message.date
|
The time of sending the webhook in timestamp format |
message.text
|
Message text |
message.external_chat_user_id
|
message.external_chat_user_id |
message.external_chat_id
|
message.external_chat_id |
+ You can add your fields that are in webhuk.
If you haven't found the right event, but the service has the right webhook, then use the universal connector "Including webhuk". It will be possible to tie the logic of bundles to any field that comes in the webhook.
Click on the name of the action to see the available fields.
API documentation — No.
Id | Name |
---|---|
departmentid
|
Department ID |
emailqueueid
|
Queue Email ID |
ticketstatusid
|
Ticket status |
ticketpriorityid
|
Ticket priority |
tickettypeid
|
Ticket type |
templategroup
|
Ticket Template |
autouserid
|
Flag for automatic user creation |
email
|
Email of the ticket creator |
fullname
|
Name of the ticket creator |
subject
|
Ticket title |
contents
|
Ticket contents |
Id | Name |
---|---|
id
|
Ticket 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.