# Integrations On the "Integrations" tab the bot is connected to external services: CRMs, spreadsheets, a mail server, SMS providers and payment systems. An integration does nothing by itself — it gives access keys to the scenario blocks that work with that service. Integrations are connected separately for every bot. They are not carried over to a copy of the bot — connect them in the copy again. > [!NOTE] > The tab works with a Pro subscription. See the [What is available without Pro](https://support.watbot.org/billing/without-pro) page for details. ## How to connect a service The tab consists of two parts. At the top are the integrations already connected, below is the "Available integrations" list. ![List of available integrations on the Integrations tab](https://support.watbot.org/_media/en/01-chatbots/12-settings/_images/integrations.webp?v=1791781230) 1. Click the service's card in the "Available integrations" list. 2. Fill in the fields in the window that opens. Keys and passwords are taken from your account in the service itself — the text in the window tells you where exactly. 3. Click "Save". The message "Integration successfully installed!" appears, and the card moves to the upper part of the tab. For some services, the "Webhook" tab with an address opens after saving. It must be copied to your account in the service: the service uses this address to tell the bot about events — for example, about a payment. One service of each kind is connected to a bot: one amoCRM account, one SMTP server and so on. ## Changing or disconnecting Click the card of a connected integration — the same window opens. Change the data and click "Save", or click "Delete" to disconnect the service from the bot. > [!WARNING] > Blocks that need a disconnected integration stop working. For example, a payment block will send the person a message that the payment system is not connected instead of an invoice. Check the scenario before disconnecting. ## Which services there are The list shows only the services that are enabled on your platform, so it may be shorter. ### CRM - **amoCRM.** Passes requests from the ["Request"](https://support.watbot.org/chatbots/blocks/notifications/notification) block to amoCRM. To connect, link an amoCRM account with the button in the integration window and allow access, then choose the pipeline, status and responsible person on the "Settings" tab. Linked accounts are visible on the "Accounts" tab — one account can be used in several bots. - **Bitrix24.** Passes requests from the "Request" block to Bitrix24. You need the "REST API webhook" — an inbound webhook from Bitrix24 with permissions for CRM and users. The window lets you choose the CRM mode, pipeline, status and responsible person. The "Two-way communication" tab is optional: it is needed for Bitrix24 to tell the bot about a change of a deal's stage. The platform also has its own CRM — it needs no integration. It is covered in the [CRM](https://support.watbot.org/chatbots/crm) section. ### Google Sheets They let scenario blocks read and change rows in the spreadsheets of your Google account. To connect, sign in with Google in the integration window and choose the account in the "Account" field. How to work with spreadsheets further is on the [Lists and tables](https://support.watbot.org/chatbots/blocks/lists) page. ### Email and SMS - **SMTP server.** Your mail server through which the emails of the ["Send email"](https://support.watbot.org/chatbots/blocks/notifications/letter-to-the-future) block go out. You need the sender's name and address, host, port, user name, password and the type of encryption. - **sms.ru.** Sends the number confirmation code in the ["Phone number request"](https://support.watbot.org/chatbots/blocks/messages/request-phone) block. You need an API key from your sms.ru account. - **SMS.to** and **SMSala.** They also send the number confirmation code. SMS.to needs an API key and a sender ID, SMSala — an API id, an API password, a brand name and a sender ID. ![The SMTP server integration window](https://support.watbot.org/_media/en/01-chatbots/12-settings/_images/smtp.webp?v=1791781230) ### Sales and advertising - **JustClick.** Needed by the ["Send contact to JustClick group"](https://support.watbot.org/chatbots/blocks/integrations/just-click-create-lead) block and the blocks for payment through JustClick. Enter the login and the API key. - **GetCourse.** Needed by the ["GetCourse order"](https://support.watbot.org/chatbots/blocks/integrations/get-course-deal) block. Enter the account name and the secret key. ### Payment systems Payment systems are connected on the same tab: YooKassa, YooMoney, Robokassa, Cloudpayments, T-Bank, bePaid, LiqPay, Prodamus, Payme — those of them that are enabled on the platform. How payment blocks work and what to enter for each system is in the [Accepting payments](https://support.watbot.org/chatbots/blocks/payments) section. ## Who can connect integrations The bot's owner and a team member with the "Bot settings" permission. The keys and passwords of connected services are visible in the integration window to everyone who has this permission — give it only to those you trust with access to your payments and CRM. ## If something does not work - **The service is not in the list.** It is not enabled on your platform or is already connected — then its card is in the upper part of the tab. - **A block says the integration is not connected.** Every bot has its own integrations: check that the service is connected to this particular bot. - **The payment went through, but the bot does not react.** Check that the address from the "Webhook" tab is added in your account in the payment system.