OneTrace.pro Help center

Integrations and channels

An integration connects OneTrace.pro to an external service: a mail server, an SMS gateway, a messenger bot, an ad platform, or file storage. Journeys and campaigns work through connected channels, audience exports and ad conversions through destinations, and regular data imports through sources.

Open the section from the menu: Engagement → Integrations.

Integrations page with connected channels

Connected integrations are grouped by type. When there are several types, a filter appears above the cards: All, Channels, CRM, and so on, with counters.

What you can connect

To connect a new integration, click Add integration: the window groups services by type, and search finds a service by name. The + button next to a group heading on the page opens the window on that type.

Channels send messages:

Channel How it works
Email Platform mail service: sending from your domain set up in Sending domains, with DKIM signing, bounces, complaints, and the suppression list handled automatically; or Own SMTP server: address, port, encryption, username and password. In both cases, you set the sender address and name and can turn on open and click tracking. For your own SMTP server, you can set a bounce domain and mailbox so that undeliverable emails unsubscribe the address automatically. Customer emails to your support address can be received in the live chat, see Incoming email in chat
SMS a provider of your choice: SMS.ru, SMSC.ru, Twilio, or your gateway's own HTTP API. Delivery statuses arrive at the URL shown in the integration
Telegram a bot created with BotFather: a token is all you need, and the bot sets up its incoming message URL itself
Viber (business messages) messages by phone number through an aggregator: SMSC.ru, Infobip, or your own HTTP API
Viber bot a Viber bot using the token from the partner account, with a welcome message for new subscribers
MAX bot a bot in the MAX messenger using the token from business.max.ru, with a welcome message and a "Share phone number" button. See MAX bot
VK community messages on behalf of a community using its access token; from the Growth plan. See VK community
Instagram Direct messages from an Instagram business account through your Meta app; from the Growth plan. See Instagram Direct
Facebook Messenger messages from a Facebook page through your Meta app; from the Growth plan. See Facebook Messenger
WhatsApp WhatsApp Business Cloud API: phone number ID, account ID, token, and Meta app secret
Web Push browser notifications; keys are created automatically and the website code collects subscriptions. See Connecting your website
Mobile push notifications in an Android and iOS app: package and Firebase service account, bundle id and APNs key. See Mobile apps
In-app messages a modal, banner, or full screen inside the open app; from the Growth plan. See Mobile apps
Wallet cards a loyalty card in Apple Wallet and Google Wallet: an Apple Pass Type ID certificate, a Google Issuer ID and service account; from the Growth plan. See Wallet cards
Webhook a request to your server with the message data, for example for your own notification system

Audience exports: Webhook, S3 (CSV), Meta Custom Audience, Yandex Audiences, VK Ads, and Google Ads Customer Match.

Ad conversions: Meta Conversions API, Yandex Metrica and Google Ads offline conversions, and VK Ads offline events. See Ad conversions.

Data sources: file by URL, file from S3, and Google Sheet.

Data warehouses: S3 (NDJSON), Google Cloud Storage, BigQuery, Snowflake, ClickHouse, and PostgreSQL for exporting project data. The group is visible on the Enterprise plan.

CRM: amoCRM, Kommo, Bitrix24, HubSpot, Pipedrive, Zoho CRM, Odoo, Salesforce, and Microsoft Dynamics 365: contacts, leads, and deals in profiles and events, journey nodes for deals and tasks, and segment export back to the CRM, see CRM. The group is visible from the Growth plan.

You can connect several integrations of the same type: for example, two SMTP servers for marketing and transactional emails. In templates, journeys, and campaigns, you choose which integration to send through.

Connect an integration

  1. Click Add integration and choose a service, for example Email. The left side of the window lists integration types with descriptions, and search by name is at the top.
  2. Enter a Name. You'll see it in templates, journeys, and exports, for example "Marketing email".
  3. Fill in the settings. Hints under the fields explain where to find the token or key in the service's account.
  4. Click Save. To choose a different service, click Back.
  5. On the integration card, click Test.

New integration window: integration types, search, and services

Email integration dialog

For some services, extra fields appear in the settings after you save: for example, Webhook URL and Verify token for WhatsApp, or Delivery status URL for SMS. Copy them into the service's account, or delivery statuses and incoming messages won't arrive.

Telegram, Viber bot, MAX bot, and WhatsApp receive incoming messages at your OneTrace.pro installation's address, which must be reachable from the internet over HTTPS.

MAX bot

  1. Create a bot on business.max.ru (a Russian legal entity, sole proprietor, or self-employed person can host a bot) and copy the token: "Чат-боты" (Chatbots) → ⋮ → "Настройки" (Settings).
  2. Click Add integration, choose MAX bot, paste the Bot token, and save. The bot sets up its incoming message URL itself, and its name appears in the settings.
  3. Optionally, set a Welcome message and the text of the “Share phone number” button: the bot sends them when a customer starts it.

MAX bot connection dialog

The bot can only message people who have started it. A customer is linked to a profile in two ways:

  • by link: your server creates a link https://max.ru/{bot}?start=… for a signed-in customer (POST /api/v1/max/link, the same as for Telegram), and the customer opens the bot with it;
  • by phone number: the customer taps the "Share phone number" button in the welcome message. If MAX has confirmed that the number belongs to their account, the bot is linked to the profile with that phone. A forwarded contact card of someone else is not linked.

Starting the bot subscribes the customer to the channel; stopping the bot or deleting the chat unsubscribes them. Customer messages to the bot become max.message events and, from the Growth plan, live chat conversations. MAX has no delivery reports: an accepted message counts as delivered. MAX rules prohibit advertising in service messages.

VK community

  1. In the community, open Manage community → Messages and turn on community messages.
  2. In Manage community → API usage → Access tokens, click "Create token" and select the "Community management", "Community messages", "Photos" and, if rules will reply to comments, "Wall" permissions.
  3. Click Add integration, choose VK community, paste the Community access token, and save. OneTrace.pro checks the token's permissions, adds the Callback API server to the community settings itself, and shows the community name and address.
  4. Optionally, set a Welcome message: it's sent to a person who allows messages from the community.

VK community connection dialog

The community can only message people who have allowed messages: they wrote first, clicked "Allow messages", or followed a vk.me link. This is the channel subscription, and blocking messages is an unsubscribe. Your server can link a person to a customer profile: POST /api/v1/vk/link creates a link https://vk.me/{community}?ref=… for a signed-in customer, and you can pass the same tag as the key to the "Allow messages" widget.

A message can contain text, an image, and link buttons. VK doesn't accept images by URL: OneTrace.pro uploads the file itself, once per campaign. People's messages become vk.message events and live chat conversations, and comments on posts trigger keyword rules. Deleting the integration also removes the Callback API server from the community settings.

Instagram Direct

Instagram is connected through your own app in Meta: for your own account, Meta app review isn't needed.

  1. In Meta for Developers, create an app, add the Instagram product, and connect the business account under API setup with Instagram login.
  2. Click "Generate access tokens" and copy the token. It needs the instagram_business_basic, instagram_business_manage_messages and, for comment replies, instagram_business_manage_comments permissions. Copy the Instagram app secret from the same place.
  3. Click Add integration, choose Instagram Direct, paste the token and the secret, and save. The settings then show the Webhook URL and Verify token.
  4. Enter the URL and token in the app's webhook settings (Instagram section). OneTrace.pro can subscribe the account to events itself.

Instagram Direct connection dialog

The token lasts 60 days, and OneTrace.pro refreshes it itself. If the refresh fails, an error appears on the integration card: create a new token and save the integration before the old one expires.

Instagram lets you message a person only within 24 hours of their message. Campaigns and journeys skip people who wrote earlier: the message isn't sent, and the subscription stays. A chat operator can reply later, up to 7 days, if the app has the Human Agent permission and Operator replies up to 7 days is turned on in the integration.

A person's first message subscribes them to the channel; "stop" unsubscribes them. POST /api/v1/instagram/link creates a conversation link with a tag for linking to a profile: https://ig.me/m/{account}?ref=…. Messages and story replies become instagram.message events and live chat conversations, and comments trigger keyword rules.

Facebook Messenger

Messenger is connected through your own app in Meta, just like Instagram: for your own page, Meta app review isn't needed.

  1. In Meta for Developers, create an app and add the Messenger product.
  2. Under Messenger → API settings, connect your Facebook page and create a Facebook page token with the pages_messaging permission. You need a non-expiring token: OneTrace.pro doesn't refresh it. Copy the App secret from App settings → Basic.
  3. Click Add integration, choose Facebook Messenger, paste the token and the secret, and save. OneTrace.pro finds the page, subscribes it to messages, and shows the Webhook URL and Verify token.
  4. Enter the URL and token in the app's webhook settings (Messenger section).

Like Instagram, Messenger lets you message a person only within 24 hours of their message: campaigns and journeys skip people who wrote earlier. A chat operator can reply up to 7 days later if the app has the Human Agent permission and Operator replies up to 7 days is turned on in the integration.

A person's first message subscribes them to the channel and triggers the Welcome message from the integration settings; "stop" unsubscribes them. The person's profile gets the facebook_psid identifier (the ID of the conversation with your page specifically) and their name from Facebook, if the page can see it. Messages, photos, and files become messenger.message events and live chat conversations. An operator's quick reply buttons arrive in Messenger as real buttons.

Incoming email in chat

In the email integration, the Incoming email in chat group receives customer emails sent to your support address in the live chat. The operator's reply goes out through the same integration in the same email thread. Options:

  • IMAP mailbox: the server, port, encryption, login, password, and folder of the support mailbox. New emails are read once a minute and marked as read.
  • Webhook: after you save, the Webhook URL with a token appears. Set it in your email service as the inbound address. Supported: Postmark (Inbound webhook), SendGrid (Inbound Parse, with or without "POST the raw, full MIME message"), Mailgun (Routes with the forward action), and Cloudflare Email Workers (forwarding the whole message). The token in the URL is a secret: don't publish the URL. If the address may have leaked, check Change the webhook address and save: a new address appears and the old one stops accepting emails. Only those who can manage the integration see the address.

The Support address is required for both options: customers write to it, and it's also the reply-to address of operator emails.

Testing and statuses

The Test button connects to the service and shows the result: Connection works with details (the bot name, the SMS provider balance, the accessible bucket) or The test failed with the error text. The time of the last test is shown on the card.

Status What it means
Active the connection is fine
Error the last test or setup failed; the error text is on the card. Fix the settings and test again
Disabled the integration was turned off with the Enabled switch in its settings; no messages are sent through it

Testing SMS through your own HTTP API only checks that the gateway address is reachable: a real SMS costs money, so test sending with a test message from a template.

Editing and deleting

  • Edit opens the settings. Passwords, tokens, and keys aren't shown after you save: leave such a field empty to keep the existing value.
  • To pause sending temporarily, turn off the Enabled switch. The settings are kept.
  • Delete integration: messages are no longer sent through it, and exports and sources that use this connection stop with an error. For Telegram, Viber, and MAX bots and SMS.ru, the platform removes its webhook itself. If the service is unavailable, you will see a warning — remove the webhook manually in the bot settings or in the service account.

Who can manage integrations

Action Roles
View integrations Owner, Administrator, Manager
Connect, edit, test, and delete Owner, Administrator

A member's role can be limited to specific integrations. See Members and roles. Such a member sees only their integrations in this section and can manage only those, if the role allows it. They can't connect a new integration, because that requires a project-wide permission. In the template and journey editors, they still choose from all integrations connected in the project.

Good to know

  • Channels don't check subscriptions and frequency themselves: these rules are shared by all channels and are set on the Messaging rules page.
  • On the same page, you can turn off an extension you don't need, such as WhatsApp. A disabled extension disappears from the project's integrations, templates, and journeys.
  • In WhatsApp, the first message and bulk sends are only possible with Meta-approved templates; free-form text is allowed within 24 hours after the customer's message. Meta templates, product carousels and WhatsApp forms are covered in Shopping in WhatsApp.
  • With the platform mail service, you add the DKIM, SPF, and bounce records once when you connect the domain. See Sending domains. For your own SMTP server, SPF, DKIM, and DMARC are set up on the server side and on your domain.