Home Settings and integrations

Settings and integrations

Team, notifications, API and MCP
Alex Mishyn
By Alex Mishyn
5 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 they can do | | --- | --- | | Admin | Everything: invites and roles, campaigns, leads, API keys, plan and payment | | Editor | Campaigns and account connections. Cannot invite people, change roles or touch payment | | Operator | Working with leads: the feed, replies, the pipeline, blocking senders. Cannot create or change campaigns | | Viewer | View only. Any change is rejected | 💡 Tip: a typical split in a team is the business owner as Admin, the marketer as Editor (they set up campaigns and keywords), and the sales managers as Operators (they work through the feed and talk to leads). ⚠️ Important: an Operator can add a sender to the blocklist but cannot take them off it - unblocking is available to Admins and Editors. This is deliberate: removing a block affects every campaign at once. A Viewer cannot change anything except one thing - their own alerts in the Telegram bot. That is a personal setting for each person, and it does not affect colleagues. Inviting someone 1. Press Invite. 2. Enter the Email and pick a Role. 3. Press Send invite. The person receives an email with a link. Once they accept, they appear in the member list. Changing a role or removing a member The member's menu has Change role and Remove from team. Removing someone closes their access to the workspace but deletes nothing: the campaigns, leads and conversations they worked on stay where they are. One account - one workspace A Telegram account can only be connected to one workspace. If you see a message during connection saying the number is already in use, disconnect it first wherever it is currently connected. Workspace number On the Settings → Profile page you can see the Workspace number in the format TG-00001. Give it to support when you get in touch - that 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 it. - The workspace name. You change your password yourself through recovery: on the sign-in page, click the forgotten-password link and we will send an email with a link to set a new one.

Last updated on Aug 02, 2026

Notifications

You do not have to check signals by hand - Telegrin can tell you about new leads itself. The page: Settings → Notifications. The Telegram bot The most convenient way: the lead card arrives in your private messages together with a reply button. 1. Connect the bot with the button on the Notifications page (or on the Agents page). 2. Turn on the Send lead alerts to Telegram switch. ℹ️ Note: this switch is personal. Each team member turns alerts on and off for themselves, and it does not affect colleagues. Muting for a while You can mute alerts inside the bot itself. If you have done that, an Alerts are muted reminder appears on the settings page with a button to bring them back - so you do not forget you once turned them off. Per campaign The Telegram bot is an ordinary deliverer agent, like Slack or a webhook. A campaign no longer has its own «Telegram alerts» toggle: the bot appears in the campaign's list of deliverers, and that is where you manage it. To mute a single campaign, detach the bot deliverer from it. The campaign keeps running; its leads simply stop arriving in Telegram. 💡 Tip: if there are too many alerts in Telegram, do not turn the bot off entirely - detach it from the loudest campaign. Otherwise you risk missing a genuinely valuable lead. Browser notifications Three settings that are stored on the specific device and do not follow you to your phone: - Push notifications - they arrive even when the tab is closed; - Sound - a short chime while the tab is open; - Desktop banner - pops up when the tab is in the background. If push will not turn on, the browser has most likely blocked it: allow notifications in the site settings. ⚠️ Important: a push subscription is tied to a specific browser. If you work from both a laptop and a desktop, turn it on separately on each. Emails Your inbox receives system emails about the balance - when 20% and 5% of the monthly credit allowance is left, and when the credits have run out. They have no separate setting and cannot be turned off. Leads arrive by email too. Add the Email delivery to a campaign, then pick the pace in Settings → Notifications: - every lead - a separate email as soon as a lead is confirmed; - once a day - one digest with the fresh leads; - once a week - the same, weekly; - off - silence. ℹ️ Tip: an empty digest is never sent - if there were no leads in the period, there is no email. The pace is set to once a week out of the box, so the inbox stays a reminder rather than spam. What is not here yet Honestly about the limits, so you do not go looking for these settings: - choosing events - every lead found goes to Telegram; - filtering by channel - you cannot turn on LinkedIn only or Telegram only; - scheduled quiet hours - only the manual mute inside the bot exists. The most flexible tool today is the per-campaign toggle.

Last updated on Sep 03, 2026

MCP and the public API

There are two ways to connect Telegrin to your tools: - MCP server - for AI assistants (Claude, ChatGPT, Cursor): the assistant gets direct access to your feed, campaigns and pipeline, so tasks get done right in the chat. - Public API - for your own integrations and scripts: the same capabilities over REST requests. The MCP server mirrors the public API one to one: everything the API can do (around 90 operations) is available to the assistant through MCP as well. MCP: connect in 2 minutes 1. Open the MCP section in the app navigation. 2. Pick the tab for your client - Claude Code, Claude Desktop or Cursor - and copy the ready-made snippet with the copy button: - Claude Code - a single command in the terminal, the server adds itself; - Claude Desktop - paste into claude_desktop_config.json (Settings → Developer → Edit Config); - Cursor - paste into the ~/.cursor/mcp.json file and restart. 3. The server address (already inside the snippets): https://mcp-tg.grinfi.io/mcp. 4. On the first connection an authorization window opens - sign in with your Telegrin account. No separate key is needed for MCP. What the assistant can do through MCP - reads the feed and approves signals right from the chat; - manages campaigns - start, pause, keywords; - shows your credit balance and limits; - moves leads through pipeline stages; - returns monitoring statistics and metrics. Example requests to the assistant: "show me today's new signals and approve the relevant ones", "pause campaign X", "how many credits are left and what did the last ones go on". Public API: keys and access 1. Open Settings → API keys. 2. Click "Create key" and give it a name. 3. Copy the key immediately - it is shown only once. 4. Pass the key in the Authorization: Bearer <key> header. ⚠️ Important: a key gives programmatic access to the entire workspace, so only the workspace admin can create and revoke keys. Revoke a compromised key on the same screen - it takes effect instantly. What the API covers Groups of operations (the same ones are available through MCP): - Campaigns - list, create, edit, start/pause, campaign deliverers. - Signals and leads - the feed, approve/reject, lead cards, pipeline stages. - Agents - the list of agents and templates. - AI cores - reading and updating cores. - Tracked posts - connecting and archiving posts. - Analytics - dashboard metrics, the monitoring funnel. - Billing - credit balance and limits (no payments - purchases happen in the app only). - Blocklist - adding and removing entries. - Webhooks - managing delivery endpoints (details in the article "Webhook delivery of leads to your CRM"). - History scanning, workspace, chat search - utility operations. Which plans include it API and MCP are available on every plan - during the trial and on the paid plans (Starter, Growth and Scale). Keys are created by the workspace admin in Settings → API keys. Related articles "Webhook delivery of leads to your CRM" · "Multiple lead delivery channels and their order" · "Plan and limits"

Last updated on Sep 03, 2026

Browser notifications

Browser notifications tell you about new signals while you are working at your computer. The level is configurable - from complete silence to push with sound. Where to find it Settings → Notifications; for quick access, use the bell icon in the top bar. If browser notifications are not available on this device, the screen says so honestly - signals still arrive in the Telegram bot. Three switches (the "This browser" block) These settings apply to the current browser - each device has its own. The screen also honestly lists what is NOT here yet: choosing events, filtering by channel, quiet hours. 1. Push Notifications arrive even when the tab is closed. The first time you turn this on, the browser will ask for permission - click "Allow", without it push will not work. ℹ️ Note: if you previously blocked notifications for tg.grinfi.io, the switch cannot turn them on by itself - the browser permission takes priority. Allow notifications in your browser settings: the lock icon in the address bar → Notifications → Allow. 2. Sound A short chime when a new signal arrives while the tab is open - handy when Telegrin sits in a window next to you. 3. Banner A system banner when the tab is open but in the background. Which combination to choose | Scenario | Browser push | Sound | System notifications | | --- | --- | --- | --- | | I want everything | On | On | On | | No banners, but with sound | Off | On | Off | | Silence | Off | Off | Off | 💡 Tip: so you do not miss signals away from your computer, also install the app on your phone and connect the Telegram bot - together these channels cover every situation. How to do it - in section 6 "Notifications and the app", the articles "Installing the app (PWA) on iOS and Android" and "Telegram notifications (bot)". Troubleshooting The "Browser push" switch will not turn on - Cause: notifications for the site are blocked at the browser level - the switch cannot override that block. - Fix: allow notifications in your browser settings (the lock icon in the address bar → Notifications → Allow) and turn the switch on again. In Incognito mode push is usually unavailable - use a normal window. There is no sound - Cause: sound is muted in the system, or the browser blocks playback until you have interacted with the page. - Fix: check the system volume, then click anywhere on the Telegrin page - that lets the browser play sound - and wait for the next signal. If notifications do not arrive despite correct settings (in particular on iOS and macOS) - the full walkthrough is in section 9 "Troubleshooting", the article "Notifications are not arriving (especially on iOS)".

Last updated on Aug 09, 2026

Notifications are not arriving (especially on iOS)

Why notifications about new signals do not arrive - in the browser, on an iPhone, on a Mac or in Telegram - and how to fix it. Browser push does not arrive - Cause: the "Browser push" switch is off, or the browser does not have notification permission. - Effect: signals appear in the app, but there are no notifications. - Fix: 1. Open Settings → Notifications - the browser switches are grouped in the "This browser" block. 2. Turn on Push - notifications will arrive even when the tab is closed. 3. When the browser asks, click "Allow" - without that permission the browser will not show push. 4. If the prompt did not appear (you clicked "Block" earlier), allow notifications for tg.grinfi.io in your browser settings: the lock icon in the address bar → Notifications → Allow. How all three notification switches work - in section 6 "Notifications and the app", the article "Browser notifications". Notifications do not arrive on iOS - Cause: on an iPhone, browser push notifications only work in an app installed to the Home Screen through Safari (iOS 16.4 or newer is required). A regular Safari tab sends no notifications. - Effect: notifications work on the computer but not on the iPhone. - Fix: 1. Open tg.grinfi.io in Safari - Chrome on iOS cannot install a PWA with push. 2. Tap Share → "Add to Home Screen" → Add - this turns Telegrin into an app with its own icon. 3. Open Telegrin only from the icon on the Home Screen - push only reaches the installed app. 4. Inside the app, turn on Push (Settings → Notifications) and confirm the iOS system prompt - that is the notification permission. 5. If there are still no notifications, check the permission for telegrin in iOS Settings under notifications (the path may differ slightly depending on your iOS version). Step-by-step installation of the app is in section 6 "Notifications and the app", the article "Installing the app (PWA) on iOS and Android". 💡 Tip: the most reliable channel on a phone is the Telegram bot @telegrin_signals_bot: it does not depend on browser permissions. Connecting it is described in section 6 "Notifications and the app", the article "Telegram notifications (bot)". Notifications do not arrive on macOS - Cause: notifications are blocked at the operating system level rather than the browser level - macOS shows no banners even when everything is allowed in the browser itself. - Fix: 1. Open System Settings → Notifications. 2. Find your browser in the list (Chrome / Safari / Edge) - that is what displays notifications from Telegrin. 3. Turn on Allow notifications and choose a banner style - this lets the system show the browser's notifications. 4. Check whether Focus / Do Not Disturb is on in Control Center - it silences notifications even when permissions are granted. Telegram notifications do not arrive - Cause: the bot is not connected, or a /mute pause is active. - Fix: 1. Open the Agents screen - the bot connection card is always at the top → Connect → confirm in Telegram with the Start button. 2. If the bot is already connected, send it /status: a pause may be on. The /unmute command resumes notifications. 3. Check that notifications from the Telegram app itself are allowed on your phone - otherwise the bot's messages will arrive silently. Sound or banners are off - Cause: the "Sound" and "Banner" switches on the Notifications screen are off. - Fix: turn on "Sound" (a short chime while the tab is open) and "Banner" (a banner when the tab is in the background). These switches apply to the browser only and do not affect the Telegram bot. ℹ️ The most reliable alternative to browser notifications is campaign deliverers: the Telegram bot or email (a message per lead or a digest) - they do not depend on browser permissions.

Last updated on Aug 09, 2026