Sendsay
Connect Sendsay to the AI agent: subscribers, groups, segments, issues and triggers
Connect Sendsay to the AI agent: subscribers, groups, segments, issues and triggers. The agent breaks down deliveries, opens and clicks and tidies up the base.
DocumentationДоставлено 18 402 письма, открытий 31,7%, кликов 4,2%.
- Выпуск «Летняя коллекция» — отписок 0,3%, это норма для базы
- Из шести ссылок 71% кликов собрала одна — кнопка в первом экране
- Возвраты выросли до 1,8%: 214 адресов из группы «Импорт-2024»
Integration scenarios
Breakdown of the latest campaign
The agent splits an issue by deliveries, opens, clicks and unsubscribes and shows which emails and links worked and which did not.
Order in the subscriber base
The agent reviews groups and segments, finds unsubscribed and long-inactive contacts and updates subscriber records from your data.
Preparing an issue and an A/B test
The agent assembles an issue from a template, sends a test email for review and shows the split test results once it has gone out.
Weekly campaign summary
On a schedule the agent sends a summary: deliverability, subscriber activity and growth of the base for the week against the previous one.
How to connect
Create a separate sublogin for the integration
Account menu → «Настройки системы» (System settings) → «Пользователи» (Users) → «Добавить пользователя»: name, login, email, password. The account owner cannot be issued an API key, so a sublogin is mandatory.
Grant rights to the sublogin and leave 2FA off
The «Менеджер» (Manager) role covers subscribers, campaigns and automations; for finer control use the «Права доступа» (Access rights) tab in advanced mode. Never enable two-factor auth here — requests with the key stop working.
Generate the API key in the sublogin card
Open the user card → «Настройка пользователя» (User settings) tab → «API-ключ» section → «Сгенерировать ключ». The key is shown once at generation: copy it immediately, a lost key can only be replaced, never re-read.
Write down the account name — your main login
The account name is the main login that created the sublogin; it is shown in the account menu and goes into the API address https://api.sendsay.ru/general/api/v100/json/<login>. The sublogin's own login will not work here.
What the agent does in the first 10 minutes
- Breaks the latest campaign down by deliveries, opens, clicks and unsubscribes, and shows which emails and links actually worked
- Cleans up the contact base: reconciles groups and segments, finds unsubscribed and inactive contacts, updates subscriber records
- Sends a weekly digest on campaigns and list growth — agree on the day and time, and it keeps running on its own
FAQ
How do I connect Sendsay?
With the account name and an API key: create a separate sublogin under System settings, Users — the account owner is not issued a key — and in its card, on the User setup tab, click Generate key. The account name is the main login.
What does the agent see in Sendsay?
Subscribers and their fields, groups and segments, issues and templates, trigger scenarios and statistics on deliveries, opens, clicks, unsubscribes and bounces.
Does the agent write to Sendsay?
It can: update subscriber records and group membership, assemble issues, send test emails and launch a campaign. The agent sends only on your explicit confirmation, never on its own.
Why is the key not working?
Most often two-factor authorization is enabled on the sublogin — requests by key do not run while it is on. The second case: the account field holds the sublogin instead of the main login.
