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 Zvonok (Call) and Unisender (Unisender)

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 Zvonok

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

API documentation — here.

Description

Not

Available fields

Id	Name
`ct_campaign_id`	Phone campaign ID (bigint type)
`ct_phone`	The customer's number in the format +79999999999
`ct_phone8`	The customer's number in the format 89999999999
`ct_phone9`	The customer's number in the format 9999999999
`ct_call_id`	Call ID (bigint type)
`ct_completed`	The end date of the call in the format 2017-12-23 23:59:59
`ct_status`	Call status (type: string)
`ct_dial_status`	Call status (type: int)
`ct_button_num`	The pressed button (may be empty if the button has not been pressed)
`ct_duration`	Duration of the call

+ 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 Unisender

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

API documentation — No.

Request fields

Id	Name
`sender_name`	Sender's name
`sender_email`	Sender's e-mail address
`subject`	The subject of the letter. May include substitution fields
`body`	The text of the letter in HTML format with the ability to add substitution fields
`list_id`	The code of the list to which the e-mail mailing list will be sent
`text_body`	The text version of the letter
`generate_text`	Generating a text version of the letter. Value: 1 - yes, 0 - no (default is 0)
`tag`	Mark. If set, the mailing list will be sent only to those recipients who have been assigned the specified label.
`lang`	Two-letter language code
`template_id`	Id of the custom email template
`system_template_id`	The ID of the system email template
`wrap_type`	Alignment of the message text to the specified edge. Values: right, left, center and skip (do not apply, default)

Answer fields

Id	Name
`message_id`	Message ID

Request fields

Id	Name
`message_id`	The code of the message to be sent
`start_time`	The date and time of the launch of the mailing list in the format "YYYY-MM-DD hh:mm", which do not exceed 100 days from the current date
`timezone`	The time zone in which the time is specified in the "start_time" argument. If not specified, the time zone from the Personal Account settings is used
`contacts`	Comma-separated email addresses
`contacts_url`	URLs with email addresses
`track_read`	Tracking the fact of reading. 1 - yes, 0 - no. The default value is 0
`track_links`	Tracking clicks on links. 1 - yes. 0 - no. The default value is 0
`track_ga`	Enabling integration with Google Analytics/Yandex.Metrica. 1 - yes. 0 - no. The default value is 0
`payment_limit`	Distribution budget limit
`ga_medium`	ga_medium
`ga_source`	ga_source
`ga_campaign`	ga_campaign
`ga_content`	ga_content
`ga_term`	ga_term

Answer fields

Id	Name
`campaign_id`	The unique mailing code is a positive 31-bit integer.
`status`	Mailing status

Swap Zvonok with Unisender

Refract turnkey

View opportunities Zvonok

View opportunities Unisender

Integration setup plan Zvonok with Unisender

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.