Upgrade to ApiMonster from Zapier, Make, and other no-code services. We have optimal tariffs and a unique Live chat support for your projects DS CLUB.

Integration Salebot and Wazzup 24 (Vazzap 24)

Connection in 5 minutes, 30 days on tests, try.

Accepted webhooks

Done actions

New clients

Try 30 days free

Free Turnkey setting, Instructions.

What data can be transmitted from: from_Service to: to_Service

Important: Please note that the presence of events and actions between the two services does not guarantee a solution your task - the available events and actions may not connect with each other in the way you need.

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 Salebot

Click on the name of the event to see the available fields.

API documentation — No.

Description

Not

Available fields

Id	Name
`id`	The ID of the message in the system
`client.id`	The client's ID in the system
`client.recepient`	The client's ID in the messenger
`client.client_type`	Type of messenger
`client.name`	Client's name
`client.avatar`	The client's avatar
`client.created_at`	Date of creation of the client
`client.tag`	Subscription Key
`client.group`	The bot that the client is linked to
`message`	Message text
`attachments`	An array that contains links to files or dictionaries of links to files
`message_id`	Id of the block from which the message was sent
`project_id`	Project ID
`is_input`	1 if the message is from the client, 0 if it is from the bot
`delivered`	1 if the message was sent successfully, 0 if a sending error occurred
`error_message`	The text of the error message sending

+ 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 Wazzup 24

Click on the name of the action to see the available fields.

API documentation — No.

Request fields

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

Answer fields

Id	Name
`messageId`	Message ID

Swap Salebot with Wazzup 24

Refract turnkey

View opportunities Salebot

View opportunities Wazzup 24

Integration setup plan Salebot with Wazzup 24

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.