Settings and integrations

Team, notifications, API and MCP

By Alex Mishyn

• 6 articles

Team and roles

A workspace can be run by a team. Every member has a role that defines what they are allowed to do. The page: Settings → Team. Four roles | Role | What it can do | | --- | --- | | Admin | Everything an Editor can, plus: inviting people and changing roles, the plan, payments and top-ups, API keys, the Slack, Grinfi, Claude, webhook and CRM connections, exporting data and deleting the workspace | | Editor | Campaigns, agents and the AI-Brain, connecting Telegram, Threads and Reddit accounts, chat selection and history scans, pipeline stages, unblocking in the blocklist, Telegram groups for leads and the email frequency. Cannot do what only an Admin can | | Operator | The feed, replies to leads, the pipeline, tasks, blocking senders. Can create campaigns, change them and pause them. Cannot connect accounts, create or change agents and the AI-Brain, or unblock | | Viewer | View only, no changes at all - and only for the campaigns assigned to them | Admin, Editor and Operator see every campaign in the workspace, with its leads and conversations. ⚠️ Important: a Viewer sees only the campaigns assigned to them, and campaigns cannot be assigned on screen at the moment. So a Viewer's campaigns, feed and pipeline are empty. If a colleague needs to see the leads, give them the Operator role. 💡 Tip: a typical split - the business owner as Admin, the marketer as Editor (sets up campaigns and agents), sales managers as Operator (work through the feed and talk to leads). ℹ️ Note: an Operator can block a sender, but only an Admin or an Editor can lift the block: unblocking affects every campaign at once. Every member connects the Telegram bot to themselves - it is a personal setting, available to every role, Viewer included. A Viewer cannot add the bot to campaigns, though. Details are in the article "Notifications". Inviting someone Only an Admin can invite people and change roles. Everyone else sees the line "Only a workspace admin can invite people and change roles" on the page. 1. Press Invite. 2. Enter the Email and choose the Role. 3. Press Send invite. The person gets an email with a link. The invite is valid for 7 days - the date is shown on the page ("Invite valid until..."). Once accepted, the person appears in the member list. Invites Invites that have not been accepted yet are collected in the Invites block: - Send again - a new email, valid for another 7 days; - Revoke invite - the link in the email stops working. Changing a role or removing a member The member's menu has Change role and Remove from team. After removal, access ends immediately, but the data stays: campaigns, leads and conversations remain in place. You cannot change your own role or remove yourself. The workspace owner's role cannot be changed, and the owner cannot be removed. One Telegram account - one workspace A Telegram account can be connected to only one workspace. If you see a message while connecting that the number is already connected in another workspace, disconnect it there first. Workspace number The Settings → Profile page shows the Workspace number in the TG-00001 format. Mention it when you contact support - it is the fastest way for us to find your account. What only support can change - A member's Name and Email - write to us and we will change them. - The Workspace name. You can change your password yourself: on the sign-in page press Forgot password?, and we will send you an email with a link to set a new one.

Last updated on Oct 15, 2026

Notifications

New leads show up in the feed, but you do not have to wait for them there - Telegrin can tell you about them itself: in Telegram, in the browser and by email. The main settings live on the Settings → Notifications page. The Telegram bot: two steps The @telegrin_signals_bot bot sends you the lead card with a button straight to the original message. For cards to start arriving, you need both steps below - connecting alone is not enough. Step 1. Connect the bot to yourself 1. Open Settings → Notifications and press Connect the bot. 2. Open the bot with Open in Telegram, or point your phone camera at the QR code. 3. In the bot, press Start. The page then shows Bot connected. Every team member connects the bot themselves, to their own Telegram. Step 2. Add the bot to campaigns The bot sends leads only from the campaigns it has been added to. It does not add itself to new campaigns, even if you have already connected it. - To several campaigns at once: on the connected bot's card, press Add to campaigns, tick the campaigns you want (or Select all) and press Add. - To one campaign: on the campaign page press Pipeline → + → Delivery → Telegram bot → Add step. The step is saved at once. ℹ️ Note: the bot in a campaign is shared by the whole team. Every member who has connected the bot gets the cards from that campaign. Every role except Viewer can add the bot to campaigns. Besides leads, the bot sends service messages to everyone who has connected it - for example, when your Telegram account gets disconnected. Those do not need the bot to be added to campaigns. Muting or disconnecting - /mute - silence for 1 hour, /unmute - turn alerts back on sooner. /status shows whether a pause is on. - /language - change the language of the alerts. - To stop one campaign from sending cards, remove the Telegram bot step from it, in the same place where you added it. The campaign keeps running, and its leads stay in the feed. - The Disconnect button on the bot's card turns alerts off for you only. The leads themselves stay - they remain in your feed. 💡 Tip: if there are too many alerts, do not disconnect the bot entirely - remove it from the loudest campaign. Leads in a Telegram group Lead cards can also go to your team's group chat - everyone at once, no personal subscriptions. 1. In the Leads in a Telegram group block, press Add to a group. 2. Telegram asks which group to add the bot to - pick it. The group gets cards from the same campaigns that have the Telegram bot added. The bot does not read your conversation there: it only sees commands addressed to it. ⚠️ Important: everyone in the group sees the leads, including people with no Telegrin access. The Admin and Editor roles can add and disconnect groups. Email Lead emails are a setting for the whole workspace, not for a campaign: there is no separate email delivery inside a campaign. The emails go to the workspace owner's address. The Email block has four options: Every lead, Once a day, Once a week and Do not send. The default is Once a week. The Admin and Editor roles can change it. With Every lead, an email arrives right away for every new lead from all campaigns. What the email contains with Once a day and Once a week: - only leads that are still unread in the feed; leads rejected by the AI are left out; - up to 10 of the newest leads: the name linking to the card and the start of the message, with the total number of new leads in the subject line; - if there are no unread leads for the period, no email is sent. Separately from this setting, you get emails about your balance - when 20% and 5% of the monthly credit allowance is left and when the credits have run out. They cannot be turned off. Browser notifications The This browser block has three switches stored on the specific device: Push notifications, Sound and Desktop banner. Unlike the bot, they do not need to be added to campaigns. Details are in the article "Browser notifications". What is not here yet The What is not here yet block honestly lists what cannot be set up yet: - choosing events - every lead found in campaigns with the bot goes to Telegram; - filtering by channel; - scheduled quiet hours - only the manual mute with /mute exists. If notifications do not arrive, go through the article "Notifications are not arriving (especially on iOS)".

Last updated on Oct 15, 2026

MCP and the public API

You can connect Telegrin to your tools in two ways: - MCP server - for AI assistants (Claude, ChatGPT, Cursor, Codex): the assistant gets direct access to the feed, campaigns and pipeline, and you get things done right in the chat. - Public API - for your own integrations and scripts: about 130 operations over plain REST requests. The MCP server works through the same public API, so the assistant has the same capabilities. MCP: connecting in 2 minutes 1. Open the MCP section in the app menu. 2. Pick the tab for your client - Claude Code, Claude Desktop, Cursor or Codex - and copy the ready-made snippet with the copy button: - Claude Code - one command in the terminal, the server adds itself; - Claude Desktop - paste into claude_desktop_config.json (Settings → Developer → Edit Config); - Cursor - paste into ~/.cursor/mcp.json and restart Cursor; - Codex - add to ~/.codex/config.toml, then run codex mcp login telegrin to sign in. 3. The server address (already inside the snippets): https://mcp-tg.grinfi.io/mcp. 4. On first connection a sign-in window opens - log in with your Telegrin account. No separate key is needed for MCP. Claude in the browser (claude.ai) In claude.ai, Telegrin is connected as a custom connector: add a connector with the address https://mcp-tg.grinfi.io/mcp and sign in with your Telegrin account. You need this connector, for example, for a Claude routine that handles new leads by itself - step by step in the article "Telegrin → Claude: your Claude routine handles new leads". What the assistant can do over MCP - reads the feed and approves signals right from the chat; - manages campaigns - launch, pause, keywords; - shows the credit balance and limits; - moves leads through pipeline stages; - reports monitoring stats and metrics. Example requests: "show today's new signals and approve the relevant ones", "pause campaign X", "how many credits are left and what were the last ones spent on". Public API: keys and access 1. Open Settings → API keys. 2. Press Create key, fill in the Name and choose the Permissions: Read only or Read and write. Press Create. 3. Copy the key right away - it is shown only once. 4. Pass the key in the Authorization: Bearer <key> header. API address: https://tg.grinfi.io/api/v1/ext. Every operation is described at tg.grinfi.io/api/v1/ext/reference. ⚠️ Important: a key grants programmatic access to the whole workspace, so only an Admin can create and revoke keys. Revoke a compromised key with the Revoke button on the same screen. The list shows when each key was last used. 💡 Tip: if an integration only needs to read data (for example, to export leads into a report), give it a Read only key. What the API covers The same groups of operations are available over MCP: - Campaigns - list, create, edit, pause and resume, archive, copy, keywords, the campaign's agents and deliverers. - Feed and leads - cards, the "lead / not a lead" verdict, conversations, sending a message to a lead, a follow-up draft, the blocklist. - Pipeline and tasks - lead stages and reminders about leads. - Agents and AI-Brains - list, create and edit. - Chat selection - the free chat catalogue and picking new chats, plus message history scans. - Delivery - webhooks, CRM connections and Grinfi lists. - Analytics - metrics and monitoring stats. - Billing - balance, limits and spending. Payments and top-ups happen only in the app. - Workspace - team members and the lead email frequency. Which plans include it The API and MCP are available on every plan, including the free trial. Related articles "Telegrin → Claude: your Claude routine handles new leads" · "Multiple lead delivery channels and their order" · "Agents in a campaign" · "Plan and limits"

Last updated on Oct 15, 2026

Telegrin → Claude: your Claude routine handles new leads

Telegrin can wake your Claude routine itself whenever a new lead appears or a lead replies in a conversation. Claude receives those leads and handles them by your rules: checks, replies, filters out. No n8n, no Make, no "just in case" runs every couple of hours. How it works - New leads and lead replies are collected into a pack and sent to Claude at most once every 5 minutes. One pack - one run of the routine. - Every run uses your Claude subscription limit. Packs keep that limit from being spent on each lead separately. - Telegrin's autopilot still writes the first replies itself. Claude takes over from there: it handles lead replies and decides what to do. What you need first - A paid Claude plan: Pro, Max, Team or Enterprise. - The Telegrin connector in claude.ai - see "MCP and the public API" for how to connect it. - Instructions for Claude: who counts as a lead, how to reply, how many messages to send. Step 1. Create a routine of the Code type 1. Open claude.ai/code/routines and create a new routine of the Code type. Chat scheduled tasks have no API trigger, and the type cannot be changed later. 2. Paste your instructions and make sure they include the phrase: "Process the Telegrin events from the routine-fire-payload block". Without it the routine will not act on the events Telegrin sends. 3. No repository is needed. In the connectors, keep Telegrin. 4. Add a daily scheduled run - it is your safety net. Pick a time a few minutes past the hour, for example 9:07: a run set exactly on the hour can start late. 5. Click Add another trigger → API and save the routine. Step 2. Copy the URL and the token Open the routine → Edit → API. Copy the URL, which looks like https://api.anthropic.com/v1/claude_code/routines/trig_…/fire, and click Generate token. ⚠️ Important: the token is shown only once - save it right away. If you lose it, click Regenerate and paste the new one into Telegrin: the old one stops working. Step 3. Connect the routine in Telegrin Agents → Deliverers tab → Create your own deliverer → Claude. Paste the URL and the token. 💡 Tip: Claude can do this for you. In a chat with Telegrin connected, write: "Create a Telegrin connection to my Claude routine, URL …, token …". Which campaigns reach the routine: - campaigns with no deliverers of their own, or with only the Telegram bot - automatically, and the bot keeps working; - campaigns with their own webhook, Slack or CRM - add Claude to their deliverers. Step 4. Check it 1. Click Send a test on the connection. The test starts one real run of the routine and uses a little of your limit. The run appears in the routine's history. 2. If you had a scheduled qualification task before, switch it off. Otherwise leads get two replies. 3. After a day or two, open claude.ai → Settings → Usage and see how much of your limit the runs use. If something is wrong | What you see | What to do | |---|---| | No Add another trigger button | It is a Chat task - create a new one of the Code type | | The routine runs but ignores the events | Add the routine-fire-payload phrase to its instructions | | The routine cannot see Telegrin | Edit → connectors → add Telegrin | | The connection shows HTTP 401 | The token is wrong or was regenerated - paste the current one | | The connection shows HTTP 400 | The routine is paused - turn it back on | | HTTP 429 | More than 30 runs an hour for one routine. Do not send tests too often: packs usually make no more than 12 runs an hour | | Your Claude limit runs out fast | Every run is a separate Claude session. Pick a lighter model, or keep just one safety run a day | ℹ️ Note: if errors come in a row, the connection switches itself off. Fix the cause and switch it back on.

Last updated on Oct 15, 2026

Browser notifications

Browser notifications tell you about new signals and new private messages from leads in Telegram while you work at your computer or on a phone with Telegrin installed. Unlike the Telegram bot, they do not need to be added to campaigns: they arrive for every campaign in the workspace. Where to find them Settings → Notifications, the This browser block. The quick way: the bell in the top bar → Notification settings. The settings are stored on the specific device and do not follow you to your phone. If you work from a laptop and an office computer, turn them on on each. Three switches Push notifications The main switch: it subscribes this browser to notifications. They arrive even when the tab is closed. Without it, neither the banner nor the sound works. The first time you turn it on, the browser asks for permission - press Allow. If it cannot be turned on, the reason is written under the switch: - "The browser blocked notifications. Allow them in site settings" - permission was refused at some point, see "Troubleshooting" below; - "This browser cannot do push notifications" - open Telegrin in another browser. Desktop banner A system banner about a new signal - it pops up when the tab is in the background or closed. If you turn it off, push keeps arriving, but nothing pops up. Sound A short chime while the Telegrin tab is open. Handy when Telegrin sits in a neighbouring window. The sound plays together with push, so Push notifications must be on as well. ℹ️ Note: when signals arrive one after another, the browser shows one combined notification rather than a dozen in a row. Which combination to choose | Scenario | Push notifications | Desktop banner | Sound | | --- | --- | --- | --- | | I want everything | On | On | On | | Sound only, no banners | On | Off | On | | Banners only, no sound | On | On | Off | | Silence in this browser | Off | - | - | 💡 Tip: the browser notifies you only on the device where push is on. To avoid missing leads away from your computer, connect the Telegram bot and add it to your campaigns - see the article "Notifications". Troubleshooting The Push notifications switch will not turn on - Cause: notifications for the site are blocked in the browser, and the switch cannot override that. - Fix: click the icon to the left of the tg.grinfi.io address → Notifications → Allow, then turn the switch on again. In Incognito mode push is usually unavailable - use a regular window. No sound - Cause: sound is off in the system, or the browser does not let the page play sound until you have interacted with it. - Fix: check the volume, click anywhere on the Telegrin page and wait for the next signal. If everything is set up and notifications still do not arrive (especially on iPhone and Mac), see the full walkthrough in the article "Notifications are not arriving (especially on iOS)".

Last updated on Oct 15, 2026

Notifications are not arriving (especially on iOS)

Why alerts about new leads are not arriving - in Telegram, in the browser, on iPhone, on a Mac or by email - and how to fix it. Start with the first section: it is the most common cause. The bot is connected, but no cards arrive - Cause: the bot has not been added to the campaign. Connecting only subscribes you to the bot; cards come from the campaigns that have a Telegram bot step. The bot does not add itself to new campaigns, even if you have already connected it. - Fix: 1. Open Settings → Notifications and press Add to campaigns on the bot's card. 2. Tick the campaigns you want (or Select all) and press Add. Campaigns that already have the bot are marked already added. 3. For a single campaign you can also do it this way: the campaign page → Pipeline → + → Delivery → Telegram bot → Add step. ℹ️ Note: the Viewer role has no Add to campaigns button - ask a colleague with another role. If a campaign is paused (it is marked paused in the list), it brings no new leads until you resume it. The bot is not connected, or the connection dropped - Cause: the Notifications page shows the Connect the bot button instead of Bot connected. This happens if Start was never pressed in the bot itself, or if the bot was blocked or its chat deleted in Telegram - the connection is then removed automatically. - Fix: 1. Settings → Notifications → Connect the bot (the same card is on the Agents page, Deliverers tab). 2. Open the bot with Open in Telegram or the QR code and press Start. 3. If you see a message that the code has expired, press Connect the bot again: the link works only once. A pause is on - Cause: the /mute command was sent in the bot - it silences alerts for 1 hour. - Fix: send the bot /status - a pause mark appears next to the account. The /unmute command turns alerts back on right away. Also check that notifications from the Telegram app are allowed on your phone and that the chat with the bot is not muted. Browser push does not arrive - Cause: Push notifications are not on for this device, or the browser has blocked notifications for the site. - Fix: 1. Open Settings → Notifications, the This browser block, and turn on Push notifications. 2. When the browser asks, press Allow. 3. If the switch says "The browser blocked notifications. Allow them in site settings", click the icon to the left of the tg.grinfi.io address → Notifications → Allow. 4. Push is on, but nothing pops up - check Desktop banner: when it is off, push arrives without a banner. If it says "This browser cannot do push notifications", open Telegrin in another browser. In Incognito mode push is usually unavailable. Alerts do not arrive on iPhone - Cause: on iPhone, push works only in the app installed to the Home Screen through Safari (iOS 16.4 or newer is required). A regular Safari tab does not get notifications. - Fix: 1. Open tg.grinfi.io in Safari specifically. 2. Tap Share → Add to Home Screen → Add. 3. Always open Telegrin from the icon on the Home Screen. 4. Inside the app, turn on Push notifications (Settings → Notifications) and confirm the iOS prompt. 5. If there are still no notifications, check the permission for telegrin in the iOS Settings, in the notifications section. 💡 Tip: the most reliable channel on a phone is the Telegram bot: it does not depend on browser permissions. Just do not forget to add it to your campaigns. Alerts do not arrive on a Mac - Cause: notifications are turned off at the macOS level, not in the browser. - Fix: 1. Open System Settings → Notifications. 2. Find your browser in the list (Chrome, Safari, Edge) and turn on Allow notifications. 3. Check whether Focus / Do Not Disturb is on: it silences notifications even when everything is allowed. Lead emails do not arrive - Cause: email is a setting for the whole workspace, not for a campaign. The emails go to the workspace owner's address, and only when there is something to send. - Fix: check the option in the Email block on the Notifications page: with Do not send there are no emails. With Once a day and Once a week, an email comes only if there are unread leads for the period. Check your spam folder too. How all the notifications work is covered in the articles "Notifications" and "Browser notifications".

Last updated on Oct 15, 2026