Connectors

You create a bot with @BotFather in Telegram, which takes a minute, and paste its token into Serlion. Serlion checks the token, stores it encrypted and sets up the connection itself. You share the bot’s link (t.me/yourbot) wherever customers should find it.

People write to the bot in a private chat. If they type /human, or ask for a person in their own words, your team is notified and answers from the Inbox. The reply arrives in the same chat with the replier’s first name on top.

A support channel that needs no visit to your website, with the same answers and lead capture as the widget, and every Telegram chat next to your website chats in one Inbox.

• Private chats only. A bot added to a group ignores the group.
• Messages sent to the bot before you connected it are not picked up.
• Photos and PDFs up to 5 MB are saved for your team, but the assistant cannot read them. Voice notes, video and stickers are not stored; the assistant is told one arrived and asks the person to write instead.

WhatsApp connects through your own Meta app, so you need a WhatsApp Business account with the Cloud API set up. You copy four values from Meta into Serlion: the phone number ID, the business account ID, a permanent access token and the app secret. Serlion checks them, then shows you a callback URL and a verify token to paste into the webhook settings of your Meta app. Messages reach Serlion only after that last step.

From then on the assistant answers incoming messages. The consent and delete questions appear as WhatsApp reply buttons, and your team’s replies arrive as ordinary WhatsApp messages that start with the replier’s first name.

Answers on the channel many of your customers already prefer. Your team sees sent, delivered and read marks on its messages in the Inbox, and how long the reply window stays open.

• There is no one-click setup. You need a Meta app, and the webhook step is done by hand in Meta.
• WhatsApp only allows free-form replies within 24 hours of the customer’s last message. After that your team cannot reply from Serlion until the customer writes again, and Serlion has no template-message fallback.
• The assistant cannot read images or PDFs. Your team can see them in the Inbox.

You turn on the Messaging API for your LINE Official Account and paste its Channel ID and channel secret into Serlion. Serlion checks them and sets the webhook at LINE itself. Two switches stay with you in LINE’s own settings: turn on “Use webhook”, and turn off LINE’s automatic and greeting messages so they do not answer next to your assistant. The card in the dashboard has a checklist and a “Check again” button.

A greeting goes out when someone adds the account. In one-to-one chats the consent and delete questions appear as LINE quick-reply buttons.

A way to serve customers in the apps where LINE is how people message businesses, with the same assistant and the same Inbox.

• One-to-one chats only. Group and room messages are ignored.
• The assistant’s replies are free while it answers within 50 seconds. Slower replies, answers that need more than five messages, and every reply from your team are push messages, and push messages count against your LINE plan’s monthly message limit. If that limit is used up, your team’s reply fails and the Inbox says why.
• When you disconnect, the webhook switch in LINE is yours to turn off. LINE has no way for Serlion to do it.

You create a bot in the Discord Developer Portal and paste its token. Serlion keeps its own live connection to Discord for that bot, so there is no webhook and no intent to switch on. You add the bot to your server with the invite link Serlion shows, which asks for no permissions. People then click the bot’s name and choose Message.

In those direct messages the slash commands /human and /delete work, and your team’s replies come back from the same bot with the replier’s first name in bold.

Community members can ask a question without posting it in public, and your team answers from the Inbox instead of from Discord.

• Direct messages only. The bot ignores everything written in server channels, on purpose, because a public channel mixes several people.
• A person has to share a server with the bot and allow direct messages from it. If they do not, they get nothing, and your team sees the reason.
• Images and PDFs are saved for your team but not read by the assistant; other files are not stored.

Serlion creates one address for your business on its own domain. You set up forwarding from your support mailbox to that address (the dashboard has the steps for Gmail, Microsoft 365 and other mailboxes) and can send a test email to confirm it works. The assistant then replies in the same thread with a complete email: greeting, answer and a sign-off under the sender name you chose.

You pick a mode. With “AI answers” the assistant replies to every email. With “Straight to the Inbox” there are no automatic replies and every new email waits for your team.

Fewer repeated questions in the support mailbox. Every automatic reply says it was written by your AI assistant and tells the customer how to reach your team.

• Replies come from your Serlion address with your sender name, not from your own address, and the customer’s follow-ups go to Serlion and appear in your Inbox, not in your mailbox.
• Automatic replies, newsletters, no-reply senders and mail from your own address or team are never answered. If you test by emailing from your own account, the email is skipped.
• Only the first image or PDF in an email is saved for your team. The assistant cannot read attachments.

You create a service key in HubSpot with two permissions (read and write contacts) and paste it into Serlion. When a visitor shares an email address or phone number, Serlion looks for that person in HubSpot first. If they exist, only empty fields are filled in. If not, a contact is created with the lifecycle stage “lead”.

The conversation goes on the contact as a note once the chat has been quiet for 15 minutes, and the note is updated if the visitor comes back within 7 days. You choose what the note holds: the whole conversation, or only the contact details and the message they came with, which is added right away.

Sales sees who asked, what they asked and a link back to the conversation in Serlion, without anyone copying details by hand.

• One way. Serlion writes to HubSpot and reads nothing back into the assistant. It creates contacts and notes only: no companies, deals or tasks, and no field mapping.
• It never overwrites a value already in HubSpot and never deletes a contact. If you edit the text of the Serlion note in HubSpot, the next update replaces your edit.
• The connector has no consent check of its own. To ask first, switch the chat to consent mode, which keeps a conversation from starting until the visitor accepts your privacy notice.
• Meetings booked in the chat are not sent as leads. Past leads are sent only if you tick the box to include the last 30 days (up to 500) when you connect.
• If a visitor deletes their chat, Serlion deletes the note it made. The contact stays.

You paste your personal API token from Pipedrive. Leads are created as the owner of that token, so use a user who may add people, leads and notes. Serlion finds an existing person by email address first, or by phone number when there is no email, and only adds what is missing.

Each conversation gets one lead in the Leads Inbox (you can switch that off and keep just the person and the note). A returning visitor whose person already has an open lead from Serlion in the last 30 days gets the new note on that lead. The note follows the same rule as in HubSpot: added after 15 quiet minutes, updated for up to 7 days.

New enquiries show up in the Leads Inbox with the whole conversation attached, ready for someone to qualify.

• One way, and no deals, organisations, activities or pipeline stages are created. Pipedrive defaults decide the lead’s owner and fields.
• Existing person data is never overwritten. The only exception is a name Serlion made up from an email address, which is replaced once a real name arrives.
• No consent check in the connector. Switch the chat to consent mode if visitors must accept your privacy notice first.
• If a visitor deletes their chat, Serlion deletes the note and the lead it made for that chat. The person stays.

You connect with your Zendesk subdomain and either an agent’s email and API token or an OAuth access token. A dedicated agent called Serlion keeps the tickets easy to recognise. A ticket is created in two cases, and you can switch each off: a visitor asks for a person outside your business hours, or a request is still waiting after 5 minutes. The first comment is an internal note with the conversation, the visitor’s name, email and phone if known, and a link back to Serlion. Later messages are added as further notes.

To import your Help Center, press Import Help Center. Serlion reads your public, published articles in the Help Center’s default language, turns them into plain text and uses them as answers. They are refreshed about once a day, and an article you unpublish is removed from the assistant at the next sync.

Handoffs that nobody could take land in the tool your support team already works in, with the context they need. Your Help Center answers questions without anyone rewriting it.

• One way. A reply written in Zendesk never reaches the visitor, and closing a ticket does not close the handoff in Serlion. Your team replies from the Inbox.
• Not every handoff becomes a ticket, only the two cases above. If your Zendesk sends an automatic confirmation to new requesters, a visitor who left an email address will get it. You can turn that off in Zendesk.
• Help Center import takes text only, public articles only and one language. The first import is started by you. Articles count together with Notion pages against your plan’s article limit (see Pricing), and you edit them in Zendesk, not in Serlion.
• If you disconnect, the imported articles are removed from the assistant.

You connect with your Freshdesk subdomain and an agent’s API key. Freshdesk’s API is part of its paid plans and trials. The ticket rules are the same as for Zendesk: a request outside business hours, or one that is still waiting after 5 minutes. The ticket carries a short public description, and the whole conversation goes in a private note that is never emailed to the visitor.

Solution articles are imported the same way as a Zendesk Help Center: published articles in folders visible to everyone, as plain text, refreshed about once a day.

The same as Zendesk: handoffs land as tickets in your support tool, and your solution articles answer questions.

• One way. Replies written in Freshdesk do not reach the visitor. Your team replies from the Inbox.
• Folders for signed-in users, agents or selected companies are never imported, and neither are drafts.
• If your Freshdesk sends automatic confirmations to new requesters, a visitor with an email address can receive one. That is set in Freshdesk.

You paste a Mailchimp API key. Serlion checks it with Mailchimp before saving it, then you pick the audience that new subscribers should join. Until you pick one, nothing is sent and the box does not appear in the chat.

Once an audience is chosen, the chat’s contact form shows an unticked box next to the email field. The wording is yours (up to 300 characters, no links) and the default is “Yes, send me news and offers by email. I can unsubscribe at any time.” A person is sent only if they ticked the box and gave an email address. An address or phone number typed inside a chat message never counts as consent.

Serlion sends the address, the name and the tag “Serlion”, and asks Mailchimp to add the person as pending. That means Mailchimp itself sends its confirmation email, so every subscriber confirms (double opt-in).

A list that grows from real conversations, with consent you can show. For each lead Serlion keeps the time of the consent, the exact wording the person saw and where they ticked it, and you can see every send in a log for 30 days.

• Nothing but the email address and name leaves Serlion. No message text, no phone number, no conversation.
• People who are already on your list are not changed. Someone who unsubscribed in Mailchimp is never subscribed again, and a bounced address stays bounced.
• Leads that existed before you connected are never sent. Deleting a chat cancels a waiting send, but a person already added stays on your list.
• If Mailchimp is unreachable, Serlion retries for about 20 hours. If your key stops working, you get one email and sends wait for up to 7 days.

You paste a Brevo API key, Serlion checks it, and you choose the list. The consent box, its wording and the rules around it are the same as for Mailchimp, and one wording serves both. If you connect both, a person who consents is added to both lists.

Unlike Mailchimp, Brevo adds a person to the list straight away and does not email them, unless you turn on double opt-in. For that you enter the ID of a confirmation template you made in Brevo and the page people land on afterwards. Then Brevo sends your template and adds the person when they confirm. The dashboard recommends turning it on.

The same as Mailchimp: consenting visitors on the list you already send from, with the proof of consent kept next to each lead.

• Single opt-in is the default for Brevo. If you need confirmed addresses, set up double opt-in before you rely on it.
• Only the email address and name are sent. People already in Brevo are not changed.
• The same retry, log and key rules as Mailchimp.

You enter your shop’s address and a WooCommerce key and secret. Create the key in WooCommerce with read permission. Serlion only ever sends read requests, but it cannot check what permission your key has, so give it read only. The shop address must be a normal https address.

For an order, the visitor gives the order number and the email address on the order, either in a small form in the chat or typed into the conversation. Serlion compares the email with the one on the order. A wrong number, a wrong email and an unknown order all get the same answer, so nobody can use the chat to find out who ordered. The visitor sees the order number, the status in plain words, the date, the items, the total and the tracking link if you use the Shipment Tracking extension. Names, addresses, phone numbers, the email and the payment method are never shown or stored.

For products, the assistant searches your published products and shows up to three cards under its answer with the picture, price, stock, a View button and an Add to cart button. The assistant is told the real prices from your shop.

Fewer “where is my order” messages for your team, and a shopper who can go from a question to a product page or the cart inside the chat.

• Status and products only. There is no returns, refund or cancel flow, and nothing can be changed in your shop.
• Each lookup is a live call to your shop. If your shop is slow or down, the assistant says it cannot look that up right now and does not guess.
• The order lookup limits how often one visitor can ask, so it cannot be used to try many numbers.
• The chat writes one line into the conversation (“Order lookup #1042: found” or “not found”). The number is in that line. The email and the order’s contents are not.
• Add to cart runs in the visitor’s own browser on your shop. You can switch it off.

Serlion has no Shopify connector, and it stores nothing from Shopify. When a visitor asks about a product on your site, Serlion uses your shop’s own public search, the one your storefront uses, and shows up to three cards. The price, the stock and the variants load in the visitor’s browser from your shop, so they match the visitor’s market and currency. Add to cart also runs in the browser.

It only works on the website you verified in Serlion, and you set “Your shop runs on” to Shopify under Flows, Shop and accounts. Detect does not turn it on.

Visitors can ask for a product in their own words and get a card with the live price and a button, with nothing to connect.

• Best effort. Password-protected shops and storefronts that do not offer the public search do not work. If your shop does not answer, the assistant is not offered the search for a short while.
• The assistant is told no prices and does not state or compare prices, discounts or stock. The cards show them.
• Products only. There is no order lookup for Shopify, because that needs a connection to your shop.

In Notion you create an internal integration, which gives you a token, and paste it into Serlion. Then, in Notion, you share the pages the assistant may use with that integration (Add connections). It can see only those pages, it can only read, and it never asks for access to people or user information.

Each page becomes one entry in the assistant’s knowledge, with its title and its text: headings, paragraphs, lists, to-dos, quotes, callouts, code and tables. Sub-pages and database rows become entries of their own. The first import runs when you connect. After that it re-reads about once a day and when you press Sync now. Pages that have not changed are skipped.

You keep writing in Notion, and the assistant answers from the latest version. A deleted, archived or unshared page is removed from the assistant at the next sync.

• Text only. Images, files, videos, PDFs and embeds are not read, and the dashboard tells you how many of each a page had.
• Anything you share can be said to people on your website. Share only pages you are happy to have answered from. Notion’s own permissions are not copied.
• It is not live. An edit shows up at the next sync, and you edit the text in Notion, not in Serlion.
• Pages count against your plan’s article limit together with imported help center articles (see Pricing). Pages beyond the limit are left out, the most recently edited ones first. A page over 20,000 characters is cut, and a page with almost no text is skipped.
• If you disconnect, the imported pages are removed from the assistant. Nothing in Notion is touched.

You paste a Cal.com API key and choose one event type, for example a 30 minute intro call. Serlion checks the key before saving it. The assistant can offer meetings only when both a key and an event type are set.

When someone asks to talk, the assistant checks your free times (the next 7 days by default, up to 14) and offers a few. It shows them in the visitor’s own time zone and says which zone it used. It books only after the visitor has confirmed one exact time and given their full name and email address, and only a time it has just looked up. Cal.com then sends the confirmation and the calendar invitation as it does for any booking.

Meetings booked in the middle of a conversation, while the visitor is still interested.

• One event type, and booking only. The chat cannot move, cancel or list meetings.
• A booking is not saved as a lead in Serlion and does not trigger an alert or a webhook. You will see it in Cal.com.
• A small daily cap per conversation, per person and per business keeps the chat from being used to fill your calendar.
• If Cal.com does not answer, the assistant says so and does not guess a time or promise a follow-up.

Each person links their own Telegram in the Inbox settings. Serlion creates a one-time link that works for 15 minutes, they open it in Telegram, and from then on Serlion’s alerts bot sends them private messages. The owner and every team member who has accepted their invitation can do this. /stop in the chat unlinks it.

Each person chooses what they hear about: a visitor asks for a person, a visitor writes in a conversation assigned to them while they are away, nobody has replied for 5 minutes, and a new lead. The message says what happened, names your business and the channel, and has an Open in Serlion button.

Your team hears about a waiting visitor on their phone, without anyone watching the dashboard.

• No visitor name, contact details or message text, on purpose. These alerts go through Serlion’s own bot, and Serlion does not hand visitor details to Telegram. Open the conversation to see who it is.
• There are no quiet hours and no daily digest. Each event is its own message, so choose events carefully.
• Messages waiting to be sent are held in memory. After a server restart, those that had not gone out yet are lost. The conversation itself is still in your Inbox.

In the tool you already use you create an incoming webhook for the channel and paste its address into Serlion. You can add up to five channels, name them and choose, for each one, whether it gets new leads, handoff requests and the 5 minute reminder. A test button sends a sample message.

The alert shows what happened, your business and the channel, the visitor’s name, email and phone number when known, and for a lead the first part of their message, with a link to the conversation.

The people who answer see a waiting visitor in the place they already work, with enough detail to pick it up.

• These alerts do include the visitor’s contact details, because they go to your own workspace. Only paste webhooks for channels where that is fine.
• Only the owner and co-owners can set them up.
• If a channel fails ten times in a row, Serlion turns it off and emails you once. For Teams you need a Workflows webhook, because Microsoft has retired the old connector addresses.
• Alerts waiting to be sent are held in memory, as with Telegram alerts.

You add a web address in Developers and choose the events: conversation started, lead created, handoff requested, handoff escalated, handoff resolved, conversation rated and conversation deleted. Each event is sent as JSON, signed so your server can check that it really came from Serlion, and Serlion keeps the log of every attempt for 30 days. You can send a test event and resend any delivery.

If your address does not answer with a success code within 10 seconds, Serlion tries again, up to seven times over about 20 hours. An address that keeps failing for three days is switched off and you get an email. Events can arrive more than once, so each carries an ID to deduplicate on.

Zapier, Make and n8n have no Serlion app. They work through their webhook and HTTP steps. You create a key with read and write access, register the tool’s hook address through the API, and use the sample events to map fields. You can also create leads in Serlion from a form or spreadsheet through the API.

Leads and conversations flow into the sheet, tool or workflow you already run, without waiting for a ready-made connector.

• There is no official Zapier, Make or n8n app. You set up the generic route yourself, or someone technical does.
• Some events carry personal data: new leads (name, email, phone, message excerpt), conversation started (the first message and the contact details when known) and ratings (the comment). Send them only to systems you trust.
• Webhooks and the read and write API are on Pro and up. A key that only starts chats works on every plan.
• The API is documented in the API reference.