# What is Plugsight? URL: https://docs.plugsight.app/get-started Plugsight connects your own accounts, like Gmail, Google Ads or Zendesk, to Claude, ChatGPT and other AI apps, safely. Plugsight lets an AI assistant work with **your own data**: your email, calendar, ad accounts, analytics, helpdesk, store and files. You connect an account once, and your AI can then answer questions like *"Which Google Ads search terms wasted money last month?"* or *"What are customers complaining about this week?"*. ## How it works 1. **Connect your accounts** in the Plugsight app. Each one is read-only, or drafts-only for email, until you allow more. 2. **Create an MCP server**: a private link that reaches the accounts you choose. 3. **Add that link to your AI app** (Claude, ChatGPT, Cursor and others) and click **Allow access**. From then on, you ask your AI in plain language. Plugsight reads the data live when it's needed, and never stores your emails or reports. [How Plugsight works](/get-started/how-it-works) explains each part in more detail. ## You stay in control - Your AI can only **read** (and write email drafts) until you switch on changes for an account. - Every change, like sending an email, waits for **your approval in the chat**. - **Activity** shows everything your AI did, and you can **pause** all changes in one tap. ## Where to go next - [Quick start](/get-started/quick-start): your first AI connection in about five minutes. - [Connect AI apps](/ai-apps): step-by-step setup for Claude, ChatGPT, Claude Code, Cursor, VS Code and others. - [Questions to try first](/get-started/first-questions): example questions for each kind of account. - [Plans](/get-started/plans): what Free, Pro and Agency include. - [Glossary](/get-started/glossary): the words used in the app and in these docs. - [Ask AI](/get-started/ask-ai): ask the help centre a question and get an answer written from these docs. > [!TIP] > Need help? Email [info@plugsight.app](mailto:info@plugsight.app). --- # Quick start URL: https://docs.plugsight.app/get-started/quick-start Connect an account, create your AI link and ask your first question, in about five minutes. You need a Plugsight account and an AI app that supports custom connectors, such as Claude (any plan) or ChatGPT (Business, Enterprise or Edu). See [Connect AI apps](/ai-apps) for the full list. ## 1. Connect an account 1. Open [app.plugsight.app](https://app.plugsight.app) and sign in. 2. Click **Add connection** and pick a service, for example **Gmail** or **Google Analytics 4**. 3. Follow the steps on screen. Most services take one sign-in. Gmail, iCloud, Yahoo and most other mailboxes use an app password instead, and the page links straight to where you make one. > [!NOTE] > On the Free plan you can connect 2 accounts. Marketing and analytics services (Google Ads, Microsoft Ads, Meta Ads, LinkedIn Ads, Search Console, GA4 and Bing Webmaster Tools) need the Pro plan for regular use; Free includes 1 marketing connection and 25 marketing tool calls a month to try them. See [Plans](/get-started/plans). ## 2. Create an MCP server 1. Go to **MCP servers** and click **Create MCP server**. 2. Give it a name, such as "Work". Your AI app shows this name. 3. Under **Account access**, choose **All accounts**, or choose **Selected accounts** and tick only the ones this link should reach. 4. Click **Create server**. You land on the server's page. 5. Under **Server URL**, click **Copy URL**. ## 3. Add it to your AI app For **Claude**: 1. In a web browser, go to [claude.ai/customize/connectors](https://claude.ai/customize/connectors). 2. Click **+ Add**, then **Add custom connector**. 3. Enter the server's name and paste the URL into **Remote MCP server URL**. 4. Click **Continue**, **Continue** again, then **Add**. 5. Next to the new connector, click **Connect**. 6. On the Plugsight screen that opens, check the server name and click **Allow access**. For ChatGPT and other apps, follow the steps in [Connect AI apps](/ai-apps). The server's page in Plugsight also shows the steps for each app under **Connect an AI app**. ## 4. Ask your first question Start a new chat. In Claude, click **+** in the message box, then **Connectors**, and check your server is switched on. Then try: - "List my connected accounts." - "What's on my calendar tomorrow?" - "Summarise my unread emails from today." The first time your AI uses a tool, the AI app may ask your permission. Choose **Allow**. More ideas: [Questions to try first](/get-started/first-questions). ## Next steps - Want your AI to send emails or update tickets? It can only read and draft until you allow changes, and each change then waits for your approval. See [Approvals in your AI app](/ai-apps/approvals). - Connected another account later? See [Refresh the tools list](/ai-apps/refresh-tools). --- # How Plugsight works URL: https://docs.plugsight.app/get-started/how-it-works How your accounts, your MCP server and your AI app fit together, and why your data is read live and never stored. Plugsight sits between your accounts and your AI app. There are three parts, and you set each one up once. | Part | What it is | Where you manage it | |---|---|---| | **Connections** | Your own accounts: a mailbox, a Zendesk account, a Google login, a store | **Connections** in the Plugsight app | | **MCP server** | A private link that reaches the accounts you choose, and nothing else | **MCP servers** in the Plugsight app | | **AI app** | Claude, ChatGPT, Claude Code, Cursor, VS Code or another MCP app | The AI app's own connector or MCP settings | ## 1. Your accounts (connections) You connect each account in Plugsight. Depending on the service, you either sign in (Google, Microsoft, Zendesk) or paste an app password (Gmail, iCloud, Yahoo and most other mailboxes). - One sign-in to one service is one **connection**. One Google service connected with one login can reach many Search Console sites, GA4 properties or Google Ads accounts, and they count as one connection. Each Google service (Search Console, GA4, Google Ads) is its own connection. - You can connect several accounts of the same type, such as a work and a personal Gmail. See [Several accounts per service](/ai-apps/multiple-accounts). - You can hide anything a connection reaches that you don't want your AI to see, such as one Search Console site or one ad account. Hidden items are never used, even if the AI asks for them by name. - Each account starts read-only (or **Drafts only** for email). Sending email, updating tickets and booking calendar events stay off until you switch them on for that account. ## 2. Your MCP server (your AI link) An MCP server is a private web address that you paste into your AI app. Through it, the AI can use only the accounts you chose for that link. - **All accounts** includes every connected account, including ones you add later. - **Selected accounts** includes only the accounts you tick. Accounts you connect later are not added: tick them in **Edit configuration**. - **Allow changes** decides whether this link may ever send or change anything. It is ticked for new servers. Untick it for a read-only link, for example one you share with a client. You can make several MCP servers, for example one with all your accounts for you, and a read-only one with one client's ad account. How many you can have depends on your [plan](/get-started/plans). ## 3. Your AI app You add the server's link to your AI app as a custom connector (Claude and ChatGPT call it that; other apps call it an MCP server). The AI app opens a Plugsight window, you sign in and click **Allow access**, and the app is connected. Claude Code and some other tools can use an API key instead of a sign-in window. The approval screen shows what the AI app will be able to do: - **Search and read**: everything in the accounts of the MCP server you choose, and nothing outside it. - **Draft, send and change**: write email drafts. Send, update tickets or book events only if that server allows changes and the account's switch is on, and only after you approve each one in the chat. Step-by-step setup for each app: [Connect AI apps](/ai-apps). ## What happens when you ask a question 1. You ask your AI something, for example "What are customers complaining about this week?" 2. The AI app picks one of Plugsight's tools, such as searching tickets, and asks Plugsight for the data. 3. Plugsight checks that the MCP server includes that account, then fetches the data live from the service (Zendesk, in this example). 4. The AI reads the answer and replies to you. 5. The request is recorded in **Activity**: when, which AI app, which account and the result. If the AI wants to change something (send an email, reply to a ticket, book a meeting), it must first show you the exact details and wait for your yes in the chat. Plugsight also checks the account's switch, the server's **Allow changes**, any pause on **Permissions**, the daily email limit and your plan. See [Approvals in your AI app](/ai-apps/approvals). ## What Plugsight stores, and what it doesn't - **Not stored:** your emails, tickets, reports and other data. They are fetched live when you or your AI ask, and aren't kept. - **Stored:** what's needed to connect (your connection credentials, encrypted with AES-256-GCM) and your settings. - **Activity:** a record of what was done (sign-ins, changes to your settings, and every tool an AI app used), kept for one year. Email bodies and attachments are never stored there, only what was done. ## The tools list AI apps load Plugsight's list of tools (actions) once and keep it. When you connect the first account of a new type, such as your first Zendesk, or remove the last one, the AI app needs to reload that list. The Plugsight app shows a notice naming each AI app that needs it, with its steps. See [Refresh the tools list](/ai-apps/refresh-tools). ## Related articles - [Quick start](/get-started/quick-start) - [How changes are allowed](/permissions/how-changes-are-allowed) - [What Plugsight stores and logs](/security/data-handling) - [Ask AI about Plugsight](/get-started/ask-ai) --- # Questions to try first URL: https://docs.plugsight.app/get-started/first-questions Example questions to ask your AI for each kind of account, from email and calendars to Google Ads, GA4 and Zendesk. Once your MCP server is added to your AI app, you ask in plain language. These examples show what works well. Change the names, dates and numbers to match your own accounts. ## Check it's working Start a new chat and ask: - "List my connected accounts." Your AI replies with every account your MCP server reaches. If one is missing, see [Several accounts per service](/ai-apps/multiple-accounts) and [Refresh the tools list](/ai-apps/refresh-tools). ## Email (Gmail, Outlook, iCloud Mail and other mailboxes) - "Summarise my unread email from customers today." - "Find every invoice we received from suppliers this quarter and list the totals." - "Which emails from last week am I still waiting on a reply to?" - "What did the contract PDF attached to Sarah's email say about payment terms?" - "Draft a reply to the latest email from Acme about the delayed order." - "List all emails with Excel attachments from the last 30 days." - "Archive every newsletter in my inbox and label the receipts 'Expenses'." Drafts are saved in your mailbox's Drafts folder and never sent. Sending needs the account's switch on and your approval in the chat. See [Approvals in your AI app](/ai-apps/approvals). ## Helpdesk (Zendesk) - "What are the top five reasons for tickets this week?" - "Which urgent tickets have had no reply for more than a day?" - "Summarise everything this customer has raised in the last 90 days." - "Find tickets tagged 'refund' that are still open." - "How many tickets did we solve last week compared with the week before?" - "Draft an internal note on ticket 4821 summarising the issue." ## Calendar (Google, Outlook and iCloud Calendar) - "What does my week look like, and which meetings could be an email?" - "Find three 45-minute slots next week when I'm free in the afternoon." - "How many hours of meetings did I have this month?" - "Find a free hour on Wednesday and book a call with sam@example.com." (Outlook and iCloud Calendar only, with the account's switch on.) Google Calendar shows your events and free time, but can't book. ## Contacts (Google, Outlook and iCloud Contacts) - "What's the mobile number for Priya at Northwind?" - "Who do I know at Acme?" - "Find my accountant's email and draft them a note about this year's receipts." ## Google Ads and Microsoft Advertising These need the Pro or Agency plan. - "Which search terms cost us money last month without converting? Suggest negative keywords." - "Compare CPA and ROAS by campaign this month vs last month." - "Which keywords have a quality score of 5 or less, and is expected CTR or the landing page the problem?" - "Across all client accounts, which ones spent more than 20% over last month?" - "How did Microsoft Ads perform last month compared with Google Ads?" - "Which campaigns are losing impression share to budget?" ## Google Search Console - "Which queries rank in positions 4–20 with the most impressions?" - "Which pages lost the most clicks compared with last month?" - "Is this URL indexed, and if not, why?" - "Where are we paying for Google Ads clicks on queries we already rank top 3 for?" ## Google Analytics 4 - "Which channels drove the most revenue this month vs last month?" - "Which landing pages have the highest conversion rate from paid search?" - "How many people are on the site right now, and from which countries?" - "Build a funnel from product page to purchase and show where mobile users drop off." ## Online stores (WooCommerce, Magento / Adobe Commerce) - "How did the shop do last month compared with the month before?" - "Which products sold best this week, and are any of them running low on stock?" - "Find order 1042 and tell me what was bought and where it's shipping." - "Who are my ten biggest customers by total spent?" - "Compare Google Ads spend last month with WooCommerce revenue for the same days." ## Email marketing (Mailchimp) - "Which of last quarter's campaigns had the best click rate, and what did their subject lines have in common?" - "Is our list growing? Show new subscribers and unsubscribes by month for the last year." - "Which links got the most clicks in last week's campaign?" ## Tips for better answers - **Name the account** when you have several of one type: "in my work Gmail", "for Bright Dental's Google Ads". Clear names on **Connections** make this easier. - **Mention Plugsight** if your AI answers from general knowledge instead of your data: "Using Plugsight, show last week's Google Ads spend." - **Check the connector is on in the chat.** In Claude, click **+** in the message box, then **Connectors**. In ChatGPT, click **+** next to the message box and select your server. - **Give a date range** for reports: "last month", "this quarter", "the last 30 days". - **Ask across accounts** in one question: "What did I promise anyone by email this week, in any inbox?" ## Related articles - [Write better questions](/guides/better-questions) - [Recipes](/recipes) - [Refresh the tools list](/ai-apps/refresh-tools) - [Quick start](/get-started/quick-start) --- # Plans URL: https://docs.plugsight.app/get-started/plans What the Free, Pro and Agency plans include, their connection and MCP server limits, and what happens when you reach a limit. Plugsight has three plans you can choose in the app: **Free**, **Pro** and **Agency**. Larger teams can ask about Enterprise. Prices are in US dollars. Paying yearly gets you two months free. Your AI app's own subscription (Claude, ChatGPT and so on) is separate and not included. ## Compare plans | | Free | Pro | Agency | |---|---|---|---| | Price | $0 | $29 a month, or $290 a year | $99 a month, or $990 a year | | Connections | 2 | 10 | 50 | | MCP servers | 1 | 5 | Unlimited | | Email (Gmail, Outlook, iCloud, IMAP) | Yes | Yes | Yes | | Zendesk | Yes | Yes | Yes | | Marketing and analytics connectors | To try: 1 connection, 25 tool calls a month | Yes | Yes | | Marketing deep dives | No | Yes | Yes | | [Custom API](/connectors/custom-api) connections | No | Yes | Yes | | [Custom MCP server](/connectors/custom-mcp) connections | No | Yes | Yes | | Google Ads manager (MCC) client accounts | Within the allowance | Yes | Yes | | Sending email and helpdesk changes, each approved by you | No | Yes | Yes | | Developer API | No | Yes | Yes | | Hide sites and ad accounts per connection | Yes | Yes | Yes | | Activity log | Yes | Yes | Yes | | Support | Email (best effort) | Email | Priority | **Enterprise** offers custom connection and server limits, onboarding and setup help, invoicing and annual contracts, a data processing agreement and a dedicated support contact. Email [info@plugsight.app](mailto:info@plugsight.app) to ask about it. ## Free For trying Plugsight with your own accounts. No credit card needed. If you've never had a paid plan or a trial, you can try everything in Pro with its 7-day free trial (card required). - 2 connections and 1 MCP server. - Your AI can search and read your accounts, and write email drafts. - Your AI can't send email or make changes (such as updating tickets or booking events). The **Allow changes** box on your MCP server can't be ticked. - Marketing and analytics connectors, to try: 1 marketing connection and 25 marketing tool calls a month (calendar months, UTC). Calls that fail don't count. Ready-made deep dives are in Pro and Agency. - Custom APIs and custom MCP servers aren't available. ## Pro For marketers and small teams. - 10 connections and 5 MCP servers. - Marketing and analytics connectors: Google Ads, Microsoft Ads, Meta Ads, LinkedIn Ads, Search Console, GA4 and Bing Webmaster Tools, plus Tag Manager, YouTube and Merchant Center once Google approves them. - Ready-made marketing deep dives. - [Custom API](/connectors/custom-api) connections: any REST API, with an OpenAPI import. - [Custom MCP server](/connectors/custom-mcp) connections: any remote MCP server's tools, in your Plugsight MCP servers. - Changes: sending email, helpdesk replies and updates, and calendar bookings, each needing the account's switch on and your approval in the chat. Plus archiving, labelling and marking emails, which need only the plan (your AI asks first before moving emails to the trash or changing more than 10). - The developer API. ## Agency For agencies with many clients. - 50 connections and unlimited MCP servers. - Everything in Pro. - Room for every client under your Google Ads manager accounts (cross-account reports and deep dives work on Pro too; Agency adds the room for more clients). - Unlimited MCP servers, so every client can have their own (Pro allows 5). Hiding individual sites and ad accounts works on Pro too. - Priority support. ## What counts as a connection One sign-in to one service: a mailbox, a Zendesk account, a Microsoft Advertising login, or one Google service such as Search Console, GA4 or Google Ads. Each Google service is its own connection, so connecting Search Console, GA4 and Google Ads with the same Google login uses three. Within one connection, everything that login can see counts once: every Search Console site, every GA4 property or every Google Ads account. A second Gmail inbox is its own connection. Marketing and analytics connectors, Custom APIs and custom MCP servers need Pro for regular use; Free includes 1 marketing connection and 25 marketing tool calls a month to try marketing connectors. Every other connector works on every plan, within your connection limit. ## When you reach a limit The **Billing** page shows how many connections and MCP servers you're using against your plan's limit. At the limit, you can't add another until you remove one or upgrade. The app shows one of these messages: ### Your Free plan includes 2 connections. Upgrade to Pro for 10. **What it means:** you already have 2 connections. **How to fix it:** remove a connection you don't need, or upgrade to Pro. ### Your Free plan includes 1 MCP server. Upgrade to Pro for 5. **What it means:** you already have an MCP server. **How to fix it:** use your existing server (it can reach all your accounts), delete it, or upgrade to Pro. ### Your Pro plan includes 10 connections. Upgrade to Agency for 50. **What it means:** you already have 10 connections. **How to fix it:** remove one, or upgrade to Agency. ### Your Pro plan includes 5 MCP servers. Upgrade to Agency for unlimited. **What it means:** you already have 5 MCP servers. **How to fix it:** delete one, or upgrade to Agency. ### Your Agency plan includes 50 connections. Contact us for a higher limit. **What it means:** you've reached the Agency limit. **How to fix it:** email [info@plugsight.app](mailto:info@plugsight.app) to ask about a higher limit. ### Your Free plan includes 1 marketing connection. Upgrade to Pro to connect more. **What it means:** you already have as many marketing or analytics connections as Free includes (1). **How to fix it:** remove it on **Connections**, or upgrade to Pro or Agency on the **Billing** page. ### You've used the 25 marketing tool calls your Free plan includes this month. **What it means:** your AI answered this with a note instead of your data, because this calendar month's marketing tool calls are used up. They start again on the 1st. **How to fix it:** wait for the new month, or upgrade to Pro or Agency on the **Billing** page for no limit. ### Sending email and changing helpdesk tickets are on the Pro plan. **What it means:** your AI tried to make a change on the Free plan. Your AI can still write drafts. **How to fix it:** upgrade to Pro or Agency on the **Billing** page. ## Changing plan - **Upgrading** applies straight away. On the **Billing** page, pick monthly or yearly, then click **Upgrade to Pro** or **Upgrade to Agency**. If you've never had a paid plan or a trial, your first Pro subscription starts with a 7-day free trial: see [Upgrade your plan](/account/upgrade#the-free-pro-trial). - **Switching to a cheaper plan or cancelling** takes effect at the end of the period you've paid for, and you keep everything until then. Use **Invoices, card & cancel** on the **Billing** page. - **When a paid plan ends** and you move to Free: marketing and analytics connectors work only within Free's 25 marketing tool calls a month, Custom APIs and custom MCP servers stop working in your AI, and your AI can't send email or make helpdesk changes (it can still read and draft). Accounts and MCP servers you already have stay, but you can't add more beyond the Free limits. For payments, invoices and cancelling, see [Plans and billing](/account/plans-and-billing). ## Related articles - [Upgrade your plan](/account/upgrade) - [Move from Free to Pro without losing anything](/guides/free-to-pro) - [Plans and limits](/troubleshooting/plan-limits) - [Cancel your plan](/account/cancel) --- # Ask AI about Plugsight URL: https://docs.plugsight.app/get-started/ask-ai Ask a question in your own words and get an answer written from these docs, with links to the articles it used, in the app, on the website or here. **Ask AI** answers questions about Plugsight in plain words. It reads the help-centre articles that match your question and writes an answer from them, with links to those articles so you can check the details. ## Where to find it - **In the Plugsight app:** click **Help** in the top bar, then **Ask AI**. Or type in the Help search box and pick **Ask** under **Ask AI assistant**. - **In these docs:** click **Ask AI** at the top of any page, pick the question under **Ask AI assistant** in search (⌘K or Ctrl+K), or click **Ask about this page** above an article to ask with that article in mind. - **On plugsight.app:** click **Ask AI** at the bottom right of any page. On a connector, AI app or setup guide page, it answers with that page's help-centre article in mind. You can ask follow-up questions in the same conversation, such as "and on Outlook?". Click **New chat** in the docs or on the website to start over. ## What it can and can't do - It answers from these docs only. If the docs don't cover your question, it says so and suggests emailing info@plugsight.app, where a person will help. - **When you're signed in to the Plugsight app**, it knows your account's settings, so it can answer about you: your plan, your connections and whether each can send or is set to drafts only, your MCP servers and their **Allow changes** switch, your pauses and daily email limit, and your AI's recent blocked actions with the reason. Ask "Why can't my AI send email?" and it names the switch that's off, with a link to the page where you change it. It only explains: it never changes a setting for you. - **In these docs and on plugsight.app**, it asks first. If you're signed in to the app in the same browser, Ask AI asks **Use your account's settings to answer?** Click **Yes, use my account** and the answers can be about you, marked **Answered using your Plugsight account's settings**; click **No thanks** and they stay general. Your choice lasts until you close the tab: **Ask without my account** and **Use my account** change it. If you're not signed in, it can't see your account and tells you where to look in the app. - It never sees what's in your connected accounts (your emails, tickets, files or reports), their email addresses or your passwords. - AI answers can be wrong. Each answer links the articles it used, so check the steps there before you rely on them. > [!TIP] > Questions with the exact words you see work best, for example: "Google says app passwords aren't available for my account" or "What does Paused next to my switch mean?" ## What happens to your question Your question, the last few messages of the conversation and the matching help-centre articles are sent to Anthropic's Claude to write the answer. In the app, and in these docs or on plugsight.app once you've said yes, a short summary of your Plugsight settings goes with it: the names you gave your connections and MCP servers, their switches and status, your plan, and recent blocked actions with the reason. Ask AI never receives data from your connected accounts (including their email addresses), and Anthropic doesn't use any of it to train its models. Plugsight doesn't save your questions, the answers or that summary; the network address used for the hourly limit is deleted within a day. Feedback you give (👍 or 👎 under an answer or at the foot of a page, and any note) is stored anonymously with the article it's about, without your question or the answer. Each week, notes left with a 👎 are sent with their article to Claude to check the article against the code. See the [privacy policy](https://plugsight.app/privacy). To keep the service fair, each visitor can ask a limited number of questions per hour; if you reach it, try again later or email info@plugsight.app. Don't type passwords, API keys or other secrets into Ask AI. It never needs them. ## Related articles - [How Plugsight works](/get-started/how-it-works) - [Frequently asked questions](/faq) - [Troubleshooting](/troubleshooting) - [What Plugsight stores and logs](/security/data-handling) --- # Glossary URL: https://docs.plugsight.app/get-started/glossary Plain-English meanings of the words used in the Plugsight app and these docs, from MCP server to Pause and app password. Terms are in alphabetical order. Words in **bold** are labels exactly as the Plugsight app shows them. ## Account access The setting on an MCP server that decides which connected accounts it reaches. **All accounts** includes every connected account, including ones you add later. **Selected accounts** includes only the accounts you tick; accounts you connect later are not added until you tick them. ## Activity The page in the Plugsight app that lists everything on your account, newest first: sign-ins, changes you made, and every read and write AI apps made through your MCP servers. Each entry shows when, which AI app, which account and the result. Entries are kept for one year. A **Blocked** result means a safety setting stopped the action; **Failed** means the service refused it. ## AI app The app you chat with: Claude, ChatGPT, Claude Code, Cursor, VS Code or another app that supports MCP. Also called an AI assistant or AI client. See [Connect AI apps](/ai-apps). ## AI link Another name for an [MCP server](#mcp-server). ## Allow access The button on Plugsight's approval screen. An AI app opens this screen when you connect it to an MCP server. Clicking **Allow access** lets that AI app use that server. Clicking **Cancel** gives it no access. ## Allow changes A tick box on each MCP server, under **Permissions** in its configuration. When ticked (the default for new servers), the AI may send email, update tickets or book events through this server, but only with accounts whose switch is on, after you approve each change in the chat, and while nothing is paused. When unticked, the server is **Read & draft only**: the AI can read and write email drafts, but can't send email, update tickets or book events, whatever the account switches say (archiving, labelling and marking emails still work). On the Free plan this box can't be ticked, because changes are on the Pro plan. ## API key A secret key for one MCP server, for tools that can't open a sign-in window, such as Claude Code on a server or your own scripts. Claude, ChatGPT and most AI apps don't need one. You create it on the server's page under **API key**. It's shown once. Anyone with the key can use that server's accounts, so keep it private, and use **Regenerate key** or **Revoke key** if it leaks. ## App password A separate password your email provider creates for Plugsight. Gmail, iCloud, Yahoo, AOL, Zoho, Fastmail and most other mailboxes connect this way. Your real password stays private, and you can delete the app password at your provider at any time to cut access. ## Approval Your yes in the chat before the AI makes a change. Before sending an email, replying to a ticket or booking an event, the AI must show you the exact details and wait for you to agree. Drafts don't need approval because they never send. See [Approvals in your AI app](/ai-apps/approvals). ## Connection One sign-in to one service: a mailbox, a Zendesk account, one Google service such as Search Console, or a Microsoft Advertising login. One Search Console connection can reach many sites, and they all count as one connection; GA4 properties and Google Ads accounts work the same way, each service as its own connection. Your plan sets how many connections you can have. You manage them on the **Connections** page. ## Connector A word with two meanings: - **In Plugsight:** a service you can connect, such as Gmail, Zendesk or Google Ads. The **Connector catalog** lists them all. - **In Claude and ChatGPT:** an outside tool added to the AI app. Your Plugsight MCP server appears in Claude as a custom connector. ## Daily email limit How many emails your AI may send from each email account in 24 hours: 20 by default, adjustable from 1 to 500 under **Permissions** → **Daily email limit**. The 24 hours roll: each email counts for 24 hours after it's sent. Drafts never count. ## Deep dive A ready-made analysis for marketing data, such as wasted ad spend or SEO opportunities. Deep dives are on the Pro and Agency plans. ## Developer API A way to pull the same live data into your own website, dashboard or system with plain HTTPS and JSON, using an MCP server's API key. It's on the Pro and Agency plans. ## Disconnect all AI apps A button in the **Danger zone** on an MCP server's page. It cuts off every AI app using that server straight away. Each one must click **Allow access** again to come back. The server, its link and its accounts stay. An API key keeps working until you revoke it. See [Disconnect an AI app](/ai-apps/disconnect). ## MCP Model Context Protocol: the open standard that Claude, ChatGPT, Cursor, VS Code and other AI apps use to reach outside tools. You don't need to know how it works to use Plugsight. ## MCP server Your AI link: a private web address that lets Claude, ChatGPT or any MCP app use the accounts you choose, and nothing else. You can make several, for example one per client, each reaching different accounts. You manage them on the **MCP servers** page. ## Needs reconnecting A connection's status when the service stopped accepting its sign-in, usually because the password changed or access was removed. Click **Reconnect** and sign in again, or paste a new app password. Your AI can't use that account until you do. ## Pause An emergency stop on the **Permissions** page. **Pause** stops every change of one type (such as all helpdesk replies and updates) for all your accounts of that type. **Pause everything** stops all types at once. Your AI can still read, and still write email drafts. A pause always wins over the account switches. Click **Resume** (or **Resume all**) to undo it. While anything is paused, every page in the app shows a red notice. ## Permissions The page in the Plugsight app where you pause changes and set the daily email limit. Whether each account may make changes is set on **Connections**, not here. ## Plan Free, Pro or Agency. Your plan sets how many connections and MCP servers you can have, and whether marketing connectors and changes (sending email, updating tickets) are included. See [Plans](/get-started/plans). ## Read-only An account or MCP server that can't change anything. Marketing and analytics, contacts, files, stores and email marketing are always read-only. ## Refresh tools list Reloading the list of Plugsight tools in your AI app, after you connect the first account of a new type or remove the last one. See [Refresh the tools list](/ai-apps/refresh-tools). ## Server URL The web address of an MCP server, shown at the top of its page with a **Copy URL** button. It's what you paste into your AI app. ## Sites & accounts A list on a marketing connection showing every site, property or ad account its login reaches. Switch off anything you want hidden from your AI. Calendar connections have a similar list called **Calendars**, and file connections one called **Drives**. ## Tools The actions Plugsight offers your AI app, such as searching email, reading a ticket or running a Google Ads report. The AI app picks the right tool for your question. ## Write access The switch on each account on the **Connections** page that decides whether your AI may change things with that one account. When off, it shows **Drafts only** for email and **Read-only** for other types: the AI can read (and draft emails) but can't send or change anything. When on, it shows **Can send** (email), **Can reply & update** (helpdesk) or **Can book & change** (calendar), and the AI may make changes once you approve each one in the chat. Accounts that only read show **Read-only** and have no switch. The line under the switch says **Ready** when changes can go through, or names the one thing still stopping them. ## Related articles - [How Plugsight works](/get-started/how-it-works) - [How changes are allowed](/permissions/how-changes-are-allowed) - [MCP servers](/mcp-servers) --- # Connect AI apps URL: https://docs.plugsight.app/ai-apps Which AI apps work with Plugsight, which of their plans you need, and step-by-step setup for each one. Plugsight works with any AI app that supports remote MCP servers. You add your MCP server's link to the app once, approve it, and then ask your questions in that app. You can use several AI apps with the same MCP server. Before you start, [create an MCP server](/get-started/quick-start) in Plugsight and copy its **Server URL**. The server's page also shows the setup steps for each app under **Connect an AI app**. ## Which AI apps work, and what you need | AI app | What you need | How it signs in | |---|---|---| | [Claude on the web](/ai-apps/claude) | Any Claude plan. The free plan allows one custom connector. On Team and Enterprise, an Owner adds the connector first. | Sign-in window: click **Allow access** | | [Claude desktop app](/ai-apps/claude-desktop) | Add the connector on claude.ai first; it then works in the desktop app. | Uses the connector added on the web | | [Claude phone app](/ai-apps/claude-mobile) | Add the connector on claude.ai first; it then works in the phone app. | Uses the connector added on the web | | [Claude Code](/ai-apps/claude-code) | Claude Code installed in your terminal (the `claude` command). | Sign-in window, or an API key | | [ChatGPT](/ai-apps/chatgpt) | chatgpt.com in a web browser, with Business, Enterprise or Edu (an admin may need to allow it). ChatGPT Pro can connect, but read-only. The free plan isn't eligible. | Sign-in window: click **Allow access** | | [Cursor](/ai-apps/cursor) | Cursor. | Sign-in window, or an API key | | [VS Code](/ai-apps/vs-code) | VS Code with Copilot agent mode. | API key | | [Other MCP apps](/ai-apps/other-apps) | Any app that supports remote MCP servers over HTTP, such as Windsurf or Gemini CLI. | Sign-in window if the app supports it, otherwise an API key | > [!NOTE] > "ChatGPT Pro" here means OpenAI's ChatGPT plan, not Plugsight's Pro plan. Your AI app's subscription is separate from your Plugsight plan. ## Sign-in window or API key? - **Sign-in window (recommended).** The AI app opens a Plugsight page. You sign in, check the MCP server's name and click **Allow access**. No keys to copy. Claude, ChatGPT and most apps work this way. - **API key.** For tools that can't open a sign-in window, such as Claude Code on a server, or your own scripts. You create the key on the MCP server's page under **API key**. Anyone with the key can use that server's accounts, so keep it private. ## After you connect - [Refresh the tools list](/ai-apps/refresh-tools) when you connect the first account of a new type. - [Several accounts per service](/ai-apps/multiple-accounts): use work and personal inboxes, or many clients' ad accounts, in one chat. - [Approvals in your AI app](/ai-apps/approvals): how your AI asks before it sends or changes anything. - [Disconnect an AI app](/ai-apps/disconnect): remove the connector in the AI app, or cut off every AI app from Plugsight. ## Common problems when connecting ### The sign-in window doesn't open, or closes with an error **What it means:** the AI app couldn't open Plugsight's approval page, or couldn't finish signing in. **How to fix it:** allow pop-ups for the AI app, make sure you're signed in to Plugsight in the same browser, then remove the connector in the AI app and add it again. ### This connector points at an MCP server that isn't in your account. **What it means:** you're signed in to Plugsight with a different account from the one that created this MCP server. This often happens with a work and a personal login in the same browser. **How to fix it:** on the approval screen, click **Switch account** and sign in with the account that created the server. Or use the URL of one of your own servers. ### You don't have an MCP server yet. **What it means:** the approval screen opened, but your Plugsight account has no MCP server to connect. **How to fix it:** click **Create one**, pick the accounts the server should reach, then go back to your AI app and connect again. ### My AI asks me to sign in to Plugsight again **What it means:** the AI app's access ended, usually because the MCP server was deleted, its access was revoked, or you used **Disconnect all AI apps**. **How to fix it:** click the sign-in prompt in the AI app, sign in to the same Plugsight account you set things up with, check the server name and click **Allow access**. ### My AI answers without using my data **What it means:** the connector isn't switched on in that chat, or the AI chose to answer from general knowledge. **How to fix it:** in Claude, click **+** in the message box, then **Connectors**, and switch your server on. In ChatGPT, click **+** next to the message box and select your server. Then ask directly, for example "Using Plugsight, show last week's Google Ads spend". --- # Claude on the web URL: https://docs.plugsight.app/ai-apps/claude Add your Plugsight MCP server to Claude as a custom connector on claude.ai, approve it, and switch it on in a chat. You add Plugsight to Claude once, on the Claude website. After that it also works in the [Claude desktop app](/ai-apps/claude-desktop) and the [Claude phone app](/ai-apps/claude-mobile). ## What you need - claude.ai in a web browser. Adding a connector only works on the website, not in the desktop or phone apps. - Any Claude plan. The free plan allows one custom connector. - A Plugsight MCP server. If you don't have one, follow the [Quick start](/get-started/quick-start). ## Connect Claude (individual plans) 1. In Plugsight, open **MCP servers** and click your server. 2. Under **Server URL**, click **Copy URL**. 3. In a web browser, go to [claude.ai/customize/connectors](https://claude.ai/customize/connectors). 4. Click **+ Add**, then **Add custom connector**. 5. In **Name**, enter your server's name, for example "Work". 6. In **Remote MCP server URL**, paste the URL you copied. 7. Click **Continue**. 8. Keep the sign-in settings Claude detects and click **Continue** again. 9. Click **Add**. 10. Next to the new connector, click **Connect**. A window opens on Plugsight. 11. Sign in to Plugsight if asked, using the same account you created the server with. 12. Check the server shown is the one you want, then click **Allow access**. The window closes and the connector shows as connected. ## Connect Claude (Team and Enterprise plans) On Team and Enterprise, an Owner adds the connector for the organisation first. **If you're an Owner:** 1. In Claude, open **Organization settings** → **Connectors**. 2. Click **Add** → **Custom** → **Web**. 3. Enter a name and paste your MCP server's URL, keeping the recommended OAuth client. **Then each person:** 1. Go to [claude.ai/customize/connectors](https://claude.ai/customize/connectors). 2. Click **Connect** on the Plugsight connector. 3. In the Plugsight window, sign in, check the server name and click **Allow access**. > [!IMPORTANT] > An MCP server belongs to the Plugsight account that created it. Whoever clicks **Connect** must sign in to that Plugsight account. Anyone signed in to a different Plugsight account sees "This connector points at an MCP server that isn't in your account." ## Turn it on in a chat 1. Start a new chat. 2. Click **+** (bottom left of the message box), then **Connectors**. 3. Make sure your server is switched on. ## Try it Ask, for example: - "List my connected accounts." - "Find emails from my accountant this month and summarise them." - "Show my open Zendesk tickets." The first time Claude uses a Plugsight tool, it may ask your permission. Choose **Allow**, or **Always allow** for tools that only read. See [Approvals in your AI app](/ai-apps/approvals). ## Refresh after adding a new type of account Claude loads Plugsight's tools list when a chat starts. After you connect the first account of a new type (your first Zendesk, say): 1. Open [claude.ai/customize/connectors](https://claude.ai/customize/connectors) and click your server under **Your connectors**. 2. Click **⋯** (top right, next to **Disconnect**), then **Refresh tools list**. 3. Start a new chat. Chats already open keep the old list. Claude can take a few minutes to pick up the new list. More detail: [Refresh the tools list](/ai-apps/refresh-tools). ## Troubleshooting ### I can't find where to add a connector **What it means:** you're probably in the desktop or phone app, which can't add connectors. **How to fix it:** open [claude.ai/customize/connectors](https://claude.ai/customize/connectors) in a web browser. ### The sign-in window doesn't open, or closes with an error **What it means:** Claude couldn't open Plugsight's approval page, or couldn't finish signing in. **How to fix it:** allow pop-ups for claude.ai, make sure you're signed in to Plugsight in the same browser, then remove the connector in Claude and add it again. ### This connector points at an MCP server that isn't in your account. **What it means:** you're signed in to Plugsight with a different account from the one that created this server. **How to fix it:** on the approval screen, click **Switch account** and sign in with the right account. ### Claude answers without using my data **What it means:** the connector isn't switched on in this chat. **How to fix it:** click **+** → **Connectors** and switch your server on, then ask again, for example "Using Plugsight, list my connected accounts". ### The new account or actions don't show **What it means:** Claude still has the old tools list, or the account isn't in this MCP server. **How to fix it:** refresh the tools list (above) and start a new chat. If the server uses **Selected accounts**, tick the new account in **Edit configuration** on the server's page. ## Related articles - [Claude desktop app](/ai-apps/claude-desktop) - [Claude phone app](/ai-apps/claude-mobile) - [Claude Code](/ai-apps/claude-code) - [Disconnect an AI app](/ai-apps/disconnect) --- # Claude desktop app URL: https://docs.plugsight.app/ai-apps/claude-desktop Use your Plugsight connector in the Claude desktop app, after adding it once on claude.ai, and refresh its tools list there. The Claude desktop app can't add a custom connector. You add it once on the Claude website, and it then appears in the desktop app too. ## Set it up 1. Add Plugsight on the Claude website by following [Claude on the web](/ai-apps/claude). Make sure you click **Connect** and then **Allow access** on the Plugsight screen. 2. Open the Claude desktop app, signed in to the same Claude account. 3. Start a new chat. 4. Click **+** (bottom left of the message box), then **Connectors**, and make sure your server is switched on. 5. Ask, for example, "List my connected accounts." The first time Claude uses a Plugsight tool, it may ask your permission. Choose **Allow**, or **Always allow** for tools that only read. ## Refresh the tools list in the desktop app After you connect the first account of a new type (your first Zendesk, say), Claude needs to reload Plugsight's tools list: 1. In the desktop app, open **Settings** → **Customize**. 2. Click your server under **Your connectors**. 3. Click **⋯** (top right, next to **Disconnect**), then **Refresh tools list**. 4. Start a new chat. Chats already open keep the old list. Not there yet? Claude can take a few minutes to pick up the new list. Wait, refresh again, then open another new chat. See [Refresh the tools list](/ai-apps/refresh-tools). ## Troubleshooting ### There's no option to add a custom connector **What it means:** connectors can only be added on the Claude website. **How to fix it:** go to [claude.ai/customize/connectors](https://claude.ai/customize/connectors) in a web browser and add it there. It then shows in the desktop app. ### Plugsight isn't listed under Connectors in a chat **What it means:** the connector was added to a different Claude account, or it was added but never connected. **How to fix it:** check you're signed in to the same Claude account on the web and in the desktop app. On [claude.ai/customize/connectors](https://claude.ai/customize/connectors), make sure the connector shows as connected; if not, click **Connect** and then **Allow access**. ### Claude answers without using my data **What it means:** the connector is switched off in this chat. **How to fix it:** click **+** → **Connectors** and switch your server on. ## Related articles - [Claude on the web](/ai-apps/claude) - [Claude phone app](/ai-apps/claude-mobile) - [Refresh the tools list](/ai-apps/refresh-tools) --- # Claude phone app URL: https://docs.plugsight.app/ai-apps/claude-mobile Use your Plugsight connector in the Claude app on your phone, after adding it once on claude.ai, and fix it when it doesn't show. The Claude phone app can't add a custom connector. You add it once on the Claude website (claude.ai in a browser), and it then appears in the phone app too. ## Set it up 1. On a computer (or your phone's web browser), add Plugsight on the Claude website by following [Claude on the web](/ai-apps/claude). Make sure you click **Connect** and then **Allow access** on the Plugsight screen. 2. Open the Claude app on your phone, signed in to the same Claude account. 3. Start a new chat. 4. Tap **+**, then **Connectors**, and make sure your server is switched on. 5. Ask, for example, "What's on my calendar tomorrow?" ## Refresh the tools list After you connect the first account of a new type, refresh the tools list on the web or in the desktop app (see [Refresh the tools list](/ai-apps/refresh-tools)). The change reaches your phone too. Then start a new chat on your phone. ## Troubleshooting ### It works on my computer but not in the Claude phone app **What it means:** the phone app hasn't picked up the connector yet, or it's switched off in this chat. **How to fix it:** open a new chat on the phone and check the connector is switched on (**+** → **Connectors**). If you've only now refreshed the tools list, give it a minute. ### Plugsight isn't listed under Connectors **What it means:** the connector was added to a different Claude account, or it was never added on the website. **How to fix it:** check you're signed in to the same Claude account on the web and on your phone. Then add it on [claude.ai/customize/connectors](https://claude.ai/customize/connectors) if it isn't there. ## Related articles - [Claude on the web](/ai-apps/claude) - [Claude desktop app](/ai-apps/claude-desktop) - [Approvals in your AI app](/ai-apps/approvals) --- # Claude Code URL: https://docs.plugsight.app/ai-apps/claude-code Add your Plugsight MCP server to Claude Code in the terminal, with a browser sign-in or an API key, and check it's connected. Claude Code can use your Plugsight accounts from the terminal, alongside your files and scripts. You can connect it in two ways: sign in with your browser (recommended), or use an API key when no browser is available. ## What you need - Claude Code installed in your terminal (the `claude` command). - A Plugsight MCP server and its **Server URL**. On the server's page in Plugsight, the steps under **Connect an AI app** → **Claude Code** show the commands with your server's URL and name already filled in. In the commands below, replace `work` with your server's name in lowercase, with dashes instead of spaces (a server called "Acme (client)" becomes `acme-client`), and replace the URL with your **Server URL**. ## Option A: sign in with your browser (recommended) 1. Run this in your terminal: ``` claude mcp add --transport http work https://app.plugsight.app/mcp/YOUR_SERVER_ID ``` 2. Start Claude Code by running `claude`. 3. Type `/mcp`. 4. Choose your server (for example `work`), then **Authenticate**. 5. Your browser opens Plugsight. Sign in if asked, check the server name, then click **Allow access**. ## Option B: use an API key (no browser) Useful on servers and in scripts, where no browser can open. 1. In Plugsight, open your MCP server's page. 2. Under **API key**, click **Create API key** (or **Regenerate key** if the server already has one). 3. Copy the key straight away. It isn't shown again. 4. Run this in your terminal, replacing `YOUR_KEY` with the key: ``` claude mcp add --transport http work https://app.plugsight.app/mcp/YOUR_SERVER_ID --header "Authorization: Bearer YOUR_KEY" ``` > [!WARNING] > Keep the key private: anyone with it can use this MCP server's accounts. If it leaks, use **Regenerate key** (the old key stops working straight away) or **Revoke key** on the server's page. When you create a key, Plugsight also shows the full Claude Code command with the key filled in, ready to copy. ## Use it in every project To use the server in every project, add `--scope user` to the add command, before the name: ``` claude mcp add --transport http --scope user work https://app.plugsight.app/mcp/YOUR_SERVER_ID ``` ## Check it's connected 1. Run `claude mcp list`. 2. Your server (for example `work`) should show as connected. 3. Start `claude` and ask, for example, "List my connected accounts." The first time Claude Code uses a Plugsight tool, it may ask your permission. Choose **Allow**. See [Approvals in your AI app](/ai-apps/approvals). ## Refresh after adding a new type of account After you connect the first account of a new type (your first Zendesk, say): 1. In Claude Code, type `/mcp`. 2. Choose your server, then **Reconnect**. Or quit and start Claude Code again. See [Refresh the tools list](/ai-apps/refresh-tools). ## Troubleshooting ### The server doesn't show as connected in claude mcp list **What it means:** with Option A, you haven't finished signing in yet. With Option B, the key is wrong, was regenerated or was revoked. **How to fix it:** for Option A, type `/mcp` in Claude Code, choose the server and **Authenticate**, then click **Allow access** in the browser. For Option B, create a new key on the server's page and run the add command again with it. ### It stopped working after I regenerated or revoked the key **What it means:** regenerating or revoking a key stops the old key straight away. Anything using it is refused until you give it the new key. Apps that signed in with the browser aren't affected. **How to fix it:** create or copy the new key, then add the server again with the new key in the `--header` option. ### This connector points at an MCP server that isn't in your account. **What it means:** the browser is signed in to a different Plugsight account from the one that created the server. **How to fix it:** click **Switch account** on the approval screen and sign in with the right account. ## Related articles - [Cursor](/ai-apps/cursor) - [Other MCP apps](/ai-apps/other-apps) - [Disconnect an AI app](/ai-apps/disconnect) --- # ChatGPT URL: https://docs.plugsight.app/ai-apps/chatgpt Add your Plugsight MCP server to ChatGPT on chatgpt.com, which ChatGPT plans can use it, and what a workspace admin must allow. You add Plugsight to ChatGPT as a custom MCP server on chatgpt.com. You don't need Developer mode. ## Which ChatGPT plans work | ChatGPT plan | Can you use Plugsight? | |---|---| | Business, Enterprise, Edu | Yes. A workspace admin may need to allow **Create custom MCP servers** first. | | ChatGPT Pro | Yes, but read-only: your AI can read your accounts but can't send or change anything. | | Free | No. The free plan isn't eligible. | > [!NOTE] > "ChatGPT Pro" is OpenAI's plan, not Plugsight's Pro plan. The two are separate subscriptions. ## What you need - chatgpt.com in a web browser. The ChatGPT desktop and phone apps can't add a custom MCP server. - A Plugsight MCP server and its **Server URL**. If you don't have one, follow the [Quick start](/get-started/quick-start). ## Connect ChatGPT 1. In Plugsight, open **MCP servers** and click your server. 2. Under **Server URL**, click **Copy URL**. 3. On chatgpt.com in a web browser, open [chatgpt.com/plugins](https://chatgpt.com/plugins). 4. Click **Add** and choose **Create custom MCP server**. On some accounts it's called **Create MCP App**. 5. Fill in the form: - **Name:** your server's name, for example "Work". - **Description:** optional, for example "My email and helpdesk". - **Server URL:** paste the URL you copied. - **Authentication:** **OAuth**. 6. Review the warning and select **I understand and want to continue**. 7. Click **Create as a plugin**. 8. ChatGPT opens Plugsight. Sign in if asked, check the server shown is the one you want, then click **Allow access**. ## For workspace admins (Business, Enterprise, Edu) If people in your workspace don't see **Create custom MCP server**, an admin must allow **Create custom MCP servers** in the workspace settings. This setting used to be called Developer mode. ## Use it in a chat 1. Start a new chat. 2. Click **+** next to the message box. 3. Select your server. ChatGPT asks before each action that changes something, such as sending an email. Review it and confirm. See [Approvals in your AI app](/ai-apps/approvals). ## Try it - "List my connected accounts." - "Find emails from my accountant this month and summarise them." - "Show my open Zendesk tickets." ## Refresh after adding a new type of account After you connect the first account of a new type (your first Zendesk, say): 1. Open [chatgpt.com/settings/plugins-settings](https://chatgpt.com/settings/plugins-settings) (**Settings** → **Plugins**) and click your server. 2. Scroll down to **Manage app** and click **Refresh tools**. 3. If any new actions show as off, switch them on. 4. Start a new chat. On Business and Enterprise, a workspace admin may need to refresh the connector and publish the update before everyone gets it. See [Refresh the tools list](/ai-apps/refresh-tools). ## Troubleshooting ### I don't see Create custom MCP server **What it means:** on Business, Enterprise and Edu, your workspace admin hasn't allowed custom MCP servers. On the free plan, the option isn't available. **How to fix it:** ask your workspace admin to allow **Create custom MCP servers** in the workspace settings (formerly Developer mode). Check you're on chatgpt.com in a web browser, not the desktop or phone app. ### My AI can read but can't send or change anything **What it means:** on ChatGPT Pro, custom MCP servers are read-only. On other plans, a Plugsight setting may be stopping the change. **How to fix it:** on ChatGPT Pro, this can't be changed. On other plans, see [Approvals in your AI app](/ai-apps/approvals) for what a change needs. ### The sign-in window doesn't open, or closes with an error **What it means:** ChatGPT couldn't open Plugsight's approval page, or couldn't finish signing in. **How to fix it:** allow pop-ups for chatgpt.com, make sure you're signed in to Plugsight in the same browser, then remove the connector in ChatGPT and add it again. ### This connector points at an MCP server that isn't in your account. **What it means:** you're signed in to Plugsight with a different account from the one that created this server. **How to fix it:** click **Switch account** on the approval screen and sign in with the right account. ### ChatGPT answers without using my data **What it means:** the server isn't selected in this chat. **How to fix it:** click **+** next to the message box and select your server, then ask again, for example "Using Plugsight, show last week's Google Ads spend". ### The new actions still don't show after refreshing **What it means:** the new actions are switched off, the chat was already open, or (on Business and Enterprise) the update hasn't been published yet. **How to fix it:** in the server's settings, check any new actions are switched on, then start a new chat. On Business and Enterprise, ask your admin to refresh and publish the update. ## Related articles - [Connect AI apps](/ai-apps) - [Refresh the tools list](/ai-apps/refresh-tools) - [Disconnect an AI app](/ai-apps/disconnect) --- # Cursor URL: https://docs.plugsight.app/ai-apps/cursor Add your Plugsight MCP server to Cursor, with a browser sign-in or an API key, and reload it after adding a new type of account. Cursor can use your Plugsight accounts inside your editor, for example to build a dashboard or script from real numbers. ## What you need - Cursor. - A Plugsight MCP server and its **Server URL**. On the server's page in Plugsight, the steps under **Connect an AI app** → **Cursor & other MCP apps** show the settings with your server's URL and name already filled in. In the examples below, replace `work` with your server's name in lowercase, with dashes instead of spaces, and replace the URL with your **Server URL**. ## Connect Cursor 1. In Cursor, open **Customize** → **MCPs** → **Add New MCP Server**. Or edit the file `~/.cursor/mcp.json` (or `.cursor/mcp.json` in a project). 2. Add your server. With a browser sign-in, the URL is all it needs: ```json {"mcpServers": {"work": {"url": "https://app.plugsight.app/mcp/YOUR_SERVER_ID"}}} ``` 3. Save. If a browser window opens, sign in to Plugsight, check the server name and click **Allow access**. 4. Ask Cursor's agent to list your connected accounts. ## Connect with an API key instead Use this if the sign-in window doesn't work for you. 1. In Plugsight, open your MCP server's page. 2. Under **API key**, click **Create API key** and copy the key. It isn't shown again. 3. Use this configuration, replacing `YOUR_KEY` with the key: ```json {"mcpServers": {"work": {"url": "https://app.plugsight.app/mcp/YOUR_SERVER_ID", "headers": {"Authorization": "Bearer YOUR_KEY"}}}} ``` To keep the key out of the file, you can store it in an environment variable called `PLUGSIGHT_API_KEY` and use: ```json {"mcpServers": {"work": {"url": "https://app.plugsight.app/mcp/YOUR_SERVER_ID", "headers": {"Authorization": "Bearer ${env:PLUGSIGHT_API_KEY}"}}}} ``` > [!WARNING] > Anyone with the key can use this MCP server's accounts. Don't commit it to a shared repository. If it leaks, use **Regenerate key** or **Revoke key** on the server's page. ## Refresh after adding a new type of account After you connect the first account of a new type (your first Zendesk, say): 1. Open **Cursor Settings** → **Tools & MCP**. 2. Switch your server off and on again. 3. Still the old list? Run **Developer: Reload Window** from the command palette, or quit and reopen Cursor. See [Refresh the tools list](/ai-apps/refresh-tools). ## Troubleshooting ### No browser window opens **What it means:** Cursor didn't start the sign-in. **How to fix it:** connect with an API key instead (above). ### It stopped working after I regenerated or revoked the key **What it means:** the old key stopped working straight away. **How to fix it:** create a new key on the server's page and put it in your configuration. ### This connector points at an MCP server that isn't in your account. **What it means:** the browser is signed in to a different Plugsight account from the one that created the server. **How to fix it:** click **Switch account** on the approval screen and sign in with the right account. ## Related articles - [VS Code](/ai-apps/vs-code) - [Other MCP apps](/ai-apps/other-apps) - [Claude Code](/ai-apps/claude-code) --- # VS Code URL: https://docs.plugsight.app/ai-apps/vs-code Add your Plugsight MCP server to VS Code for Copilot agent mode, using an API key that VS Code stores securely. VS Code can use your Plugsight accounts in Copilot agent mode. You connect it with your MCP server's URL and an API key. ## What you need - VS Code with Copilot agent mode. - A Plugsight MCP server and its **Server URL**. - An API key for that server. ## Create an API key 1. In Plugsight, open **MCP servers** and click your server. 2. Under **API key**, click **Create API key**. 3. Copy the key straight away. It isn't shown again. > [!WARNING] > Anyone with the key can use this MCP server's accounts. If it leaks, use **Regenerate key** or **Revoke key** on the server's page. ## Connect VS Code 1. In your project, create or open the file `.vscode/mcp.json`. 2. Add this, replacing the URL with your **Server URL**: ```json {"inputs": [{"type": "promptString", "id": "plugsight-key", "description": "Plugsight API key", "password": true}], "servers": {"plugsight": {"type": "http", "url": "https://app.plugsight.app/mcp/YOUR_SERVER_ID", "headers": {"Authorization": "Bearer ${input:plugsight-key}"}}}} ``` 3. Save the file. VS Code asks for the key once and stores it securely. Paste the key you copied. 4. In Copilot agent mode, ask it to use the Plugsight tools, for example "List my connected Plugsight accounts." ## Refresh after adding a new type of account After you connect the first account of a new type (your first Zendesk, say), open VS Code's MCP settings and restart or reconnect the Plugsight server (or switch it off and on), then start a new chat. See [Refresh the tools list](/ai-apps/refresh-tools). ## Troubleshooting ### It stopped working after I regenerated or revoked the key **What it means:** the old key stopped working straight away. **How to fix it:** create a new key on the server's page, then give VS Code the new key in place of the stored one. ### The agent doesn't use my data **What it means:** the agent didn't pick a Plugsight tool for your question. **How to fix it:** ask it directly to use the Plugsight tools, for example "Using Plugsight, show last week's Google Ads spend". ## Related articles - [Cursor](/ai-apps/cursor) - [Other MCP apps](/ai-apps/other-apps) - [Claude Code](/ai-apps/claude-code) --- # Other MCP apps URL: https://docs.plugsight.app/ai-apps/other-apps Connect Plugsight to Windsurf, Gemini CLI or any other app that supports remote MCP servers over HTTP. Plugsight works with any app that supports remote MCP servers over HTTP, such as Windsurf and Gemini CLI. If your app isn't covered by its own article, use these steps. ## What you need - An app that supports remote MCP servers over HTTP. - A Plugsight MCP server and its **Server URL**. On the server's page in Plugsight, the steps under **Connect an AI app** → **Cursor & other MCP apps** show the settings with your server's URL and name already filled in. ## Connect the app 1. Find the app's MCP settings. Apps usually have an "MCP servers" or "Tools" section. 2. Add the server. - **If the app supports sign-in (OAuth)**, the URL is all it needs: ```json {"mcpServers": {"work": {"url": "https://app.plugsight.app/mcp/YOUR_SERVER_ID"}}} ``` - **If it only supports headers**, create an API key on the server's page (under **API key**, click **Create API key**) and use: ```json {"mcpServers": {"work": {"url": "https://app.plugsight.app/mcp/YOUR_SERVER_ID", "headers": {"Authorization": "Bearer YOUR_KEY"}}}} ``` 3. If a browser window opens, sign in to Plugsight and click **Allow access**. 4. Ask the AI to list your connected accounts. Replace `work` with your server's name in lowercase with dashes, the URL with your **Server URL**, and `YOUR_KEY` with your key. ## Gemini CLI Add this to `~/.gemini/settings.json`, replacing the URL and key: ```json {"mcpServers": {"plugsight": {"httpUrl": "https://app.plugsight.app/mcp/YOUR_SERVER_ID", "headers": {"Authorization": "Bearer YOUR_API_KEY"}}}} ``` Then reload Gemini CLI and ask it to use the Plugsight tools. ## Refresh after adding a new type of account Open the app's connector or MCP settings and refresh Plugsight (or switch it off and on, or reconnect or restart the server), then start a new chat. See [Refresh the tools list](/ai-apps/refresh-tools). ## Your own scripts and systems To pull Plugsight data into your own website, dashboard or system without an AI app, use the developer API (Pro and Agency plans). It's on each MCP server's page under **Developer API**. ## Related articles - [Cursor](/ai-apps/cursor) - [VS Code](/ai-apps/vs-code) - [Claude Code](/ai-apps/claude-code) --- # Refresh the tools list URL: https://docs.plugsight.app/ai-apps/refresh-tools When your AI app needs to reload Plugsight's tools after you add a new type of account, and the exact steps in each AI app. AI apps load Plugsight's list of tools (actions) once and keep it. Claude, for example, loads it when a chat starts. When the kinds of actions change, your AI app needs to reload that list before it can use them. ## When you need to refresh Refresh your AI app after you: - connect the **first account of a new type**, for example your first Zendesk or your first Google Analytics 4, or - remove the **last account** of a type. ## When you don't need to refresh You don't need to refresh after you: - add a second account of a type you already have, - rename an account, - turn changes on or off for an account, or tick or untick **Allow changes** on a server, - change the daily email limit, - hide sites, ad accounts, calendars or drives. These take effect straight away. ## The reminder in Plugsight When an AI app still has the old list, Plugsight shows a notice at the top of **Overview**, **Connections** and **MCP servers**, headed **Refresh [app] to use your changes**. It names each AI app that needs a refresh, with its steps, and the servers it applies to. The notice goes away by itself once the app has the new list. Plugsight checks every 20 seconds while the notice is showing, and again when you come back to the tab. Your AI may also tell you in the chat. When its list is out of date, Plugsight adds a note to its answers naming the new (or removed) tools and asking it to tell you to refresh and start a new chat. ## Claude (web and desktop) 1. Open [claude.ai/customize/connectors](https://claude.ai/customize/connectors). In the desktop app, open **Settings** → **Customize**. 2. Click your Plugsight server under **Your connectors**. 3. Click **⋯** (top right, next to **Disconnect**), then **Refresh tools list**. 4. Start a **new chat**. Chats already open keep the old list. Not there yet? Claude can take a few minutes to pick up the new list. Wait, refresh again, then open another new chat. **Claude phone app:** refresh on the web or in the desktop app. The change reaches your phone too. ## ChatGPT 1. Open [chatgpt.com/settings/plugins-settings](https://chatgpt.com/settings/plugins-settings) (**Settings** → **Plugins**) and click your Plugsight server. 2. Scroll down to **Manage app** and click **Refresh tools**. 3. If any new actions show as off, switch them on. 4. Start a **new chat**. On Business or Enterprise, a workspace admin may need to refresh the connector and publish the update first, before everyone gets it. ## Claude Code 1. Type `/mcp`. 2. Choose your Plugsight server, then **Reconnect**. Or quit and start Claude Code again. ## Cursor 1. Open **Cursor Settings** → **Tools & MCP**. 2. Switch your Plugsight server off and on again. 3. Still the old list? Run **Developer: Reload Window** from the command palette, or quit and reopen Cursor. ## VS Code and other apps 1. Open the app's connector or MCP settings and refresh Plugsight, or switch it off and on (some apps call this reconnecting or restarting the server). 2. Start a new chat. ## Developer API Nothing to do. `GET /v1/tools` always returns the current list. ## I can't find the refresh option Menus in AI apps move from time to time. If you can't find it: 1. Remove the Plugsight connector in your AI app. 2. Add it again with the same server URL. 3. Sign in and click **Allow access** once more. Your accounts stay connected in Plugsight; nothing is lost. ## I refreshed, but the new actions still don't show Work through these: 1. **Start a new chat.** Open chats keep the old list. 2. **In ChatGPT**, check any new actions are switched on. 3. **In Claude**, wait a few minutes and refresh again. 4. **Check you refreshed the right connector.** With more than one MCP server (say "Work" and "Clients"), the account must be in the server your AI app uses. 5. **Check the account is in that server.** Open **MCP servers** and look at **Account access**. With **Selected accounts**, accounts you connect later aren't added by themselves: tick the new one in **Edit configuration** and save, or choose **All accounts**. Ask your AI "list my Plugsight accounts" to see exactly what it can reach. ## I removed an account, but my AI still mentions it **What it means:** your AI app is using the list it loaded earlier. **How to fix it:** if that was the last account of its type, refresh your AI app as above. Until then, asking about it returns "unknown account", and nothing is read from it. ## Related articles - [Several accounts per service](/ai-apps/multiple-accounts) - [Claude on the web](/ai-apps/claude) - [ChatGPT](/ai-apps/chatgpt) --- # Several accounts per service URL: https://docs.plugsight.app/ai-apps/multiple-accounts Use several Gmail inboxes, Google Ads logins or helpdesks in one AI chat, and keep each client's accounts apart. Built-in connectors in AI apps often limit you to one account per service. Claude's built-in connectors link one account per app: one Gmail, one Google login. Other AI apps vary, and some allow a second account for a few apps. These limits change over time, so check your AI app for its current rules. Through Plugsight, your AI can use as many accounts as your plan allows (work and personal inboxes, every client's Google Ads, each brand's helpdesk) and search across all of them in one question. ## How it works 1. **Connect each account in Plugsight.** Sign in to each one separately: your second Gmail is another connection. One Google Ads or Analytics sign-in brings every account that login can see. 2. **Know their names.** Every connection has a short name, shown in code style on **Connections**, that you and your AI can use. Email accounts connected with an app password can also get a clearer name, such as "Work Gmail", in **Name this connection (optional)** when you connect them. 3. **Choose what each MCP server reaches.** One server can reach everything, or you can make one per client or team so each only sees its own accounts. 4. **Ask across them.** Your AI searches every account the server reaches, or only the one you name. You add **one** Plugsight MCP server to your AI app, and it brings all the accounts that server reaches. You don't need a separate connector in your AI app for each account. > [!TIP] > Claude's free plan allows one custom connector. One Plugsight MCP server with **All accounts** gives Claude every account you've connected through that single connector. ## What counts as one connection - **Each separate login is one connection.** A second Gmail inbox is its own connection, and so is a second Zendesk account. - **Google Ads, Analytics, Search Console and Microsoft Advertising** each bring every account the login can see, in one connection per service (so Search Console and GA4 on the same Google login are two connections). That includes Google Ads client accounts under a manager (MCC) account. - Your plan sets how many connections you can have: Free 2, Pro 10, Agency 50. See [Plans](/get-started/plans). ## Asking about one account Every result says which account it came from. When you have several accounts of one type, name the one you mean: - "In my work Gmail, find the latest invoice from Northwind." - "For Bright Dental's Google Ads, which search terms wasted money last month?" Or ask across all of them: - "What did I promise anyone by email this week, in any inbox?" - "Rank my clients by wasted ad spend last month." - "Compare refund requests across our UK and US helpdesks." ## Keep clients apart - **One MCP server per client.** Create a server that reaches only that client's accounts (choose **Selected accounts** and tick them). Add that server to the AI app you use for that client, or give it to the client. You can disconnect or delete one server without touching the others. - **Read-only servers.** Untick **Allow changes** on a server you share, so it can read and draft but never send or change anything. - **Hide individual items.** On **Connections**, open a connection's **Sites & accounts** and switch off any site, property or ad account you don't want your AI to see. Hidden items are never used, even if the AI asks for them by name. - **Different permissions per account.** Let your AI send from your work inbox while your personal one stays **Drafts only**. Every change still needs your approval in the chat. How many MCP servers you can have depends on your plan: Free 1, Pro 5, Agency unlimited. ## Several MCP servers in one AI app You can add more than one Plugsight MCP server to the same AI app if the app allows several connectors, for example "Work" and "Clients". Each appears under its own name. When you ask about an account, make sure it's in the server that's switched on in your chat. ## Troubleshooting ### My AI uses the wrong account, or asks which one **What it means:** you have several accounts of one type and the question didn't say which. **How to fix it:** name the account in your question, for example "in my work Gmail". The short name shown on **Connections** works too. To keep a client's data out of a chat entirely, give them their own MCP server with only their accounts. ### I connected a new account but my AI can't see it **What it means:** the account isn't in the MCP server your AI app uses, or your AI app needs to reload its tools. **How to fix it:** 1. Open **MCP servers** and look at **Account access**. With **Selected accounts**, accounts you connect later aren't added by themselves: tick the new one in **Edit configuration** and save, or choose **All accounts**. 2. If it's the first account of a new type, [refresh the tools list](/ai-apps/refresh-tools) in your AI app. Ask your AI "list my Plugsight accounts" to see exactly what it can reach. ### The AI says an account is unknown **What it means:** that account isn't included in this MCP server. **How to fix it:** on the server's page, use **Edit configuration**: choose **All accounts**, or tick the account. ## Related articles - [Refresh the tools list](/ai-apps/refresh-tools) - [Plans](/get-started/plans) - [Questions to try first](/get-started/first-questions) - [Switch AI apps](/guides/switch-ai-apps) --- # Approvals in your AI app URL: https://docs.plugsight.app/ai-apps/approvals How your AI asks before it sends an email, updates a ticket or books a meeting, what you see in each AI app, and what a change needs. Your AI can read your accounts and write email drafts without asking you each time. Before it **sends or changes** anything, it must show you exactly what it will do and wait for your yes in the chat. ## Two kinds of prompt You may see two different prompts. They do different jobs. ### 1. The AI app's own permission prompt Most AI apps ask your permission the first time the AI uses a tool from a connector. - **Claude** (web, desktop, phone and Claude Code): the first time the AI uses a Plugsight tool, it may ask your permission. Choose **Allow**. For tools that only read, you can choose **Always allow**. - **ChatGPT**: ChatGPT asks before each action that changes something. Review it and confirm. - **Cursor, VS Code and other apps**: each app has its own way of asking; follow what it shows. > [!TIP] > Use **Always allow** only for tools that read. For tools that send or change things, keep the prompt so you see each one. ### 2. Plugsight's approval in the chat On top of what the AI app asks, Plugsight requires the AI to get your explicit yes for each change. The AI must show you the details first: | Change | What the AI must show you first | |---|---| | Send an email (new, reply or forward) | The From account, To, Cc, Bcc, subject, full body and attachment names | | Reply to or add a note on a Zendesk ticket | The exact text and the ticket | | Update a Zendesk ticket (status, priority, tags, assignee) | The exact changes | | Apply a Zendesk macro | A preview of what the macro will change | | Create a Zendesk ticket | The exact ticket details | | Book or change a calendar event | The exact event details or changes | | Cancel a calendar event | Which event will be cancelled | If the AI tries to make the change without your approval, Plugsight refuses it and tells the AI to show you the details first. **Archiving, labelling and marking emails** work a little differently, because they can be undone. For a handful of emails you asked about, the AI does it and tells you what changed. Before moving emails to the trash, or changing more than 10 emails at once, it says what will happen and asks first. **Drafts** never need approval: they're saved in your Drafts folder and never sent. ## What a change needs Your yes in the chat is the last step. Before that, every one of these must be true: 1. **Your plan includes changes.** Changes are on the Pro and Agency plans. See [Plans](/get-started/plans). 2. **The account's switch is on.** On **Connections**, the switch under **Write access** shows **Can send**, **Can reply & update** or **Can book & change**. 3. **The MCP server allows changes.** **Allow changes** is ticked in the server's **Edit configuration**. 4. **Nothing is paused** on **Permissions**. 5. **For email, the daily limit isn't reached.** 20 emails per account in a rolling 24 hours by default, adjustable from 1 to 500 under **Permissions** → **Daily email limit**. Archiving, labelling and marking emails don't need the account's switch; only the plan and the pause apply. Which changes are possible at all: sending email, Zendesk replies and updates, and booking or changing events in Outlook Calendar and iCloud Calendar. Marketing and analytics, contacts, files, stores and email marketing are always read-only. Google Calendar shows your events and free time, but can't book. The line under each account's switch on **Connections** says **Ready** when changes can go through, or names the one thing still stopping them. ## When the AI says it can't make a change The AI's message includes Plugsight's reason. Fixing it works straight away, with no refresh needed. Every attempt, including blocked ones, shows in **Activity**. ### Sending email and changing helpdesk tickets are on the Pro plan. **What it means:** your plan doesn't include changes. **How to fix it:** upgrade to Pro or Agency on the **Billing** page. Until then, ask the AI to save a draft. ### Sending is off for "[account]". Turn it on under Connections, or save it as a draft. **What it means:** the email account's switch is off (**Drafts only**). **How to fix it:** on **Connections**, switch on **Write access** for that account. ### Changes are off for "[account]". Allow them under Connections first. **What it means:** the helpdesk or calendar account's switch is off. **How to fix it:** on **Connections**, switch on **Write access** for that account. ### The "[server]" MCP is set to drafts only. Save it as a draft instead. **What it means:** the MCP server your AI app uses has **Allow changes** unticked. **How to fix it:** on the server's page, open **Edit configuration**, tick **Allow changes** and click **Save changes**. ### The "[server]" MCP is read-only. Allow changes on the MCP server first (MCP servers page). **What it means:** the same as above, for a helpdesk or calendar change. **How to fix it:** tick **Allow changes** in the server's **Edit configuration**. ### All write actions are paused for this account (Permissions page). **What it means:** **Pause everything** is on. **How to fix it:** click **Resume all** on **Permissions**, or on the red notice at the top of any page. ### Email sending is paused (Permissions page). **What it means:** email changes are paused on **Permissions**. The same message names helpdesk ("Helpdesk replies and updates are paused") or calendar ("Calendar changes are paused") when those are paused. **How to fix it:** click **Resume** for that type on **Permissions**. ### Daily limit reached The full message reads: Daily limit reached: "[account]" sent [number] emails in the last 24 hours (limit [number], which you can change on the Permissions page). Save it as a draft instead. **What it means:** this email account has sent its daily limit in the last 24 hours. **How to fix it:** wait until the next send frees up (**Permissions** → **Daily email limit** shows exactly when), or raise the limit there. Drafts never count. ### Not sent: show the user the final email and set confirm: true only after they explicitly approve. **What it means:** the AI tried to send before you approved. Plugsight refused it. Similar messages start "Not posted", "Not updated", "Not applied", "Not created", "Not booked", "Not changed" or "Not cancelled". **How to fix it:** nothing is wrong. The AI should now show you the details. Read them and reply yes if you want it to go ahead. ## ChatGPT Pro is read-only On ChatGPT Pro (OpenAI's plan), custom MCP servers connect with read-only access, so the AI can't send or change anything there, whatever your Plugsight settings say. See [ChatGPT](/ai-apps/chatgpt). ## Related articles - [How Plugsight works](/get-started/how-it-works) - [Glossary](/get-started/glossary) - [Disconnect an AI app](/ai-apps/disconnect) --- # Disconnect an AI app URL: https://docs.plugsight.app/ai-apps/disconnect Remove Plugsight from one AI app, cut off every AI app at once with Disconnect all AI apps, or revoke an API key or delete a server. There are several ways to stop an AI app using your Plugsight accounts. Pick the one that matches what you want. | You want to | Do this | Where | |---|---|---| | Stop using Plugsight in one AI app | Remove or disconnect the connector | In the AI app | | Cut off every AI app using one MCP server, now | **Disconnect all AI apps** | The server's page in Plugsight | | Stop Claude Code or a script that uses a key | **Revoke key** | The server's page, under **API key** | | Stop the server's link working anywhere, for good | **Delete server** | The server's page, under **Danger zone** | | Keep AI apps connected but stop all changes | **Pause everything** | **Permissions** in Plugsight | ## Remove the connector in your AI app This stops that one AI app using Plugsight. Your accounts and MCP servers in Plugsight aren't touched. - **Claude:** open [claude.ai/customize/connectors](https://claude.ai/customize/connectors) (desktop app: **Settings** → **Customize**), click your Plugsight server under **Your connectors**, then click **Disconnect** (top right). - **ChatGPT, Cursor, VS Code and other apps:** open the app's connector or MCP settings and remove the Plugsight server there. To use it again later, add the connector again with the same server URL, sign in and click **Allow access**. Nothing in Plugsight is lost. > [!NOTE] > Removing the connector happens in the AI app. To be certain no AI app can still use a server, for example after a lost device, use **Disconnect all AI apps** in Plugsight as well. ## Disconnect all AI apps This cuts off every AI app using one MCP server (Claude, ChatGPT and others) straight away. 1. In Plugsight, open **MCP servers** and click the server. 2. Scroll to **Danger zone**. 3. Click **Disconnect all AI apps**. 4. In the box that opens, click **Disconnect all**. Plugsight shows "Every AI app was disconnected from this server." **When to use it:** a device was lost, someone else had access, or you want a clean start. **What stays:** the server, its link, its accounts and settings all stay. Each AI app can come back by clicking **Allow access** again: the next time it's used, it asks you to sign in to Plugsight. > [!WARNING] > An API key, if the server has one, keeps working after **Disconnect all AI apps**. Revoke it separately (below). The **AI apps connected** number in the server's **Details** shows how many AI apps have clicked **Allow access** for this server and can use it now. ## Revoke or replace an API key For Claude Code, Cursor, VS Code or scripts that use an API key: 1. On the server's page, go to **API key**. 2. Click **Revoke key**, then confirm with **Revoke key**. The key stops working straight away, and the server has no key until you create a new one. Or click **Regenerate key**, then **Replace key**, to get a new key. The current one stops working straight away, and anything using it is refused until you paste in the new key. Claude, ChatGPT and other apps that signed in with the browser aren't affected by either. ## Delete the MCP server 1. On the server's page, scroll to **Danger zone**. 2. Click **Delete server**, then confirm with **Delete server**. This can't be undone. The server's link stops working in every AI app, and its API key, if any, is deleted. Your connected accounts aren't touched, and other MCP servers keep working. To use Plugsight again in those AI apps, create a new server and add it to them. ## Stop changes without disconnecting If you only want to stop your AI sending or changing things, you don't need to disconnect. On **Permissions**, click **Pause everything**. Your AI can still read and write drafts; click **Resume all** to undo it. To make one server read-only for good, untick **Allow changes** in its **Edit configuration**. ## Remove an account instead To stop AI apps reaching one account (one inbox, say) without disconnecting anything else, take it out of the server: in the server's **Edit configuration**, choose **Selected accounts** and untick it. Do this on every server that includes it. Or remove the connection on **Connections**, which takes it out of every server. ## Troubleshooting ### My AI asks me to sign in to Plugsight again **What it means:** its access ended, usually because the server was deleted, its access was revoked, or you used **Disconnect all AI apps**. **How to fix it:** click the sign-in prompt in the AI app, sign in to the same Plugsight account you set things up with, check the server name and click **Allow access**. ## Related articles - [Connect AI apps](/ai-apps) - [Approvals in your AI app](/ai-apps/approvals) - [Glossary](/get-started/glossary) --- # Connectors URL: https://docs.plugsight.app/connectors Every service you can connect to Plugsight, grouped by type, with what your AI can do, which plan you need and what it can change. A connector is a service you can connect to Plugsight, such as Gmail, Google Ads or WooCommerce. Each account you connect becomes a **connection** on the **Connections** page. Your AI can use a connection once it's part of an MCP server. To add one, open **Connections** and click **Add connection**, or open the **Connector catalog**. You can search the catalog and filter it by type. ## How to read this page - **Plan**: marketing and analytics connectors are for regular use on **Pro** and **Agency**; Free can try them within its allowance of 1 marketing connection and 25 marketing tool calls a month. Custom APIs and custom MCP servers need **Pro** or **Agency**. Everything else works on every plan, within your plan's number of connections. See [Plans](/get-started/plans). - **Changes**: most connectors only read. Email, Zendesk, Outlook and iCloud calendars, Custom APIs and custom MCP servers can make changes, but only when you switch changes on for that account, and each change waits for your approval in the chat. See [Read-only connectors](/permissions/read-only-connectors). - **Coming soon**: some Google connectors are waiting for Google to approve their permissions. Until then they aren't listed in the catalog. ## Email Search, read, draft and send email. Sending is off until you switch it on, and each email needs your approval. See [What your AI can do with email](/connectors/email-tools) and [Sending, drafts and the daily email limit](/connectors/email-safety). | Connector | How you connect | Plan | Changes | | --- | --- | --- | --- | | [Outlook / Microsoft 365](/connectors/outlook) | Sign in with Microsoft | All plans | Send, archive, label, with approval | | [Gmail / Google Workspace](/connectors/gmail) | A Google app password | All plans | Send, archive, label, with approval | | [Gmail (sign in with Google)](/connectors/gmail-google-sign-in) | Sign in with Google (beta, limited users) | All plans | Send, archive, label, with approval | | [iCloud Mail](/connectors/icloud-mail) | An Apple app-specific password | All plans | Send, move, mark, with approval | | [Yahoo Mail](/connectors/yahoo-mail) | An app password | All plans | Send, move, mark, with approval | | [AOL Mail](/connectors/aol-mail) | An app password | All plans | Send, move, mark, with approval | | [Zoho Mail](/connectors/zoho-mail) | An app password | All plans | Send, move, mark, with approval | | [Fastmail](/connectors/fastmail) | An app password | All plans | Send, move, mark, with approval | | [Yandex Mail](/connectors/yandex-mail) | An app password | All plans | Send, move, mark, with approval | | [Other IMAP server](/connectors/other-imap) | Your IMAP and SMTP details | All plans | Send, move, mark, with approval | More mailbox providers: - [Connect any email address](/connectors/connect-any-email): type your address and Plugsight finds the right way to connect. - [Email hosting and business email](/connectors/email-hosting-providers) - [Mail.com, GMX and Proton Mail](/connectors/email-providers-global) - [European email providers](/connectors/email-providers-europe) - [Email providers in the Americas](/connectors/email-providers-americas) - [Asia-Pacific email providers](/connectors/email-providers-asia-pacific) ## Helpdesk & support Tickets, replies and internal notes. | Connector | How you connect | Plan | Changes | | --- | --- | --- | --- | | [Zendesk](/connectors/zendesk) | Sign in with Zendesk | All plans | Replies, notes, new tickets, updates and macros, with approval | Already using an API token? See [Connect Zendesk with an API token](/connectors/zendesk-api-token). ## Marketing & analytics Search, analytics and ad performance for deep-dive analysis. All read-only. See [How your AI analyses marketing data](/connectors/marketing-data) and [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). | Connector | How you connect | Plan | Availability | | --- | --- | --- | --- | | [Google Search Console](/connectors/google-search-console) | Sign in with Google | Pro | Everyone | | [Google Analytics 4](/connectors/google-analytics-4) | Sign in with Google | Pro | Everyone | | [Google Ads](/connectors/google-ads) | Sign in with Google | Pro | Everyone | | [Microsoft Advertising (Bing Ads)](/connectors/microsoft-advertising) | Sign in with Microsoft | Pro | Everyone | | [Meta Ads (Facebook & Instagram)](/connectors/meta-ads) | Sign in with Facebook | Pro | Everyone | | [LinkedIn Ads (Campaign Manager)](/connectors/linkedin-ads) | Sign in with LinkedIn | Pro | Everyone | | [TikTok Ads](/connectors/tiktok-ads) | Sign in with TikTok for Business | Pro | Coming soon: TikTok is reviewing it | | [Bing Webmaster Tools](/connectors/bing-webmaster) | Paste an API key | Pro | Everyone | | [Google Tag Manager](/connectors/google-tag-manager) | Sign in with Google | Pro | Coming soon: Google is reviewing it | | [YouTube Analytics](/connectors/youtube) | Sign in with Google | Pro | Coming soon: Google is reviewing it | | [Google Merchant Center](/connectors/google-merchant-center) | Sign in with Google | Pro | Coming soon: Google is reviewing it | Every MCP server also has a [PageSpeed Insights](/connectors/pagespeed-insights) check for any public web page. It needs no connection and works on every plan. ## Email marketing Newsletters, audiences and campaign results. Read-only. | Connector | How you connect | Plan | | --- | --- | --- | | [Mailchimp](/connectors/mailchimp) | Paste an API key | All plans | ## E-commerce Orders, sales, products and customers from your online store. Read-only. | Connector | How you connect | Plan | | --- | --- | --- | | [WooCommerce](/connectors/woocommerce) | Approve Plugsight in your WordPress admin, or paste REST API keys | All plans | | [Magento / Adobe Commerce](/connectors/magento) | Add an integration in your Magento admin and paste its four keys | All plans | | [Shopify](/connectors/shopify) | Create an app in Shopify's Dev Dashboard and paste its client ID and secret, one connection per store | All plans | ## Docs & files Documents, spreadsheets, forms and meeting transcripts. Read-only. | Connector | How you connect | Plan | Availability | | --- | --- | --- | --- | | [Google Drive](/connectors/google-drive) | Sign in with Google | All plans | Coming soon: waiting for Google's security audit | | [Google Sheets](/connectors/google-sheets) | Sign in with Google | All plans | Coming soon: Google is reviewing it | | [Google Docs](/connectors/google-docs) | Sign in with Google | All plans | Coming soon: Google is reviewing it | | [Google Forms](/connectors/google-forms) | Sign in with Google | All plans | Coming soon: Google is reviewing it | | [Google Meet](/connectors/google-meet) | Sign in with Google | All plans | Coming soon: Google is reviewing it | ## Calendar Events, availability and booking. See [What your AI can do with calendars](/connectors/calendar-tools) for every action. | Connector | How you connect | Plan | Changes | | --- | --- | --- | --- | | [Google Calendar](/connectors/google-calendar) | Sign in with Google | All plans | Read-only for now | | [Outlook Calendar / Microsoft 365](/connectors/outlook-calendar) | Sign in with Microsoft | All plans | Book, move and cancel events, with approval | | [iCloud Calendar](/connectors/icloud-calendar) | Apple ID and an app-specific password | All plans | Book, move and cancel events, with approval | ## Contacts Address books and directories. Read-only. | Connector | How you connect | Plan | | --- | --- | --- | | [Google Contacts](/connectors/google-contacts) | Sign in with Google | All plans | | [Outlook Contacts / Microsoft 365](/connectors/outlook-contacts) | Sign in with Microsoft | All plans | | [iCloud Contacts](/connectors/icloud-contacts) | Apple ID and an app-specific password | All plans | ## Custom APIs and MCP servers Any REST API or remote MCP server you connect yourself, with its endpoints or tools as AI tools. See [Custom API](/connectors/custom-api) and [Custom MCP server](/connectors/custom-mcp). | Connector | How you connect | Plan | Changes | | --- | --- | --- | --- | | [Custom API](/connectors/custom-api) | Its https address and an API key, token, password or OAuth client; optionally an OpenAPI spec | Pro | `POST`, `PUT`, `PATCH` and `DELETE` requests, with approval | | [Custom MCP server](/connectors/custom-mcp) | Its https address, and a sign-in with the server (OAuth), a token or headers | Pro | Tools the server doesn't mark read-only, with approval | ## What the catalog labels mean - **Pro** with **On Pro: upgrade to connect**: the connector needs the Pro plan. Clicking it opens **Billing**. - **Unavailable**: the connector isn't set up on this Plugsight server yet. Tapping it says why. - **Connected** or **2 connected**: you already have this connector. Click **Add another account** to connect one more. - **New** or **Beta**: a recently added connector, or one with limits while the provider reviews it. ## After you connect 1. Add the connection to an MCP server, or use a server set to **All accounts**. See [Edit an MCP server](/mcp-servers/edit). 2. If it's the first connection of a new type (your first Zendesk or Google Analytics, say), [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. If your AI still can't see it, see [Your AI can't see an account](/troubleshooting/ai-cant-see-account). --- # Connect any email address URL: https://docs.plugsight.app/connectors/connect-any-email Type your email address and Plugsight works out your provider and the right way to connect it, or pick it from the list. Plugsight connects almost any mailbox. You don't need to know your provider's server settings: type your address and Plugsight finds them. ## Find your provider from your address 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. Only the team's Owner and Admins see this button. If you don't, ask one of them to add the connection. 2. In the **Connector catalog**, type your email address in the box that says **Or type an email address to detect its provider**. 3. Click **Detect**. Plugsight checks your address and sends you to the right page: | What Plugsight finds | Where you go | | --- | --- | | An Outlook.com, Hotmail, Live or MSN address, or a company domain whose mail is with Microsoft 365 | Straight to Microsoft's sign-in page. See [Outlook / Microsoft 365](/connectors/outlook). | | A Gmail address, or a company domain whose mail is with Google Workspace | The Gmail app password page. See [Gmail](/connectors/gmail). | | A provider Plugsight knows (iCloud, Yahoo, AOL, Zoho, Fastmail and about 60 others) | That provider's connect page, with the server settings filled in. The page says **Detected** and the provider's name. | | A provider listed in Thunderbird's public provider database | The **Connect an IMAP account** page, with the server settings filled in. It says **Detected Thunderbird's provider database. We filled in the server settings; check them and add your password.** | | Nothing | The **Connect an IMAP account** page, with the message **We couldn't detect this provider's settings. Enter its IMAP (and SMTP) details below.** See [Other IMAP server](/connectors/other-imap). | Plugsight looks at your domain's mail servers too, so a company address hosted by GoDaddy, Rackspace, Titan, Hostinger, Namecheap, Fastmail, iCloud, mailbox.org, IONOS, Yandex or Zoho is recognised even though the address itself is your own domain. ## Pick your provider from the list instead 1. Click **Add connection**. 2. Click **Email** in the list of types, or search for your provider's name or domain in **Search connectors, providers or domains…**. 3. Click your provider's tile. The email list starts with sign-in providers (Outlook), then Gmail, then every other provider, then **Other IMAP server** for anything not listed. ## Which method your account uses - **Outlook and Microsoft 365**: you sign in with Microsoft and click to allow access. No password to copy. - **Gmail, iCloud, Yahoo, AOL, Zoho, Fastmail, Yandex and most others**: you create an *app password* at your provider and paste it into Plugsight. The connect page links straight to where you make one. - **Smaller and regional providers**: some use your normal email password, some a special code. The connect page says which. - **Anything else**: enter the server settings yourself on [Other IMAP server](/connectors/other-imap). > [!NOTE] > An app password is a separate password your provider creates only for Plugsight. Your normal password stays private, and you can delete the app password at your provider at any time to cut off access. ## What happens when you click Test connection & save Plugsight signs in to your mailbox to check the password works, and only saves anything if it does. You then see a message such as `Connected you@example.com (14 folders) as "you-example-com"`. The part in quotes is the account's id: the name your AI uses for it. It's made from the connection's name, which is your email address unless you type another one under **Name this connection (optional)**. If you connect the same address again, for example with a new app password, Plugsight updates the existing connection instead of adding a second one, and says **Reconnected**. ## Troubleshooting ### We couldn't work out your provider automatically. Pick it from the list, or enter its server settings yourself. **What it means:** the address lookup failed, for example because the domain doesn't exist or didn't answer in time. **How to fix it:** check the address for typos. Then click **Pick your provider** to choose it from the list, or **Enter server settings** to fill them in on [Other IMAP server](/connectors/other-imap). ### The wrong provider was detected **What it means:** your domain's mail may be handled by a different company than you expect, for example a company address that moved to Microsoft 365. **How to fix it:** if your mail is in Outlook or Microsoft 365, use [Outlook](/connectors/outlook), even if you also have a Google account on that address. Otherwise click **Different provider?** at the bottom of the connect form and pick the right one. ## Related articles - [What your AI can do with email](/connectors/email-tools) - [Sending, drafts and the daily email limit](/connectors/email-safety) - [Gmail](/connectors/gmail) - [Outlook / Microsoft 365](/connectors/outlook) - [Other IMAP server](/connectors/other-imap) - [Fastmail](/connectors/fastmail) --- # Gmail and Google Workspace URL: https://docs.plugsight.app/connectors/gmail Connect Gmail or a Google Workspace mailbox with a Google app password, step by step, including 2-Step Verification and fixes when Google blocks it. Connect your Gmail or Google Workspace (work or school) mailbox so your AI can search, read and draft your email, and send when you allow it. Gmail connects with a Google **app password**: a 16-letter password Google creates only for Plugsight. It takes about two minutes. ## What your AI can do - Search your whole mailbox live, including with Gmail search syntax such as `from:amazon newer_than:7d`. - Read full emails, conversations and attachments (PDF, Word, Excel and PowerPoint are read as text). - Save drafts, replies and forwards to your Gmail **Drafts**. - Send email, once you switch sending on and approve each email in the chat. - Archive, label, star and mark emails read or unread. Labels work on Gmail (and on Outlook, where they're categories); other mailboxes use folders instead. Try asking: - "Find every invoice we received from suppliers this quarter and list the totals." - "Summarise my unread email from customers today." - "Draft a reply to the latest email from Acme about the delayed order." - "Archive every newsletter in my inbox and label the receipts 'Expenses'." - "What did the contract PDF attached to Sarah's email say about payment terms?" See [What your AI can do with email](/connectors/email-tools) for every action in detail. ## What you need - A Gmail address, or a Google Workspace address whose mail is in Gmail. - **2-Step Verification** turned on for that Google account. Google only offers app passwords when it is on. - For a work or school account: your administrator must allow app passwords. ## Connect Gmail 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click the **Gmail / Google Workspace** tile. (Or type your address in the detect box: Gmail addresses go to this same page.) 3. Type your address in **Gmail address**. Do this first: the buttons in the next steps then open that exact Google account. 4. Follow the steps on the page, described below. 5. Paste the app password into **App password** and click **Test connection & save**. The page shows the server settings it uses (`imap.gmail.com:993` and `smtp.gmail.com:465`), so there's nothing to fill in. ### Step 1: Turn on 2-Step Verification (skip if it's already on) 1. Click **Open 2-Step Verification ↗**. Google's 2-Step Verification page opens in a new tab. 2. If you see a blue **Turn on 2-Step Verification** button, add your **Phone number** first. 3. Then click **Turn on 2-Step Verification**. ### Step 2: Create an app password 1. Click **Open App passwords ↗**. Google's App passwords page opens. 2. Type **Plugsight** as the name. 3. Click **Create**. Google shows a 16-letter password. ### Step 3: Copy it Google shows the password only once. Copy it before you close that tab. > [!WARNING] > If you close Google's tab before copying the password, you can't see it again. Create a new one the same way. ### Step 4: Paste it and click Test connection & save Paste the password into **App password** in Plugsight. Spaces are fine: Plugsight removes them. Plugsight signs in to check the password works before saving anything. Your normal Google password stays private. ## If you're signed in to several Google accounts Google opens its pages in whichever account your browser uses first, which may not be the one you're connecting. Plugsight's buttons add your address to the link (Google's `authuser` setting), so they open the account you typed in **Gmail address**. - If you haven't typed the address yet, the page says **Type your Gmail address above first, so these links open the right Google account.** - Once you have, it says the links open that address. Before creating the password, check that the photo at the top right of Google's page shows the right account. ## What it can and can't change New connections start on **Drafts only**: your AI can read and write drafts, but can't send. To let it send: 1. On **Connections**, click the account's switch so it says **Can send**. This needs the Pro or Agency plan. 2. Check the line under the switch says **Ready**. Every email still needs your yes in the chat before it goes. Archiving, labelling and marking emails don't need the switch, but do need a plan that includes changes. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Limits - Your AI can send up to 20 emails per account in any 24 hours by default (you can choose 1 to 500). Drafts don't count. - Gmail has its own limit of about 500 emails a day. Google Workspace allows more. - Attachments you send can total up to 20 MB per email. ## Troubleshooting ### Google says "The setting you are looking for is not available for your account" **What it means:** Google is hiding the App passwords page from this account. There are four possible reasons. **How to fix it:** check them in this order. 1. **2-Step Verification is off.** Turn it on (step 1 above), then open App passwords again. 2. **2-Step Verification uses only passkeys or security keys.** Add a phone number or an authenticator app on the 2-Step Verification page, then try again. 3. **It's a work or school account (Google Workspace).** Your administrator has turned app passwords off. Ask them to allow 2-Step Verification and app passwords in the Google Admin console. 4. **Advanced Protection is on.** Google doesn't allow app passwords on these accounts, so this account can't be connected with an app password. ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** Google refused the sign-in. Usually the password is your normal Google password, was mistyped, or the app password was deleted. **How to fix it:** create a new app password (step 2) and paste it. Check the address in **Gmail address** is the same account you created the password in. ### The App passwords page opened a different Google account **What it means:** your browser is signed in to several Google accounts. **How to fix it:** type your address in **Gmail address** before clicking **Open App passwords ↗**, and check the photo at the top right of Google's page. See [If you're signed in to several Google accounts](#if-youre-signed-in-to-several-google-accounts). ### The connection says it needs reconnecting: "The mail server rejected the password; it may have been changed or revoked." **What it means:** Google no longer accepts the app password, usually because it was deleted or your Google account's sign-in settings changed. Your AI can't use the account until you reconnect it. **How to fix it:** on **Connections**, click **Reconnect**. The Gmail page opens with your address filled in. Create a new app password and click **Test connection & save**. Your settings and MCP servers stay as they were. ### Labels are a Gmail feature. For this mailbox, move the email to a folder instead (move_to). **What it means:** your AI tried to add a label to a mailbox that isn't Gmail. You won't see this on a Gmail connection; it means the AI picked a different account. **How to fix it:** tell your AI which account to use, for example "in my work Gmail". ## Related articles - [Gmail with Google sign-in (beta)](/connectors/gmail-google-sign-in) - [What your AI can do with email](/connectors/email-tools) - [Sending, drafts and the daily email limit](/connectors/email-safety) - [Connect any email address](/connectors/connect-any-email) --- # Gmail with Google sign-in (beta) URL: https://docs.plugsight.app/connectors/gmail-google-sign-in Why Gmail connects with an app password today, and how the limited beta of Gmail with Google sign-in works when it's offered. Plugsight has a second way to connect Gmail: signing in with Google instead of creating an app password. It is a **beta**, and most people can't use it yet. For almost everyone, the way to connect Gmail is an app password: see [Gmail and Google Workspace](/connectors/gmail). ## What your AI can do The same as Gmail with an app password, whichever way you connect: - Search your whole mailbox live, read full emails, conversations and attachments. - Save drafts, replies and forwards to your Gmail **Drafts**. - Send email, once you switch sending on and approve each email in the chat. - Archive, label, star and mark emails read or unread. See [What your AI can do with email](/connectors/email-tools) for every action in detail. ## Why it's limited Reading and sending Gmail through Google sign-in needs a permission that Google classes as *restricted*. Google only lets an app offer it to everyone after a paid security audit. Until then, Google limits the app to a small number of users and shows an "unverified app" warning on its sign-in screen. So, today: - The **Gmail (sign in with Google)** tile appears in the **Connector catalog** only when Plugsight has the beta switched on. It carries a **Beta** badge and the note *Beta: Google shows an "unverified app" warning and allows a limited number of users.* - When it isn't offered, the tile isn't shown at all, and typing a Gmail or Google Workspace address in the detect box takes you to the app password page instead. If you don't see the tile, use [the app password method](/connectors/gmail). Your AI can do exactly the same things either way. ## Connect with Google sign-in If the **Gmail (sign in with Google)** tile is in your catalog: 1. Click the tile. The **Connect Gmail** page explains what Google will ask. 2. Click **Continue to Google**. 3. **Choose your Google account.** 4. If Google says **Google hasn't verified this app**, click **Advanced**, then **Go to Plugsight (unsafe)**. Google shows this while it reviews new apps; it doesn't mean anything is wrong. 5. **Tick the permission box.** Google asks: *"Read, compose, send, and permanently delete all your email from Gmail"*. Tick it, or the connection can't work. Plugsight only reads, and sends only when you allow it. 6. You're back in Plugsight, with a message such as `Connected you@gmail.com (14 folders).` Plugsight never sees your Google password. ## What it can and can't change The same as Gmail with an app password: your AI reads and drafts; sending is off until you switch the account to **Can send** on **Connections** (Pro or Agency plan) and approve each email in the chat. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Troubleshooting ### Gmail access wasn't granted. Tick the Gmail permission and try again. **What it means:** you left the Gmail permission box unticked on Google's screen. **How to fix it:** click the tile again, and tick the box this time. ### Google returned no refresh token. Remove the app's access in your Google account and try again. **What it means:** Google didn't give Plugsight lasting access, so the connection couldn't be saved. **How to fix it:** remove Plugsight's access in your Google account, then connect again. ### … is a Google account without a Gmail inbox. The full message continues: *If your email is in Outlook or Microsoft 365, connect it with Outlook instead; for other providers, use "Connect a mailbox".* **What it means:** you signed in with a Google account on a company address whose mail is somewhere else, often Microsoft 365. Plugsight doesn't keep the connection. **How to fix it:** connect the mailbox where your mail really is: [Outlook / Microsoft 365](/connectors/outlook), or [find your provider](/connectors/connect-any-email). ### You didn't allow access in Google. Click Connect again and allow it, ticking every permission box. **What it means:** access wasn't allowed on Google's screen. **How to fix it:** start again and allow access. ### The Google sign-in expired before it finished. Click Connect and sign in again. **What it means:** the sign-in took too long or was interrupted. **How to fix it:** start again from the tile. ## Related articles - [Gmail and Google Workspace (app password)](/connectors/gmail) - [What your AI can do with email](/connectors/email-tools) - [Connect any email address](/connectors/connect-any-email) --- # Outlook and Microsoft 365 email URL: https://docs.plugsight.app/connectors/outlook Connect Outlook.com, Hotmail, Live or a Microsoft 365 work mailbox by signing in with Microsoft, including when your admin must approve. Connect an Outlook mailbox so your AI can search, read and draft your email, and send when you allow it. You sign in with Microsoft: there's no password to copy. It works with Outlook.com, Hotmail, Live and MSN addresses, and with Microsoft 365 work or school accounts. ## What your AI can do - Search every folder live, including with Outlook search syntax such as `from:amazon AND received>=2026-01-01`. - Read full emails, conversations and attachments (PDF, Word, Excel and PowerPoint are read as text). - Save drafts, replies and forwards, with Outlook's own threading. - Send email, once you switch sending on and approve each email in the chat. - Archive, move, flag and mark emails read or unread, and add or remove Outlook **categories**. Try asking: - "Summarise everything the finance team sent me this week." - "Find the latest version of the proposal we sent to Contoso." - "Draft polite follow-ups to everyone who hasn't replied to my meeting request." - "List all emails with Excel attachments from the last 30 days." - "What are the open questions in my thread with legal about the NDA?" See [What your AI can do with email](/connectors/email-tools) for every action in detail. ## What you need - An Outlook.com, Hotmail, Live or MSN account, or a Microsoft 365 work or school account with a mailbox. - For some work accounts: your IT administrator's approval (see below). ## Connect Outlook 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click the **Outlook / Microsoft 365** tile. Microsoft's sign-in page opens straight away. (Typing an Outlook or Microsoft 365 address in the detect box goes to the same place, with your address filled in.) 3. Choose or sign in to your Microsoft account. 4. Microsoft asks you to allow Plugsight access to your mail. Allow it. 5. You're back on **Connections**, with a message such as `Connected you@outlook.com (12 folders).` Plugsight asks Microsoft for permission to read your mail, create drafts and send. It never sees your Microsoft password. The connection is named after the mailbox's address. > [!NOTE] > Outlook Calendar and Outlook Contacts are separate connections, each with only its own permission. Connecting your email doesn't give Plugsight your calendar. See [Outlook Calendar](/connectors/outlook-calendar) and [Outlook Contacts](/connectors/outlook-contacts). ## When your administrator must approve Many companies stop employees from allowing new apps on their Microsoft 365 account. Microsoft then shows that an administrator must approve, and Plugsight shows: > Your organisation needs an administrator to approve Plugsight in Microsoft. Ask your IT admin, or if you are the admin, sign in and consent on behalf of the organisation. - **If you're not the admin:** ask your IT administrator to approve Plugsight. Once they have, click the **Outlook / Microsoft 365** tile again. - **If you are the admin:** sign in, and on Microsoft's permission screen tick **Consent on behalf of your organisation**, then accept. ## What it can and can't change New connections start on **Drafts only**: your AI can read and write drafts, but can't send. To let it send, click the account's switch on **Connections** so it says **Can send** (Pro or Agency plan), and check the line under it says **Ready**. Every email still needs your yes in the chat. Archiving, moving, categories and read/unread don't need the switch, but do need a plan that includes changes. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Limits - Your AI can send up to 20 emails per account in any 24 hours by default (you can choose 1 to 500). Drafts don't count. - Each file you attach to an Outlook email can be up to 3 MB. All attachments together can be up to 20 MB. - Attachments that are links to OneDrive or SharePoint files can't be read: they aren't stored in the email. ## Troubleshooting ### Your organisation needs an administrator to approve Plugsight in Microsoft. **What it means:** your company only allows apps an administrator has approved. **How to fix it:** see [When your administrator must approve](#when-your-administrator-must-approve). ### You didn't allow access in Microsoft. Click Connect again and allow it, ticking every permission box. **What it means:** access wasn't allowed on Microsoft's permission screen. **How to fix it:** click the **Outlook / Microsoft 365** tile again and allow access. ### Microsoft didn't grant lasting access. Remove Plugsight at myapps.microsoft.com, then connect again. **What it means:** Microsoft let you sign in but didn't give Plugsight the ongoing access it needs. **How to fix it:** go to myapps.microsoft.com, remove Plugsight, then click the tile again. ### We couldn't read this account's email address. Sign in again, choosing an account that has an email address. **What it means:** the Microsoft account you chose has no mailbox address. **How to fix it:** connect again and pick the account that has your mailbox. ### The Microsoft sign-in expired before it finished. Click Connect and sign in again. **What it means:** the sign-in took too long or was interrupted. **How to fix it:** click the tile and sign in again. ### Your session changed during sign-in. Please try again. **What it means:** your Plugsight sign-in changed while Microsoft's page was open, for example you signed in with another Plugsight account in the same browser. **How to fix it:** check you're signed in to the right Plugsight account, then connect again. ### This Outlook account was connected read-only. Reconnect it in the app (Connections → Reconnect) to allow drafts and sending. **What it means:** this connection was made before Plugsight asked for permission to write drafts and send. On **Connections** it shows **Read-only**. **How to fix it:** click **Read-only** on the account, then **Reconnect Outlook**, and allow the extra permission when Microsoft asks. Nothing is lost; your settings stay. ### … is larger than 3 MB, which isn't supported for Outlook yet. **What it means:** your AI tried to attach a file over 3 MB to an Outlook email or draft. **How to fix it:** send a link to the file instead, or attach a smaller version. ### The connection says it needs reconnecting: "Microsoft rejected this connection's access." **What it means:** Microsoft stopped accepting the connection, for example because you removed Plugsight's access or changed your password. **How to fix it:** on **Connections**, click **Reconnect** and sign in again. ## Related articles - [What your AI can do with email](/connectors/email-tools) - [Sending, drafts and the daily email limit](/connectors/email-safety) - [Outlook Calendar](/connectors/outlook-calendar) - [Outlook Contacts](/connectors/outlook-contacts) --- # iCloud Mail URL: https://docs.plugsight.app/connectors/icloud-mail Connect your iCloud Mail (icloud.com, me.com or mac.com) with an app-specific password from your Apple account, in three steps. Connect your iCloud Mail so your AI can search, read and draft your email, and send when you allow it. Apple requires an **app-specific password**: a separate password you create in your Apple account only for Plugsight. ## What your AI can do - Search your mailbox live, with filters such as sender, date, unread and attachments. - Read full emails, conversations and attachments (PDF, Word, Excel and PowerPoint are read as text). - Save drafts, replies and forwards to your iCloud **Drafts**. - Send email, once you switch sending on and approve each email in the chat. - Move emails to folders, flag them and mark them read or unread. Try asking: - "Find the booking confirmation for my trip in March." - "Summarise the emails from my accountant this year." - "Draft a reply accepting the invitation from James." - "Which subscriptions sent me receipts last month?" See [What your AI can do with email](/connectors/email-tools) for every action in detail. ## What you need - An iCloud Mail address (`@icloud.com`, `@me.com` or `@mac.com`). - Two-factor authentication on your Apple ID. Apple only offers app-specific passwords when it is on. ## Connect iCloud Mail 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click the **iCloud Mail** tile. (Or type your iCloud address in the detect box.) 3. Under **Create an app password**, click **Open iCloud Mail in a new tab ↗**. Your Apple account page opens. 4. Go to **Sign-In and Security** → **App-Specific Passwords**, and create a password. 5. Copy it. Apple shows it once, so copy it before closing that tab. 6. Back in Plugsight, type your address in **Email address** and paste the password into **App-specific password**. Spaces are fine. 7. Click **Test connection & save**. Plugsight signs in to check the password works before saving anything. The server settings (`imap.mail.me.com:993` and `smtp.mail.me.com:587`) are filled in for you. > [!TIP] > If you also connect iCloud Calendar or iCloud Contacts, you can create another app-specific password or reuse this one. Your normal Apple password never works here, and stays private. ## What it can and can't change New connections start on **Drafts only**: your AI can read and write drafts, but can't send. To let it send, click the account's switch on **Connections** so it says **Can send** (Pro or Agency plan), and check the line under it says **Ready**. Every email still needs your yes in the chat. Labels are a Gmail feature, so on iCloud your AI organises email by moving it to folders instead. Moving and marking emails don't need the switch, but do need a plan that includes changes. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Limits - Your AI can send up to 20 emails per account in any 24 hours by default (you can choose 1 to 500). Drafts don't count. - Attachments you send can total up to 20 MB per email. ## Troubleshooting ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** Apple refused the sign-in. Usually the password is your normal Apple ID password, or the app-specific password was mistyped or revoked. **How to fix it:** create a new app-specific password and paste it. Check the address is your iCloud Mail address. ### The connection says it needs reconnecting: "The mail server rejected the password; it may have been changed or revoked." **What it means:** Apple no longer accepts the app-specific password, for example because you revoked it in your Apple account. **How to fix it:** on **Connections**, click **Reconnect**. The iCloud Mail page opens with your address filled in. Paste a new app-specific password and click **Test connection & save**. ### This mailbox has no Archive folder. Move it to a folder from list_folders instead (move_to: ""). **What it means:** your AI tried to archive email, but your mailbox has no folder marked as the archive. **How to fix it:** ask your AI to move the emails to a named folder, for example "move them to the Receipts folder". ## Related articles - [iCloud Calendar](/connectors/icloud-calendar) - [iCloud Contacts](/connectors/icloud-contacts) - [What your AI can do with email](/connectors/email-tools) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # Yahoo Mail URL: https://docs.plugsight.app/connectors/yahoo-mail Connect Yahoo Mail, including ymail, rocketmail, Rogers and country Yahoo addresses, with a Yahoo app password. Connect Yahoo Mail so your AI can search, read and draft your email, and send when you allow it. Yahoo needs an **app password**: a separate password Yahoo creates only for Plugsight. ## What your AI can do - Search your mailbox live, with filters such as sender, date, unread and attachments. - Read full emails, conversations and attachments (PDF, Word, Excel and PowerPoint are read as text). - Save drafts, replies and forwards to your Yahoo **Drafts**. - Send email, once you switch sending on and approve each email in the chat. - Move emails to folders, flag them and mark them read or unread. Try asking: - "Summarise the unread emails I got today." - "Find every order confirmation from last month and list what I bought." - "Draft a reply to the last message from the school." See [What your AI can do with email](/connectors/email-tools) for every action in detail. ## Which addresses this covers `yahoo.com`, `ymail.com`, `rocketmail.com`, `rogers.com`, and Yahoo's country addresses: `yahoo.co.uk`, `yahoo.fr`, `yahoo.de`, `yahoo.it`, `yahoo.es`, `yahoo.ca`, `yahoo.com.au`, `yahoo.co.in`, `yahoo.in`, `yahoo.com.br`, `yahoo.com.mx`, `yahoo.com.ar`, `yahoo.com.sg`, `yahoo.com.ph`, `yahoo.co.id`, `yahoo.com.hk`, `yahoo.com.tw`, `yahoo.ie`, `yahoo.gr`, `yahoo.se`, `yahoo.dk`, `yahoo.no`, `yahoo.pl` and `yahoo.ro`. Comcast.net and Cox.net mail that has moved to Yahoo also connects here. Yahoo! JAPAN Mail is a separate service: see [Asia-Pacific email providers](/connectors/email-providers-asia-pacific). ## Connect Yahoo Mail 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click the **Yahoo Mail** tile. (Or type your address in the detect box.) 3. Under **Create an app password**, click **Open Yahoo Mail in a new tab ↗**. Yahoo's account security page opens. 4. In your Yahoo account, go to **Account security** → **External connections** → **Create app password**, and create one. 5. Copy it. Yahoo shows it once, so copy it before closing that tab. 6. Back in Plugsight, type your address in **Email address** and paste the password into **App password**. Spaces are fine. 7. Click **Test connection & save**. Plugsight signs in to check the password works before saving anything. The server settings (`imap.mail.yahoo.com:993` and `smtp.mail.yahoo.com:465`) are filled in for you. ## What it can and can't change New connections start on **Drafts only**. To let your AI send, click the account's switch on **Connections** so it says **Can send** (Pro or Agency plan). Every email still needs your yes in the chat. Labels are a Gmail feature, so your AI organises Yahoo email by moving it to folders. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Limits - Your AI can send up to 20 emails per account in any 24 hours by default (you can choose 1 to 500). Drafts don't count. - Attachments you send can total up to 20 MB per email. ## Troubleshooting ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** Yahoo refused the sign-in. Usually the password is your normal Yahoo password, or the app password was mistyped. **How to fix it:** create a new app password in Yahoo and paste it. ### The connection says it needs reconnecting: "The mail server rejected the password; it may have been changed or revoked." **What it means:** Yahoo no longer accepts the app password. **How to fix it:** on **Connections**, click **Reconnect**, paste a new app password and click **Test connection & save**. ## Related articles - [AOL Mail](/connectors/aol-mail) - [Americas email providers](/connectors/email-providers-americas) (Comcast, Cox and others) - [What your AI can do with email](/connectors/email-tools) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # AOL Mail URL: https://docs.plugsight.app/connectors/aol-mail Connect AOL Mail, AIM and Verizon.net addresses with an AOL app password, so your AI can search, read and draft your email. Connect AOL Mail so your AI can search, read and draft your email, and send when you allow it. AOL needs an **app password**: a separate password AOL creates only for Plugsight. ## What your AI can do - Search your mailbox live, with filters such as sender, date, unread and attachments. - Read full emails, conversations and attachments (PDF, Word, Excel and PowerPoint are read as text). - Save drafts, replies and forwards to your AOL **Drafts**. - Send email, once you switch sending on and approve each email in the chat. - Move emails to folders, flag them and mark them read or unread. Try asking: - "What did my bank email me about this month?" - "Find the email with the plumber's quote and tell me the total." - "Draft a thank-you reply to my sister's last email." See [What your AI can do with email](/connectors/email-tools) for every action in detail. ## Which addresses this covers `aol.com`, `aim.com`, `verizon.net`, `aol.co.uk`, `aol.fr` and `aol.de`. Verizon.net addresses use AOL, so connect them here. ## Connect AOL Mail 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click the **AOL Mail** tile. (Or type your address in the detect box.) 3. Under **Create an app password**, click **Open AOL Mail in a new tab ↗**. AOL's account security page opens. 4. In your AOL account, go to **Account security** → **Generate app password**, and create one. 5. Copy it. AOL shows it once, so copy it before closing that tab. 6. Back in Plugsight, type your address in **Email address** and paste the password into **App password**. Spaces are fine. 7. Click **Test connection & save**. Plugsight signs in to check the password works before saving anything. The server settings (`imap.aol.com:993` and `smtp.aol.com:465`) are filled in for you. ## What it can and can't change New connections start on **Drafts only**. To let your AI send, click the account's switch on **Connections** so it says **Can send** (Pro or Agency plan). Every email still needs your yes in the chat. Labels are a Gmail feature, so your AI organises AOL email by moving it to folders. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Limits - Your AI can send up to 20 emails per account in any 24 hours by default (you can choose 1 to 500). Drafts don't count. - Attachments you send can total up to 20 MB per email. ## Troubleshooting ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** AOL refused the sign-in. Usually the password is your normal AOL password, or the app password was mistyped. **How to fix it:** generate a new app password in AOL and paste it. ### The connection says it needs reconnecting: "The mail server rejected the password; it may have been changed or revoked." **What it means:** AOL no longer accepts the app password. **How to fix it:** on **Connections**, click **Reconnect**, paste a new app password and click **Test connection & save**. ## Related articles - [Yahoo Mail](/connectors/yahoo-mail) - [What your AI can do with email](/connectors/email-tools) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # Zoho Mail URL: https://docs.plugsight.app/connectors/zoho-mail Connect Zoho Mail personal or organisation accounts in any data centre (US, EU, India, Australia, Japan): turn on IMAP, then add your password. Connect Zoho Mail so your AI can search, read and draft your email, and send when you allow it. Zoho has a separate entry for each of its data centres, and one for organisation (custom domain) accounts. ## What your AI can do - Search your mailbox live, with filters such as sender, date, unread and attachments. - Read full emails, conversations and attachments (PDF, Word, Excel and PowerPoint are read as text). - Save drafts, replies and forwards to your Zoho **Drafts**. - Send email, once you switch sending on and approve each email in the chat. - Move emails to folders, flag them and mark them read or unread. Try asking: - "Summarise this week's customer enquiries." - "Find the signed contract from Northwind and tell me the renewal date." - "Draft a reply to the last message from the supplier." See [What your AI can do with email](/connectors/email-tools) for every action in detail. ## What you need - **A paid Zoho Mail plan.** IMAP isn't available on Zoho's Forever Free plan. - **IMAP turned on** in Zoho Mail → **Settings** → **Mail Accounts**. - If you use two-factor login: an **app-specific password** from your Zoho account. ## Pick the right Zoho entry | Entry in Plugsight | For | IMAP server | SMTP server | | --- | --- | --- | --- | | **Zoho Mail** | `zoho.com` and `zohomail.com` addresses | `imap.zoho.com:993` | `smtp.zoho.com:465` | | **Zoho Mail (EU)** | `zoho.eu` and `zohomail.eu` addresses | `imap.zoho.eu:993` | `smtp.zoho.eu:465` | | **Zoho Mail (India)** | `zoho.in` and `zohomail.in` addresses | `imap.zoho.in:993` | `smtp.zoho.in:465` | | **Zoho Mail (Australia)** | accounts in Zoho's Australian data centre | `imap.zoho.com.au:993` | `smtp.zoho.com.au:465` | | **Zoho Mail (Japan)** | accounts in Zoho's Japanese data centre | `imap.zoho.jp:993` | `smtp.zoho.jp:465` | | **Zoho Mail (organisation)** | custom-domain accounts in the US data centre | `imappro.zoho.com:993` | `smtppro.zoho.com:465` | Organisation (custom domain) accounts: pick your data centre's entry. If you type a custom-domain address in the detect box, Plugsight checks your domain's mail servers and picks the matching Zoho entry for you. ## Connect Zoho Mail 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click your Zoho entry from the table above, or type your address in the detect box. 3. Turn on IMAP in Zoho Mail → **Settings** → **Mail Accounts**, if it isn't on already. 4. If you use two-factor login, create an app-specific password in your Zoho account. On the **Zoho Mail** entry, the **Open Zoho Mail in a new tab ↗** button opens that page. 5. Copy the password. 6. Back in Plugsight, type your address in **Email address** and paste the password. Without two-factor login, use your normal Zoho password. 7. Click **Test connection & save**. On the **Zoho Mail** entry the password box is called **App-specific password (if 2FA is on)**; on the other Zoho entries it's called **Password**. Either way, Plugsight signs in to check it works before saving anything. ## What it can and can't change New connections start on **Drafts only**. To let your AI send, click the account's switch on **Connections** so it says **Can send** (Pro or Agency plan). Every email still needs your yes in the chat. Labels are a Gmail feature, so your AI organises Zoho email by moving it to folders. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Limits - Your AI can send up to 20 emails per account in any 24 hours by default (you can choose 1 to 500). Drafts don't count. - Attachments you send can total up to 20 MB per email. ## Troubleshooting ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** Zoho refused the sign-in. **How to fix it:** check, in order: your plan is a paid Zoho Mail plan; IMAP is on in **Settings** → **Mail Accounts**; you're using an app-specific password if two-factor login is on; and you picked your data centre's entry. If you think you picked the wrong data centre, click **Different provider?** at the bottom of the form and choose the entry from the table above that matches your account. ### The connection says it needs reconnecting: "The mail server rejected the password; it may have been changed or revoked." **What it means:** Zoho no longer accepts the password. **How to fix it:** on **Connections**, click **Reconnect**, paste a new password and click **Test connection & save**. ## Related articles - [Email hosting and business email](/connectors/email-hosting-providers) - [Connect any email address](/connectors/connect-any-email) - [What your AI can do with email](/connectors/email-tools) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # Fastmail URL: https://docs.plugsight.app/connectors/fastmail Connect Fastmail, including custom domains hosted at Fastmail, with a Fastmail app password that keeps Mail access. Connect Fastmail so your AI can search, read and draft your email, and send when you allow it. Fastmail needs an **app password**: a separate password Fastmail creates only for Plugsight. ## What your AI can do - Search your mailbox live, with filters such as sender, date, unread and attachments. - Read full emails, conversations and attachments (PDF, Word, Excel and PowerPoint are read as text). - Save drafts, replies and forwards to your Fastmail **Drafts**. - Send email, once you switch sending on and approve each email in the chat. - Move emails to folders, flag them and mark them read or unread. Try asking: - "Which newsletters did I get this week, and what were the main stories?" - "Find the invoice from our hosting company and tell me when it's due." - "Draft a reply to Alex saying Thursday works." See [What your AI can do with email](/connectors/email-tools) for every action in detail. ## What you need - A Fastmail plan that allows app passwords. They aren't available on Basic plans. Addresses at `fastmail.com`, `fastmail.fm`, `fastmail.net`, `fastmail.org`, `fastmail.us`, `fastmail.to`, `messagingengine.com`, `sent.com` and `use.startmail.com` are recognised automatically. Your own domain hosted at Fastmail is too, when you type it in the detect box. ## Connect Fastmail 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click the **Fastmail** tile. (Or type your address in the detect box.) 3. Under **Create an app password**, click **Open Fastmail in a new tab ↗**. Fastmail's help page on app passwords opens. 4. In Fastmail, go to **Settings** → **Privacy & Security** → **Connected apps & API tokens** → **Manage app passwords and access** → **New app password**. Keep **Mail** access. 5. Copy it. Fastmail shows it once, so copy it before closing that tab. 6. Back in Plugsight, type your address in **Email address** and paste the password into **App password**. Spaces are fine. 7. Click **Test connection & save**. Plugsight signs in to check the password works before saving anything. The server settings (`imap.fastmail.com:993` and `smtp.fastmail.com:465`) are filled in for you. ## What it can and can't change New connections start on **Drafts only**. To let your AI send, click the account's switch on **Connections** so it says **Can send** (Pro or Agency plan). Every email still needs your yes in the chat. Labels are a Gmail feature, so your AI organises Fastmail email by moving it to folders. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Limits - Your AI can send up to 20 emails per account in any 24 hours by default (you can choose 1 to 500). Drafts don't count. - Attachments you send can total up to 20 MB per email. ## Troubleshooting ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** Fastmail refused the sign-in. Usually the password is your normal Fastmail password, or the app password doesn't include Mail access. **How to fix it:** create a new app password with **Mail** access and paste it. ### The connection says it needs reconnecting: "The mail server rejected the password; it may have been changed or revoked." **What it means:** Fastmail no longer accepts the app password. **How to fix it:** on **Connections**, click **Reconnect**, paste a new app password and click **Test connection & save**. ## Related articles - [Connect any email address](/connectors/connect-any-email) - [What your AI can do with email](/connectors/email-tools) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # Yandex Mail URL: https://docs.plugsight.app/connectors/yandex-mail Connect Yandex Mail by turning on IMAP and app passwords in Yandex, then pasting a Yandex app password into Plugsight. Connect Yandex Mail so your AI can search, read and draft your email, and send when you allow it. Yandex needs an **app password** from your Yandex ID. ## What your AI can do - Search your mailbox live, with filters such as sender, date, unread and attachments. - Read full emails, conversations and attachments (PDF, Word, Excel and PowerPoint are read as text). - Save drafts, replies and forwards to your Yandex **Drafts**. - Send email, once you switch sending on and approve each email in the chat. - Move emails to folders, flag them and mark them read or unread. Try asking: - "Summarise the unread emails from this week." - "Find every email about the apartment lease." - "Draft a reply to the last message from my landlord." See [What your AI can do with email](/connectors/email-tools) for every action in detail. ## Which addresses this covers `yandex.com`, `yandex.ru`, `ya.ru`, `yandex.by`, `yandex.kz`, `yandex.ua` and `yandex.com.tr`. Your own domain hosted at Yandex is recognised too, when you type it in the detect box. ## Connect Yandex Mail 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click the **Yandex Mail** tile. (Or type your address in the detect box.) 3. In Yandex Mail, go to **Settings** → **Email clients**. Turn on IMAP, and turn on **App passwords and OAuth tokens**. 4. Under **Create an app password** in Plugsight, click **Open Yandex Mail in a new tab ↗**. The app passwords page of your Yandex ID opens. Create an app password. 5. Copy it before closing that tab. 6. Back in Plugsight, type your address in **Email address** and paste the password into **App password**. Spaces are fine. 7. Click **Test connection & save**. Plugsight signs in to check the password works before saving anything. The server settings (`imap.yandex.com:993` and `smtp.yandex.com:465`) are filled in for you. ## What it can and can't change New connections start on **Drafts only**. To let your AI send, click the account's switch on **Connections** so it says **Can send** (Pro or Agency plan). Every email still needs your yes in the chat. Labels are a Gmail feature, so your AI organises Yandex email by moving it to folders. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Limits - Your AI can send up to 20 emails per account in any 24 hours by default (you can choose 1 to 500). Drafts don't count. - Attachments you send can total up to 20 MB per email. ## Troubleshooting ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** Yandex refused the sign-in. **How to fix it:** check IMAP and **App passwords and OAuth tokens** are both on in **Settings** → **Email clients**, then create a new app password and paste it. ### The connection says it needs reconnecting: "The mail server rejected the password; it may have been changed or revoked." **What it means:** Yandex no longer accepts the app password. **How to fix it:** on **Connections**, click **Reconnect**, paste a new app password and click **Test connection & save**. ## Related articles - [European email providers](/connectors/email-providers-europe) (including Mail.ru) - [What your AI can do with email](/connectors/email-tools) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # Mail.com, GMX and Proton Mail URL: https://docs.plugsight.app/connectors/email-providers-global How to connect Mail.com and GMX (gmx.com) mailboxes, their server settings, and why Proton Mail can't be connected. This article covers international providers that don't have their own article: Mail.com, GMX (gmx.com) and Proton Mail. For GMX addresses in Germany, Austria and Switzerland (`gmx.de`, `gmx.net`, `gmx.at`, `gmx.ch`), see [European email providers](/connectors/email-providers-europe). Once connected, your AI can search, read and draft your email, and send when you allow it. See [What your AI can do with email](/connectors/email-tools). ## How to connect 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click **Email** and pick your provider, or type your address in the detect box. 3. Do what the provider's row below says. The connect page shows the same instructions at the top. 4. Type your address in **Email address** and your password in **Password**. 5. Click **Test connection & save**. The server settings are filled in for you. Plugsight signs in to check the password works before saving anything. ## Mail.com | | | | --- | --- | | **Addresses** | `mail.com`, `email.com`, `usa.com`, `myself.com`, `consultant.com`, `post.com`, `europe.com`, `asia.com`, `iname.com`, `writeme.com`, `dr.com`, `engineer.com`, `cheerful.com` | | **Before you connect** | IMAP needs a Mail.com Premium plan. Then enable POP3/IMAP access in Mail.com settings. | | **Password** | Your Mail.com password | | **IMAP server** | `imap.mail.com:993` | | **SMTP server** | `smtp.mail.com:587` | ## GMX (gmx.com) | | | | --- | --- | | **Addresses** | `gmx.com`, `gmx.us`, `gmx.co.uk`, `gmx.fr`, `gmx.es` | | **Before you connect** | Turn on POP3/IMAP access in GMX settings → **POP3 & IMAP**. | | **Password** | Your GMX password. With two-factor login on, create an app-specific password in GMX and use that. | | **IMAP server** | `imap.gmx.com:993` | | **SMTP server** | `mail.gmx.com:587` | ## Proton Mail: not supported Proton Mail (`proton.me`, `protonmail.com`, `protonmail.ch`, `pm.me`) only works through Proton Mail Bridge running on your own computer, so it can't be connected to a cloud service like Plugsight. Its connect page shows **Not supported** with this explanation. ## What it can and can't change New connections start on **Drafts only**. To let your AI send, click the account's switch on **Connections** so it says **Can send** (Pro or Agency plan). Every email still needs your yes in the chat. Labels are a Gmail feature, so your AI organises these mailboxes by moving email to folders. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Troubleshooting ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** the provider refused the sign-in. **How to fix it:** check that IMAP access is turned on in your provider's settings (and, for Mail.com, that you have Premium). If two-factor login is on, use an app-specific password. ### The connection says it needs reconnecting: "The mail server rejected the password; it may have been changed or revoked." **What it means:** the provider no longer accepts the password, for example because you changed it. **How to fix it:** on **Connections**, click **Reconnect**, enter the current password and click **Test connection & save**. ## Related articles - [Connect any email address](/connectors/connect-any-email) - [Other IMAP server](/connectors/other-imap) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # Email providers in the Americas URL: https://docs.plugsight.app/connectors/email-providers-americas Connect AT&T, Xfinity (Comcast), Cox, Spectrum, UOL, BOL and Terra mailboxes: what each needs and their server settings. Plugsight has the server settings for these providers built in, so you only need your address and the right password. Once connected, your AI can search, read and draft your email, and send when you allow it. See [What your AI can do with email](/connectors/email-tools). ## How to connect 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click **Email** and pick your provider, or type your address in the detect box. 3. Do what the provider's row below says. The connect page shows the same instructions at the top. 4. Type your address in **Email address** and paste or type the password. The box's name tells you what to use: for example AT&T's is called **Secure mail key**. 5. Click **Test connection & save**. Plugsight signs in to check the password works before saving anything. ## Providers | Provider in Plugsight | Addresses | What to use as the password | IMAP server | SMTP server | | --- | --- | --- | --- | --- | | **AT&T Mail** | `att.net`, `sbcglobal.net`, `bellsouth.net`, `pacbell.net`, `flash.net`, `prodigy.net`, `swbell.net`, `ameritech.net`, `wans.net`, `nvbell.net`, `snet.net` | A **secure mail key**: create one in your AT&T profile → **Sign-in info** → **Secure mail key**. | `imap.mail.att.net:993` | `smtp.mail.att.net:465` | | **Xfinity / Comcast** | `comcast.net` | Your Xfinity password, after allowing third-party access in Xfinity Connect settings → **Security**. | `imap.comcast.net:993` | `smtp.comcast.net:587` | | **Cox** | `cox.net` | Your Cox email password. | `imap.cox.net:993` | `smtp.cox.net:465` | | **Spectrum (Charter)** | `charter.net`, `spectrum.net`, `twc.com`, `rr.com`, `roadrunner.com` | Your Spectrum email password. | `mobile.charter.net:993` | `mobile.charter.net:587` | | **UOL** | `uol.com.br` | Your UOL password. Allow external access in UOL Mail settings first. | `imap.uol.com.br:993` | `smtps.uol.com.br:587` | | **BOL** | `bol.com.br` | Your BOL password. | `imap.bol.com.br:993` | `smtps.bol.com.br:587` | | **Terra** | `terra.com.br` | Your Terra password. | `imap.terra.com.br:993` | `smtp.terra.com.br:587` | ## Comcast and Cox mail that moved to Yahoo Some Comcast.net and Cox.net mailboxes are now run by Yahoo. - **Comcast:** if your Comcast.net mail has moved to Yahoo, choose [Yahoo Mail](/connectors/yahoo-mail) instead. - **Cox:** Cox.net mail has moved to Yahoo. If the **Cox** entry doesn't connect, choose [Yahoo Mail](/connectors/yahoo-mail) and use a Yahoo app password. ## What it can and can't change New connections start on **Drafts only**. To let your AI send, click the account's switch on **Connections** so it says **Can send** (Pro or Agency plan). Every email still needs your yes in the chat. Labels are a Gmail feature, so your AI organises these mailboxes by moving email to folders. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Troubleshooting ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** the provider refused the sign-in. **How to fix it:** check the row above for what to use as the password. For AT&T, use a secure mail key, not your normal password. For Comcast and Cox, try the Yahoo Mail entry if your mail has moved. ### The connection says it needs reconnecting: "The mail server rejected the password; it may have been changed or revoked." **What it means:** the provider no longer accepts the password or key. **How to fix it:** on **Connections**, click **Reconnect**, enter a current password (or a new secure mail key) and click **Test connection & save**. ## Related articles - [Yahoo Mail](/connectors/yahoo-mail) - [Connect any email address](/connectors/connect-any-email) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # European email providers URL: https://docs.plugsight.app/connectors/email-providers-europe Connect GMX, WEB.DE, T-Online, mailbox.org, Posteo, Orange, Free, SFR, BT, Sky, Virgin Media, Mail.ru and other European mailboxes. Plugsight has the server settings for these providers built in, so you only need your address and the right password. Once connected, your AI can search, read and draft your email, and send when you allow it. See [What your AI can do with email](/connectors/email-tools). Zoho Mail (EU) is covered in [Zoho Mail](/connectors/zoho-mail) and Yandex in [Yandex Mail](/connectors/yandex-mail). ## How to connect 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click **Email** and pick your provider, or type your address in the detect box. 3. Do what the provider's row below says. The connect page shows the same instructions at the top. 4. Type your address in **Email address** and paste or type the password. The box's name tells you what to use: for example T-Online's is called **E-Mail-Passwort**. 5. Click **Test connection & save**. Plugsight signs in to check the password works before saving anything. ## Germany, Austria and Switzerland | Provider in Plugsight | Addresses | Before you connect, and what to use as the password | IMAP server | SMTP server | | --- | --- | --- | --- | --- | | **GMX (gmx.de / .net / .at / .ch)** | `gmx.de`, `gmx.net`, `gmx.at`, `gmx.ch` | In GMX: **E-Mail** → **Einstellungen** → **POP3/IMAP Abruf**, enable access. Use your GMX password, or with two-factor login on, an *anwendungsspezifisches Passwort*. | `imap.gmx.net:993` | `mail.gmx.net:587` | | **WEB.DE** | `web.de` | In WEB.DE: **Einstellungen** → **POP3/IMAP Abruf**, enable access. Use your WEB.DE password, or with two-factor login on, an *anwendungsspezifisches Passwort*. | `imap.web.de:993` | `smtp.web.de:587` | | **T-Online** | `t-online.de`, `magenta.de` | Create an **E-Mail-Passwort** in the T-Online Kundencenter. It's different from your login password. | `secureimap.t-online.de:993` | `securesmtp.t-online.de:465` | | **mailbox.org** | `mailbox.org` | Your mailbox.org password, or one created under **Settings** → **mailbox.org** → **Email App Passwords**. | `imap.mailbox.org:993` | `smtp.mailbox.org:465` | | **Posteo** | `posteo.de`, `posteo.net`, `posteo.eu`, `posteo.org` | Your Posteo password. | `posteo.de:993` | `posteo.de:465` | ## France | Provider in Plugsight | Addresses | Password | IMAP server | SMTP server | | --- | --- | --- | --- | --- | | **Orange** | `orange.fr`, `wanadoo.fr` | Your Orange email password | `imap.orange.fr:993` | `smtp.orange.fr:465` | | **Free** | `free.fr` | Your Free email password | `imap.free.fr:993` | `smtp.free.fr:465` | | **SFR** | `sfr.fr`, `neuf.fr` | Your SFR email password | `imap.sfr.fr:993` | `smtp.sfr.fr:465` | | **La Poste** | `laposte.net` | Your La Poste email password | `imap.laposte.net:993` | `smtp.laposte.net:465` | ## Italy | Provider in Plugsight | Addresses | Password | IMAP server | SMTP server | | --- | --- | --- | --- | --- | | **Libero** | `libero.it`, `inwind.it`, `iol.it`, `blu.it` | Your Libero password | `imapmail.libero.it:993` | `smtpmail.libero.it:465` | | **Virgilio** | `virgilio.it` | Your Virgilio password | `in.virgilio.it:993` | `out.virgilio.it:465` | | **TIM (Alice)** | `alice.it`, `tim.it` | Your TIM email password | `in.alice.it:993` | `out.alice.it:465` | ## United Kingdom | Provider in Plugsight | Addresses | Password | IMAP server | SMTP server | | --- | --- | --- | --- | --- | | **BT Email** | `btinternet.com`, `btopenworld.com`, `talk21.com` | Your BT Email password, not your My BT ID password | `mail.btinternet.com:993` | `mail.btinternet.com:465` | | **Sky Mail** | `sky.com` | Your Sky email password | `imap.tools.sky.com:993` | `smtp.tools.sky.com:465` | | **Virgin Media** | `virginmedia.com`, `ntlworld.com`, `blueyonder.co.uk` | A Virgin Media Mail app password: create one in **My Virgin Media** → **Account details** | `imap.virginmedia.com:993` | `smtp.virginmedia.com:465` | ## Central and Eastern Europe | Provider in Plugsight | Addresses | Before you connect, and what to use as the password | IMAP server | SMTP server | | --- | --- | --- | --- | --- | | **Seznam** | `seznam.cz`, `email.cz`, `post.cz` | Allow IMAP in Seznam Email settings, then use your password. | `imap.seznam.cz:993` | `smtp.seznam.cz:465` | | **WP Poczta** | `wp.pl` | Enable IMAP in WP Poczta settings → **Konta zewnętrzne**, then use your password. | `imap.wp.pl:993` | `smtp.wp.pl:465` | | **Onet Poczta** | `onet.pl`, `op.pl`, `vp.pl`, `onet.eu` | Enable IMAP in Onet Poczta settings, then use your password. | `imap.poczta.onet.pl:993` | `smtp.poczta.onet.pl:465` | | **Interia Poczta** | `interia.pl`, `interia.eu`, `poczta.fm` | Enable IMAP in Interia Poczta settings, then use your password. | `poczta.interia.pl:993` | `poczta.interia.pl:465` | | **UKR.NET** | `ukr.net` | Enable IMAP access in UKR.NET settings, then use your password. | `imap.ukr.net:993` | `smtp.ukr.net:465` | ## Mail.ru Mail.ru (`mail.ru`, `inbox.ru`, `list.ru`, `bk.ru`, `internet.ru`) needs an app password, and third-party mail apps now need a paid Mail.ru plan. 1. Click the **Mail.ru** tile, or type your address in the detect box. 2. Under **Create an app password**, click **Open Mail.ru in a new tab ↗**. 3. In Mail.ru, go to **Security** → **Passwords for external applications**, and create one with IMAP/SMTP access. 4. Copy it before closing that tab. 5. Back in Plugsight, type your address in **Email address**, paste the password into **App password** and click **Test connection & save**. Mail.ru's servers are `imap.mail.ru:993` and `smtp.mail.ru:465`. ## What it can and can't change New connections start on **Drafts only**. To let your AI send, click the account's switch on **Connections** so it says **Can send** (Pro or Agency plan). Every email still needs your yes in the chat. Labels are a Gmail feature, so your AI organises these mailboxes by moving email to folders. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Troubleshooting ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** the provider refused the sign-in. **How to fix it:** check that IMAP (POP3/IMAP) access is turned on in your provider's settings, and that you're using the password the row above names: for example T-Online's E-Mail-Passwort, BT Email's password rather than your My BT ID password, or an app password where two-factor login is on. ### The connection says it needs reconnecting: "The mail server rejected the password; it may have been changed or revoked." **What it means:** the provider no longer accepts the password. **How to fix it:** on **Connections**, click **Reconnect**, enter the current password and click **Test connection & save**. ## Related articles - [Mail.com, GMX and Proton Mail](/connectors/email-providers-global) - [Connect any email address](/connectors/connect-any-email) - [Other IMAP server](/connectors/other-imap) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # Asia-Pacific email providers URL: https://docs.plugsight.app/connectors/email-providers-asia-pacific Connect QQ, NetEase 163 and 126, Sina, Aliyun, Naver, Daum, Kakao, Yahoo! JAPAN, Rediffmail Pro and Telstra mailboxes. Plugsight has the server settings for these providers built in, so you only need your address and the right password or code. Once connected, your AI can search, read and draft your email, and send when you allow it. See [What your AI can do with email](/connectors/email-tools). Zoho Mail (India, Australia and Japan) is covered in [Zoho Mail](/connectors/zoho-mail). ## How to connect 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click **Email** and pick your provider, or type your address in the detect box. 3. Do what the provider's row below says. The connect page shows the same instructions at the top. 4. Type your address in **Email address** and paste the password or code. The box's name tells you what to use: for example QQ Mail's is called **Authorization code (授权码)**. 5. Click **Test connection & save**. Plugsight signs in to check it works before saving anything. Spaces in a pasted code are fine. ## China | Provider in Plugsight | Addresses | Before you connect, and what to use as the password | IMAP server | SMTP server | | --- | --- | --- | --- | --- | | **QQ Mail** | `qq.com`, `foxmail.com`, `vip.qq.com` | QQ Mail → **Settings** → **Account**: enable IMAP/SMTP and generate an **authorization code (授权码)**. | `imap.qq.com:993` | `smtp.qq.com:465` | | **NetEase 163** | `163.com`, `vip.163.com` | 163 Mail → **Settings** → **POP3/SMTP/IMAP**: enable IMAP and create an **authorization code (授权码)**. | `imap.163.com:993` | `smtp.163.com:465` | | **NetEase 126** | `126.com`, `vip.126.com` | 126 Mail → **Settings** → **POP3/SMTP/IMAP**: enable IMAP and create an **authorization code (授权码)**. | `imap.126.com:993` | `smtp.126.com:465` | | **NetEase Yeah.net** | `yeah.net` | Enable IMAP in Yeah.net settings and create an **authorization code (授权码)**. | `imap.yeah.net:993` | `smtp.yeah.net:465` | | **Sina Mail** | `sina.com`, `sina.cn` | Enable IMAP in Sina Mail settings and create an **authorization code**. | `imap.sina.com:993` | `smtp.sina.com:465` | | **Aliyun Mail** | `aliyun.com` | Enable IMAP in Aliyun Mail settings, then use your password. | `imap.aliyun.com:993` | `smtp.aliyun.com:465` | ## Korea | Provider in Plugsight | Addresses | Before you connect, and what to use as the password | IMAP server | SMTP server | | --- | --- | --- | --- | --- | | **Naver Mail** | `naver.com` | Naver Mail → **Settings** → **POP3/IMAP**: enable IMAP. Use your password, or with 2-step verification on, an app password. | `imap.naver.com:993` | `smtp.naver.com:465` | | **Daum / Hanmail** | `daum.net`, `hanmail.net` | Daum Mail → **Settings** → **IMAP/POP3**: enable IMAP, then use your password. | `imap.daum.net:993` | `smtp.daum.net:465` | | **Kakao Mail** | `kakao.com` | Kakao Mail → **Settings** → **IMAP/SMTP**: enable it. Use an app password if 2-step verification is on. | `imap.kakao.com:993` | `smtp.kakao.com:465` | ## Japan, India and Australia | Provider in Plugsight | Addresses | Before you connect, and what to use as the password | IMAP server | SMTP server | | --- | --- | --- | --- | --- | | **Yahoo! JAPAN Mail** | `yahoo.co.jp`, `ymail.ne.jp` | Yahoo! JAPAN Mail → **Settings** → **IMAP/POP/SMTP access**: enable it, then use your password. | `imap.mail.yahoo.co.jp:993` | `smtp.mail.yahoo.co.jp:465` | | **Rediffmail Pro** | Your business domain | Rediffmail Pro (business) accounts only; free Rediffmail doesn't offer IMAP. Use your mailbox password. | `imap.rediffmailpro.com:993` | `smtp.rediffmailpro.com:465` | | **Telstra / BigPond** | `bigpond.com`, `bigpond.net.au`, `telstra.com` | Your Telstra Mail password. | `imap.telstra.com:993` | `smtp.telstra.com:465` | ## What it can and can't change New connections start on **Drafts only**. To let your AI send, click the account's switch on **Connections** so it says **Can send** (Pro or Agency plan). Every email still needs your yes in the chat. Labels are a Gmail feature, so your AI organises these mailboxes by moving email to folders. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Troubleshooting ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** the provider refused the sign-in. **How to fix it:** check that IMAP is enabled in your provider's settings. For QQ, NetEase and Sina, paste the authorization code, not your login password. For Naver and Kakao with 2-step verification, use an app password. ### The connection says it needs reconnecting: "The mail server rejected the password; it may have been changed or revoked." **What it means:** the provider no longer accepts the password or code. **How to fix it:** on **Connections**, click **Reconnect**, paste a new code or the current password and click **Test connection & save**. ## Related articles - [Connect any email address](/connectors/connect-any-email) - [Other IMAP server](/connectors/other-imap) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # Email hosting and business email URL: https://docs.plugsight.app/connectors/email-hosting-providers Connect business mailboxes hosted at GoDaddy, IONOS, Namecheap Private Email, Titan, Hostinger or Rackspace, on your own domain. If your business email is on your own domain and hosted by one of these companies, Plugsight has its server settings built in. Once connected, your AI can search, read and draft your email, and send when you allow it. See [What your AI can do with email](/connectors/email-tools). Business mail at Microsoft 365 connects with [Outlook](/connectors/outlook), at Google Workspace with [Gmail](/connectors/gmail), and at Zoho with [Zoho Mail](/connectors/zoho-mail). ## How to connect 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Type your address in the detect box and click **Detect**. Plugsight checks your domain's mail servers and recognises GoDaddy, IONOS, Namecheap, Titan, Hostinger and Rackspace. Or click **Email** and pick your host from the list. 3. Type your address in **Email address** and your mailbox password in **Password**. 4. Click **Test connection & save**. Plugsight signs in to check the password works before saving anything. ## Hosts | Provider in Plugsight | Password | IMAP server | SMTP server | | --- | --- | --- | --- | | **GoDaddy Workspace Email** | Your GoDaddy email password | `imap.secureserver.net:993` | `smtpout.secureserver.net:465` | | **IONOS (1&1)** | Your mailbox password | `imap.ionos.com:993` | `smtp.ionos.com:465` | | **Namecheap Private Email** | Your Private Email mailbox password | `mail.privateemail.com:993` | `mail.privateemail.com:465` | | **Titan Email** | Your Titan mailbox password | `imap.titan.email:993` | `smtp.titan.email:465` | | **Hostinger Email** | Your Hostinger mailbox password | `imap.hostinger.com:993` | `smtp.hostinger.com:465` | | **Rackspace Email** | Your Rackspace mailbox password | `secure.emailsrvr.com:993` | `secure.emailsrvr.com:465` | ### GoDaddy mailboxes moved to Microsoft 365 GoDaddy is moving Workspace Email to Microsoft 365. If your GoDaddy mailbox has moved, connect it with [Outlook](/connectors/outlook) instead. ### IONOS in Germany or the UK The **IONOS (1&1)** entry uses `imap.ionos.com`. For ionos.de or ionos.co.uk accounts, use [Other IMAP server](/connectors/other-imap) with `imap.ionos.de` or `imap.ionos.co.uk`. ## What it can and can't change New connections start on **Drafts only**. To let your AI send, click the account's switch on **Connections** so it says **Can send** (Pro or Agency plan). Every email still needs your yes in the chat. Labels are a Gmail feature, so your AI organises these mailboxes by moving email to folders. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Troubleshooting ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** the mail server refused the sign-in. **How to fix it:** check you're using the password of the mailbox itself, not your hosting account's login. If your GoDaddy mail has moved to Microsoft 365, use Outlook. ### The connection says it needs reconnecting: "The mail server rejected the password; it may have been changed or revoked." **What it means:** the mail server no longer accepts the password, for example because it was changed. **How to fix it:** on **Connections**, click **Reconnect**, enter the current password and click **Test connection & save**. ## Related articles - [Other IMAP server](/connectors/other-imap) - [Connect any email address](/connectors/connect-any-email) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # Other IMAP server URL: https://docs.plugsight.app/connectors/other-imap Connect any mailbox by entering its IMAP and SMTP settings yourself: what IMAP and SMTP are, which ports to use, and how to fix errors. If your provider isn't in Plugsight's list and couldn't be detected, you can connect any mail server that supports IMAP by entering its settings yourself. ## IMAP and SMTP - **IMAP** is how your AI reads your mail. It's required. - **SMTP** is how it sends. It's optional: without it, your AI can read and write drafts, but can't send. Plugsight signs in to both with the same email address and password. ## What you need Your provider's **IMAP settings** (and SMTP settings, if you want your AI to send): a server name and a port number for each. Search your email provider's help pages for "IMAP settings" or "IMAP/SMTP settings". ## Connect 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click **Email**, then **Other IMAP server**. (Or type your address in the detect box: if detection finds nothing, you land on this page.) 3. On **Connect an IMAP account**, type your address in **Email address**. 4. Type the mailbox's password in **Password**. 5. Under **Server settings**, fill in: - **IMAP server**, for example `imap.example.com` - **IMAP port**: usually `993` - **SMTP server (optional, for sending)**, for example `smtp.example.com` - **SMTP port**: usually `465` or `587` 6. Optional: open **Name this connection (optional)** and type a name. It defaults to the email address. 7. Click **Test connection & save**. Plugsight signs in to your IMAP server to check the settings and password work before saving anything. The SMTP settings are first used when your AI sends an email. > [!TIP] > If Plugsight found your provider in Thunderbird's provider database, the page says **Detected Thunderbird's provider database. We filled in the server settings; check them and add your password.** Check the settings against your provider's help pages before saving. ## Ports | Port | Used for | Security | | --- | --- | --- | | `993` | IMAP | SSL/TLS from the start | | `143` | IMAP | STARTTLS | | `465` | SMTP | SSL/TLS from the start | | `587` | SMTP | STARTTLS | If your provider doesn't say, IMAP is usually 993 and SMTP 465 or 587. Plugsight uses SSL/TLS from the start on IMAP port 993 and SMTP port 465, and STARTTLS on any other port. > [!NOTE] > On this page, Plugsight uses your password exactly as you type it, spaces included. (On the pages for named providers, spaces are removed, because app passwords are often shown in groups.) If you paste an app password that has spaces, remove them. ## What your AI can do The same as any mailbox: search, read, attachments, drafts, sending (with SMTP), and moving, flagging and marking emails. See [What your AI can do with email](/connectors/email-tools). Labels are a Gmail feature, so your AI organises the mailbox by moving email to folders. ## What it can and can't change New connections start on **Drafts only**. To let your AI send, add SMTP settings, then click the account's switch on **Connections** so it says **Can send** (Pro or Agency plan). Every email still needs your yes in the chat. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Troubleshooting ### IMAP server is required. **What it means:** **IMAP server** is empty. **How to fix it:** enter your provider's IMAP server name. ### Couldn't find … Check the server name for typos. **What it means:** the server name doesn't exist. **How to fix it:** check the spelling against your provider's help pages. Server names look like `imap.example.com`, without `https://`. ### … refused the connection. Check the port number, or whether the server allows this kind of access. **What it means:** the server is there but isn't accepting connections on that port, or IMAP access is turned off. **How to fix it:** check the port, and check IMAP access is turned on in your mailbox settings. ### Couldn't reach … in time. Check the server name and port, then try again. **What it means:** the server didn't answer. **How to fix it:** check the server name and port. A wrong port often looks like this. ### The secure connection to … failed. Check the port and whether it expects SSL/TLS. **What it means:** the port and the type of security don't match, or the server's security certificate isn't valid. **How to fix it:** use 993 for IMAP over SSL/TLS (or 143 for STARTTLS). If your provider gives a different server name for secure connections, use that. ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** the server refused the email address or password. **How to fix it:** check the password, and whether your provider needs an app password. Some servers need a username that differs from the email address; Plugsight always signs in with the email address, so such servers can't be connected this way. ### Sending isn't available for this account type (no outgoing mail server configured). **What it means:** your AI tried to send from a mailbox connected without SMTP settings. **How to fix it:** connect the same address again: **Add connection** → **Email** → **Other IMAP server**. Enter the password and all the server settings again, this time including **SMTP server** and **SMTP port**, and click **Test connection & save**. Connecting the same address again updates the existing connection rather than adding a second one. Until then, your AI can still save drafts. ## Related articles - [Connect any email address](/connectors/connect-any-email) - [Email hosting and business email](/connectors/email-hosting-providers) - [What your AI can do with email](/connectors/email-tools) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # Sending, drafts and the daily email limit URL: https://docs.plugsight.app/connectors/email-safety How Plugsight keeps email safe: drafts versus sending, what sending needs, the rolling 24-hour daily limit, and the rules for archiving and labels. Your AI can always read and draft email. Sending, and changing emails, are guarded by several switches and limits, so nothing goes out unless you mean it to. ## Drafts versus sending | | Drafts | Sending | | --- | --- | --- | | What happens | The email is saved in your **Drafts** folder. Nothing leaves your mailbox. | The email goes to its recipients straight away. | | Plan | Every plan | Pro or Agency | | Account switch on **Connections** | Not needed | Must say **Can send** | | MCP server's **Allow changes** | Not needed | Must be ticked | | Pause on **Permissions** | Still works while paused | Stopped while paused | | Daily email limit | Never counts | Counts | | Your yes in the chat | Not needed | Needed for every email | New email connections start on **Drafts only**. That's the safest way to use email with AI: your AI writes, you check the draft in your own mail app and press send yourself. ## What sending needs All of these must be true. Plugsight checks them every time, and your AI tells you the first one that's missing: 1. **Your plan includes changes.** Sending is on the Pro and Agency plans. On Free, the account shows **Drafts only · Upgrade**. 2. **Nothing is paused.** On **Permissions**, neither **Pause everything** nor the **Email** pause is on. 3. **The MCP server allows changes.** On **MCP servers**, open the server, click **Edit configuration** and tick **Allow changes**. New servers have it ticked. 4. **The account may send.** On **Connections**, the account's switch says **Can send**. 5. **The account is under its daily email limit.** 6. **You said yes in the chat.** Before sending, your AI shows you the account it sends from, To, Cc, Bcc, subject, full text and attachment names, and sends only after your clear yes to that exact email. On **Connections**, the line under the account's switch says **Ready: your AI asks you in the chat before each change.** when everything is set, or names the one thing still stopping it. > [!NOTE] > Plugsight sends from each account one email at a time, so several requests arriving together can't slip past the daily limit. ## The daily email limit The daily email limit stops a mistake from ever sending hundreds of emails. - **Default:** 20 emails per email account. - **Range:** any whole number from 1 to 500. - **Per account:** the number applies to each email account separately. Five accounts can each send 20. - **Rolling 24 hours:** there's no fixed reset time. Each email counts for 24 hours after it's sent, then frees up a send. - **What counts:** emails your AI sent successfully, including sent drafts. Drafts, blocked attempts and failed sends don't count. Emails you send yourself in your mail app don't count either. ### Change the limit 1. Go to **Permissions**. 2. Under **Daily email limit**, type a number in **Emails per account, per 24 hours**. 3. Click **Save**. You see **Saved: up to … emails per account per 24 hours.** To go back to the default, click **Reset to 20**. > [!WARNING] > Your email provider has its own daily limits too: Gmail allows about 500 emails a day, Google Workspace and Microsoft 365 more. A very high number can get an account temporarily blocked by your provider. ### See how much is used Under **Used in the last 24 hours**, each email account shows, for example, **7 of 20 sent**, with: - **None sent in the last 24 hours: all 20 available.** - **13 left. The oldest send stops counting today at 3:42 PM (in 2 h 5 min).** - **Limit reached. The next send frees up tomorrow at 9:10 AM (in 6 h 12 min).** - **Sending is off for this account (drafts only). Turn it on under Connections.** ## Archiving, labelling and marking emails Your AI can mark emails read or unread, flag them, add or remove labels (Gmail labels and Outlook categories), and move them to archive, trash, inbox, junk or any folder, up to 100 emails at a time. These changes can be undone, so the rules are lighter than for sending: - They need a plan that includes changes (Pro or Agency). - They stop while **Pause everything** or the **Email** pause is on. - They **don't** need the account's **Can send** switch or the MCP server's **Allow changes**. - They don't count toward the daily email limit. - For a few emails you asked about, your AI does it and tells you what changed. Before moving emails to trash, or changing more than 10 at once, it tells you what will happen and waits for your yes. How each mailbox handles them: - **Gmail:** "archive" moves email out of the inbox into All Mail, as Gmail's own Archive does. Labels are Gmail labels; new ones are created. - **Outlook:** labels are Outlook categories; new ones are created. "archive" moves email to the Archive folder. - **Every other mailbox:** labels aren't available, so your AI moves email to folders instead. "archive" works when the mailbox has a folder marked as its archive. ## Everything is logged Every draft, send, blocked attempt and change is listed on **Activity**, with the account, recipients and subject, and the exact reason when something was blocked or failed. ## Messages your AI may show ### Sending email and changing helpdesk tickets are on the Pro plan. Upgrade under Billing to turn write access on. **What it means:** your plan is Free, which doesn't include sending or changes. **How to fix it:** upgrade under **Billing**, or keep using drafts. ### All write actions are paused for this account (Permissions page). Save it as a draft instead. **What it means:** **Pause everything** is on. **How to fix it:** on **Permissions**, click **Resume all**. ### Email sending is paused (Permissions page). Save it as a draft instead. **What it means:** the **Email** type is paused. (When organising emails, the same pause shows as **Email changes are paused (Permissions page).**) **How to fix it:** on **Permissions**, click **Resume** next to **Email**. ### The "…" MCP is set to drafts only. Save it as a draft instead. **What it means:** the MCP server your AI app uses has **Allow changes** unticked. **How to fix it:** on **MCP servers**, open that server, click **Edit configuration** and tick **Allow changes**. ### Sending is off for "…". Turn it on under Connections, or save it as a draft. **What it means:** the account's switch says **Drafts only**. **How to fix it:** on **Connections**, click the switch so it says **Can send**. ### Daily limit reached: "…" sent … emails in the last 24 hours (limit …, which you can change on the Permissions page). Save it as a draft instead. **What it means:** this account has used its daily email limit. **How to fix it:** wait until a send frees up (**Permissions** → **Daily email limit** shows when), or raise the limit there. Your AI can save the email as a draft meanwhile. ### Sending is turned off on this server. Save it as a draft instead. **What it means:** sending is switched off for the whole Plugsight service. **How to fix it:** save drafts for now. If it continues, email info@plugsight.app. ### Not sent: show the user the final email and set confirm: true only after they explicitly approve. **What it means:** your AI tried to send without your clear yes, and Plugsight stopped it. **How to fix it:** ask your AI to show you the email, then say yes to send it. ## Related articles - [What your AI can do with email](/connectors/email-tools) - [Connect any email address](/connectors/connect-any-email) - [Gmail](/connectors/gmail) - [Outlook / Microsoft 365](/connectors/outlook) --- # What your AI can do with email URL: https://docs.plugsight.app/connectors/email-tools Every email action Plugsight gives your AI (search, read, attachments, drafts, sending and organising), with example questions. When an MCP server includes an email account, your AI gets the actions below. They work the same for every email connection: Gmail, Outlook, iCloud, Yahoo and any other IMAP mailbox. Your email is read live from your mail server when your AI asks, and Plugsight doesn't store it. You don't need to name the actions: ask in plain words and your AI picks the right one. The names are shown so you can recognise them in your AI app and on Plugsight's **Activity** page. ## Reading ### List connected accounts (`list_accounts`) Lists the accounts this MCP server can use, with each one's id and whether it may send. For email accounts it shows sending as **on**, **off (drafts only)** or **paused**. - "List my Plugsight accounts." - "Which of my inboxes can send email?" ### List folders (`list_folders`) Lists one mailbox's folders (or Gmail labels) with how many emails, and how many unread, each holds. - "Which folders do I have in my work email, and which have unread mail?" ### Search and list emails (`search_emails`) Searches one account or all of them at once, live, across the whole mailbox history. With no filters it lists the latest emails in the inbox. Your AI can combine any of these: - Free text anywhere in the email. On Gmail it also understands Gmail search syntax (`from:amazon newer_than:7d`); on Outlook, Outlook search syntax (`from:amazon AND received>=2026-01-01`). - Sender, recipient (To, Cc, Bcc), subject or body containing some text, or one of a list of senders. - Leaving out senders, subjects or text. - A date range. - Unread or read, flagged (starred) or not, replied to or not. - Has attachments; attachment file name; attachment type (pdf, image, document, spreadsheet, presentation, calendar, archive, email, audio, video, or a file extension). - Size larger or smaller than a number of KB. - A folder: inbox (the default), sent, drafts, trash, junk, archive, all (every folder except trash and junk), or any folder from the folder list. Results come newest first (or oldest first), up to 100 at a time with a short preview, and your AI can page through more. - "Summarise my unread emails from today." - "Find every invoice we received from suppliers this quarter." - "Which emails from last week am I still waiting on a reply to?" - "List all emails with Excel attachments from the last 30 days." - "Find emails larger than 10 MB in my sent folder." ### Read an email (`get_email`) Returns the full email: sender, recipients, date, subject, body text and the list of attachments. Links in HTML emails are kept. Images inside the body are marked so your AI can open them. Reading an email doesn't mark it as read. - "What does the latest email from Acme say?" ### Read a conversation (`get_thread`) Returns every email in the same conversation, oldest first. - "What are the open questions in my thread with legal about the NDA?" ### Read an attachment (`get_attachment`) Opens one attachment, including images inside the body. - PDF, Word (.docx), Excel (.xlsx), PowerPoint (.pptx), HTML, CSV and other text files are read as text. - Images up to 10 MB are shown to your AI as images. - Files inside a forwarded email (.eml) or an Outlook `winmail.dat` can be opened too. - Long text is cut off after a set length; your AI can ask for more. Try: - "What did the contract PDF attached to Sarah's email say about payment terms?" - "Add up the totals on the spreadsheet attached to the supplier's last email." ## Writing ### Create a draft (`create_draft`) Saves a new email, reply, reply-all or forward in the account's **Drafts** folder. Nothing is sent. Replies keep the conversation together and quote the original below; forwards include the original's attachments. Your AI can attach files, including attachments copied from another email in the same account. Drafts are always allowed: on every plan, with sending off, with an MCP server set to read-only, and even while changes are paused. They never count toward the daily email limit. - "Draft a reply to the latest email from Acme about the delayed order." - "Draft polite follow-ups to everyone who hasn't replied to my meeting request." - "Forward the invoice from Northwind to accounts@example.com as a draft." ### Send an email (`send_email`) Sends a new email, reply or forward straight away. Before sending, your AI must show you the account it sends from, To, Cc, Bcc, subject, full text and attachment names, and wait for your clear yes. It never sends on its own initiative. - "Reply to Sam saying Thursday at 3 works, and send it." ### Send a draft (`send_draft`) Sends a draft that's already in your Drafts folder (one your AI wrote, or one you wrote yourself) and removes it from Drafts. Your AI reads the draft first and shows it to you before sending. - "Send the draft to the landlord I wrote this morning." Sending needs more than your yes: see [Sending, drafts and the daily email limit](/connectors/email-safety). ## Organising ### Archive, label or mark emails (`organize_emails`) Changes up to 100 emails at a time: - Mark read or unread. - Flag (star) or remove the flag. - Add or remove labels: Gmail labels or Outlook categories. New ones are created. Other mailboxes don't have labels, so your AI moves email to folders instead. - Move to archive, trash, inbox, junk, or any folder. For a few emails you asked about, your AI does it and tells you what changed. Before moving emails to trash, or changing more than 10 at once, it tells you what will happen and waits for your yes. - "Archive every newsletter in my inbox and label the receipts 'Expenses'." - "Mark all of yesterday's notifications as read." - "Move the emails from the old project into the Archive 2025 folder." ## Attachments you send - All attachments on one email can total up to 20 MB. - On Outlook, each file can be up to 3 MB. ## Several email accounts Each account has an id (shown by `list_accounts`). When you have several, your AI searches all of them at once unless you name one. To be specific, say which: "in my work Gmail", "from my iCloud". ## Related articles - [Sending, drafts and the daily email limit](/connectors/email-safety) - [Connect any email address](/connectors/connect-any-email) - [Gmail](/connectors/gmail) - [Outlook / Microsoft 365](/connectors/outlook) - [Email tools](/developers/email-tools) --- # Outlook Calendar URL: https://docs.plugsight.app/connectors/outlook-calendar Connect your Outlook.com or Microsoft 365 calendar so your AI can see events, find free time and book meetings with your approval. Connect your Outlook calendar so your AI can see what's coming up, find free time and, once you allow it, book, move and cancel events. It works with Outlook.com and Hotmail accounts and with Microsoft 365 work or school accounts. ## What your AI can do - See events across all your Outlook calendars, with guests, locations and Teams meeting links. - List repeating events occurrence by occurrence. - Find busy times and free gaps of any length, for scheduling. - Book, move and cancel events and invite guests, with your approval. Try asking: - "What's on my calendar this week, and which meetings could be an email?" - "Find a free hour on Wednesday and book a call with sam@example.com." - "Move Friday's team review to Monday at the same time and let everyone know." - "How many hours of meetings did I have last month?" See [What your AI can do with calendars](/connectors/calendar-tools) for every action in detail. ## What you need - An Outlook.com, Hotmail or Live account, or a Microsoft 365 work or school account. - For some work accounts: your IT administrator's approval. See [When your administrator must approve](/connectors/outlook#when-your-administrator-must-approve). ## Connect Outlook Calendar 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click **Calendar**, then the **Outlook Calendar / Microsoft 365** tile. Microsoft's sign-in page opens straight away. 3. Choose or sign in to your Microsoft account. 4. Microsoft asks you to allow Plugsight access to your calendars. Allow it. 5. You're back on **Connections**, with a message such as `Connected you@outlook.com: 3 calendars.` Plugsight asks Microsoft only for calendar access with this connection, separate from your email and contacts. Every calendar you can open is included; you can hide any of them (see below). ## What it can and can't change The connection starts **Read-only**: your AI can see events and free time, but can't change anything. To let it book: 1. On **Connections**, click the calendar connection's switch so it says **Can book & change**. This needs the Pro or Agency plan. 2. Check the line under the switch says **Ready**. Every booking, move or cancellation still needs your yes in the chat. See [What changes need](/connectors/calendar-tools#what-changes-need). How Outlook handles changes: - **Invitations:** Outlook always emails invitations to guests when an event is booked with them. - **Repeating events:** changing or cancelling affects only that one occurrence. - **Cancelling:** if you organised the event and it has guests, they're sent a cancellation. Otherwise the event is removed from your calendar only. - **Calendars you can only view** (for example someone else's, shared read-only) can't have events added or changed. ## Hide a calendar On **Connections**, click **Show calendars** under the connection, then switch off any calendar you don't want your AI to see. Hidden calendars are never read or booked. ## Troubleshooting ### Outlook always emails invitations to guests. Book without guests, or allow the invitations. **What it means:** your AI tried to book an event with guests without sending invitations. Outlook doesn't allow that. **How to fix it:** let the invitations go, or book the event without guests. ### Your organisation needs an administrator to approve Plugsight in Microsoft. **What it means:** your company only allows apps an administrator has approved. **How to fix it:** ask your IT administrator to approve Plugsight. If you are the admin, tick **Consent on behalf of your organisation** on Microsoft's permission screen. See [When your administrator must approve](/connectors/outlook#when-your-administrator-must-approve). ### Microsoft didn't grant lasting access. Remove Plugsight at myapps.microsoft.com, then connect again. **What it means:** Microsoft let you sign in but didn't give Plugsight ongoing access. **How to fix it:** remove Plugsight at myapps.microsoft.com, then connect again. ### You didn't allow access in Microsoft. Click Connect again and allow it, ticking every permission box. **What it means:** access wasn't allowed on Microsoft's permission screen. **How to fix it:** click the tile again and allow access. ### The connection says it needs reconnecting: "Microsoft rejected this connection's access." **What it means:** Microsoft stopped accepting the connection, usually because the password changed or access was removed. **How to fix it:** on **Connections**, click **Reconnect** and sign in again. For messages about pauses, plans and read-only MCP servers, see [Messages your AI may show](/connectors/calendar-tools#messages-your-ai-may-show). ## Related articles - [What your AI can do with calendars](/connectors/calendar-tools) - [Outlook / Microsoft 365 email](/connectors/outlook) - [Outlook Contacts](/connectors/outlook-contacts) --- # iCloud Calendar URL: https://docs.plugsight.app/connectors/icloud-calendar Connect your iPhone and Mac calendar with your Apple ID and an app-specific password, so your AI can find free time and book with approval. Connect your iCloud calendar, the one on your iPhone and Mac, so your AI can see what's coming up, find free time and, once you allow it, book, move and cancel events. Apple has no sign-in button for other apps, so you use your Apple ID and an **app-specific password**. ## What your AI can do - See events across all your iCloud calendars, with guests, locations and notes. - List repeating events occurrence by occurrence. - Find busy times and free gaps of any length, for scheduling. - Book, move and cancel events and invite guests, with your approval. Try asking: - "What's on my calendar this week, and where do I have a free afternoon?" - "Find a 30-minute slot on Thursday and book a call with sam@example.com." - "Move my dentist appointment on Friday to next Monday at the same time." - "How many hours of meetings did I have last month?" See [What your AI can do with calendars](/connectors/calendar-tools) for every action in detail. ## What you need - Your Apple ID (the one you use on your iPhone or Mac). - Two-factor authentication on that Apple ID. Apple needs it switched on before you can create an app-specific password. ## Connect iCloud Calendar It takes about two minutes. 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click **Calendar**, then the **iCloud Calendar** tile. The **Connect iCloud Calendar** page opens. 3. Click **Open Apple account in a new tab ↗** and sign in at account.apple.com with your Apple ID. 4. Go to **Sign-In and Security** → **App-Specific Passwords** → **Generate an app-specific password**, name it "Plugsight" and click **Create**. 5. Copy the password. It looks like `abcd-efgh-ijkl-mnop`. 6. Back in Plugsight, type your Apple ID in **Apple ID email** and paste the password into **App-specific password**. 7. Optional: type a **Name** for the connection, for example "iCloud Calendar (personal)". 8. Click **Test connection & save**. While Plugsight checks, the button says **Checking with Apple…**. Plugsight signs in to check it works before saving anything. You then see a message such as `Connected you@icloud.com: 4 calendars.` Every calendar on your iCloud account that holds events is included; you can hide any of them (see below). > [!TIP] > Already connected iCloud Mail or iCloud Contacts? You can make a new app-specific password or reuse that one. Your normal Apple password never works here, and stays private. ## What it can and can't change The connection starts **Read-only**: your AI can see events and free time, but can't change anything. To let it book: 1. On **Connections**, click the calendar connection's switch so it says **Can book & change**. This needs the Pro or Agency plan. 2. Check the line under the switch says **Ready**. Every booking, move or cancellation still needs your yes in the chat. See [What changes need](/connectors/calendar-tools#what-changes-need). How iCloud handles changes: - **Repeating events:** changing or cancelling affects the whole series, not one occurrence. - **Guests:** by default, guests are invited by email. Your AI can book with guests without emailing them if you ask. - **Video links:** Google Meet links can't be added; your AI can put a video link in the description instead. ## Hide a calendar On **Connections**, click **Show calendars** under the connection, then switch off any calendar you don't want your AI to see. Hidden calendars are never read or booked. ## Troubleshooting ### Apple didn't accept that Apple ID and password. Use an app-specific password (account.apple.com → Sign-In and Security → App-Specific Passwords), not your normal password. **What it means:** Apple refused the sign-in when you connected. Usually it's your normal Apple password, a mistyped app-specific password, or the wrong Apple ID. **How to fix it:** create a new app-specific password and paste it, and check **Apple ID email** is the Apple ID you use on your iPhone or Mac. ### Apple rejected the Apple ID or app-specific password. Make a new app-specific password and reconnect. **What it means:** the connection was working, but Apple no longer accepts the password, for example because you revoked it in your Apple account. The connection shows **Reconnect needed**. **How to fix it:** on **Connections**, click **Reconnect iCloud Calendar**. The connect page opens with your Apple ID filled in. Paste a new app-specific password and click **Test connection & save**. ### The event changed in iCloud meanwhile. Fetch it again, then retry. **What it means:** the event was edited somewhere else (on your phone, say) while your AI was changing it. **How to fix it:** ask your AI to look at the event again, then make the change. ### iCloud didn't accept the … (HTTP …). Try again in a minute. **What it means:** Apple's server didn't accept the change. **How to fix it:** wait a minute and ask again. For messages about pauses, plans and read-only MCP servers, see [Messages your AI may show](/connectors/calendar-tools#messages-your-ai-may-show). ## Related articles - [What your AI can do with calendars](/connectors/calendar-tools) - [iCloud Contacts](/connectors/icloud-contacts) - [iCloud Mail](/connectors/icloud-mail) --- # Google Calendar URL: https://docs.plugsight.app/connectors/google-calendar Connect Google Calendar with Google sign-in so your AI can see events and find free time. It's read-only today; booking comes once Google approves it. Connect Google Calendar so your AI can see what's coming up and find free time across every calendar your Google account can see. > [!NOTE] > **Google Calendar is read-only today.** Booking, moving and cancelling events needs a permission Google is still reviewing for Plugsight. Booking in Google Calendar comes once Google approves it. To let your AI book meetings now, connect [Outlook Calendar](/connectors/outlook-calendar) or [iCloud Calendar](/connectors/icloud-calendar). ## What your AI can do - See events across all your Google calendars, with attendees, locations and descriptions. - Find busy times and free gaps of any length, for scheduling. - See each calendar's time zone. Try asking: - "What does my week look like, and which meetings could be an email?" - "Find three 45-minute slots next week when I'm free in the afternoon." - "When did I last meet Priya, and what was it about?" - "How many hours of meetings did I have this month?" See [What your AI can do with calendars](/connectors/calendar-tools) for every action in detail. ## What you need - A Google account (personal Gmail or Google Workspace) with Google Calendar. ## Connect Google Calendar It takes about a minute. You sign in on Google's own page; Plugsight never sees your password. 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click **Calendar**, then the **Google Calendar** tile. The **Connect Google Calendar** page shows what Google will ask. 3. Click **Continue to Google**. 4. **Choose your Google account**: the one whose calendars you want. 5. If Google says **Google hasn't verified this app**, click **Advanced**, then **Go to Plugsight (unsafe)**. Google shows this while it reviews new apps; it doesn't mean anything is wrong. 6. **Tick the permission box.** Google asks: *"See and download any calendar you can access using your Google Calendar"*. Tick it, or the connection can't work. 7. You're back in Plugsight, with a message such as `Connected you@gmail.com: 5 calendars.` Plugsight lists every calendar that login can see. You can hide any of them (see below). ## What it can and can't change Nothing. On **Connections**, the connection shows **Read-only** with no switch. Clicking it explains: *Plugsight only reads Google Calendar here, so there's no switch to turn on.* ## Hide a calendar On **Connections**, click **Show calendars** under the connection, then switch off any calendar you don't want your AI to see. Hidden calendars are never read. ## Troubleshooting ### Google Calendar access wasn't granted. Tick the permission and try again. **What it means:** the permission box was left unticked on Google's screen. **How to fix it:** click the tile again, and tick the box this time. ### Google returned no refresh token. Remove the app's access in your Google account and try again. **What it means:** Google didn't give Plugsight lasting access, so the connection couldn't be saved. **How to fix it:** remove Plugsight's access in your Google account, then connect again. ### You didn't allow access in Google. Click Connect again and allow it, ticking every permission box. **What it means:** access wasn't allowed on Google's screen. **How to fix it:** click the tile again and allow access. ### My AI says it can't book in Google Calendar **What it means:** Google Calendar connections are read-only for now, so your AI has no booking actions for them. **How to fix it:** to book with your AI today, connect [Outlook Calendar](/connectors/outlook-calendar) or [iCloud Calendar](/connectors/icloud-calendar). ## Related articles - [What your AI can do with calendars](/connectors/calendar-tools) - [Google Contacts](/connectors/google-contacts) - [Gmail](/connectors/gmail) - [Prepare for meetings and follow up](/guides/meeting-prep-and-follow-up) --- # What your AI can do with calendars URL: https://docs.plugsight.app/connectors/calendar-tools Every calendar action Plugsight gives your AI (events, free time, booking, moving and cancelling), the rules for changes and the messages you may see. When an MCP server includes a calendar connection (Outlook Calendar, iCloud Calendar or Google Calendar), your AI gets the actions below. Events are read live from your calendar when your AI asks, and Plugsight doesn't store them. You don't need to name the actions: ask in plain words. The names are shown so you can recognise them in your AI app and on **Activity**. ## Reading ### List calendars (`calendar_list_calendars`) The calendars this connection can see, with each one's time zone, whether it's your main (primary) calendar, and whether events can be added to it. - "Which calendars do you see in my Outlook?" ### List events (`calendar_list_events`) Events between two dates or times, across all your calendars or one, optionally matching text in the title, description, location or guests. Repeating events are listed occurrence by occurrence. Up to 500 events at a time; if there are more, your AI is told and carries on from where the list stopped. A date on its own, like "tomorrow" or "18 November", means that whole day in your calendar's own time zone, so evening meetings aren't missed. Your AI can also name a time zone. - "What's on my calendar this week?" - "When did I last meet Priya, and what was it about?" - "How many hours of meetings did I have last month?" ### Read one event (`calendar_get_event`) Everything about one event: the full description (agenda, notes), the video-call link and dial-in (Google Meet, Zoom, Teams), location, every guest and their reply, and any attached files. - "What's the dial-in for tomorrow's 10am call?" - "What's on the agenda for the board meeting?" ### Find free time (`calendar_find_free_time`) Your busy times across all your calendars between two dates or times, and the free gaps of at least a given length (5 minutes to 24 hours; 30 minutes unless you say otherwise). All-day busy, tentative and out-of-office days count as busy; events marked free don't. If a calendar can't be checked, your AI is told rather than treating it as free. - "Find three 45-minute slots next week when I'm free in the afternoon." - "When am I free on Thursday?" ## Changing (Outlook and iCloud calendars) These actions appear only when at least one calendar connection in the MCP server is allowed to book. Google Calendar can't be booked yet: see [Google Calendar](/connectors/google-calendar). Before any change, your AI shows you the calendar, title, date, start and end time with time zone, location and every guest, and waits for your clear yes. It never books, moves or cancels on its own initiative. ### Book an event (`calendar_create_event`) Creates an event on your main calendar (or one you name), optionally with a description, location and guests to invite. All-day events are supported. Guests get an email invitation unless you say not to (Outlook always sends invitations: see below). - "Find a free hour on Wednesday and book a call with sam@example.com." ### Change an event (`calendar_update_event`) Moves an event, or changes its title, description or location, or adds guests. Only what you ask for changes. To move an event, your AI gives both a new start and a new end. - "Move Friday's team review to Monday at the same time and let everyone know." ### Cancel an event (`calendar_cancel_event`) Deletes an event and, unless you say not to, emails guests a cancellation. - "Cancel my 4pm on Thursday." ### Repeating events - **Outlook:** changing or cancelling affects only the one occurrence. - **iCloud:** changing or cancelling affects the whole series. ## What changes need All of these must be true: 1. **Your plan includes changes** (Pro or Agency). 2. **Nothing is paused** on **Permissions**: neither **Pause everything** nor the **Calendar** pause. 3. **The MCP server allows changes**: **Allow changes** ticked under **Edit configuration**. 4. **The connection may book**: on **Connections**, its switch says **Can book & change**. When off, it says **Read-only**. 5. **You said yes in the chat** to the exact details. There's no daily limit for calendar changes. Every change is listed on **Activity**. ## Hide a calendar from your AI On **Connections**, click **Show calendars** under the calendar connection, then switch off any calendar you want hidden. Your AI never reads, searches or books hidden calendars, even if asked for one by name. ## Several calendar connections When an MCP server has more than one calendar connection, your AI needs to know which to use: name it, for example "on my iCloud calendar". Each connection's id is shown by "List my Plugsight accounts". ## Messages your AI may show ### Calendar changes are paused (Permissions page). **What it means:** the **Calendar** type is paused. **How to fix it:** on **Permissions**, click **Resume** next to **Calendar**. ### All write actions are paused for this account (Permissions page). **What it means:** **Pause everything** is on. **How to fix it:** on **Permissions**, click **Resume all**. ### The "…" MCP is read-only. Allow changes on the MCP server first (MCP servers page). **What it means:** the MCP server your AI app uses has **Allow changes** unticked. **How to fix it:** on **MCP servers**, open that server, click **Edit configuration** and tick **Allow changes**. ### Changes are off for "…". Allow them under Connections first. **What it means:** the calendar connection's switch says **Read-only**. **How to fix it:** on **Connections**, click the switch so it says **Can book & change**. ### Sending email and changing helpdesk tickets are on the Pro plan. Upgrade under Billing to turn write access on. **What it means:** your plan is Free, which doesn't include changes of any kind, calendar booking included. **How to fix it:** upgrade under **Billing**. ### You can only view "…", not change it. Pick another calendar. **What it means:** you can see that calendar but not edit it, for example one shared with you read-only. **How to fix it:** ask your AI to use one of your own calendars. "List my calendars" shows which ones can have events added. ### Unknown or hidden calendar. Call calendar_list_calendars. **What it means:** the calendar doesn't exist, or you've hidden it from your AI. **How to fix it:** show the calendar again on **Connections** (**Show calendars**), or ask your AI to use another one. ### Google Meet links can only be added to Google calendars. Add a video link in the description instead. **What it means:** your AI tried to add a Google Meet link to an Outlook or iCloud event. **How to fix it:** ask for the video link to go in the description. ### This MCP has 2 calendar connections; pass account (one of: …). **What it means:** your AI didn't say which calendar connection to use. **How to fix it:** name the calendar connection in your request. ## Related articles - [Outlook Calendar](/connectors/outlook-calendar) - [iCloud Calendar](/connectors/icloud-calendar) - [Google Calendar](/connectors/google-calendar) - [Calendar tools](/developers/calendar-tools) --- # Google Contacts URL: https://docs.plugsight.app/connectors/google-contacts Connect Google Contacts so your AI can look up anyone you know, including people you've emailed: names, emails, phone numbers and companies. Connect Google Contacts so your AI can find people's email addresses, phone numbers and companies. It searches your saved contacts and your "other contacts": people you've emailed, which Google saves for you automatically. ## What your AI can do Contacts are read-only: your AI can look people up, but never adds, changes or deletes contacts. - **Search contacts** (`contacts_search`): finds people by name, email, phone number or company, in your saved contacts and other contacts. Up to 60 results. - **List contacts** (`contacts_list`): your saved contacts, most recently changed first, page by page (up to 1,000 at a time). - **Get a contact** (`contacts_get`): everything saved for one person: emails, phones, organisation, addresses, notes, birthday and links. Try asking: - "What's the phone number for Priya Shah at Northwind?" - "Who do I know at Acme, and when did I add them?" - "Find everyone in my contacts at a .gov.uk address." - "Find my accountant's email and draft them a note about this year's receipts." (with an email account in the same MCP server) ## What you need - A Google account (personal or Google Workspace). ## Connect Google Contacts You sign in on Google's own page; Plugsight never sees your password. 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click **Contacts**, then the **Google Contacts** tile. The **Connect Google Contacts** page shows what Google will ask. 3. Click **Continue to Google**. 4. **Choose your Google account.** 5. If Google says **Google hasn't verified this app**, click **Advanced**, then **Go to Plugsight (unsafe)**. Google shows this while it reviews new apps; it doesn't mean anything is wrong. 6. **Tick the permission boxes.** Google asks *"See and download your contacts"*, which is required, and *"See and download contact info automatically saved in your 'Other contacts'"*, which is optional. Tick both so your AI can also find people you've emailed but never saved. 7. You're back in Plugsight, with a message saying how many contacts it found, such as `Connected you@gmail.com: 1,240 contacts.` > [!NOTE] > If you leave "Other contacts" unticked, the connection still works, but searches cover only your saved contacts. To add it later, connect Google Contacts again and tick it. ## What it can and can't change Nothing. On **Connections**, the connection shows **Read-only** with no switch. ## Troubleshooting ### Google Contacts access wasn't granted. Tick the permission and try again. **What it means:** the box *"See and download your contacts"* was left unticked on Google's screen. **How to fix it:** click the tile again, and tick that box. Tick "Other contacts" too, if you want your AI to find people you've emailed. ### Google returned no refresh token. Remove the app's access in your Google account and try again. **What it means:** Google didn't give Plugsight lasting access, so the connection couldn't be saved. **How to fix it:** remove Plugsight's access in your Google account, then connect again. ### You didn't allow access in Google. Click Connect again and allow it, ticking every permission box. **What it means:** access wasn't allowed on Google's screen. **How to fix it:** click the tile again and allow access. ### This MCP has 2 contacts connections; pass account (one of: …). **What it means:** the MCP server has more than one contacts connection, and your AI didn't say which to use. **How to fix it:** name it in your request, for example "in my Google contacts". ## Related articles - [Outlook Contacts](/connectors/outlook-contacts) - [iCloud Contacts](/connectors/icloud-contacts) - [Google Calendar](/connectors/google-calendar) - [Gmail](/connectors/gmail) - [Contacts tools](/developers/contacts-tools) - [Look up a contact's details](/recipes/look-up-a-contact) --- # Outlook Contacts URL: https://docs.plugsight.app/connectors/outlook-contacts Connect Outlook Contacts with Microsoft sign-in so your AI can look up names, emails, phone numbers and job titles in your address book. Connect Outlook Contacts so your AI can find people's email addresses, phone numbers, companies and job titles. It works with Outlook.com and Hotmail accounts and with Microsoft 365 work or school accounts. ## What your AI can do Contacts are read-only: your AI can look people up, but never adds, changes or deletes contacts. - **Search contacts** (`contacts_search`): finds people by name, email, phone number or company. Up to 60 results. - **List contacts** (`contacts_list`): your contacts, page by page (up to 1,000 at a time). - **Get a contact** (`contacts_get`): everything saved for one person: emails, phones, job title and company, addresses, notes, birthday and web page. Try asking: - "What's the mobile number for Priya at Northwind?" - "Who do I know at Contoso, and what are their job titles?" - "Find my accountant's email and draft them a note about this year's receipts." (with an email account in the same MCP server) ## What you need - An Outlook.com, Hotmail or Live account, or a Microsoft 365 work or school account. - For some work accounts: your IT administrator's approval. See [When your administrator must approve](/connectors/outlook#when-your-administrator-must-approve). ## Connect Outlook Contacts 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click **Contacts**, then the **Outlook Contacts / Microsoft 365** tile. Microsoft's sign-in page opens straight away. 3. Choose or sign in to your Microsoft account. 4. Microsoft asks you to allow Plugsight to read your contacts. Allow it. 5. You're back on **Connections**, with a message such as `Connected you@outlook.com: 312 contacts.` Plugsight asks Microsoft only for permission to read your contacts with this connection, separate from your email and calendar. ## What it can and can't change Nothing. On **Connections**, the connection shows **Read-only** with no switch. ## Limits - Plugsight reads up to 5,000 contacts from an Outlook address book. Most address books are far smaller. - Contacts are kept for up to 5 minutes between searches, so a contact you add or change in Outlook can take a few minutes to show up. ## Troubleshooting ### Your organisation needs an administrator to approve Plugsight in Microsoft. **What it means:** your company only allows apps an administrator has approved. **How to fix it:** ask your IT administrator to approve Plugsight. If you are the admin, tick **Consent on behalf of your organisation** on Microsoft's permission screen. ### Microsoft didn't grant lasting access. Remove Plugsight at myapps.microsoft.com, then connect again. **What it means:** Microsoft let you sign in but didn't give Plugsight ongoing access. **How to fix it:** remove Plugsight at myapps.microsoft.com, then connect again. ### You didn't allow access in Microsoft. Click Connect again and allow it, ticking every permission box. **What it means:** access wasn't allowed on Microsoft's permission screen. **How to fix it:** click the tile again and allow access. ### No contact with id "…". Use an id from contacts_search. **What it means:** your AI asked for a contact that no longer exists, for example one deleted in Outlook. **How to fix it:** ask your AI to search for the person again. ### The connection says it needs reconnecting: "Microsoft rejected this connection's access." **What it means:** Microsoft stopped accepting the connection, usually because the password changed or access was removed. **How to fix it:** on **Connections**, click **Reconnect** and sign in again. ## Related articles - [Outlook Calendar](/connectors/outlook-calendar) - [Outlook / Microsoft 365 email](/connectors/outlook) - [Google Contacts](/connectors/google-contacts) - [iCloud Contacts](/connectors/icloud-contacts) --- # iCloud Contacts URL: https://docs.plugsight.app/connectors/icloud-contacts Connect your iPhone and Mac contacts with your Apple ID and an app-specific password, so your AI can look up emails, phones and companies. Connect iCloud Contacts, the address book on your iPhone and Mac, so your AI can find people's email addresses, phone numbers and companies. Apple has no sign-in button for other apps, so you use your Apple ID and an **app-specific password**. ## What your AI can do Contacts are read-only: your AI can look people up, but never adds, changes or deletes contacts. Every address book on your iCloud account is included. - **Search contacts** (`contacts_search`): finds people by name, email, phone number or company. Up to 60 results. - **List contacts** (`contacts_list`): your contacts in name order, page by page (up to 1,000 at a time). - **Get a contact** (`contacts_get`): everything saved for one person: emails, phones, organisation, addresses, notes, birthday and links. Try asking: - "What's the mobile number for Priya at Northwind?" - "Who do I know at Acme?" - "Find the email address of my accountant and draft them a note about this year's receipts." (with an email account in the same MCP server) ## What you need - Your Apple ID (the one you use on your iPhone or Mac). - Two-factor authentication on that Apple ID. Apple needs it switched on before you can create an app-specific password. ## Connect iCloud Contacts It takes about two minutes. 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click **Contacts**, then the **iCloud Contacts** tile. The **Connect iCloud Contacts** page opens. 3. Click **Open Apple account in a new tab ↗** and sign in at account.apple.com with your Apple ID. 4. Go to **Sign-In and Security** → **App-Specific Passwords** → **Generate an app-specific password**, name it "Plugsight" and click **Create**. 5. Copy the password. It looks like `abcd-efgh-ijkl-mnop`. 6. Back in Plugsight, type your Apple ID in **Apple ID email** and paste the password into **App-specific password**. 7. Optional: type a **Name** for the connection. 8. Click **Test connection & save**. While Plugsight checks, the button says **Checking with Apple…**. Plugsight signs in to check it works before saving anything. You then see a message such as `Connected you@icloud.com: 1 address book.` > [!TIP] > Already connected iCloud Mail or iCloud Calendar? You can make a new app-specific password or reuse that one. Your normal Apple password never works here, and stays private. ## What it can and can't change Nothing. On **Connections**, the connection shows **Read-only** with no switch. ## Limits Contacts are kept for up to 5 minutes between searches, so a contact you add or change on your phone can take a few minutes to show up. ## Troubleshooting ### Apple didn't accept that Apple ID and password. Use an app-specific password (account.apple.com → Sign-In and Security → App-Specific Passwords), not your normal password. **What it means:** Apple refused the sign-in when you connected. Usually it's your normal Apple password, a mistyped app-specific password, or the wrong Apple ID. **How to fix it:** create a new app-specific password and paste it, and check **Apple ID email** is the Apple ID you use on your iPhone or Mac. ### Apple rejected the Apple ID or app-specific password. Make a new app-specific password and reconnect. **What it means:** the connection was working, but Apple no longer accepts the password, for example because you revoked it in your Apple account. The connection shows **Reconnect needed**. **How to fix it:** on **Connections**, click **Reconnect iCloud Contacts**. The connect page opens with your Apple ID filled in. Paste a new app-specific password and click **Test connection & save**. ### No contact with id "…". Use an id from contacts_search. **What it means:** your AI asked for a contact that no longer exists, for example one you deleted on your phone. **How to fix it:** ask your AI to search for the person again. ## Related articles - [iCloud Calendar](/connectors/icloud-calendar) - [iCloud Mail](/connectors/icloud-mail) - [Google Contacts](/connectors/google-contacts) - [Outlook Contacts](/connectors/outlook-contacts) --- # Zendesk URL: https://docs.plugsight.app/connectors/zendesk Connect Zendesk by signing in as yourself, then let your AI search, summarise and answer tickets, add notes and update them with your approval. Connect Zendesk Support so your AI can search and summarise tickets, count them, and, once you allow it, reply, add internal notes, update tickets, apply macros and open new tickets. You sign in to Zendesk as yourself and click **Allow**: there are no tokens to copy. ## What your AI can do Your AI works as you, with your Zendesk role's permissions: it sees only what you can see in Zendesk. ### Reading - **Search tickets** (`zendesk_search_tickets`): finds tickets with Zendesk search, for example `status:open`, `requester:jane@acme.com`, `assignee:me status2026-01-01`, or plain words. Newest updated first, up to 100 at a time, sorted by updated, created, priority or status. - **Read a ticket** (`zendesk_get_ticket`): the ticket with its requester, assignee, group, organisation, CCs and followers, custom fields (by their names, with the option chosen), its custom status if your Zendesk has them, form, brand, the support address replies go out from, due date, satisfaction rating and the whole conversation (public replies and internal notes, oldest first). Each reply lists its attachments and any images pasted into it, such as a customer's screenshot, marked where they appear. - **Open attachments and screenshots** (`zendesk_get_attachment`): your AI can look at a screenshot or image a customer pasted or attached, and read PDF, Word, Excel, PowerPoint, CSV and text files, including files inside an attached email. - **Read side conversations** (`zendesk_get_side_conversations`): the separate email or Slack threads agents started from a ticket, with their messages. - **Find users** (`zendesk_find_users`): customers or agents by name, email or phone, with their phone and organisation. - **Ticket counts** (`zendesk_ticket_stats`): how many tickets are new, open, pending, on hold, unsolved and urgent right now, plus how many were created and solved in a period. Can be narrowed with a Zendesk search, such as `tags:refund`, `group:Billing` or `assignee:me`. - **List macros** (`zendesk_list_macros`): the macros (saved replies and actions) you can use, optionally filtered by words in the title. - **List support addresses** (`zendesk_list_support_addresses`): the email addresses customers write to, each with its brand and whether it's the default. - **List ticket statuses** (`zendesk_list_ticket_statuses`): the ticket statuses agents can choose, including your own, such as "Waiting on customer", each with the built-in status it belongs to. ### Changing (with your approval) - **Reply or add a note** (`zendesk_add_comment`): a public reply, which Zendesk emails to the requester, or an internal note that only agents see. It can also set the status to open, pending, on hold or solved, or to one of your custom ticket statuses. - **Update a ticket** (`zendesk_update_ticket`): status (including your custom ticket statuses), priority, type, assignee, adding or removing tags, and the support address its replies go out from. - **Apply a macro** (`zendesk_apply_macro`): your AI first previews exactly what the macro will change (its reply text, status, tags and other fields) and shows you, then applies it after your yes. - **Create a ticket** (`zendesk_create_ticket`): a new ticket for a customer by email (Zendesk adds the person if they're new), with a subject, first message, priority, type, tags, assignee and, if you want, which support address it comes from. The first message is an internal note by default, so the customer isn't emailed, unless you ask for it to be sent to them. Before every change, your AI shows you the exact ticket and the full text or every field change, and waits for your clear yes. It never changes anything on its own initiative. Try asking: - "What are the top five reasons for tickets this week?" - "Summarise everything this customer has raised in the last 90 days." - "Look at the screenshot on ticket 4821 and tell me what error the customer is seeing." - "Which urgent tickets have had no reply for more than a day?" - "Draft an internal note on ticket 4821 summarising the issue." - "Find tickets tagged 'refund' that are still open." - "How many tickets did we solve last week compared with the week before?" - "Apply the 'Close and thank' macro to ticket 4821." - "Which support addresses do we have in Zendesk?" - "Open a ticket for jane@customer.com from help@brand-b.com." - "Set ticket 4821 to Waiting on customer." ## What you need - A Zendesk Support account, and your Zendesk address (the part before `.zendesk.com`). - A Zendesk login with the **agent** or **admin** role. End users (customers) can't be connected. ## Connect Zendesk 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click the **Zendesk** tile. The **Connect Zendesk** page opens. 3. In **Your Zendesk address**, type the part before `.zendesk.com`, as in your browser's address bar when you use Zendesk. Pasting the full address also works. 4. Click **Continue with Zendesk**. Your Zendesk opens. 5. Sign in to Zendesk as yourself (an agent or admin), if you aren't already. 6. Click **Allow**. You come straight back to **Connections**, with a message such as `Connected yourcompany.zendesk.com as Jane Smith (admin), id "yourcompany-zendesk".` The id is the name your AI uses for this Zendesk. > [!NOTE] > Only have an older Zendesk API token? See [Connect Zendesk with an API token](/connectors/zendesk-api-token). Most people don't need it. ## What it can and can't change Replies and updates start off: the connection's switch on **Connections** says **Read-only**, and your AI can search and read but not change anything. To allow changes: 1. On **Connections**, click the Zendesk connection's switch so it says **Can reply & update**. This needs the Pro or Agency plan. 2. Check the MCP server your AI app uses has **Allow changes** ticked (**MCP servers** → **Edit configuration**). 3. Check nothing is paused on **Permissions** (neither **Pause everything** nor the **Helpdesk** pause). 4. Check the line under the switch says **Ready**. Every reply, note, update, macro and new ticket still needs your yes in the chat, and is listed on **Activity**. Changes appear in Zendesk as made by you. There's no daily limit for Zendesk changes. ## Send from a different address or brand One Zendesk account can have several support addresses, often one per brand, such as support@brand-a.com and help@brand-b.com. Zendesk sends a ticket's replies from its support address. - **New tickets** go out from your default support address unless you name another, for example "from help@brand-b.com". The ticket then also belongs to that address's brand. - **An existing ticket** keeps the address the customer wrote to. To answer from a different one, ask your AI to change it first, for example "Send replies on ticket 4821 from help@brand-b.com". That also moves the ticket to that brand. - If you have several addresses and don't say which, your AI asks you. The address must be one of your Zendesk support addresses. Ask "Which support addresses do we have in Zendesk?" to see them. These changes need your yes like any other. ## Custom ticket statuses Zendesk lets admins add their own ticket statuses, such as "Waiting on customer" or "In progress". Each one belongs to a built-in status: new, open, pending, on hold or solved. - Ask "Which ticket statuses do we have in Zendesk?" to see them. - Name the status as it's called in Zendesk, in any case, for example "Set ticket 4821 to Waiting on customer". Your AI can also set one when it replies or adds a note. - Setting a custom status also sets the ticket's built-in status to the one it belongs to. - When your AI reads or searches tickets, it sees each ticket's custom status as well as its built-in status. If your Zendesk doesn't have custom ticket statuses, your AI uses the built-in ones. These changes need your yes like any other. ## Several Zendesk accounts You can connect more than one Zendesk. When an MCP server has several, name the one you mean, for example "in the EU support desk". ## Troubleshooting ### That Zendesk user isn't an agent. Use an agent or admin account. **What it means:** you signed in to Zendesk as an end user (customer). **How to fix it:** connect again, signing in with an agent or admin login. ### Enter your Zendesk address, like yourcompany.zendesk.com. **What it means:** **Your Zendesk address** was empty or couldn't be read. **How to fix it:** type the part before `.zendesk.com`, for example `yourcompany`. ### That isn't a Zendesk address. Enter just your Zendesk address, like yourcompany.zendesk.com. **What it means:** what you typed isn't a valid Zendesk address. **How to fix it:** check the address in your browser when you use Zendesk, and type the part before `.zendesk.com`. ### Zendesk sign-in failed: … **What it means:** Zendesk didn't complete the sign-in. The rest of the message says why, for example **You didn't allow access in Zendesk. Click Connect again and allow it, ticking every permission box.** **How to fix it:** click **Continue with Zendesk** again and click **Allow** in Zendesk. ### Sign in with Zendesk isn't set up on this server yet. If you already have a Zendesk API token, use that. **What it means:** Zendesk sign-in isn't available right now. The **Connect Zendesk** page then shows **Connect with an existing API token** instead. **How to fix it:** if you have an active Zendesk API token, use it: see [Connect Zendesk with an API token](/connectors/zendesk-api-token). Otherwise, email info@plugsight.app. ### Zendesk sign-in expired or was revoked. Reconnect this account in the app. **What it means:** Zendesk no longer accepts the connection's sign-in. The connection shows **Reconnect needed**. **How to fix it:** on **Connections**, click **Reconnect** and sign in to Zendesk again. ### Zendesk refused this action for that agent (…). Ask a Zendesk admin for that permission, or reconnect as an admin. **What it means:** your Zendesk role doesn't allow that change. The part in brackets is Zendesk's own reason. **How to fix it:** ask a Zendesk admin for the permission, or connect with an admin login. ### Zendesk has no ticket or user with that id. Use zendesk_search_tickets or zendesk_find_users to find the right one. **What it means:** the ticket or person doesn't exist, or was deleted. **How to fix it:** check the ticket number, or ask your AI to search for it. ### … isn't one of your Zendesk support addresses. Use one of: … **What it means:** the address your AI was asked to send from isn't a support address in this Zendesk account. The message lists the ones it can use. **How to fix it:** pick one of the listed addresses. To use a new one, add it in Zendesk first (Admin Center → **Channels** → **Email**), then ask again. ### … isn't one of your active Zendesk ticket statuses. Use one of: … **What it means:** the status your AI was asked to set isn't one of this Zendesk's active ticket statuses. The message lists the ones it can use. **How to fix it:** pick one of the listed statuses. To use a new one, a Zendesk admin adds it in Zendesk first; then ask again. ### This Zendesk account doesn't have custom ticket statuses (or this agent can't see them), so … can't be set. Use status instead. **What it means:** your Zendesk has only the built-in statuses, or your Zendesk role can't see the custom ones. **How to fix it:** ask for one of the built-in statuses instead: open, pending, on hold or solved. ### Pass either status or custom_status, not both: a custom status also sets the ticket's status (its category). **What it means:** your AI asked for a built-in status and a custom status in the same change. **How to fix it:** ask for just one status. A custom status already sets the built-in status it belongs to. ### Helpdesk replies and updates are paused (Permissions page). **What it means:** the **Helpdesk** type is paused. **How to fix it:** on **Permissions**, click **Resume** next to **Helpdesk**. ### Changes are off for "…". Allow them under Connections first. **What it means:** the Zendesk connection's switch says **Read-only**. **How to fix it:** on **Connections**, click the switch so it says **Can reply & update**. ### The "…" MCP is read-only. Allow changes on the MCP server first (MCP servers page). **What it means:** the MCP server your AI app uses has **Allow changes** unticked. **How to fix it:** on **MCP servers**, open that server, click **Edit configuration** and tick **Allow changes**. ### Sending email and changing helpdesk tickets are on the Pro plan. Upgrade under Billing to turn write access on. **What it means:** your plan is Free, which doesn't include changes. **How to fix it:** upgrade under **Billing**. Your AI can still search, read and count tickets on Free. ## Related articles - [Connect Zendesk with an API token](/connectors/zendesk-api-token) - [Connect any email address](/connectors/connect-any-email) - [Support teams](/use-cases/support-teams) --- # Connect Zendesk with an API token URL: https://docs.plugsight.app/connectors/zendesk-api-token The fallback way to connect Zendesk with an existing agent API token, and why Zendesk is switching these tokens off. Most people connect Zendesk by signing in: see [Zendesk](/connectors/zendesk). This article is for the fallback: connecting with a Zendesk **API token** you already have. > [!WARNING] > Zendesk stopped creating new API tokens on 27 October 2026 and switches existing ones off on 30 April 2027. Tokens unused for 30 days already stop working, and Zendesk accounts created since 28 July 2026 can't use tokens. Use this only if you have a token that's still active; otherwise use **Sign in with Zendesk**. ## When you'd use a token - You have an active Zendesk API token and prefer to use it. - **Sign in with Zendesk** isn't available. The **Connect Zendesk** page then shows **Connect with an existing API token** with the note *Zendesk sign-in isn't set up on this server, so connect with a token you already have.* ## What you need - Your Zendesk address (the part before `.zendesk.com`). - An active Zendesk API token. - The email address of the agent your AI should act as. Its actions appear in Zendesk as that agent. It must be an agent or admin, not an end user. ## Connect with a token 1. In [app.plugsight.app](https://app.plugsight.app), go to **Connections** and click **Add connection**. 2. Click the **Zendesk** tile. 3. If you see **Sign in with Zendesk**, open **Have an older Zendesk API token? (most people don't need this)** below it. 4. In **Your Zendesk address**, type the part before `.zendesk.com`. 5. Optional: type a **Name**, for example "Support desk". 6. Type the agent's email address in **Agent email**. 7. Paste the token into **API token**. 8. Click **Test connection & save**. Plugsight checks the token with Zendesk before saving anything. You then see a message such as `Connected yourcompany.zendesk.com as Jane Smith (agent), id "support-desk".` Once connected, a token connection works exactly like a signed-in one: the same actions, the same **Can reply & update** switch and the same approval in the chat. See [Zendesk](/connectors/zendesk). ## Moving from a token to sign-in Before your token stops working, connect the same Zendesk again with **Continue with Zendesk**, signing in as the same agent. Plugsight recognises the same agent on the same Zendesk and replaces the token with the sign-in, keeping your settings. The message then says **Reconnected**. ## Troubleshooting ### Could not connect: Zendesk rejected the credentials. Check the agent email and API token. Zendesk no longer issues new tokens, so use Sign in with Zendesk if this one was removed. **What it means:** Zendesk didn't accept the email and token together. The token may be mistyped, switched off, unused for over 30 days, or belong to another Zendesk. **How to fix it:** check the agent email and token. If the token no longer works, connect with **Sign in with Zendesk** instead: Zendesk won't issue a new token. ### Could not connect: That Zendesk user isn't an agent. Use an agent or admin account. **What it means:** the email belongs to an end user (customer). **How to fix it:** use the email of an agent or admin. ### Enter your Zendesk address, like yourcompany.zendesk.com. **What it means:** **Your Zendesk address** was empty or couldn't be read. **How to fix it:** type the part before `.zendesk.com`, for example `yourcompany`. ### The connection says it needs reconnecting: "Zendesk rejected the API token." **What it means:** a token that was working has stopped, for example because it was switched off or went unused for 30 days. **How to fix it:** connect again with **Sign in with Zendesk**, as the same agent. See [Moving from a token to sign-in](#moving-from-a-token-to-sign-in). ## Related articles - [Zendesk](/connectors/zendesk) --- # How your AI analyses marketing data URL: https://docs.plugsight.app/connectors/marketing-data How the AI's marketing tools pull data from Google Ads, Microsoft Advertising, Meta Ads, LinkedIn Ads, TikTok Ads, Search Console and GA4, with example questions to ask. When you connect Google Ads, Microsoft Advertising, Meta Ads, LinkedIn Ads, TikTok Ads, Google Search Console or Google Analytics 4, your AI gets one shared set of marketing tools. The same tools work for all seven, so one question can cover every site, property and ad account you have connected. TikTok Ads is coming soon, once TikTok approves Plugsight's access. You don't need to know the tool names. Ask in plain English and your AI picks the right tool. The names are shown here because your AI app may display them when it uses one. > [!NOTE] > Marketing and analytics connectors are on the **Pro** and **Agency** plans. The Free plan includes 1 marketing connection and 25 marketing tool calls a month to try them; every tool on this page counts as a marketing tool call, and calls that fail don't count. ## Which connectors these tools cover | Connector | What the tools read | | --- | --- | | [Google Ads](/connectors/google-ads) | Campaigns, ad groups, keywords, search terms, ads, products, locations, conversions and impression share | | [Microsoft Advertising](/connectors/microsoft-advertising) | The same kinds of data for Bing Ads, plus age, gender, audiences and Performance Max asset groups | | [Meta Ads](/connectors/meta-ads) | Facebook and Instagram campaigns, ad sets and ads: spend, reach, frequency, clicks, purchases, leads and ROAS, by age, gender, country, platform, placement and device | | [LinkedIn Ads](/connectors/linkedin-ads) | Campaign groups, campaigns and ads: spend, clicks, landing page clicks, website conversions, Lead Gen Form leads, engagement and ROAS | | [TikTok Ads](/connectors/tiktok-ads) (coming soon) | TikTok campaigns, ad groups and ads: spend, reach, clicks, conversions, purchases, ROAS and video views, by age, gender, country and device platform | | [Google Search Console](/connectors/google-search-console) | Organic clicks, impressions, CTR and position by query, page, country, device and search appearance | | [Google Analytics 4](/connectors/google-analytics-4) | Sessions, users, engagement, key events, revenue, ecommerce and any GA4 dimension or metric | [Google Tag Manager](/connectors/google-tag-manager), [YouTube](/connectors/youtube) and [Google Merchant Center](/connectors/google-merchant-center) have their own tools, described on their pages. [PageSpeed Insights](/connectors/pagespeed-insights) works on every MCP server without a connection. ## The tools ### List marketing accounts (`list_marketing_accounts`) Lists your marketing connections and everything they reach: Search Console sites, GA4 properties, Google Ads accounts (including client accounts under a manager), Microsoft Advertising accounts, Meta ad accounts, LinkedIn ad accounts and TikTok ad accounts. Your AI calls this first, to learn the names and ids of your accounts. - Hidden sites and accounts are left out. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). - The list is kept for 15 minutes. Your AI can ask for a fresh list if you have just added an account at Google, Microsoft, Meta, LinkedIn or TikTok. - If a service didn't answer, the list includes the error, so your AI can tell you. ### List data fields (`list_marketing_fields`) Shows every field your AI can ask for, for one connector, split into **dimensions** (what you group by, such as campaign, keyword, query or landing page) and **metrics** (the numbers, such as cost, clicks or sessions). Your AI uses it to pick the right fields before pulling data. Some metrics are worked out from others: CTR, CPC, CPM, CPA, ROAS and conversion rate. These are recalculated after rows are combined, so they stay correct when you add several accounts together. For GA4, any GA4 field name also works, including your custom dimensions and metrics. ### Get marketing data (`get_marketing_data`) The main tool. It pulls any mix of dimensions and metrics from one connector, for one account, several, or all of them at once, and returns a table with totals. Plugsight picks the right report automatically: asking for search terms uses the search-term report, asking for keywords uses the keyword report. What your AI can set: | Setting | What it does | Default | | --- | --- | --- | | Accounts | Which accounts, properties or sites to include | All visible ones | | Date range | A preset (today, yesterday, last 7, 14, 28, 30, 90, 180 or 365 days, this month, last month, this year, last year) or exact dates | Last 30 days | | Filters | Conditions such as "conversions equal 0" or "cost greater than 20". Text matching ignores capital letters. All filters must match | None | | Order | Which column to sort by | The first metric, highest first | | Row limit | How many rows come back, after sorting | 500 (up to 50,000) | | Rows per account | How many rows are fetched from each account before combining | 100,000 (100 to 500,000) | | Totals | Whether to add a totals row | On | Extra options: - **Search Console**: the search type (web, image, video, news, Discover or Google News), and whether to include fresh, not-yet-final data (included by default). - **Google Ads**: whether to include removed campaigns. "Last 30 days" means the 30 full days before today. Dates use UTC. Meta Ads and TikTok Ads read at most 10,000 rows per ad account for each question. Raising **Rows per account** can't lift that. When an answer says it's partial, ask again for a shorter date range, fewer breakdowns or fewer ad accounts. LinkedIn Ads returns at most 15,000 rows per ad account for each question. When an answer says it's partial, ask again for a shorter date range, monthly instead of daily rows, or campaigns instead of ads. #### Rows from several accounts When you ask about several accounts, rows with the same values are added together. For example, the same search term in two accounts becomes one row. To see each account separately, ask your AI to split by account ("show it per account"). If your accounts use different currencies, money is added as-is and your AI is told so. Ask it to split by account or currency to keep them apart. #### Data notes Google and Microsoft sometimes hold data back. When that affects an answer, Plugsight adds a note your AI can pass on, for example: - Google Ads hides low-volume search terms for privacy. Their cost is in campaign totals but not in the search-term rows. - Search Console hides rare queries. The note says what share of clicks and impressions that is. - Search Console data becomes final about 2–3 days after the date, so the latest days may still grow. - GA4 can apply data thresholds (for example with age and gender), sample results, or group rare values into "(other)". - GA4's daily API quota is running low. - A report stopped at the per-account row limit. ### Deep dives (`marketing_deep_dive`) Ready-made analyses that run several queries and return findings plus tables. | Deep dive | What it finds | Works with | | --- | --- | --- | | Account overview | Every connected platform and account, this period against the previous one: spend, conversions, CPA, ROAS, organic clicks, sessions and revenue | All four | | Wasted spend | Search terms and keywords that cost money without converting, the share of budget wasted, and negative-keyword candidates | Google Ads, Microsoft Advertising | | Scale opportunities | Campaigns and keywords at or below your average CPA that lose impression share to budget or rank | Google Ads, Microsoft Advertising | | Search term winners | Converting search terms that aren't keywords yet | Google Ads, Microsoft Advertising | | Quality score audit | Spend by quality score, and which part (expected CTR, ad relevance or landing page) drags low scores down | Google Ads, Microsoft Advertising | | Paid vs organic | Where you pay for clicks on queries you already rank top 3 for, paid winners with weak SEO, and organic queries worth a paid test | Google Ads or Microsoft Advertising, with Search Console | | SEO opportunities | Queries just off page one, page-one results with low CTR, and pages losing clicks | Search Console | | Period comparison | Any metrics, this period against the previous period or the same period last year, with the biggest gains and drops | Any of the four | Defaults your AI can change: the last 30 days, compared with the previous period; at least 10 in spend for wasted-spend lists; at least 1 conversion for winners and scale reports; at least 100 impressions for SEO reports; 25 rows per table (up to 1,000). Ad reports use Google Ads unless you ask for Microsoft Advertising. ### Tools for questions reports can't answer | Tool | What it does | | --- | --- | | `search_console_inspect_url` | How Google sees one URL: whether it's indexed, last crawl, canonical, mobile usability and rich results | | `search_console_sitemaps` | Sitemaps submitted for a site, with submitted and indexed counts, errors and warnings | | `analytics_realtime` | GA4 activity in the last 30 minutes, for example active users by country or page | | `analytics_key_events` | The events a GA4 property counts as key events (conversions), and how many happened in a period | | `analytics_funnel` | A funnel of 2 to 10 steps (events or page visits), showing how many users reach each step and where they drop off. Can be split by device or channel | | `analytics_metadata` | Every dimension and metric a GA4 property offers, including its custom ones | | `google_ads_query` | Runs a read-only Google Ads Query Language (GAQL) query against one account, for anything else. Only SELECT queries are allowed | | `microsoft_ads_campaigns` | Campaign settings in a Microsoft Advertising account: status, type, budget and bidding strategy | | `meta_ads_campaigns` | Campaign settings in a Meta ad account: status, objective, budget and bid strategy | | `linkedin_ads_campaigns` | Campaign settings in a LinkedIn ad account: status, type, objective, campaign group, budget, bid and schedule | | `tiktok_ads_campaigns` | Campaign settings in a TikTok ad account: status, objective and budget | ## Example questions **Across everything** - "Give me an overview of all my marketing accounts this month against last month." - "Compare spend, conversions and CPA by platform for the last 90 days." **Paid search** - "Which search terms cost us money last month without converting? Suggest negative keywords." - "Which keywords convert below our average CPA but lose impression share to budget?" - "Which keywords have a quality score of 5 or less, and is expected CTR or the landing page the problem?" - "Which converting search terms aren't keywords yet?" - "Across all client accounts, which ones spent more than 20% over last month?" **SEO** - "Which queries rank in positions 4–20 with the most impressions?" - "Which page-one results get much lower CTR than expected for their position?" - "Is https://example.com/pricing indexed, and if not, why?" - "Where are we paying for Google Ads clicks on queries we already rank top 3 for?" **Analytics** - "Which channels drove the most revenue this month vs last month?" - "Build a funnel from product page to purchase and show where mobile users drop off." - "How many people are on the site right now, and from which countries?" - "What counts as a conversion in this GA4 property, and how many happened last week?" > [!TIP] > With several accounts, name the one you mean: "for Bright Dental's Google Ads" or "on the shop's GA4 property". Clear connection names on **Connections** make this easier. ## Common messages ### Unknown field "…" for Google Ads. Call list_marketing_fields. **What it means:** Your AI asked for a field that connector doesn't have. The message may suggest similar names. **How to fix it:** Usually your AI corrects itself. If not, ask it to "list the available fields first". ### These fields come from different Google Ads reports and can't be combined in one query **What it means:** Some fields live in separate reports at Google or Microsoft (for example search terms and quality score) and can't be pulled together. **How to fix it:** Ask for them in two separate questions. The same applies to the Microsoft Advertising version of this message. ### No Google Ads accounts are connected and visible. **What it means:** None of the MCP server's connections reach an account of that type, or every one is hidden. **How to fix it:** Check the connection is in this MCP server, and show the account again under **Show sites & accounts** on **Connections**. ### No connection in this MCP reaches Google Analytics 4 "…" (or it is hidden). **What it means:** The site, property or account named isn't reachable by this MCP server, or you have hidden it. **How to fix it:** Check the id is right, that the account is visible, and that its connection is part of this MCP server. If you added it at Google minutes ago, use **Refresh list** on **Connections**. ### This report needs connector google_ads or bing_ads. **What it means:** Wasted spend, scale opportunities, search term winners and quality score audit only work for ad platforms. **How to fix it:** Ask for the report on Google Ads or Microsoft Advertising. ### period_comparison needs fields, e.g. [campaign, cost, conversions, cpa]. **What it means:** A period comparison needs to know what to compare. **How to fix it:** Say what you want compared, for example "compare cost and conversions by campaign with last month". ### Report … still pending after 2 minutes; try a shorter date range. **What it means:** Microsoft builds reports on request, and a long range took too long. **How to fix it:** Ask for a shorter date range. ## Related articles - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts) - [Google Ads](/connectors/google-ads) - [Microsoft Advertising](/connectors/microsoft-advertising) - [Meta Ads](/connectors/meta-ads) - [LinkedIn Ads](/connectors/linkedin-ads) - [TikTok Ads](/connectors/tiktok-ads) - [Google Search Console](/connectors/google-search-console) - [Google Analytics 4](/connectors/google-analytics-4) --- # Choose which sites and accounts your AI can see URL: https://docs.plugsight.app/connectors/hide-sites-and-accounts Hide or show individual Search Console and Bing sites, GA4 properties, ad accounts, drives and calendars, and refresh the list after changes. One Google or Microsoft sign-in often reaches many things: every Search Console site, GA4 property or Google Ads account that login can open. You can hide any of them from your AI, for example to keep a client's account or a test site out of answers. ## Which connections have a list | Connection | What's listed | Button on Connections | | --- | --- | --- | | Google Search Console | Sites and domain properties | **Show sites & accounts** | | Google Analytics 4 | GA4 properties | **Show sites & accounts** | | Google Ads | Ad accounts, including client accounts under a manager | **Show sites & accounts** | | Microsoft Advertising | Ad accounts | **Show sites & accounts** | | Bing Webmaster Tools | Sites | **Show sites & accounts** | | Google Tag Manager | Containers | **Show sites & accounts** | | YouTube | Channels | **Show sites & accounts** | | Google Merchant Center | Merchant Center accounts | **Show sites & accounts** | | Google Drive | My Drive and your shared drives | **Show drives** | | Calendars | Each calendar | **Show calendars** | Google Sheets, Docs, Forms and Meet show a single line saying what they reach (for example "Any spreadsheet you can open, by link"), because they open files by link rather than from a list. To keep one of these away from an AI, leave the connection out of that MCP server instead. ## Hide or show an item 1. Open **Connections**. 2. Find the connection and click **Show sites & accounts** (or **Show drives**, **Show calendars**). 3. Find the item. If there are more than 8, type in the **Search…** box. Items are shown 10 to a page. 4. Click the switch next to it. **Visible** means your AI can use it; **Hidden** means it can't. The heading of each group shows how many are visible, for example "3 of 12 visible to AI apps". To change many at once, click **Hide all** or **Show all**. If you typed in the search box, these change only the items that match your search. ## What hiding does - A hidden item is invisible to your AI on **every** MCP server, even if it asks for it by name. - Nothing changes at Google, Microsoft or Bing. The site, property or account is untouched, and you can show it again any time. - Each change is recorded on **Activity**, for example "Hid … from AI apps". - Hiding is per connection. If two connections reach the same account, hide it on both. > [!TIP] > To give a client their own AI link with only their data, create a separate MCP server that reaches only that client's connections. Hiding works on every server at once, so it can't hide one client's ad account from one server only: if a single login reaches several clients, use a separate login per client instead. See [Use several MCP servers](/mcp-servers/multiple-servers). ## Refresh the list Plugsight remembers what a login reaches for 15 minutes. If you have just added a site, property, account or calendar at Google, Microsoft or Bing: 1. Open the connection's list on **Connections**. 2. Click **Refresh list** at the bottom. New items appear as **Visible**. Your AI can also ask for a fresh list itself when it can't find something you named. ## What the labels mean - **Domain property**: a Search Console property that covers a whole domain, including every subdomain and both http and https. - The small grey text under a name shows its id and, where useful, more detail: the account currency for ad accounts, the Analytics account for GA4 properties, "shared drive" for shared drives, or "primary" for your main calendar. ## Troubleshooting ### "Google Ads didn't answer: …" **What it means:** Plugsight couldn't load that service's list. The rest of the connection may still work. **How to fix it:** Click **Refresh list**. If it keeps failing, click **Reconnect** next to the connection, or remove it and connect it again. ### "This login doesn't reach anything yet." **What it means:** The account you signed in with has no sites, properties or ad accounts, or no access to them. **How to fix it:** Make sure you signed in with the Google or Microsoft account that has access. If you need to, add that account as a user at Google or Microsoft, then click **Refresh list**. Otherwise remove the connection and connect again with the right account. ### My AI says it can't find a site or account I can see here **What it means:** It may be hidden, or the connection isn't part of the MCP server you're using. **How to fix it:** Check the switch says **Visible**. Then open **MCP servers** and check the server reaches that connection. ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [All connectors](/connectors) --- # Google Ads URL: https://docs.plugsight.app/connectors/google-ads Connect Google Ads so your AI can analyse campaigns, keywords, search terms and conversions across every account, including MCC clients. Connect Google Ads and your AI can answer questions about campaigns, keywords, search terms, ads and conversions in every Google Ads account your Google login can open, including client accounts under a manager (MCC) account. Plugsight only reads: it never changes campaigns, bids, budgets or keywords. ## What your AI can do - Report on campaigns, ad groups, keywords, search terms, ads, products and locations, for any date range. - Show cost, clicks, impressions, conversions, conversion value, CPA, ROAS and CTR. - Show quality score and its three parts: expected CTR, ad relevance and landing page experience. - Show impression share and the share lost to budget or rank. - Break results down by device, network, location, landing page, hour, day of the week, week, month, quarter or year. - Add up several accounts in one answer, or compare them side by side. - Run ready-made deep dives: wasted spend, scale opportunities, search term winners, quality score audit, paid vs organic, and period comparison. - Run any read-only Google Ads Query Language (GAQL) query for anything else. See [How your AI analyses marketing data](/connectors/marketing-data) for how these tools work. ### Example questions - "Which search terms cost us money last month without converting? Suggest negative keywords." - "Which keywords convert below our average CPA but lose impression share to budget?" - "Compare CPA and ROAS by campaign this month vs last month." - "Which keywords have a quality score of 5 or less, and is expected CTR or the landing page the problem?" - "Across all client accounts, which ones spent more than 20% over last month?" ## What you need - A **Pro** or **Agency** plan, or the Free plan to try it: Free includes 1 marketing connection and 25 marketing tool calls a month. See [Plans](/get-started/plans). - A Google account that can open your Google Ads accounts. If you manage clients, sign in with the account that has access to your manager (MCC) account: Plugsight finds every client under it. ## Connect Google Ads 1. Open **Connections** and click **Add connection**. 2. Choose **Google Ads**. 3. Read **What happens next** and click **Continue to Google**. 4. Choose the Google account that can see your ad accounts. 5. If Google says **"Google hasn't verified this app"**, click **Advanced**, then **Go to Plugsight (unsafe)**. Google shows this while it reviews new apps; it doesn't mean anything is wrong. 6. Google asks: "See, edit, create and delete your Google Ads accounts and data". Tick the box and continue. Without the tick, the connection can't work. 7. You're back on **Connections**, with a message such as "Connected you@example.com: 12 Google Ads accounts." > [!NOTE] > Google offers no read-only permission for Google Ads, so it asks for full access. Plugsight only ever reads from it. Then add the connection to an MCP server (or use a server set to **All accounts**). If this is your first marketing connection, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. To choose which accounts your AI can see, click **Show sites & accounts** next to the connection. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## What it can and can't change Google Ads is **read-only** in Plugsight. Your AI can't pause campaigns, change bids or budgets, add keywords or edit ads. The **Write access** column shows **Read-only** and there is no switch to turn changes on. ## Limits - **Manager accounts** can't report their own metrics. Your AI reports on the client accounts under them instead. - **Search terms**: Google hides low-volume search terms for privacy. Their cost is still in campaign totals, but not in search-term rows. Your AI is told when this affects an answer. - **Currencies**: accounts in different currencies are added as-is, and your AI is told so. Ask it to split results by account. - **Removed campaigns** are left out unless you ask for them. - **Rows**: up to 100,000 rows are fetched per account by default (up to 500,000), and up to 50,000 rows are returned. GAQL queries return up to 50,000 rows. - Some fields come from separate Google Ads reports and can't be pulled together in one question. ## Troubleshooting ### Marketing and analytics connectors (Google Ads, Microsoft Ads, Search Console, GA4 and others) are on the Pro plan. Upgrade under Billing to connect them. **What it means:** Your plan doesn't include marketing connectors. In the catalog, the tile says **On Pro: upgrade to connect**. **How to fix it:** Upgrade to Pro or Agency on **Billing**, then connect again. ### The Google Ads tile says Unavailable **What it means:** Google Ads isn't set up on this Plugsight server. **How to fix it:** Contact info@plugsight.app. ### "…the Google Ads developer token only has test access, so real ad accounts are blocked." **What it means:** Google is only allowing test accounts for now. **How to fix it:** Contact info@plugsight.app. Your connection is saved and starts working once the access is approved; then click **Refresh list**. ### Google Ads access wasn't granted. Tick the permission and try again. **What it means:** The permission box on Google's screen wasn't ticked. **How to fix it:** Connect again and tick the box at step 6. ### You didn't allow access in Google. Click Connect again and allow it, ticking every permission box. **What it means:** You clicked **Cancel** or didn't allow access on Google's screen. **How to fix it:** Connect again and allow access. ### Google returned no refresh token. Remove the app's access in your Google account and try again. **What it means:** Google didn't give Plugsight lasting access, usually because access was granted before. **How to fix it:** In your Google account's security settings, remove Plugsight's access, then connect again. ### The Google sign-in expired before it finished. Click Connect and sign in again. **What it means:** The sign-in page was left open too long. **How to fix it:** Start again from **Add connection**. ### "customer 123…: …" when listing accounts **What it means:** One of the accounts your login can open didn't answer. Cancelled or suspended accounts often show up this way. **How to fix it:** You can ignore it for cancelled accounts. Otherwise click **Refresh list**, or check the account in Google Ads. ### Reconnect needed: "Google sign-in was revoked or has expired." **What it means:** Google stopped accepting the login, for example after a password change or after access was removed in your Google account. **How to fix it:** Click **Reconnect** next to the connection. Your settings and MCP servers stay as they are. ### My AI doesn't see Google Ads **What it means:** The connection isn't in the MCP server you're using, the account is hidden, or your AI app hasn't loaded the marketing tools yet. **How to fix it:** Check the MCP server reaches this connection, check the account shows **Visible**, then [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts) - [Microsoft Advertising](/connectors/microsoft-advertising) - [Google Search Console](/connectors/google-search-console) - [Google Analytics 4](/connectors/google-analytics-4) - [Bing Webmaster Tools](/connectors/bing-webmaster) --- # Microsoft Advertising URL: https://docs.plugsight.app/connectors/microsoft-advertising Connect Microsoft Advertising (Bing Ads) so your AI can report on campaigns, keywords, search queries and conversions next to Google Ads. Connect Microsoft Advertising (formerly Bing Ads) and your AI can report on every ad account your Microsoft login can open, in the same conversation as Google Ads. Plugsight only reads: it never changes campaigns, bids, budgets or keywords. ## What your AI can do - Report on campaigns, ad groups, keywords, search queries, ads and locations, for any date range. - Show cost, clicks, impressions, conversions, revenue, CPA and ROAS. - Show quality score and its parts, and impression share lost to budget or rank. - Break results down by age, gender, audience, where searchers actually were, device, network, hour of day and day of the week. - Report on Shopping products and Performance Max asset groups. - Show campaign settings: status, type, budget and bidding strategy. - Run deep dives: wasted spend, scale opportunities, search term winners, quality score audit and period comparison. See [How your AI analyses marketing data](/connectors/marketing-data) for how these tools work. ### Example questions - "How did Microsoft Ads perform last month compared with Google Ads?" - "Which Bing search queries spent money without converting?" - "Show cost and conversions by campaign per week for the last quarter." - "Which keywords have the lowest quality score and highest spend?" - "Which campaigns are losing impression share to budget?" - "Which hours of the day and age groups convert best on Bing?" ## What you need - A **Pro** or **Agency** plan, or the Free plan to try it: Free includes 1 marketing connection and 25 marketing tool calls a month. See [Plans](/get-started/plans). - A Microsoft account that is a user on your Microsoft Advertising accounts. ## Connect Microsoft Advertising 1. Open **Connections** and click **Add connection**. 2. Choose **Microsoft Advertising (Bing Ads)**. 3. Sign in with Microsoft, using the account that can open your ad accounts. 4. Click **Accept**. 5. You're back on **Connections**, with a message such as "Connected you@example.com: 3 Microsoft Advertising accounts." Then add the connection to an MCP server (or use a server set to **All accounts**). If this is your first marketing connection, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. To choose which ad accounts your AI can see, click **Show sites & accounts** next to the connection. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## What it can and can't change Microsoft Advertising is **read-only** in Plugsight. Your AI can't pause campaigns, change bids or budgets, or edit ads and keywords. ## Limits - Microsoft builds each report on request, so long date ranges can take a few seconds longer. If a report isn't ready after 2 minutes, your AI is asked to try a shorter range. - Accounts in different currencies are added as-is, and your AI is told so. Ask it to split results by account. - Some fields come from separate Microsoft reports and can't be pulled together in one question. ## Troubleshooting ### Your Free plan includes 1 marketing connection. Upgrade to Pro to connect more. **What it means:** the Free plan includes 1 marketing or analytics connection to try, and you already have that many. **How to fix it:** remove the marketing connection you don't need on **Connections**, or upgrade to Pro or Agency on **Billing**. ### The tile says Unavailable **What it means:** Microsoft Advertising isn't set up on this Plugsight server. **How to fix it:** Contact info@plugsight.app. ### Your organisation needs an administrator to approve Plugsight in Microsoft. **What it means:** Your company restricts which apps can use Microsoft sign-in. **How to fix it:** Ask your IT admin to approve Plugsight. If you are the admin, sign in and tick **Consent on behalf of your organisation**. ### Microsoft didn't grant lasting access. Remove Plugsight at myapps.microsoft.com, then connect again. **What it means:** Microsoft didn't give Plugsight the access it needs to keep working. **How to fix it:** Go to myapps.microsoft.com, remove Plugsight, then connect again. ### We couldn't read this account's email address. **What it means:** The Microsoft account you chose has no email address Plugsight can read. **How to fix it:** Sign in again, choosing an account that has an email address. ### You didn't allow access in Microsoft. Click Connect again and allow it, ticking every permission box. **What it means:** You cancelled on Microsoft's screen. **How to fix it:** Connect again and click **Accept**. ### This login doesn't reach anything yet. **What it means:** The Microsoft account isn't a user on any Microsoft Advertising account. **How to fix it:** Add that Microsoft account as a user in Microsoft Advertising, then click **Refresh list**. Or connect again with the right account. ### Microsoft Advertising failed to build the report. **What it means:** Microsoft couldn't produce the report you asked for. **How to fix it:** Ask again with fewer fields or a shorter date range. ### Report … still pending after 2 minutes; try a shorter date range. **What it means:** The report took too long at Microsoft. **How to fix it:** Ask for a shorter date range. ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts) - [Google Ads](/connectors/google-ads) - [Google Ads vs Microsoft Advertising](/recipes/google-vs-microsoft-ads) - [Meta Ads](/connectors/meta-ads) --- # Meta Ads URL: https://docs.plugsight.app/connectors/meta-ads Connect Meta Ads so your AI can report on Facebook and Instagram ad spend, reach, results and ROAS next to Google and Microsoft Ads. Read-only. Connect Meta Ads and your AI can report on every Facebook and Instagram ad account your Facebook login can open, in the same conversation as Google Ads and Microsoft Advertising. Plugsight only reads: it never changes campaigns, ad sets, ads, budgets or audiences. ## What your AI can do - Report on ad accounts, campaigns, ad sets and ads, for any date range, per day or per month. - Show spend, impressions, reach, frequency, clicks, link clicks, CTR, CPC and CPM. - Show purchases, purchase value, ROAS, leads, cost per lead, adds to cart, checkouts started, registrations and landing page views. - Break results down by age, gender, country, region, platform (Facebook, Instagram, Audience Network, Messenger), placement, device and hour of the day. - Show campaign settings: status, objective, budget and bid strategy. - Include Meta Ads in the account overview and period comparison deep dives. See [How your AI analyses marketing data](/connectors/marketing-data) for how these tools work. ### Example questions - "How much did we spend on Meta last month, and what was the ROAS by campaign?" - "Which ad sets have the highest cost per lead this month?" - "Is Instagram or Facebook cheaper per purchase for us?" - "Which ads are being shown too often to the same people?" - "Compare Meta, Google Ads and Microsoft Ads spend and conversions for the last 30 days." ## What you need - A **Pro** or **Agency** plan, or the Free plan to try it: Free includes 1 marketing connection and 25 marketing tool calls a month. See [Plans](/get-started/plans). - A Facebook account that can open your ad accounts in Meta Ads Manager. ## Connect Meta Ads 1. Open **Connections** and click **Add connection**. 2. Choose **Meta Ads (Facebook & Instagram)**. 3. Log in to Facebook with the account that can open your ad accounts, if you aren't logged in already. 4. Meta shows that Plugsight wants to read your ads. Continue, leaving that permission on. 5. You're back on **Connections**, with a message such as "Connected Alex Morgan: 3 Meta ad accounts." Then add the connection to an MCP server (or use a server set to **All accounts**). If this is your first marketing connection, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. To choose which ad accounts your AI can see, click **Show sites & accounts** next to the connection. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## What it can and can't change Meta Ads is **read-only** in Plugsight. It only asks Meta for permission to read your ads, so your AI can't pause campaigns, change budgets or bids, or edit ads and audiences. ## Limits - Meta's sign-ins last about 60 days and can't be renewed in the background. When yours expires, the connection asks to be reconnected: connect it again the same way. - Conversions and conversion value count purchases. To count another result, such as leads, ask your AI to use that result instead. - Reach counts each person once, so it can't be added up across days or ad accounts. For one ad account, ask for it without a daily split to get one figure. Across several ad accounts, combined reach shows as empty: ask for reach by account instead. - Meta only allows some breakdowns together: age with gender, and platform with placement and device. Ask for other combinations in separate questions. - Accounts in different currencies are added as-is, and your AI is told so. Ask it to split results by account. ## Troubleshooting ### Your Free plan includes 1 marketing connection. Upgrade to Pro to connect more. **What it means:** the Free plan includes 1 marketing or analytics connection to try, and you already have that many. **How to fix it:** remove the marketing connection you don't need on **Connections**, or upgrade to Pro or Agency on **Billing**. ### Meta Ads isn't set up on this server yet. **What it means:** This Plugsight server has no Meta app set up. **How to fix it:** Contact info@plugsight.app. ### You didn't allow access in Meta. Click Connect again and allow it, ticking every permission box. **What it means:** You cancelled on Meta's screen. **How to fix it:** Connect again and continue on Meta's screen. ### Meta Ads access wasn't granted. Click Connect again and allow Plugsight to read your ads. **What it means:** You turned off the permission to read your ads on Meta's screen. **How to fix it:** Connect again and leave that permission on. ### This login doesn't reach anything yet. **What it means:** The Facebook account has no ad accounts it can open. **How to fix it:** Ask the ad account's admin to give that Facebook account access in Meta, then click **Refresh list**. Or connect again with the right account. ### This Meta Ads sign-in expired on …: Meta sign-ins last about 60 days. Reconnect Meta Ads on the Connections page. **What it means:** About 60 days have passed since you connected, and Meta's sign-in has run out. **How to fix it:** On **Connections**, connect Meta Ads again. Your hidden ad accounts and MCP servers stay as they were. ### Meta no longer accepts this Meta Ads sign-in: it expired (Meta sign-ins last about 60 days) or access was removed. Reconnect Meta Ads on the Connections page. **What it means:** Meta stopped accepting the sign-in early, for example because the Facebook password changed or Plugsight was removed from the account's apps. **How to fix it:** On **Connections**, connect Meta Ads again. ### Meta is limiting requests … right now. Wait a few minutes before asking again, and ask for fewer accounts or a shorter date range. **What it means:** Meta allows only so many requests in a short time, for a login, an ad account or an app. **How to fix it:** Wait a few minutes, then ask again, ideally about fewer ad accounts or a shorter period. ### Meta can't return that much data at once. Ask for a shorter date range, fewer fields or fewer accounts. **What it means:** The question asked Meta for more rows than it returns in one go. **How to fix it:** Ask about a shorter period, fewer breakdowns or fewer ad accounts. ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts) - [Google Ads](/connectors/google-ads) - [Microsoft Advertising](/connectors/microsoft-advertising) - [LinkedIn Ads](/connectors/linkedin-ads) - [TikTok Ads](/connectors/tiktok-ads) - [Reconnect a connection](/troubleshooting/reconnect-needed) --- # LinkedIn Ads URL: https://docs.plugsight.app/connectors/linkedin-ads Connect LinkedIn Ads so your AI can report on Campaign Manager spend, clicks, leads, conversions and ROAS next to your other ad platforms. Read-only. Connect LinkedIn Ads and your AI can report on every LinkedIn ad account you have a role on in Campaign Manager, in the same conversation as Google Ads, Microsoft Advertising and Meta Ads. Plugsight only reads: it never changes campaigns, ads, budgets, bids or audiences. ## What your AI can do - Report on ad accounts, campaign groups, campaigns and ads, for any date range, per day or per month. - Show spend, impressions, clicks, landing page clicks, CTR, CPC and CPM. - Show website conversions, conversion value, ROAS, Lead Gen Form leads, form opens and cost per lead. - Show video views, engagements, reactions, comments, shares and follows. - Show campaign settings: status, type, objective, campaign group, budget, bid and schedule. - Include LinkedIn Ads in the account overview and period comparison deep dives. See [How your AI analyses marketing data](/connectors/marketing-data) for how these tools work. ### Example questions - "Which LinkedIn campaigns had the lowest cost per lead last month?" - "How much did each LinkedIn campaign group spend this quarter, and what did it bring in?" - "Which LinkedIn ads have the best click-through rate?" - "Compare LinkedIn, Google Ads and Meta spend and conversions for the last 30 days." ## What you need - A **Pro** or **Agency** plan. See [Plans](/get-started/plans). - A LinkedIn account with a role on your ad accounts in Campaign Manager. A viewer role is enough. ## Connect LinkedIn Ads 1. Open **Connections** and click **Add connection**. 2. Choose **LinkedIn Ads (Campaign Manager)**. 3. Sign in to LinkedIn with the account that has a role on your ad accounts, if you aren't signed in already. 4. LinkedIn shows that Plugsight wants to read your ads and their reporting. Allow it. 5. You're back on **Connections**, with a message such as "Connected Sam Lee: 2 LinkedIn ad accounts." Then add the connection to an MCP server (or use a server set to **All accounts**). If this is your first marketing connection, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. To choose which ad accounts your AI can see, click **Show sites & accounts** next to the connection. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## What it can and can't change LinkedIn Ads is **read-only** in Plugsight. It only asks LinkedIn for permission to read your ads, their reporting and your name, so your AI can't pause campaigns, change budgets or bids, or edit ads and audiences. ## Limits - Conversions and conversion value are website conversions, counted by the conversion tracking set up in Campaign Manager. Leads from LinkedIn's Lead Gen Forms are counted separately, as leads. - LinkedIn returns at most 15,000 rows for each ad account and question. When an answer says it's partial, ask for a shorter date range, monthly instead of daily rows, or campaigns instead of ads. - Accounts in different currencies aren't added together in the account overview: totals are given per currency. - LinkedIn's sign-ins last about 60 days. Plugsight renews them in the background when LinkedIn allows it; when it can't, the connection asks to be reconnected. ## For server admins: set up the LinkedIn app Plugsight's own service already has a LinkedIn app, so you don't need this to connect. It's for whoever runs a Plugsight server, which offers LinkedIn Ads only once its LinkedIn app is set up. 1. In the LinkedIn Developer Portal, create an app and associate it with your company's LinkedIn Page. 2. On the app's Products tab, request access to the Advertising API and fill in LinkedIn's access form. LinkedIn starts approved apps on a Development tier with lower limits. Check what each tier allows on LinkedIn's Increasing access page, and apply for the Standard tier if you need more. 3. On the app's Auth tab, add the server's redirect URL: its address followed by `/auth/linkedin/callback`, for example `https://app.plugsight.app/auth/linkedin/callback`. 4. Give the server the app's client ID and client secret, as described in the project's README. ## Troubleshooting ### Marketing and analytics connectors (…) are on the Pro plan. Upgrade under Billing to connect them. **What it means:** Your plan doesn't include marketing connectors. **How to fix it:** Upgrade to Pro or Agency on **Billing**, then connect again. ### LinkedIn Ads isn't set up on this server yet. **What it means:** This Plugsight server has no LinkedIn app set up. **How to fix it:** Contact info@plugsight.app. ### You didn't allow access in LinkedIn. Click Connect again and allow it, ticking every permission box. **What it means:** You cancelled on LinkedIn's screen. **How to fix it:** Connect again and allow access on LinkedIn's screen. ### LinkedIn Ads access wasn't granted. Click Connect again and allow Plugsight to read your ads and their reporting. **What it means:** LinkedIn didn't give Plugsight permission to read your ads or their reporting. **How to fix it:** Connect again and allow every permission LinkedIn asks for. ### This login doesn't reach anything yet. **What it means:** The LinkedIn account has no role on any ad account. **How to fix it:** Ask an admin of the ad account to add that LinkedIn account in Campaign Manager, then click **Refresh list**. Or connect again with the right account. ### This LinkedIn Ads sign-in expired on [date]. Reconnect LinkedIn Ads on the Connections page. **What it means:** The LinkedIn sign-in ran out and LinkedIn didn't let Plugsight renew it. **How to fix it:** On **Connections**, connect LinkedIn Ads again. Your hidden ad accounts and MCP servers stay as they were. ### LinkedIn no longer accepts this LinkedIn Ads sign-in: it expired or access was removed. Reconnect LinkedIn Ads on the Connections page. **What it means:** LinkedIn stopped accepting the sign-in, for example because Plugsight was removed from the account's permitted services or the yearly renewal ran out. **How to fix it:** On **Connections**, connect LinkedIn Ads again. ### LinkedIn is limiting requests right now. Wait a few minutes before asking again, and ask for fewer accounts or a shorter date range. **What it means:** LinkedIn allows only so many requests in a day, for Plugsight's app and for each member. Plugsight already waited and tried again. **How to fix it:** Wait a few minutes, then ask again, ideally about fewer ad accounts or a shorter period. If LinkedIn's message says a daily limit was reached, waiting minutes won't help: LinkedIn resets its daily limits at midnight UTC. ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts) - [Meta Ads](/connectors/meta-ads) - [Google Ads](/connectors/google-ads) - [Microsoft Advertising](/connectors/microsoft-advertising) - [Reconnect a connection](/troubleshooting/reconnect-needed) --- # TikTok Ads URL: https://docs.plugsight.app/connectors/tiktok-ads Connect TikTok Ads so your AI can report on TikTok ad spend, video views, clicks, conversions and ROAS next to your other ad platforms. Read-only. Connect TikTok Ads and your AI can report on every TikTok ad account you share with Plugsight, in the same conversation as Google Ads, Microsoft Advertising and Meta Ads. Plugsight only reads: it never changes campaigns, ad groups, ads, budgets or audiences. > [!IMPORTANT] > TikTok Ads is coming soon. TikTok is still reviewing Plugsight's access to its API for Business. Until TikTok approves it, only Plugsight admins can connect TikTok Ads, and it doesn't appear in your **Connector catalog**. If you already have a TikTok Ads connection, you can still reconnect it. ## What your AI can do - Report on ad accounts, campaigns, ad groups and ads, for any date range, per day or per month. - Show spend, impressions, reach, frequency, clicks, CTR, CPC and CPM. - Show conversions, cost per conversion, results, website purchases, purchase value and ROAS. - Show video views, 2-second and 6-second views, how far people watched (25%, 50%, 75% and 100%), likes, comments, shares, follows and profile visits. - Break results down by age, gender, country and device platform. - Show campaign settings: status, objective and budget. - Include TikTok Ads in the account overview and period comparison deep dives. See [How your AI analyses marketing data](/connectors/marketing-data) for how these tools work. ### Example questions - "How much did we spend on TikTok last month, and what was the ROAS by campaign?" - "Which TikTok ads have the best video completion rate this month?" - "Which age groups are cheapest per conversion on TikTok?" - "Compare TikTok, Meta and Google Ads spend and conversions for the last 30 days." ## What you need - A **Pro** or **Agency** plan. See [Plans](/get-started/plans). - A TikTok for Business login that can open your ad accounts in TikTok Ads Manager. ## Connect TikTok Ads 1. Open **Connections** and click **Add connection**. 2. Choose **TikTok Ads**. 3. Log in to TikTok for Business with the login that can open your ad accounts, if you aren't logged in already. 4. TikTok shows that Plugsight wants access to your ad accounts. Choose the ad accounts your AI may read, then confirm. 5. You're back on **Connections**, with a message such as "Connected Acme Shop and 1 more: 2 TikTok ad accounts." Then add the connection to an MCP server (or use a server set to **All accounts**). If this is your first marketing connection, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. To choose which ad accounts your AI can see, click **Show sites & accounts** next to the connection. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). To add an ad account you didn't share the first time, connect TikTok Ads again and choose it too: the existing connection is updated. ## What it can and can't change TikTok Ads is **read-only** in Plugsight. Plugsight only ever reads reports, ad accounts and campaign settings from TikTok, so your AI can't pause campaigns, change budgets or bids, or edit ads and audiences. ## Limits - Conversions are TikTok's own conversions column: the event each ad group is set to optimise for. Conversion value and ROAS use website purchase value. To see other results, ask for purchases or results instead. - TikTok reports at most 30 days at a time. Plugsight reads longer periods in 30-day parts and adds them up. - Reach counts each person once, so it can't be added up across days, 30-day parts or ad accounts. Ask for reach per day, or over 30 days or less, without a monthly split, for one ad account at a time. - When TikTok doesn't report a figure, it shows as empty, not as zero. - Rates and averages TikTok calculates, such as its own CTR or cost per conversion asked for by name, show as empty wherever rows are combined (across 30-day parts, months or ad accounts). Plugsight's own CTR, CPC, CPM, cost per conversion and ROAS are worked out from the totals, so they are given whenever the figures behind them are known. If TikTok doesn't report one of those figures, the result is empty, not zero. - If TikTok is busy or briefly down when Plugsight renews a sign-in, your AI is told to try again in a few minutes. You only need to reconnect if TikTok refuses the sign-in. - TikTok Ads reads at most 10,000 rows per ad account for each question. When an answer says it's partial, ask about a shorter period, fewer breakdowns or fewer ad accounts. - Accounts in different currencies are added as-is, and your AI is told so. Ask it to split results by account. ## Set up TikTok's developer app (server administrators) This is only needed if you run your own Plugsight server and see "TikTok Ads isn't set up on this server yet." TikTok needs a developer app before anyone can connect. Follow TikTok's own guides, linked below: 1. Register as a developer on TikTok API for Business with your TikTok for Business account. See [TikTok's developer registration guide](https://business-api.tiktok.com/portal/docs?id=1738855099573250). 2. Create a developer app for Plugsight. As the advertiser redirect URL, enter your server's address followed by `/auth/tiktok/callback`, for example `https://app.plugsight.app/auth/tiktok/callback`. See [TikTok's guide to creating a developer app](https://business-api.tiktok.com/portal/docs?id=1738855242728450). 3. Give the app read-only permissions only: reading ad account details and reporting. Plugsight never needs permission to manage ads. 4. Submit the app and wait for TikTok to approve it. 5. Copy the app's ID and secret into the server's `TIKTOK_APP_ID` and `TIKTOK_APP_SECRET` settings and restart it. TikTok Ads then appears under **Add connection**. TikTok's [authentication guide](https://business-api.tiktok.com/portal/docs?id=1738373164380162) explains how advertisers authorise an app. ## Troubleshooting ### Marketing and analytics connectors (…) are on the Pro plan. Upgrade under Billing to connect them. **What it means:** Your plan doesn't include marketing connectors. **How to fix it:** Upgrade to Pro or Agency on **Billing**, then connect again. ### TikTok Ads is coming soon. **What it means:** TikTok hasn't approved Plugsight's access to its API for Business yet, so TikTok Ads isn't open to everyone. **How to fix it:** Nothing to do for now. This article and [What's new](/whats-new) say when it's available. ### TikTok Ads isn't set up on this server yet. **What it means:** This Plugsight server has no TikTok developer app set up. **How to fix it:** Contact info@plugsight.app. If you run your own server, see [Set up TikTok's developer app](#set-up-tiktoks-developer-app-server-administrators). ### The TikTok sign-in didn't finish. Click Connect and sign in again. **What it means:** TikTok didn't confirm the sign-in, for example because it took too long or you cancelled on TikTok's screen. The message may end with what TikTok said. **How to fix it:** Connect again and confirm on TikTok's screen. ### No TikTok ad account was shared with Plugsight. Click Connect again and choose at least one ad account. **What it means:** You confirmed on TikTok's screen without choosing an ad account. **How to fix it:** Connect again and choose the ad accounts your AI may read. ### This login doesn't reach anything yet. **What it means:** The ad accounts you shared have since been removed from your TikTok for Business login, or you no longer have access to them. **How to fix it:** Ask the ad account's admin to give your login access in TikTok Ads Manager, then connect TikTok Ads again. ### TikTok no longer accepts this TikTok Ads sign-in: access was removed or the authorisation was revoked. Reconnect TikTok Ads on the Connections page. **What it means:** TikTok stopped accepting the sign-in, for example because Plugsight's access was removed from the ad account. **How to fix it:** On **Connections**, connect TikTok Ads again. Your hidden ad accounts and MCP servers stay as they were. ### This TikTok Ads sign-in expired on …, and TikTok can't renew it. Reconnect TikTok Ads on the Connections page. **What it means:** TikTok gave this sign-in an end date, and it has passed. **How to fix it:** On **Connections**, connect TikTok Ads again. ### TikTok is limiting requests right now. Wait a few minutes before asking again, and ask for fewer accounts or a shorter date range. **What it means:** TikTok allows only so many requests in a short time. Plugsight already waited and tried again a few times. **How to fix it:** Wait a few minutes, then ask again, ideally about fewer ad accounts or a shorter period. ### TikTok can't return that much data at once. Ask for a shorter date range, fewer fields or fewer accounts. **What it means:** The question asked TikTok for more data than it returns in one go. **How to fix it:** Ask about a shorter period, fewer breakdowns or fewer ad accounts. ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts) - [Meta Ads](/connectors/meta-ads) - [Google Ads](/connectors/google-ads) - [Reconnect a connection](/troubleshooting/reconnect-needed) --- # Google Search Console URL: https://docs.plugsight.app/connectors/google-search-console Connect Google Search Console so your AI can turn organic search data, URL inspection and sitemaps into SEO actions. Connect Google Search Console and your AI can read search performance for every site and domain property your Google login can open. Plugsight only reads: it never submits sitemaps, requests indexing or changes settings. ## What your AI can do - Report clicks, impressions, CTR and average position. - Break them down by query, page, country, device, date, hour and search appearance. - Cover web, image, video, news, Discover and Google News results. - Inspect one URL as Google sees it: whether it's indexed, last crawl, canonical, mobile usability and rich results. - List submitted sitemaps with submitted and indexed counts, errors and warnings. - Run deep dives: SEO opportunities, paid vs organic (with Google Ads or Microsoft Advertising), and period comparison. See [How your AI analyses marketing data](/connectors/marketing-data) for how these tools work. ### Example questions - "Which queries rank in positions 4–20 with the most impressions?" - "Which page-one results get much lower CTR than expected for their position?" - "Which pages lost the most clicks compared with last month?" - "Is https://example.com/pricing indexed, and if not, why?" - "Are there errors in our sitemaps?" - "Where are we paying for Google Ads clicks on queries we already rank top 3 for?" ## What you need - A **Pro** or **Agency** plan, or the Free plan to try it: Free includes 1 marketing connection and 25 marketing tool calls a month. See [Plans](/get-started/plans). - A Google account that has access to your sites in Search Console. ## Connect Google Search Console 1. Open **Connections** and click **Add connection**. 2. Choose **Google Search Console**. 3. Read **What happens next** and click **Continue to Google**. 4. Choose the Google account that can see your sites. 5. If Google says **"Google hasn't verified this app"**, click **Advanced**, then **Go to Plugsight (unsafe)**. 6. Google asks: "View Search Console data for your verified sites". Tick the box and continue. 7. You're back on **Connections**, with a message such as "Connected you@example.com: 4 Search Console sites." Then add the connection to an MCP server. If this is your first marketing connection, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. To choose which sites your AI can see, click **Show sites & accounts** next to the connection. Domain properties are marked **Domain property**. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). > [!TIP] > You can name a site the way you'd say it, such as "example.com". Plugsight matches it to the URL-prefix or domain property you have. ## What it can and can't change Search Console is **read-only** in Plugsight. Google's permission is read-only too. ## Limits - **Anonymised queries**: Google hides rare queries. When you break results down by query or page, Plugsight works out how many clicks and impressions are missing from the rows and tells your AI. They are still counted in totals. - **Fresh data**: Search Console data becomes final about 2–3 days after the date. Fresh data is included by default, so the latest days may still grow. - **Rows**: up to 100,000 rows are fetched per site by default (up to 500,000). If a report stops at the limit, your AI is told to add filters or shorten the range. ## Troubleshooting ### Google Search Console access wasn't granted. Tick the permission and try again. **What it means:** The permission box on Google's screen wasn't ticked. **How to fix it:** Connect again and tick the box at step 6. ### "This login doesn't reach anything yet." **What it means:** The Google account you used has no sites in Search Console. **How to fix it:** Add that account as a user on the site in Search Console, then click **Refresh list**. Or connect again with the account that owns the sites. ### No connection in this MCP reaches Google Search Console "…" (or it is hidden). **What it means:** The site named isn't reachable by this MCP server, or it is hidden. **How to fix it:** Check the site shows **Visible**, and that its connection is part of the MCP server you're using. ### Your Free plan includes 1 marketing connection. Upgrade to Pro to connect more. **What it means:** the Free plan includes 1 marketing or analytics connection to try, and you already have that many. **How to fix it:** remove the marketing connection you don't need on **Connections**, or upgrade to Pro or Agency on **Billing**. ### Reconnect needed: "Google sign-in was revoked or has expired." **What it means:** Google stopped accepting the login. **How to fix it:** Click **Reconnect** next to the connection. For other sign-in messages, see the troubleshooting section of [Google Ads](/connectors/google-ads): they're the same for every Google connector. ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Google Analytics 4](/connectors/google-analytics-4) - [PageSpeed Insights](/connectors/pagespeed-insights) - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts) - [Bing Webmaster Tools](/connectors/bing-webmaster) --- # Google Analytics 4 URL: https://docs.plugsight.app/connectors/google-analytics-4 Connect Google Analytics 4 so your AI can answer questions about traffic, conversions, revenue, funnels and realtime visitors. Connect Google Analytics 4 and your AI can read every GA4 property your Google login can open. Plugsight only reads: it never changes properties, events or settings. ## What your AI can do - Report sessions, users, engagement, page views, key events (conversions) and revenue. - Break them down by channel, source / medium, campaign, landing page, page, device, browser, country, region, city, language and date. - Report ecommerce: purchases, items viewed, add-to-carts, checkouts and item revenue by product, brand or category. - Show Google Ads cost, clicks and ROAS, and Search Console data, for properties linked to them in GA4. - Use any GA4 dimension or metric, including your own custom definitions. - Build a funnel from 2 to 10 steps and show where people drop off, optionally split by device or channel. - List your key events and how many happened in a period. - Show who is on the site right now (the last 30 minutes). - Run the account overview and period comparison deep dives. See [How your AI analyses marketing data](/connectors/marketing-data) for how these tools work. ### Example questions - "Which channels drove the most revenue this month vs last month?" - "Which landing pages have the highest conversion rate from paid search?" - "Which products were added to cart most but bought least?" - "How many people are on the site right now, and from which countries?" - "Show sessions and key events by week for the last quarter." - "Build a funnel from product page to purchase and show where mobile users drop off." - "What counts as a conversion in this property?" ## What you need - A **Pro** or **Agency** plan, or the Free plan to try it: Free includes 1 marketing connection and 25 marketing tool calls a month. See [Plans](/get-started/plans). - A Google account with access to your GA4 properties. ## Connect Google Analytics 4 1. Open **Connections** and click **Add connection**. 2. Choose **Google Analytics 4**. 3. Read **What happens next** and click **Continue to Google**. 4. Choose the Google account that can see your properties. 5. If Google says **"Google hasn't verified this app"**, click **Advanced**, then **Go to Plugsight (unsafe)**. 6. Google asks: "See and download your Google Analytics data". Tick the box and continue. 7. You're back on **Connections**, with a message such as "Connected you@example.com: 5 GA4 properties." Then add the connection to an MCP server. If this is your first marketing connection, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. To choose which properties your AI can see, click **Show sites & accounts** next to the connection. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## What it can and can't change GA4 is **read-only** in Plugsight. Google's permission is read-only too. ## Limits GA4 sometimes holds data back. When it does, your AI is told so it can explain the answer: - **Data thresholds**: with age, gender or small numbers of users, Google may withhold rows. Removing demographic breakdowns or widening the date range usually helps. - **Sampling**: large reports may be based on a sample of events. - **"(other)"**: when there are too many different values, GA4 groups the rest into "(other)". Add filters or ask for fewer breakdowns. - **Daily quota**: GA4 limits how much each property can be queried per day. Your AI is warned when it's running low. Funnel completion and drop-off rates come back as fractions (0.25 means 25%); your AI turns them into percentages. If a property has no key events, your AI is told to mark events as key events in GA4 under **Admin → Data display → Events**. ## Troubleshooting ### Google Analytics 4 access wasn't granted. Tick the permission and try again. **What it means:** The permission box on Google's screen wasn't ticked. **How to fix it:** Connect again and tick the box at step 6. ### "This login doesn't reach anything yet." **What it means:** The Google account you used has no GA4 properties. **How to fix it:** Give that account access to the property in GA4, then click **Refresh list**. Or connect again with the right account. ### Step "…": give either event or page_contains. **What it means:** Each funnel step must be either an event (such as add_to_cart) or a page whose address contains some text, not both or neither. **How to fix it:** Describe each step clearly, for example "step 1: viewed a page containing /product; step 2: add_to_cart event". ### Your Free plan includes 1 marketing connection. Upgrade to Pro to connect more. **What it means:** the Free plan includes 1 marketing or analytics connection to try, and you already have that many. **How to fix it:** remove the marketing connection you don't need on **Connections**, or upgrade to Pro or Agency on **Billing**. ### Reconnect needed: "Google sign-in was revoked or has expired." **What it means:** Google stopped accepting the login. **How to fix it:** Click **Reconnect** next to the connection. For other sign-in messages, see the troubleshooting section of [Google Ads](/connectors/google-ads). ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Google Search Console](/connectors/google-search-console) - [Google Tag Manager](/connectors/google-tag-manager) - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts) - [Who's on the site right now](/recipes/realtime-visitors) - [Bing Webmaster Tools](/connectors/bing-webmaster) --- # Bing Webmaster Tools URL: https://docs.plugsight.app/connectors/bing-webmaster Connect Bing Webmaster Tools with an API key so your AI can read Bing search clicks, queries, crawl stats and sitemaps. Read-only. Connect Bing Webmaster Tools and your AI can read how your sites do in Bing search. Plugsight only reads: it never submits URLs, changes settings or removes sites. ## What your AI can do - List the sites in your Bing Webmaster Tools account that you haven't hidden, and show whether each one is verified. - Report clicks and impressions by day. - Show your top search queries and top pages, with clicks, impressions, CTR and average position. Your AI can sort them by clicks or by impressions. - Show how Bing crawls a site, day by day: pages crawled, pages in the index, crawl errors and pages blocked by robots.txt. - Show the responses Bing got, by status: 2xx, 301, 4xx and 5xx. - List the sitemaps and feeds submitted for a site, with what Bing reports for each. - Look up one page: whether and when Bing discovered and crawled it, and its index details. ### Example questions - "Which Bing search queries brought the most clicks over the last three months?" - "Which pages get a lot of Bing impressions but few clicks?" - "Has Bing crawled https://example.com/pricing, and when?" - "Did Bing report crawl errors or pages blocked by robots.txt this month?" - "Which sitemaps have we submitted to Bing?" ## What you need - A **Pro** or **Agency** plan. See [Plans](/get-started/plans). - A Bing Webmaster Tools account with at least one site added and verified. - Access to that account's **Settings** → **API access** page, where you make the API key. ## Connect Bing Webmaster Tools 1. Sign in to Bing Webmaster Tools at bing.com/webmasters. 2. Open **Settings** → **API access**. 3. Generate an API key and copy it. It's 32 letters and numbers. 4. In Plugsight, open **Connections** and click **Add connection**. 5. Choose **Bing Webmaster Tools**. 6. Paste the key into **API key**. 7. Optional: type a name in **Name**, such as "Company sites". It can be up to 60 characters. 8. Click **Test connection & save**. Plugsight checks the key with Bing before it saves anything. 9. You're back on **Connections**, with a message that says how many sites the key reaches. > [!NOTE] > One key reads every site in your Bing Webmaster Tools account. Generating a new key stops the old one working. Then add the connection to an MCP server. If this is your first marketing connection, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. > [!TIP] > If more than one of your sites is visible to your AI, name the one you mean, such as example.com. If only one is visible, your AI uses it without being asked. ## Choose which sites your AI can see Click **Show sites & accounts** next to the connection on **Connections** to see every site the key reaches. Switch a site to **Hidden** and your AI can't read it, even by name. If only one site is left visible, your AI uses it without being asked. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## What it can and can't change Bing Webmaster Tools is **read-only** in Plugsight. Plugsight only reads with your key. It never submits URLs, changes settings or removes sites. See [Read-only connectors](/permissions/read-only-connectors). ## Limits - **About six months**: Bing keeps about six months of data. By default your AI gets everything Bing has. - **Weekly rows**: Bing reports queries and pages by week. When your AI picks a start and end date, it gets whole weeks. Clicks and impressions by day, and crawl stats, are daily. - **Top lists**: your AI shows the top 25 queries and pages by default. It can ask for between 1 and 200. - **Average position**: when a query or page spans several weeks, the average is weighted by impressions. - **One site at a time**: each question is about one site. With several sites, your AI needs to know which one. ## Troubleshooting ### That isn't a Bing Webmaster API key. It's 32 letters and numbers, from Settings → API access in Bing Webmaster Tools. **What it means:** what you pasted isn't 32 letters and numbers. **How to fix it:** in Bing Webmaster Tools, open **Settings** → **API access**, copy the key again and paste all of it into **API key**. ### Bing Webmaster Tools didn't accept that API key. Check you copied all of it, and that it hasn't been regenerated since. **What it means:** Bing turned the key down while you were connecting. **How to fix it:** copy the key again from **Settings** → **API access**. If you generated a new key since, use the newest one. ### Bing Webmaster Tools rejected the API key; it may have been regenerated or removed. Reconnect Bing Webmaster Tools on the Connections page in Plugsight. **What it means:** the key that was saved no longer works. This usually happens after someone generates a new key in Bing Webmaster Tools. **How to fix it:** make a key under **Settings** → **API access** in Bing Webmaster Tools, then click **Reconnect** next to the connection. It opens the connect form, where you paste the new key. ### Couldn't reach Bing Webmaster Tools. Try again in a minute. **What it means:** Plugsight couldn't get an answer from Bing. **How to fix it:** wait a minute and ask again. ### This Bing Webmaster account can't read …. Use a site exactly as bing_webmaster_sites lists it, and check it's verified in Bing Webmaster Tools. **What it means:** Bing won't let this key read that site. The address may be spelt differently from the one Bing lists, or the site may not be verified. **How to fix it:** ask your AI to list your Bing sites first, then use an address exactly as listed. In Bing Webmaster Tools, check the site is verified. ### This Bing Webmaster account has no sites yet. Add and verify one in Bing Webmaster Tools first. **What it means:** the key works, but the account has no sites. **How to fix it:** add and verify a site in Bing Webmaster Tools, then ask again. ### This Bing Webmaster account has … sites; pass site_url (one of: …). **What it means:** more than one of your sites is visible to your AI, and it didn't say which one you mean. **How to fix it:** name the site in your question, for example "for https://example.com/". Use one of the addresses in the message. ### … is hidden from AI apps on this Bing Webmaster connection. Show it under Show sites & accounts on the Connections page in Plugsight. **What it means:** you hid that site on **Connections**, so your AI can't read it. **How to fix it:** open **Connections**, click **Show sites & accounts** next to the connection and switch the site to **Visible**. ### Every site on this Bing Webmaster connection is hidden from AI apps. Show one under Show sites & accounts on the Connections page in Plugsight. **What it means:** every site the key reaches is hidden, so there's nothing your AI may read. **How to fix it:** open **Connections**, click **Show sites & accounts** next to the connection and switch at least one site to **Visible**. ### Your Free plan includes 1 marketing connection. Upgrade to Pro to connect more. **What it means:** the Free plan includes 1 marketing or analytics connection to try, and you already have that many. **How to fix it:** remove the marketing connection you don't need on **Connections**, or upgrade to Pro or Agency on **Billing**. ### My AI doesn't see Bing Webmaster Tools **What it means:** the connection isn't in the MCP server you're using, or your AI app hasn't loaded the marketing tools yet. **How to fix it:** check the MCP server includes this connection. Then [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. For other messages from your AI's tools, see [Errors from your AI's tools](/troubleshooting/tool-errors). ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Google Search Console](/connectors/google-search-console) - [Microsoft Advertising](/connectors/microsoft-advertising) - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts) - [Bing Webmaster Tools tools reference](/developers/bing-webmaster-tools) - [Read-only connectors](/permissions/read-only-connectors) --- # Google Tag Manager URL: https://docs.plugsight.app/connectors/google-tag-manager Connect Google Tag Manager so your AI can list your tags, triggers and versions and audit your tracking for common problems. Connect Google Tag Manager and your AI can read every container your Google login can open: tags, triggers, variables and version history. It can also audit a container for common tracking problems. Plugsight only reads: it never edits, publishes or deletes anything. > [!IMPORTANT] > Google is still reviewing the Tag Manager permission. Until Google approves it, Google Tag Manager isn't offered to everyone and may not appear in your **Connector catalog**. ## What your AI can do - **List containers**: every container with its GTM id (GTM-…), account, and where it's used. - **Read a container**: everything in the published (live) version: each tag with its type, the triggers it fires on and whether it's paused, plus every trigger and variable. - **Read one tag in full**: its settings (measurement or conversion ids, event names, parameters), its triggers and its blocking triggers. - **Audit a container**: checks the live version for - tags with no firing trigger, which never run (high) - Universal Analytics tags, which collect nothing since Google retired UA (high) - paused tags (medium) - possible duplicates: tags of the same type with the same id, which can double-count (medium) - triggers no tag uses, and variables nothing refers to (low) - Custom HTML tags, to check they're still needed It also lists changes waiting unpublished in workspaces. - **Version history**: published versions, newest first, with how many tags, triggers and variables each had (up to 100). ### Example questions - "Audit our GTM container and tell me what to fix first." - "Are any of our conversion tags firing twice?" - "Which GA4 measurement id does the GA4 config tag send to?" - "How many tags, triggers and variables did each of the last five published versions have?" - "Are there unpublished changes waiting in any workspace?" ## What you need - A **Pro** or **Agency** plan, or the Free plan to try it: Free includes 1 marketing connection and 25 marketing tool calls a month. See [Plans](/get-started/plans). - A Google account with access to your Tag Manager containers. ## Connect Google Tag Manager 1. Open **Connections** and click **Add connection**. 2. Choose **Google Tag Manager**. 3. Read **What happens next** and click **Continue to Google**. 4. Choose the Google account that can see your containers. 5. If Google says **"Google hasn't verified this app"**, click **Advanced**, then **Go to Plugsight (unsafe)**. 6. Google asks: "View your Google Tag Manager container and its subcomponents". Tick the box and continue. 7. You're back on **Connections**, with a message such as "Connected you@example.com: 2 Tag Manager containers." Then add the connection to an MCP server and [refresh the tools list](/ai-apps/refresh-tools) in your AI app. To choose which containers your AI can see, click **Show sites & accounts** next to the connection. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## What it can and can't change Tag Manager is **read-only**, and Google's permission is read-only too. Your AI can't add, edit, pause or publish tags. ## Limits - Container contents, tags and audits come from the **published** version. Drafts in workspaces are only listed as pending changes in the audit. - If you have one container, your AI uses it without asking. With several, it needs the GTM id or name. ## Troubleshooting ### This Google service is coming soon. **What it means:** Google hasn't finished reviewing the permission, so Tag Manager isn't open to everyone yet. **How to fix it:** Nothing to do for now. It will appear in the **Connector catalog** once Google approves it. ### No tag "…" in the published version of GTM-…. Use tag_manager_container to list them. **What it means:** The tag name or id wasn't found in the live version. It may only exist in a draft. **How to fix it:** Ask your AI to list the container's tags first, then pick one. ### This MCP reaches 3 containers; pass one of: … **What it means:** You have several containers and your AI didn't say which. **How to fix it:** Name the container in your question, for example "in GTM-ABC123". ### This MCP reaches no Google Tag Manager container. **What it means:** The connection isn't in this MCP server, or every container is hidden. **How to fix it:** Check the MCP server reaches the connection, and that the container shows **Visible**. ### Google Tag Manager access wasn't granted. Tick the permission and try again. **What it means:** The permission box on Google's screen wasn't ticked. **How to fix it:** Connect again and tick the box. For other sign-in messages, see the troubleshooting section of [Google Ads](/connectors/google-ads). ## Related articles - [Google Analytics 4](/connectors/google-analytics-4) - [Google Ads](/connectors/google-ads) - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts) - [Google Tag Manager tools](/developers/tag-manager-tools) --- # YouTube URL: https://docs.plugsight.app/connectors/youtube Connect YouTube so your AI can report on your channels' views, watch time, subscribers, top videos and traffic sources. Connect YouTube (shown in the catalog as **YouTube Analytics**) and your AI can read analytics for the channels your Google login manages. Plugsight only reads: it never uploads, edits or deletes videos, comments or channel settings. > [!IMPORTANT] > Google is still reviewing the YouTube permission. Until Google approves it, YouTube isn't offered to everyone and may not appear in your **Connector catalog**. ## What your AI can do - **List channels**: each channel with its subscribers, total views and number of videos. - **Channel report** for any period: views, watch time, average view duration, subscribers gained and lost, likes, comments and shares, with totals. The report can be split by: - day or month (trends) - video (top videos, with titles) - country - device - traffic source (search, suggested, external and so on) - playback location - subscribed status (subscribers vs non-subscribers) - age and gender (share of viewers) - **List videos**: a channel's uploads, newest first, with publish date, length, views, likes, comments and link. It can search by title. ### Example questions - "How did my channel do last month compared with the month before?" - "Which ten videos got the most watch time in the last 90 days?" - "Where do my viewers come from: search, suggested videos or outside YouTube?" - "How many subscribers did I gain and lose each month this year?" - "What share of my viewers are 25–34?" - "List my latest uploads and how many views each has." ## What you need - A **Pro** or **Agency** plan, or the Free plan to try it: Free includes 1 marketing connection and 25 marketing tool calls a month. See [Plans](/get-started/plans). - The Google account that manages your YouTube channel. ## Connect YouTube 1. Open **Connections** and click **Add connection**. 2. Choose **YouTube Analytics**. 3. Read **What happens next** and click **Continue to Google**. 4. Choose the Google account that manages your channel. 5. If Google says **"Google hasn't verified this app"**, click **Advanced**, then **Go to Plugsight (unsafe)**. 6. Google asks: "View your YouTube account". Tick the box and continue. 7. You're back on **Connections**, with a message such as "Connected you@example.com: 1 YouTube channel." Then add the connection to an MCP server and [refresh the tools list](/ai-apps/refresh-tools) in your AI app. To choose which channels your AI can see, click **Show sites & accounts** next to the connection. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## What it can and can't change YouTube is **read-only**, and Google's permission is read-only too. ## Limits - Reports default to the last 28 days. Other presets: last 7, 30, 90 or 365 days, this month, last month, this year, last year, or exact dates. - Reports and video lists return up to 200 rows (25 by default). - YouTube allows only some figures with some splits. Splits by traffic source, device or playback location show views and watch time; the age and gender split shows the share of viewers. - If a channel hides its subscriber count, the count isn't shown. - If you have one channel, your AI uses it without asking. With several, it needs the channel name or id. ## Troubleshooting ### This Google service is coming soon. **What it means:** Google hasn't finished reviewing the permission, so YouTube isn't open to everyone yet. **How to fix it:** Nothing to do for now. It will appear in the **Connector catalog** once Google approves it. ### "This login doesn't reach anything yet." **What it means:** The Google account you used doesn't manage a YouTube channel. **How to fix it:** Connect again and choose the account that manages the channel, then click **Refresh list**. ### This MCP reaches 2 channels; pass one of: … **What it means:** You have several channels and your AI didn't say which. **How to fix it:** Name the channel in your question. ### YouTube access wasn't granted. Tick the permission and try again. **What it means:** The permission box on Google's screen wasn't ticked. **How to fix it:** Connect again and tick the box. For other sign-in messages, see the troubleshooting section of [Google Ads](/connectors/google-ads). ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Google Analytics 4](/connectors/google-analytics-4) - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts) - [YouTube tools](/developers/youtube-tools) --- # Google Merchant Center URL: https://docs.plugsight.app/connectors/google-merchant-center Connect Google Merchant Center so your AI can check product feed health, find disapproved products and report Shopping performance. Connect Google Merchant Center and your AI can check your product feed, find products with problems and report how your Shopping ads and free listings perform. Plugsight only reads: it never changes products, feeds or account settings. > [!IMPORTANT] > Google is still reviewing the Merchant Center permission. Until Google approves it, Google Merchant Center isn't offered to everyone and may not appear in your **Connector catalog**. ## What your AI can do - **List accounts**: the Merchant Center accounts your login can open. - **Feed health**: how many products are approved, limited (disapproved in some countries), pending or disapproved, and the most common product issues, with how many products each affects, examples and Google's help link. - **List products**: each product's status, price, availability, link and issues. Filter by status (approved, limited, pending, disapproved) or by text in the title or offer id. - **Performance**: impressions, clicks, click-through rate, conversions and conversion value from Shopping ads and free listings, by product, by day or in total. ### Example questions - "How healthy is our product feed? What are the top issues?" - "Which products are disapproved, and why?" - "Which products got the most Shopping clicks in the last 30 days?" - "Show Shopping clicks and conversions per day for last month." - "Is the blue running shoe approved, and does it have any issues?" ## What you need - A **Pro** or **Agency** plan, or the Free plan to try it: Free includes 1 marketing connection and 25 marketing tool calls a month. See [Plans](/get-started/plans). - A Google account with access to your Merchant Center account. ## Connect Google Merchant Center 1. Open **Connections** and click **Add connection**. 2. Choose **Google Merchant Center**. 3. Read **What happens next** and click **Continue to Google**. 4. Choose the Google account that can see your Merchant Center account. 5. If Google says **"Google hasn't verified this app"**, click **Advanced**, then **Go to Plugsight (unsafe)**. 6. Google asks: "Manage your product listings and accounts for Google Shopping". Tick the box and continue. 7. You're back on **Connections**, with a message such as "Connected you@example.com: 1 Merchant Center account." > [!NOTE] > Google offers no read-only permission for Merchant Center, so it asks for management access. Plugsight only ever reads from it. Then add the connection to an MCP server and [refresh the tools list](/ai-apps/refresh-tools) in your AI app. To choose which accounts your AI can see, click **Show sites & accounts** next to the connection. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## What it can and can't change Merchant Center is **read-only** in Plugsight. Your AI can't edit products, fix issues or change feeds. ## Limits - Feed health counts up to the first 20,000 products. If you have more, your AI is told. - Product lists return up to 500 products (50 by default). Feed health lists up to 100 issues (15 by default). - Performance returns up to 1,000 rows (50 by default) and covers the last 28 days unless you ask for another period. - If you have one Merchant Center account, your AI uses it without asking. With several, it needs the account name or id. ## Troubleshooting ### This Google service is coming soon. **What it means:** Merchant Center isn't open to everyone yet. **How to fix it:** Nothing to do for now. It will appear in the **Connector catalog** once it's available. ### Google is switching on Merchant Center for Plugsight, which takes up to 5 minutes the first time. Try again in a few minutes. **What it means:** The first time Plugsight reads Merchant Center data, Google needs a few minutes to set up access. **How to fix it:** Wait five minutes and ask again. ### Merchant Center isn't ready on Plugsight yet: Google refused the one-time setup (…). **What it means:** Google refused a setup step on Plugsight's side. **How to fix it:** Contact info@plugsight.app with the message. ### Google Merchant Center access wasn't granted. Tick the permission and try again. **What it means:** The permission box on Google's screen wasn't ticked. **How to fix it:** Connect again and tick the box. ### This MCP reaches no Google Merchant Center account. **What it means:** The connection isn't in this MCP server, or every account is hidden. **How to fix it:** Check the MCP server reaches the connection, and that the account shows **Visible**. For other sign-in messages, see the troubleshooting section of [Google Ads](/connectors/google-ads). ## Related articles - [Google Ads](/connectors/google-ads) - [WooCommerce](/connectors/woocommerce) - [Magento / Adobe Commerce](/connectors/magento) - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts) - [Google Merchant Center tools](/developers/merchant-center-tools) --- # PageSpeed Insights URL: https://docs.plugsight.app/connectors/pagespeed-insights Your AI can check the speed, Core Web Vitals and SEO scores of any public web page, with no connection and on every plan. Every MCP server includes a page speed check powered by Google PageSpeed Insights. You don't need to connect anything: your AI can check any public web page. ## What your AI can do For one page, on mobile or desktop, your AI gets: - **Scores** out of 100 for performance, SEO, accessibility and best practices. - **Real-user Core Web Vitals** (Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift), for the page and for the whole site, from Chrome users over the last 28 days. These are the same figures Google Search uses. - **Lab timings** from one test run, such as first contentful paint, total blocking time and server response time. - **The biggest fixes**: up to eight changes that would save the most time, with how much each would save. ### Example questions - "Check the speed of https://example.com/pricing on mobile." - "Do our product pages pass Core Web Vitals?" - "What are the three changes that would make our home page load fastest?" - "Compare our home page's mobile and desktop performance scores." - "Check the SEO and accessibility scores of our blog's latest article." ## What you need Nothing. It works on every plan and every MCP server, whatever you have connected. The page must be public: PageSpeed Insights can't open pages behind a login. ## Limits - Each check takes 10 to 40 seconds. - Mobile is checked unless you ask for desktop. Mobile is what Google ranks on. - Real-user data needs enough Chrome visits. For a quiet page or a new site, your AI is told "Not enough Chrome visits to this exact page for real-user data" (or "to this site"). Lab scores still work. - Lab data is one test run, so it can vary a little between checks. - If you leave out https://, Plugsight adds it. ## What it can and can't change Nothing. A page speed check only loads the page, the way a visitor would. ## Troubleshooting ### PageSpeed Insights didn't accept that request. … (PageSpeed Insights said: …) **What it means:** Google couldn't check the page, for example because the address is wrong, the page is private, or the site didn't load for Google's test. The text after "said:" is Google's own reason. **How to fix it:** Open the address in a private browser window to check it loads without signing in, then ask again. ### PageSpeed Insights is limiting requests right now. Wait a minute, then try again. **What it means:** Google has received too many checks in a short time. **How to fix it:** Wait a minute, then ask again. ### PageSpeed Insights is having problems right now. Try again in a few minutes. **What it means:** Google's service had an error. **How to fix it:** Try again in a few minutes. ## Related articles - [Google Search Console](/connectors/google-search-console) - [How your AI analyses marketing data](/connectors/marketing-data) - [PageSpeed tool](/developers/pagespeed-tools) --- # Google Drive URL: https://docs.plugsight.app/connectors/google-drive Google Drive lets your AI search and read Docs, Sheets, Slides, PDFs and Office files, including shared drives. Not yet open to everyone. Connect Google Drive and your AI can search your Drive and read files as text: Google Docs, Sheets and Slides, PDFs, Word, Excel and PowerPoint files, CSV and text files, in My Drive and your shared drives. Plugsight only reads: it never creates, edits, moves, shares or deletes files. > [!IMPORTANT] > Google Drive is **coming soon**. Google treats full Drive access as a restricted permission that needs a security audit before an app can offer it to everyone. Until that's done, Google Drive isn't listed in the **Connector catalog**. Meanwhile, [Google Sheets](/connectors/google-sheets) and [Google Docs](/connectors/google-docs) can read single files by link once Google approves them. ## What your AI can do - **Search Drive** by words inside files, file name, type (document, spreadsheet, presentation, PDF, folder or image), modified date, owner, folder or shared drive. Results come newest first, unless you search by words. - **Read a file** as text: Google Docs, every sheet of a Google Sheet, Google Slides, PDFs, Word, Excel, PowerPoint (with speaker notes), CSV and text files. Images are shown to your AI so it can look at them, and shortcuts open the file they point to. Scanned PDFs without a text layer, and old .doc, .xls and .ppt files, can't be read as text; your AI tells you so. - **List drives**: My Drive and the shared drives this connection can use. ### Example questions - "Find the latest version of the 2026 marketing plan and summarise it." - "What does the contract PDF in the Legal shared drive say about termination?" - "List the spreadsheets Sam shared with me this month." - "Which documents in the Proposals folder mention Acme?" ## What you need - Any plan. Google Drive isn't a marketing connector, so it's on the Free plan too. - A Google account with access to the files. ## Connect Google Drive When Google Drive becomes available: 1. Open **Connections** and click **Add connection**. 2. Choose **Google Drive**. 3. Read **What happens next** and click **Continue to Google**. 4. Choose your Google account. 5. If Google says **"Google hasn't verified this app"**, click **Advanced**, then **Go to Plugsight (unsafe)**. 6. Google asks: "See and download all your Google Drive files". Tick the box and continue. 7. You're back on **Connections**, with a message saying how many drives it reaches. To keep a shared drive away from your AI, click **Show drives** next to the connection and switch it to **Hidden**. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## What it can and can't change Google Drive is **read-only**, and Google's permission is read-only too. ## Limits - Searches return up to 100 files at a time (25 by default); your AI can ask for the next page. - Files are read up to 40,000 characters by default, and up to 200,000 on request. Longer files are cut, and your AI is told. - Folders can't be read as text: your AI searches inside them instead. - Images and some Google file types can't be read as text. Your AI gets the file's link instead. - Files in hidden drives are never searched or read. ## Troubleshooting ### Google Drive is coming soon. **What it means:** Google Drive isn't open yet, while Google's security audit is pending. **How to fix it:** Nothing to do for now. Use [Google Sheets](/connectors/google-sheets) or [Google Docs](/connectors/google-docs) for single files when they're available to you. ### That drive is hidden from AI apps. **What it means:** You hid this shared drive (or My Drive) on **Connections**. **How to fix it:** Click **Show drives** and switch it back to **Visible**, if you want your AI to use it. ### That file is in a drive hidden from AI apps. **What it means:** The file is in a drive you've hidden. **How to fix it:** Show the drive again, or leave it hidden to keep the file private. ## Related articles - [Google Sheets](/connectors/google-sheets) - [Google Docs](/connectors/google-docs) - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts) - [Google Drive tools](/developers/drive-tools) --- # Google Sheets URL: https://docs.plugsight.app/connectors/google-sheets Connect Google Sheets so your AI can read any spreadsheet you can open, from its link. Read-only. Offered once Google approves it. Connect Google Sheets and your AI can read any spreadsheet you can open: give it the link and ask your question. Plugsight only reads: it never edits, adds or deletes cells, tabs or files. > [!IMPORTANT] > Google is still reviewing the Sheets permission. Until Google approves it, Google Sheets isn't offered to everyone and may not appear in your **Connector catalog**. ## What your AI can do - **Spreadsheet details**: the title, the tabs (with their size) and named ranges. - **Read a spreadsheet**: values as they're shown in Google Sheets (or the formulas, if you ask), from a whole tab, a range such as "Sales!A1:F200", or a named range. The names of the other tabs come back too, so your AI knows what else is there. The first row is used as column names, unless you say it isn't a header row. Your AI reads a spreadsheet by its link (from your browser's address bar) or its id. It can't browse or search your Drive for spreadsheets. ### Example questions - "Here's our budget: https://docs.google.com/spreadsheets/d/… Which categories are over budget this quarter?" - "Read the Leads tab of this sheet and list everyone from London." - "What tabs does this spreadsheet have, and how big is each?" - "Total the Amount column in Sales!A1:F500 by month." ## What you need - Any plan, once Google approves it. It's in **Docs & files**, not marketing, so it's on the Free plan too. - A Google account that can open the spreadsheets. ## Connect Google Sheets 1. Open **Connections** and click **Add connection**. 2. Choose **Google Sheets**. 3. Read **What happens next** and click **Continue to Google**. 4. Choose the Google account that can open your spreadsheets. 5. If Google says **"Google hasn't verified this app"**, click **Advanced**, then **Go to Plugsight (unsafe)**. 6. Google asks: "See all your Google Sheets spreadsheets". Tick the box and continue. 7. You're back on **Connections**, with a message such as "Connected you@example.com: ready to read any spreadsheet you can open, by link." Then add the connection to an MCP server and [refresh the tools list](/ai-apps/refresh-tools) in your AI app. ## What it can and can't change Google Sheets is **read-only**, and Google's permission is read-only too. ## Limits - Up to 5,000 rows per read (500 by default). For bigger sheets, ask for a smaller range. - Without a range, the first tab is read. - If you have more than one Google Sheets connection in an MCP server, your AI needs to know which one to use. ## Troubleshooting ### That isn't a Google Sheets link or id. Paste the spreadsheet's link from the browser's address bar. **What it means:** What you gave your AI doesn't look like a spreadsheet link. **How to fix it:** Open the spreadsheet in your browser and copy the full address from the address bar. ### Google couldn't find that item. … / Google says this login isn't allowed to do that. … **What it means:** The spreadsheet doesn't exist, or the Google account you connected can't open it. **How to fix it:** Check the link, and that the connected Google account can open the spreadsheet. If someone else owns it, ask them to share it with that account. ### This Google service is coming soon. **What it means:** Google hasn't finished reviewing the permission. **How to fix it:** Nothing to do for now. It will appear in the **Connector catalog** once Google approves it. ### Google Sheets access wasn't granted. Tick the permission and try again. **What it means:** The permission box on Google's screen wasn't ticked. **How to fix it:** Connect again and tick the box. ## Related articles - [Google Docs](/connectors/google-docs) - [Google Forms](/connectors/google-forms) - [Google Drive](/connectors/google-drive) - [Google Sheets tools](/developers/sheets-tools) --- # Google Docs URL: https://docs.plugsight.app/connectors/google-docs Connect Google Docs so your AI can read any document you can open, from its link, with headings, lists and tables kept. Connect Google Docs and your AI can read any document you can open: give it the link and ask your question. Plugsight only reads: it never edits, comments on or deletes documents. > [!IMPORTANT] > Google is still reviewing the Docs permission. Until Google approves it, Google Docs isn't offered to everyone and may not appear in your **Connector catalog**. ## What your AI can do - **Read a document** as text, keeping headings, bullet lists, tables, links, @mentions of people, dates, images (as their description), footnotes, headers and footers. Documents with several tabs (and tabs inside tabs) are read in full. Suggested edits are left out, so you get the text as it stands. Your AI opens a document by its link (from your browser's address bar) or its id. It can't browse or search your Drive for documents. ### Example questions - "Summarise this proposal: https://docs.google.com/document/d/…" - "What are the action items in our meeting notes doc?" - "Compare the pricing section of these two documents." - "Draft a reply to Sarah's email using the figures in this doc." ## What you need - Any plan, once Google approves it. It's in **Docs & files**, so it's on the Free plan too. - A Google account that can open the documents. ## Connect Google Docs 1. Open **Connections** and click **Add connection**. 2. Choose **Google Docs**. 3. Read **What happens next** and click **Continue to Google**. 4. Choose the Google account that can open your documents. 5. If Google says **"Google hasn't verified this app"**, click **Advanced**, then **Go to Plugsight (unsafe)**. 6. Google asks: "See all your Google Docs documents". Tick the box and continue. 7. You're back on **Connections**, with a message such as "Connected you@example.com: ready to read any document you can open, by link." Then add the connection to an MCP server and [refresh the tools list](/ai-apps/refresh-tools) in your AI app. ## What it can and can't change Google Docs is **read-only**, and Google's permission is read-only too. ## Limits - Documents are read up to 60,000 characters by default, and up to 500,000 on request. Longer documents are cut. - If you have more than one Google Docs connection in an MCP server, your AI needs to know which one to use. ## Troubleshooting ### That isn't a Google Docs link or id. Paste the document's link from the browser's address bar. **What it means:** What you gave your AI doesn't look like a document link. **How to fix it:** Open the document in your browser and copy the full address from the address bar. ### Google couldn't find that item. … / Google says this login isn't allowed to do that. … **What it means:** The document doesn't exist, or the Google account you connected can't open it. **How to fix it:** Check the link, and that the connected Google account can open the document. ### This Google service is coming soon. **What it means:** Google hasn't finished reviewing the permission. **How to fix it:** Nothing to do for now. It will appear in the **Connector catalog** once Google approves it. ### Google Docs access wasn't granted. Tick the permission and try again. **What it means:** The permission box on Google's screen wasn't ticked. **How to fix it:** Connect again and tick the box. ## Related articles - [Google Sheets](/connectors/google-sheets) - [Google Drive](/connectors/google-drive) - [Google Meet](/connectors/google-meet) - [Google Docs tool](/developers/docs-tools) --- # Google Forms URL: https://docs.plugsight.app/connectors/google-forms Connect Google Forms so your AI can read your forms' questions and responses, and total the answers for leads, surveys and bookings. Connect Google Forms and your AI can read the questions and responses of forms you can edit: leads, surveys, bookings, quizzes and sign-ups. Plugsight only reads: it never edits forms or responses. > [!IMPORTANT] > Google is still reviewing the Forms permissions. Until Google approves them, Google Forms isn't offered to everyone and may not appear in your **Connector catalog**. ## What your AI can do - **Form details**: the title, description, fill-in link, and every question with its type and options, including each row of grid questions. - **Responses** as a table, newest first: when each was submitted, the respondent's email (when the form collects it), and one column per question. You can ask only for responses since a date. - **Summary**: totals per question: how many chose each option of choice, scale and rating questions, and how many answered the others. Your AI opens a form by its **edit link** (the address when you're editing the form in Google Forms) or its id. The link people use to fill the form in doesn't work. ### Example questions - "Here's our feedback form: https://docs.google.com/forms/d/…/edit. What are the most common complaints this month?" - "How many people chose each option in the event sign-up form?" - "List everyone who asked for a quote since Monday, with their email." - "What's the average rating in the customer survey?" ## What you need - Any plan, once Google approves it. It's in **Docs & files**, so it's on the Free plan too. - A Google account that can edit the forms. ## Connect Google Forms 1. Open **Connections** and click **Add connection**. 2. Choose **Google Forms**. 3. Read **What happens next** and click **Continue to Google**. 4. Choose the Google account that owns or edits your forms. 5. If Google says **"Google hasn't verified this app"**, click **Advanced**, then **Go to Plugsight (unsafe)**. 6. Google asks for two permissions: "See all your Google Forms forms" and "See all responses to your Google Forms forms". Tick both and continue. 7. You're back on **Connections**, with a message such as "Connected you@example.com: ready to read the questions and responses of forms you can edit, by link." Then add the connection to an MCP server and [refresh the tools list](/ai-apps/refresh-tools) in your AI app. ## What it can and can't change Google Forms is **read-only**, and both of Google's permissions are read-only too. ## Limits - Up to 5,000 responses per request (200 by default). - Written answers aren't summarised by the summary tool; your AI reads them from the responses. - If you have more than one Google Forms connection in an MCP server, your AI needs to know which one to use. ## Troubleshooting ### That's the link people fill in. Open the form in Google Forms (where you edit it) and paste that link instead. **What it means:** You gave your AI the public fill-in link (it contains /forms/d/e/ or forms.gle). **How to fix it:** Open the form in Google Forms, copy the address from your browser while editing it, and give your AI that link. ### That isn't a Google Forms link or id. Paste the link from the form's edit page. **What it means:** What you gave your AI doesn't look like a form link. **How to fix it:** Copy the full address from the form's edit page. ### Google couldn't find that item. … / Google says this login isn't allowed to do that. … **What it means:** The form doesn't exist, or the connected Google account can't edit it. **How to fix it:** Check the link, and ask the form's owner to add the connected account as an editor. ### Google Forms access wasn't granted. Tick the permission and try again. **What it means:** One or both permission boxes weren't ticked. **How to fix it:** Connect again and tick both boxes. ### This Google service is coming soon. **What it means:** Google hasn't finished reviewing the permissions. **How to fix it:** Nothing to do for now. It will appear in the **Connector catalog** once Google approves it. ## Related articles - [Google Sheets](/connectors/google-sheets) - [Google Docs](/connectors/google-docs) - [Mailchimp](/connectors/mailchimp) - [Google Forms tools](/developers/forms-tools) - [Form responses summary](/recipes/form-responses-summary) --- # Google Meet URL: https://docs.plugsight.app/connectors/google-meet Connect Google Meet so your AI can list your meetings, see who joined and read transcripts to summarise decisions and action items. Connect Google Meet and your AI can list the meetings you organised, see who joined, and read transcripts when transcription was turned on. Plugsight only reads: it never starts, joins, records or changes meetings. > [!IMPORTANT] > Google is still reviewing the Meet permission. Until Google approves it, Google Meet isn't offered to everyone and may not appear in your **Connector catalog**. ## What your AI can do - **List meetings** you organised in a period, newest first: start time, length, who joined, and whether a transcript exists. - **Read a transcript** as "Name: words" lines, with who joined, and a link to the transcript document when Google made one. Google keeps the line-by-line transcript for about 30 days; for older meetings it's read from the transcript document instead (this needs a Google Docs or Drive connection on the same MCP server). ### Example questions - "Summarise yesterday's meeting with Acme and list the action items." - "Which meetings did I run this week, and who joined each?" - "What did Priya say about the launch date in Tuesday's call?" - "Draft a follow-up email with the decisions from my last meeting." ## What you need - Any plan, once Google approves it. It's in **Docs & files**, so it's on the Free plan too. - The Google account you use to organise meetings. - For transcripts: transcription turned on in the meeting (in Meet: **Activities → Transcripts**). ## Connect Google Meet 1. Open **Connections** and click **Add connection**. 2. Choose **Google Meet**. 3. Read **What happens next** and click **Continue to Google**. 4. Choose the Google account you organise meetings with. 5. If Google says **"Google hasn't verified this app"**, click **Advanced**, then **Go to Plugsight (unsafe)**. 6. Google asks: "Read information about any of your Google Meet conferences". Tick the box and continue. 7. You're back on **Connections**, with a message such as "Connected you@example.com: ready to read your meetings and their transcripts." Then add the connection to an MCP server and [refresh the tools list](/ai-apps/refresh-tools) in your AI app. ## What it can and can't change Google Meet is **read-only**, and Google's permission is read-only too. ## Limits - Only meetings **you organised** are listed, not ones you were invited to. - Meetings come from the last 7 days unless you ask for another period: last 28, 30 or 90 days, this month, last month, or exact dates. - Up to 100 meetings per request (25 by default). - Transcripts are read up to 80,000 characters by default, and up to 500,000 on request. Longer ones are cut, and your AI is told. - If you have more than one Google Meet connection in an MCP server, your AI needs to know which one to use. ## Troubleshooting ### This meeting has no transcript: transcription wasn't turned on. Turn it on in Meet (Activities → Transcripts) next time. **What it means:** Google only makes a transcript when someone turns transcription on during the meeting. **How to fix it:** Turn on transcription in future meetings: **Activities → Transcripts** in Meet. ### My meeting isn't in the list **What it means:** Only meetings you organised are listed, and only for the period asked. **How to fix it:** Ask for a longer period, or connect the Google account of the person who organised the meeting. ### Google Meet access wasn't granted. Tick the permission and try again. **What it means:** The permission box on Google's screen wasn't ticked. **How to fix it:** Connect again and tick the box. ### This Google service is coming soon. **What it means:** Google hasn't finished reviewing the permission. **How to fix it:** Nothing to do for now. It will appear in the **Connector catalog** once Google approves it. ## Related articles - [Google Docs](/connectors/google-docs) - [Google Drive](/connectors/google-drive) - [Google Meet tools](/developers/meet-tools) - [Prepare for meetings and follow up](/guides/meeting-prep-and-follow-up) --- # WooCommerce URL: https://docs.plugsight.app/connectors/woocommerce Connect your WooCommerce store so your AI can report on sales, orders, best sellers, stock and customers. Read-only, about a minute. Connect your WooCommerce store and your AI can tell you how the shop is doing: sales, orders, best sellers, stock and customers. Plugsight gets read-only access: it can't change orders, products, prices or settings. ## What your AI can do - **Sales report** for any period: gross and net sales, orders, items sold, average order, tax, shipping, refunds and discounts, broken down by day (or by month for long periods), plus the best-selling products. - **List orders**, newest first, by status (pending, processing, on hold, completed, cancelled, refunded, failed or checkout draft), date range, or a search for a customer name, email, order number or product. - **Read one order** in full: items with the options chosen (size, colour, add-ons), totals, fees, coupons, discounts, shipping and tracking numbers (from common tracking plugins), refunds, payment method and transaction id, paid and completed dates, customer, addresses, the customer's note and order notes. - **Search products** by name or SKU, or only those out of stock or on backorder, with price, sale price, stock level, total sales and rating, and optionally every variation (each size or colour with its own stock and SKU). Sort by popularity to see all-time best sellers. - **Search customers** by name or email, with how many orders each placed and how much they spent. ### Example questions - "How did the shop do last month compared with the month before?" - "Which products sold best this week, and are any of them running low on stock?" - "Find order 1042 and tell me what was bought and where it's shipping." - "Who are my ten biggest customers by total spent?" - "Which orders are still on hold?" - "Compare Google Ads spend last month with WooCommerce revenue for the same days." ## What you need - Any plan. WooCommerce isn't a marketing connector. - Your store's web address. The store must use **https** and be reachable from the internet. - A WordPress login as an **administrator** or **shop manager**. ## Connect by approving Plugsight in your store This is the quickest way, and takes about a minute. 1. Open **Connections** and click **Add connection**. 2. Choose **WooCommerce**. 3. Under **Approve in your store**, type your **Store web address**: the address customers visit, like shop.example.com. 4. Click **Continue to my store**. 5. Your store opens. Log in to WordPress as an administrator or shop manager, if you aren't already. 6. WooCommerce shows "Plugsight would like to connect" with **Read** access. Click **Approve**. 7. You come straight back to **Connections**, with the message "Connected shop.example.com." ## Connect with REST API keys instead Use this if your host blocks the approval screen (you'll see a message saying so). 1. On the **Connect WooCommerce** page, open **Connect with REST API keys instead**. 2. Type your **Store web address**. 3. Click **Open your store's REST API keys**. Or, in WordPress, go to **WooCommerce → Settings → Advanced → REST API** and click **Add key**. 4. Describe the key as "Plugsight", pick your user, set **Permissions** to **Read** and click **Generate API key**. 5. Copy the **Consumer key** and **Consumer secret**. WooCommerce shows the secret only once, so copy both before leaving the page. 6. Back in Plugsight, paste them into **Consumer key** (starts ck_) and **Consumer secret** (starts cs_). Optionally give the connection a **Name**, such as "Main shop". 7. Click **Test connection & save**. Plugsight checks the keys with your store before saving anything. When it works, you see a message like "Connected shop.example.com (1,234 orders), id "…"." Then add the connection to an MCP server. If this is your first store, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. > [!TIP] > Connecting the same store again replaces its keys and keeps your settings. The message says "Reconnected" instead of "Connected". ## What it can and can't change WooCommerce is **read-only** in Plugsight, whichever way you connect. Your AI can't create, edit, refund or cancel orders, or change products, prices, stock or settings. To cut access, delete the Plugsight key in **WooCommerce → Settings → Advanced → REST API**, and remove the connection on **Connections**. ## Limits - Order, product and customer lists return up to 100 at a time (25 by default). Your AI can ask for the next page. - Sales reports list up to 50 best-selling products (10 by default). - Customer search covers registered customers. Guest checkouts appear in orders, not in the customer list. - If you connect more than one store, your AI needs to know which one you mean: name it in your question. ## Troubleshooting ### Enter your store's web address, like shop.example.com. **What it means:** The address box was empty or the address wasn't valid. Addresses with a port number or without a dot aren't accepted. **How to fix it:** Type the address customers visit, such as shop.example.com. ### That address isn't a public website. Enter your store's web address, like shop.example.com. **What it means:** The address points to a private or local network, which Plugsight can't reach. **How to fix it:** Use your store's public address on the internet. ### The store wasn't connected: the approval was cancelled. Click Connect and choose Approve. **What it means:** You didn't click **Approve** on the WooCommerce screen. **How to fix it:** Start again and click **Approve**. ### … approved Plugsight but couldn't send us the keys (some hosts block this). Use "Connect with REST API keys" below instead. **What it means:** Your hosting blocked WooCommerce from sending Plugsight the keys after you approved. **How to fix it:** Use [Connect with REST API keys instead](#connect-with-rest-api-keys-instead). ### … didn't answer like a WooCommerce store (HTTP …). Check the address, and that WooCommerce is installed and its REST API isn't blocked by a security plugin. **What it means:** The address didn't return WooCommerce data. The address may be wrong, WooCommerce may not be installed, or a security plugin or firewall is blocking its REST API. **How to fix it:** Check the address. If it's right, allow the WooCommerce REST API (addresses under /wp-json/wc/) in your security plugin or firewall. ### The store didn't accept these keys. Copy both again in full from WooCommerce → Settings → Advanced → REST API, with Read access. **What it means:** The consumer key or secret is wrong or incomplete. **How to fix it:** Create a new key with **Read** permissions and paste both values again in full. ### The store rejected Plugsight's keys; they may have been revoked. Reconnect the store on the Connections page in Plugsight. **What it means:** The key was deleted or changed in WooCommerce. The connection shows **Reconnect needed**. **How to fix it:** Connect the store again, by approving or with new keys. ### The store's keys don't allow this. Reconnect and approve read access, or check a security plugin isn't blocking the WooCommerce API. **What it means:** The key doesn't have read permission, or a plugin is blocking the request. **How to fix it:** Connect again with **Read** access, and check your security plugin. ### Couldn't find shop.example.com. Check the server name for typos. **What it means:** The address doesn't exist on the internet. **How to fix it:** Check the spelling of your store's address. ### Couldn't reach shop.example.com in time. Check the server name and port, then try again. **What it means:** Your store didn't answer within 20 seconds. **How to fix it:** Check the store is online, then try again. ## Related articles - [Magento / Adobe Commerce](/connectors/magento) - [Shopify](/connectors/shopify) - [Mailchimp](/connectors/mailchimp) - [Google Merchant Center](/connectors/google-merchant-center) - [Google Analytics 4](/connectors/google-analytics-4) - [WooCommerce tools](/developers/woocommerce-tools) - [Review your store's sales](/guides/store-sales-review) - [Customers who haven't reordered](/recipes/customers-not-reordered) --- # Magento / Adobe Commerce URL: https://docs.plugsight.app/connectors/magento Connect a Magento Open Source or Adobe Commerce store so your AI can report on sales, orders, best sellers, low stock and customers. Connect your Magento Open Source or Adobe Commerce 2.4 store and your AI can tell you how it's doing: sales, orders, best sellers, low stock and customers. You add Plugsight as an **Integration** in your Magento admin, with read-only resources. No extension is needed. Plugsight only reads: it can't change anything in your store. ## What your AI can do - **Sales report** for any period, added up from all your orders in it: revenue, orders, items sold, average order, discounts, shipping, tax and refunds, day by day, plus the best-selling products. Only paid orders (processing, complete and closed) count as revenue; the others are listed separately. Stores selling in several currencies get totals per currency. - **List orders**, newest first, by status (for example pending, processing, complete, canceled, closed or holded), date range or customer email. - **Read one order** in full, by the order number customers see (for example 000000123): items with the options chosen, totals, discounts, shipping with tracking numbers, invoices, refunds (credit memos), payment method, addresses and comments. - **Search products** by name or SKU, with price, special price, stock quantity, type and status, or list products whose stock is at or below a quantity you choose. - **Search customers** by email or name, with when they joined and their default address. ### Example questions - "How did the store do last month compared with the month before?" - "Which products sold best this week, and which are running low on stock?" - "List products with 5 or fewer in stock." - "Find order 000001042 and tell me what was bought and where it's shipping." - "Show every order from ann@example.com this year." - "Compare Google Ads spend last month with Magento revenue for the same days." ## What you need - Any plan. Magento isn't a marketing connector. - A Magento Open Source or Adobe Commerce 2.4 store, on https and reachable from the internet. - An admin login that can create integrations, and your admin password. ## Connect your store This takes about 3 minutes, in your Magento admin. ### 1. Add a new integration 1. In your Magento admin, go to **System → Extensions → Integrations**. 2. Click **Add New Integration**. 3. Name it "Plugsight" and enter your admin password. ### 2. Choose what it can read 1. Open the **API** tab. 2. Set **Resource Access** to **Custom**. 3. Tick **Sales → Operations → Orders**, **Catalog → Inventory → Products** and **Customers → All Customers**. 4. Click **Save**. ### 3. Activate it and copy the four keys 1. Next to Plugsight in the list, click **Activate**, then **Allow**. 2. Magento shows four keys: **Consumer Key**, **Consumer Secret**, **Access Token** and **Access Token Secret**. You can see them again later with **Edit → Integration Details**. ### 4. Paste them into Plugsight 1. In Plugsight, open **Connections**, click **Add connection** and choose **Magento / Adobe Commerce**. 2. Type your **Store web address**, like shop.example.com. 3. Optionally give the connection a **Name**, such as "Main shop". 4. Paste each key into the matching box: **Consumer Key**, **Consumer Secret**, **Access Token** and **Access Token Secret**. 5. Click **Test connection & save**. Plugsight checks the keys with your store before saving anything. When it works, you see a message like "Connected shop.example.com (5,210 orders), id "…"." Then add the connection to an MCP server. If this is your first store, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. > [!NOTE] > Magento gives every integration four keys, and Plugsight uses all four to sign each request. This works on every 2.4 store without changing settings. ## What it can and can't change Magento is **read-only** in Plugsight. Your AI can't create, edit, invoice, ship or cancel orders, or change products, prices, stock, customers or settings. To cut access, delete the Plugsight integration in **System → Extensions → Integrations**, and remove the connection on **Connections**. ## Limits - A sales report reads as many orders as it can in about 40 seconds. On a very busy store it can stop early: your AI is told the totals are incomplete and how far they reach. Ask for a shorter period. - Sales report dates and order date filters use UTC. - Order, product and customer lists return up to 100 at a time (25 by default). Your AI can ask for the next page. - Sales reports list up to 50 best-selling products (10 by default). - If you connect more than one store, name the one you mean in your question. ## Troubleshooting ### Enter your store's web address, like shop.example.com. **What it means:** The address box was empty or the address wasn't valid. **How to fix it:** Type your store's address, such as shop.example.com. ### That address isn't a public website. Enter your store's web address, like shop.example.com. **What it means:** The address points to a private or local network, which Plugsight can't reach. **How to fix it:** Use your store's public address on the internet. ### The store didn't accept these keys. Copy all four again from the integration's details in Magento admin, and check the integration says Active. **What it means:** One of the keys is wrong or incomplete, or the integration isn't activated. **How to fix it:** In Magento admin, open **Edit → Integration Details**, copy all four keys again, and check the integration's status is **Active**. ### The integration isn't allowed to read this. In Magento admin, edit the integration's API resources to include …, save, then reauthorize it. **What it means:** The integration is missing one of the resources: orders, products or customers. **How to fix it:** Edit the integration, open the **API** tab, tick the resource the message names (**Sales → Operations → Orders**, **Catalog → Inventory → Products** or **Customers**), click **Save**, then reauthorize the integration. ### The store rejected Plugsight's integration keys; the integration may have been deleted or its keys renewed. Reconnect the store on the Connections page in Plugsight. **What it means:** The integration was deleted or its keys changed. The connection shows **Reconnect needed**. **How to fix it:** Copy the current four keys (or create the integration again) and connect the store again. ### … didn't answer like a Magento store (HTTP …). Check the address, and that the REST API isn't blocked by a firewall or security module. **What it means:** The address didn't return Magento data. **How to fix it:** Check the address. If it's right, allow Magento's REST API (addresses under /rest/V1/) in your firewall or security module. ### Couldn't find shop.example.com. Check the server name for typos. **What it means:** The address doesn't exist on the internet. **How to fix it:** Check the spelling of your store's address. ## Related articles - [WooCommerce](/connectors/woocommerce) - [Shopify](/connectors/shopify) - [Mailchimp](/connectors/mailchimp) - [Google Merchant Center](/connectors/google-merchant-center) - [Magento tools](/developers/magento-tools) - [Review your store's sales](/guides/store-sales-review) --- # Shopify URL: https://docs.plugsight.app/connectors/shopify Connect one Shopify store or many with a read-only app from Shopify's Dev Dashboard, so your AI can report on sales, orders, stock and customers. Connect your Shopify stores and your AI can tell you how each one is doing: sales, orders, best sellers, stock at each location and customers. You create a small app for each store in Shopify's Dev Dashboard, give it read-only access, and paste its client ID and secret into Plugsight. Nothing goes through the Shopify App Store. Plugsight only reads: it can't change anything in your stores. Each store is its own connection, so an agency or a business with several stores can connect all of them and ask about one, or compare them. ## What your AI can do - **Sales report** for any period, added up from all your orders in it: revenue, orders, items sold, average order, discounts, shipping, tax and refunds, day by day, plus the best-selling products. Only paid orders (paid, partially paid, partially refunded and refunded) count as revenue; pending, authorised-only, voided and expired payments, cancelled orders and test orders are listed separately. - **List orders**, newest first, by status, payment status, fulfilment status, date range, customer email or any text. - **Read one order** in full, by the order number customers see (for example #1001): items with their variant and SKU, what's still to ship, totals, discount codes, shipping, tax, refunds, tracking numbers, addresses, note and tags. - **Search products** by title, SKU, vendor, type or status, with price, compare-at price and stock for each variant, or list variants whose stock is at or below a quantity you choose. - **Stock by location** for one product: available, on hand, committed and incoming at each location. - **Search customers** by name or email, with how many orders they've placed, how much they've spent and when they joined. ### Example questions - "Compare last month's sales across my Shopify stores." - "Which products sold best this week, and which variants are running low on stock?" - "How much of SKU TS-42 do we have at each location?" - "Find order #1042 and tell me what was bought and where it's shipping." - "Show every order from ann@example.com this year." - "Compare Meta Ads spend last month with Shopify revenue for the same days." ## What you need - Any plan. Shopify isn't a marketing connector. Each store counts as one connection towards your plan's limit. - For each store, a staff account in the organisation that owns the store with the App developer role (or, on Shopify Plus, a role with the Build and manage apps permission). The store owner can create the app, or give someone this role. - Collaborator accounts, the kind agencies are often given, can't use Shopify's Dev Dashboard. Plugsight can only get access with an app made in the store's own organisation, so an agency can't make one app for all its clients' stores. For each client, either the client's staff creates the app and sends you its client ID and secret, or the client gives you a staff account with the App developer role. - The store's myshopify.com address, like your-store.myshopify.com. Shopify shows it in your admin under **Settings → Domains**. ## Connect a store This takes about 5 minutes per store, in your Shopify admin and Shopify's Dev Dashboard. Repeat it for each store you want to connect. ### 1. Create an app in Shopify's Dev Dashboard 1. In your Shopify admin, go to **Settings → Apps** and click **Develop apps**. 2. In Shopify, click **Build apps in Dev Dashboard**. Starting from the store's own admin keeps the app in the organisation that owns the store, which Shopify requires. If you can't open the Dev Dashboard, ask the store owner for the App developer role (see [What you need](#what-you-need)). 3. In Shopify's Dev Dashboard, click **Create app** and choose **Start from Dev Dashboard**. 4. Name it "Plugsight" and, in Shopify, click **Create**. ### 2. Give it read-only access 1. In the app's version, add these access scopes: read_orders, read_all_orders, read_products, read_customers, read_inventory and read_locations. 2. Release the version. read_all_orders lets your AI see orders older than 60 days. Without it, Shopify only shares the last 60 days. ### 3. Turn on protected customer data Shopify doesn't share customers' names, emails, addresses or phone numbers with a new app until you ask for them. Without this step, customer searches and order details can fail with a message telling you to turn it on. 1. In Shopify's Dev Dashboard, open the app, click **Settings** and go to **Access requests**. 2. In Shopify, find **Protected customer data** and click **Manage**. 3. Select **Customer data**, give your reason (for example, "Reports on orders and customers for the store's owner") and, in Shopify, click **Apply reasons**. 4. Select the Name, Email, Address and Phone fields, give your reason and, in Shopify, click **Apply reasons**. 5. Fill in Shopify's **Data protection details**, then click **Save** in Shopify. ### 4. Install it on the store 1. Open the app in Shopify's Dev Dashboard and click **Install app**. 2. Choose your store and approve the access it asks for. ### 5. Paste the client ID and secret into Plugsight 1. Open the app's settings in the Dev Dashboard. Its client ID and client secret are there. 2. In Plugsight, open **Connections**, click **Add connection** and choose **Shopify**. 3. Type the **Store address**, like your-store.myshopify.com. You can also paste the store's admin address. 4. Optionally give the connection a **Name**, such as "Client: North Outfitters". 5. Paste the **Client ID** and **Client secret**. 6. Click **Test connection & save**. Plugsight checks the app's access with Shopify before saving anything. When it works, you see a message like "Connected North Outfitters (north-outfitters.myshopify.com), id "…"." If the app is missing an access scope, the message says which. Then add the connection to an MCP server. If this is your first store, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. > [!NOTE] > Plugsight exchanges the client ID and secret for an Admin API access token that Shopify makes last about a day, and gets a new one when it runs out. Shopify only allows this for apps owned by the same organisation as the store, which is why the app is made from the store's own admin. ### Already have a custom app with an access token? Custom apps made in the Shopify admin before 2026 have an Admin API access token that starts with shpat\_. Shopify no longer lets stores make new ones, but existing ones keep working. 1. On the Shopify connect page in Plugsight, open **Use an existing custom app's access token instead**. 2. Type the **Store address** and paste the **Admin API access token**. 3. Click **Test connection & save**. The app needs read access to orders, products, customers, inventory and locations. ## Several stores - Each store you connect is its own connection, named after the store. Connect as many as your plan allows. - Connecting a store that's already connected replaces its credentials instead of adding it twice. - When an MCP server has more than one store, name the store in your question ("for North Outfitters…"). Your AI passes the right connection to each tool. ## What it can and can't change Shopify is **read-only** in Plugsight. Your AI can't create, edit, fulfil, refund or cancel orders, or change products, prices, stock, customers, discounts or settings. The app only has read access scopes. To cut access, uninstall the app from your store in Shopify, and remove the connection on **Connections**. ## Limits - A sales report reads up to 10,000 orders and stops asking Shopify for more after about 40 seconds. On a very busy store or a long period, or if Shopify stops answering part-way, it can stop early: your AI is told the totals are incomplete and how far they reach. Ask for a shorter period. - Best-selling products count the first 10 different items of each order. Revenue and items sold always count every item. - Sales report dates and order date filters use UTC. - Order and customer lists return up to 100 at a time (25 by default), product lists up to 50. Your AI can ask for the next page. - Sales reports list up to 50 best-selling products (10 by default). - Without read_all_orders, only the last 60 days of orders can be read; a sales report reaching further back says it's incomplete. - On Shopify's Basic plan, Shopify may hide customers' names, emails, addresses and phone numbers from custom apps, even with protected customer data turned on. Shopify keeps some of this access for stores on its Grow plan or higher. - Stock by location lists up to 20 variants of a product, and up to 10 locations for each. - Shopify limits how fast an app can ask for data. Plugsight waits and retries when it's asked to slow down. ## Troubleshooting ### Enter your store's myshopify.com address, like your-store.myshopify.com. Your Shopify admin shows it under Settings → Domains. **What it means:** The address isn't a myshopify.com address. Plugsight only connects to stores by that address, never by a custom domain such as shop.example.com. **How to fix it:** In your Shopify admin, open **Settings → Domains** and copy the address ending in .myshopify.com. ### Shopify didn't accept this client ID and secret for …. Check you copied both from the app's settings in the Dev Dashboard, that the app is installed on this store, and that the store belongs to the same organisation as the app. **What it means:** Shopify wouldn't give Plugsight an access token. The client ID or secret is wrong, the app isn't installed on this store, or the app was made outside the organisation that owns the store. **How to fix it:** Copy both again from the app's settings. Check the app is installed on the store you typed. If it was made elsewhere, for example in an agency's own organisation, create it again starting from the store's own admin with a staff account of that store, as in [step 1](#1-create-an-app-in-shopifys-dev-dashboard). ### The app on … can't read orders. Add the read_orders access scope (and …) to the app, release a new version and update the app on the store, then try again. **What it means:** The app doesn't have the read_orders access scope, which Plugsight needs. **How to fix it:** Add the access scopes the message lists to the app's version, release it, approve the update on your store, then connect again. ### The Plugsight app on … doesn't have the … access scope. Add it to the app's access scopes, release a new version, then update the app on the store (or reconnect). **What it means:** Your AI asked for something the app can't read, such as customers without read_customers. **How to fix it:** Add the access scope the message names, release a new version of the app and approve the update on your store. ### The Plugsight app on … isn't allowed to read customers' details (…). In the Dev Dashboard, open the app, click Settings, go to Access requests and, under Protected customer data, turn on customer data and the name, email, address and phone fields. Then try again. **What it means:** Shopify won't share customers' details with the app, because it hasn't been given access to protected customer data. The message names what Shopify held back, such as the email field. **How to fix it:** Follow [step 3](#3-turn-on-protected-customer-data), then ask again. On Shopify's Basic plan, Shopify may still hold back some customer details from custom apps. ### Shopify rejected the app's client ID and secret; the app may have been uninstalled or its secret rotated. Reconnect the store on the Connections page in Plugsight. **What it means:** The app was uninstalled from the store or its secret changed. The connection shows **Reconnect needed**. **How to fix it:** Install the app again if needed, copy the current client ID and secret, and connect the store again. ### Shopify rejected the Admin API access token; the app may have been uninstalled or the token revoked. Reconnect the store on the Connections page in Plugsight. **What it means:** The custom app was uninstalled or its token no longer works. The connection shows **Reconnect needed**. **How to fix it:** Create a Dev Dashboard app for the store and connect with its client ID and secret, as in [Connect a store](#connect-a-store). ### The Admin API access token starts with shpat\_. **What it means:** What you pasted isn't a custom app's Admin API access token. **How to fix it:** Copy the whole token. If you have a client ID and secret instead, use the main form. ### Shopify is limiting requests to … right now. Wait a minute, then try again. **What it means:** The store's app hit Shopify's rate limit, even after Plugsight waited and retried. **How to fix it:** Wait a minute and ask again, or ask for a shorter period or fewer results. ## Related articles - [WooCommerce](/connectors/woocommerce) - [Magento / Adobe Commerce](/connectors/magento) - [Shopify tools](/developers/shopify-tools) - [Review your store's sales](/guides/store-sales-review) - [Agencies](/use-cases/agencies) - [Connection errors](/troubleshooting/connection-errors) --- # Mailchimp URL: https://docs.plugsight.app/connectors/mailchimp Connect Mailchimp with an API key so your AI can report on campaign results, audience growth and subscribers. Read-only. Connect Mailchimp and your AI can tell you how your newsletters are doing: opens, clicks, revenue, unsubscribes and audience growth. You connect with an API key you create in Mailchimp. Plugsight only reads: it never sends, schedules, edits or deletes campaigns, audiences or contacts. ## What your AI can do - **List audiences** (lists) with subscribers, unsubscribes, cleaned addresses, average open and click rates, and how many campaigns each has had. - **List campaigns**, newest first, with subject, audience, emails sent, open and click rates, and orders and revenue when your store is connected to Mailchimp. Filter by status (sent, drafts, scheduled, sending or paused), send date or audience. - **Campaign report** for one sent campaign: opens, clicks, bounces, unsubscribes, spam complaints, orders and revenue, how it compares with your audience's average and your industry, its most-clicked links, and each version's results for A/B tests. - **Automations and segments**: your classic automations with their emails and results, and each audience's segments and tags with how many people are in them. (Mailchimp doesn't let other apps read Customer Journeys.) - **Audience growth**, month by month: new subscribers (opt-ins and imports), unsubscribes, cleaned addresses and the total at the end of each month. - **Find a subscriber** by email address or name, across audiences: their status (subscribed, unsubscribed, cleaned), when they joined, tags, groups, the fields you collect (such as name, phone or birthday), rating and average open and click rates. ### Example questions - "Which of last quarter's campaigns had the best click rate, and what did their subject lines have in common?" - "How does our latest newsletter compare with our audience average and the industry?" - "Is our list growing? Show new subscribers and unsubscribes by month for the last year." - "Which links got the most clicks in last week's campaign?" - "Is jane@example.com still subscribed, and when did she join?" ## What you need - Any plan. Mailchimp is in **Email marketing**, not marketing & analytics, so it's on the Free plan too. - A Mailchimp login that can create API keys. ## Connect Mailchimp This takes about a minute. 1. Log in to Mailchimp and open **API keys** (or click your profile picture → **Profile** → **Extras** → **API keys**). 2. Click **Create A Key**, name it "Plugsight" and click **Generate Key**. 3. Copy the key. Mailchimp shows it only once. It ends with something like -us21. 4. In Plugsight, open **Connections**, click **Add connection** and choose **Mailchimp**. 5. Paste the key into **API key**. Optionally give the connection a **Name**, such as "Newsletter". 6. Click **Test connection & save**. Plugsight checks the key with Mailchimp before saving anything. When it works, you see a message like "Connected Acme Ltd (12,480 subscribers), id "…"." Then add the connection to an MCP server. If this is your first Mailchimp connection, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. > [!WARNING] > New Mailchimp API keys expire after a year. When yours does, create a new key and connect Mailchimp again with it. ## What it can and can't change Mailchimp is **read-only** in Plugsight. Your AI can't create, send, schedule or edit campaigns, or add, change or remove contacts. To cut access, delete the key in Mailchimp under **API keys**, and remove the connection on **Connections**. ## Limits - Campaign lists return up to 100 campaigns at a time (25 by default). Sent campaigns are listed by default. - Audience growth covers up to 60 months (12 by default). - Campaign reports list up to 50 most-clicked links (10 by default). - Up to 100 audiences are listed. - Orders and revenue only appear when your online store is connected to Mailchimp. ## Troubleshooting ### That isn't a Mailchimp API key. It ends with a dash and your data centre, like -us21. **What it means:** The key you pasted is incomplete, or isn't a Mailchimp API key. **How to fix it:** Copy the whole key again, including the ending such as -us21. ### Mailchimp didn't accept that API key. Check you copied all of it, including the ending like -us21, and that it hasn't been deleted. **What it means:** Mailchimp doesn't recognise the key. **How to fix it:** Check you copied all of it. If it was deleted or you can't copy it again, create a new key. ### Mailchimp rejected the API key; it may have been deleted or disabled. Reconnect Mailchimp on the Connections page in Plugsight. **What it means:** The key stopped working, for example because it was deleted or it expired. The connection shows **Reconnect needed**. **How to fix it:** Create a new key in Mailchimp and connect Mailchimp again with it. ### Mailchimp couldn't find that. Check the id (list tools return valid ids). **What it means:** Your AI asked for a campaign or audience that doesn't exist. **How to fix it:** Ask your AI to list campaigns or audiences first, then pick one. ## Related articles - [WooCommerce](/connectors/woocommerce) - [Magento / Adobe Commerce](/connectors/magento) - [Google Forms](/connectors/google-forms) - [Mailchimp tools](/developers/mailchimp-tools) --- # Custom API URL: https://docs.plugsight.app/connectors/custom-api Connect any REST API, such as your own app or a tool without a connector, so your AI can read from it and, with your approval, make changes. Connect any REST API on a public https address: your own app, an internal tool, or a service Plugsight has no connector for. You give Plugsight the API's address and how it signs in. Your AI can then call it through your MCP server. Import the API's OpenAPI (Swagger) spec and each endpoint becomes its own tool, so your AI knows what the API can do. ## What your AI can do - **Read from the API**: any `GET` request under the address you connect, with JSON answers read for your AI. - **Use each endpoint as a tool**: with an OpenAPI 3 or Swagger 2.0 spec imported, every endpoint is its own tool, with its parameters and request body, for APIs with up to 50 endpoints. - **Look up endpoints**: your AI can list and search every imported endpoint (up to 300), with its parameters, and call any of them. - **Make changes**: `POST`, `PUT`, `PATCH` and `DELETE` requests, only when you allow changes, and each one waits for your approval in the chat. ### Example questions - "Using the Acme CRM API, list the customers who signed up this week." - "Look up order 1042 in our fulfilment API and tell me where it's stuck." - "Which endpoints does the inventory API have for stock levels?" - "Create a ticket in our tracker for the bug I just described." ## What you need - The Pro or Agency plan. On Free, the Custom API tile shows **On Pro: upgrade to connect**. See [Plans](/get-started/plans). - The API's base URL: the public https address every request starts with, like https://api.example.com/v1. - How it signs in, from the API's documentation or settings: an API key, a bearer token, a username and password, or an OAuth 2.0 client ID and secret. - Optionally, the API's OpenAPI or Swagger spec, as a web address or a file you can copy from (JSON or YAML, up to 2 MB). > [!TIP] > Make a key just for Plugsight, with only the access your AI needs. You can delete it at the API's end any time to cut access. ## Connect your API 1. In Plugsight, open **Connections**, click **Add connection** and choose Custom API (any REST API) in the catalog. 2. Type the API's **Base URL**, like https://api.example.com/v1. Your AI can only call paths under it. 3. Optionally give the connection a **Name**, such as "Acme CRM". It also starts the names of the API's tools, so keep it short. 4. Under **How it signs in**, choose one, then fill in the boxes it shows: - **API key**: choose where to send it under **Send the key in** (a header or the query string), type the header or parameter name your API expects, such as X-API-Key, and paste the **API key**. - **Bearer token**: paste the **Token**. It's sent as "Authorization: Bearer" and the token. - **Username and password**: type the **Username** and **Password**. - **OAuth 2.0 client credentials**: type the **Token URL**, **Client ID** and **Client secret**, and the **Scope** if your API needs one. Plugsight gets an access token itself and renews it when it expires. - **No sign-in**: for APIs anyone can call. 5. If your API wants more on every request, such as an account id, click **Add header** under **Extra headers** and type its name and value. 6. To import a spec, choose **From a web address** or **Paste it** under **OpenAPI spec**, then give the **Spec address** or paste the **Spec**. 7. Optionally type a **Test path**, such as /me. Plugsight sends a `GET` request to it before saving, and only saves if it succeeds. Pick one that only reads. 8. Click **Test connection & save**. When it works, you see a message like "Connected Acme CRM (api.example.com), id "acme-crm". Imported 12 operations, each a tool your AI can use." Then add the connection to an MCP server. Each import adds or changes tools, so [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. ### Connect it again To change the key, or import a new version of the spec, connect it again with the same **Base URL** and **Name**: Plugsight replaces what it has. Without a new spec, the endpoints already imported stay. With a different **Name**, it's a second connection, which is how you connect the same API twice, for example with a test key and a live key. ## What it can and can't change Reading is always on: your AI can send `GET` and `HEAD` requests whenever the connection is in its MCP server. `POST`, `PUT`, `PATCH` and `DELETE` requests change things in your API, so they need all of these: 1. Your plan includes changes (Pro and Agency do). 2. The connection's switch on **Connections** says **Can make changes**. It starts as **Read-only** for every API you connect. 3. **Allow changes** is ticked on the MCP server your AI app uses. 4. **Custom APIs and MCP servers** isn't paused on **Permissions**. 5. You approve the exact request in the chat. See [How changes are allowed](/permissions/how-changes-are-allowed). What Plugsight never does, whatever you allow: - It never calls an address outside the base URL. A request for a full address, another site, or a path that climbs out of the base URL (with `..`) is refused before anything is sent. - It never calls private or local networks, and never follows redirects. - It never shows your key, token, password, client secret or extra headers to your AI. They're stored encrypted, and cut from anything the API sends back. - It never sets headers such as Host, Cookie or Content-Length, and your AI can't replace the sign-in or your extra headers. To cut access, delete the key at the API's end, and remove the connection on **Connections**. ## Limits - Public https addresses on the standard port only. - Each request has 30 seconds to answer. Plugsight reads up to 1 MB of the answer, and gives your AI up to 100,000 characters of it; anything longer is cut, and your AI is told so. - Request bodies are JSON or plain text, up to 1 MB. File uploads and forms aren't supported. - A spec can have up to 300 endpoints imported. With more than 50, they don't get tools of their own: your AI finds them in the list and calls them by name. - Only references inside the spec are followed; parts that point to other files are described loosely. - Up to 20 extra headers. ## Troubleshooting ### Custom API connections are on the Pro plan. Upgrade under Billing to connect your own APIs. **What it means:** Your plan doesn't include Custom APIs. **How to fix it:** Upgrade under **Billing**. See [Plans](/get-started/plans). ### The base URL must start with https://. Plugsight only sends keys over encrypted connections. **What it means:** The address starts with http://, so keys would travel unencrypted. **How to fix it:** Use the API's https:// address. If it has none, Plugsight can't connect to it. ### That address isn't a public website. Enter the API's public https address, like https://api.example.com/v1. **What it means:** The address points to a private or local network, which Plugsight never calls. **How to fix it:** Use the API's public address on the internet. ### The test request (GET [path]) answered HTTP [status]. Check the base URL, the sign-in details and the test path. **What it means:** The API answered the test path with an error, so nothing was saved. 401 or 403 usually means the sign-in is wrong; 404 means the base URL or test path is. **How to fix it:** Check each detail against the API's documentation, or leave **Test path** empty to save without the test. ### The token URL didn't give an access token (HTTP …). Check the token URL, client ID, client secret and scope. **What it means:** The OAuth token endpoint refused the client ID and secret, or answered something else. **How to fix it:** Copy the client ID and secret again, check the **Token URL**, and leave **Scope** empty unless your API needs one. ### That OpenAPI spec is larger than 2 MB. Import a smaller one, or call the API by path instead. **What it means:** The spec is too big to import. **How to fix it:** Import a smaller version of the spec, such as one section of the API, or connect without a spec. Your AI can still call the API by method and path. ### The API rejected the saved sign-in details (HTTP 401). **What it means:** The API no longer accepts the key or token. The connection shows **Reconnect needed**. **How to fix it:** Make a new key or token, then [connect it again](#connect-it-again) with the same **Base URL** and **Name**. ### Changes are off for "[connection]". Allow them under Connections first. **What it means:** The connection's switch is **Read-only**, so your AI can read but not change anything. **How to fix it:** On **Connections**, click the switch so it says **Can make changes**. ### Custom API changes are paused (Permissions page). **What it means:** Changes through Custom APIs and custom MCP servers are paused for every connection. **How to fix it:** On **Permissions**, resume **Custom APIs and MCP servers**. See [Pause changes](/permissions/pause). ## Related articles - [How changes are allowed](/permissions/how-changes-are-allowed) - [Approvals in the chat](/permissions/approvals) - [Refresh the tools list](/ai-apps/refresh-tools) - [Custom API tools](/developers/custom-api-tools) - [Custom MCP server](/connectors/custom-mcp) - [Connectors](/connectors) --- # Custom MCP server URL: https://docs.plugsight.app/connectors/custom-mcp Add any remote MCP server's tools to your Plugsight MCP servers, signed in with OAuth, a token or headers, with changes behind your approval. Add any remote MCP server on a public https address: your own, an internal one, or a service that offers an MCP server Plugsight has no connector for. Plugsight connects to it, lists its tools and offers them in your Plugsight MCP servers, next to your other accounts. Your AI app then needs only Plugsight, and the same switches and approvals apply to every change. ## What your AI can do - **Use the server's tools**: every tool the server lists (up to 100) becomes a tool of your MCP server, named after the connection, like `notes__search_notes` for a connection called "Notes". - **Read straight away**: tools the server marks read-only work whenever the connection is in your MCP server. - **Make changes, with your approval**: every other tool counts as a change. It works only when you allow changes, and each call waits for your approval in the chat. - **Refresh the tools**: your AI can ask Plugsight to list the server's tools again, for example after the server adds one. ### Example questions - "Search my notes server for anything about the Q3 launch." - "Using the Notes tools, create a note with today's meeting actions." - "Which tools does the Notes server have, and which of them make changes?" - "Refresh the Notes server's tools and tell me what's new." ## What you need - The Pro or Agency plan. On Free, the Custom MCP server tile shows **On Pro: upgrade to connect**. See [Plans](/get-started/plans). - The server's remote MCP address, from its documentation. It starts with https:// and often ends in /mcp. Older servers' addresses can end in /sse; that works too. - How it signs you in: most servers ask you to sign in with them (OAuth); others take a token, or a header with a key. > [!WARNING] > Only connect servers you trust. Your AI reads what the server's tools send back, and the server writes its own tool descriptions. Plugsight marks those descriptions as the server's own words and never lets them change its rules, but a server could still try to mislead your AI. ## Connect a custom MCP server 1. In Plugsight, open **Connections**, click **Add connection** and choose Custom MCP server (any remote MCP server) in the catalog. 2. Type the **Server address**, like https://mcp.example.com/mcp. 3. Optionally give the connection a **Name**, such as "Notes". It also starts the names of the server's tools, so keep it short. 4. Under **How Plugsight signs in**, choose one: - **Sign in with the server (OAuth)**: click **Sign in**. You go to the server's own sign-in page, then come back to **Connections**. Plugsight finds the server's sign-in and registers itself there; if the server doesn't allow that, see [Use your own OAuth client](#use-your-own-oauth-client). - **Bearer token**: paste the **Token**. It's sent as "Authorization: Bearer" and the token. - **Headers**: type each header's name and value, such as X-API-Key and your key. Click **Add header** for another. - **No sign-in**: for servers anyone can use. 5. For every choice but OAuth, click **Test connection & save**. Plugsight connects to the server and lists its tools before saving. When it works, you see a message like "Connected Notes (mcp.example.com), id "notes". It has 6 tools: 4 that only read, and 2 that can make changes (off until you allow changes)." Then add the connection to an MCP server, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. ### Use your own OAuth client Some servers don't let apps register themselves. Then, in the server's settings or documentation, create an OAuth client with the redirect address shown under **Use my own OAuth client** (it ends in /auth/custom-mcp/callback). Back in Plugsight, choose **Sign in with the server (OAuth)**, tick **Use my own OAuth client**, type its **Client ID** and **Client secret**, and the **Scope** if the server needs one, then click **Sign in**. ### Connect it again To change the token or headers, or to sign in again, connect it again with the same **Server address** and **Name**: Plugsight replaces the sign-in. With a different **Name**, it's a second connection, which is how you connect the same server twice, for example with two accounts. ## What it can and can't change Tools the server marks read-only always work while the connection is in your MCP server. Plugsight decides this from the server's own read-only mark, so a tool without that mark counts as a change, whatever its description says. Every other tool needs all of these: 1. Your plan includes changes (Pro and Agency do). 2. The connection's switch on **Connections** says **Can make changes**. It starts as **Read-only** for every server you connect. 3. **Allow changes** is ticked on the MCP server your AI app uses. 4. **Custom APIs and MCP servers** isn't paused on **Permissions**. 5. You approve the exact call in the chat. See [How changes are allowed](/permissions/how-changes-are-allowed). What Plugsight never does, whatever you allow: - It never connects to private or local networks, plain http addresses or other ports, for the server and its sign-in alike, and never follows redirects. - It never shows your token, headers or sign-in to your AI. They're stored encrypted, and cut from anything the server sends back. The server's address is stored encrypted too: the app shows only its host. - It never lets a tool's description change how the tool is treated: descriptions are shown as the server's own words, and cut short. To cut access, remove the connection on **Connections**, and sign Plugsight out or delete its token at the server's end. ## Limits - Public https addresses on the standard port only, with no query string. - Up to 100 tools per server. A server with more offers its first 100, and says so. - Plugsight keeps each server's tool list for a few minutes, and on the connection, so a server that's slow or down doesn't hide its tools. While it can't be reached, your AI is told how old the list is. - Each call has 60 seconds. Plugsight passes on text only (images and files are described, not passed on), up to 100,000 characters; anything longer is cut, and your AI is told so. - Tool descriptions are cut to 1,000 characters, and the descriptions inside a tool's argument list to 500. A tool whose argument list is very large (or one past a server's total for argument lists) is offered without it, and your AI is told to give the arguments the server expects. ## Troubleshooting ### Custom MCP server connections are on the Pro plan. Upgrade under Billing to connect your own MCP servers. **What it means:** Your plan doesn't include custom MCP servers. **How to fix it:** Upgrade under **Billing**. See [Plans](/get-started/plans). ### The server address must start with https://. Plugsight only signs in over encrypted connections. **What it means:** The address starts with http://, so your sign-in would travel unencrypted. **How to fix it:** Use the server's https:// address. If it has none, Plugsight can't connect to it. ### That address isn't a public website. Enter the MCP server's public https address, like https://mcp.example.com/mcp. **What it means:** The address points to a private or local network, which Plugsight never calls. **How to fix it:** Use the server's public address on the internet. ### No MCP server answered at that address on [host] (HTTP …). Check the address: it often ends in /mcp. **What it means:** Something answered at that address, but not an MCP server. **How to fix it:** Copy the remote MCP address from the server's documentation again. It's often the site's address followed by /mcp or /sse. ### [host] doesn't let apps register themselves. In the server's settings or documentation, create an OAuth client with the redirect address …, then tick Use my own OAuth client and enter its client ID (and secret). **What it means:** The server's sign-in needs a client made for Plugsight in advance. **How to fix it:** Follow [Use your own OAuth client](#use-your-own-oauth-client). ### This sign-in was started in another browser, replaced by a newer one, or took too long. Start it again from the custom MCP server page. **What it means:** The sign-in must finish in the same browser that started it, within 30 minutes. A browser has one sign-in at a time: starting another one cancels the first. **How to fix it:** Open the custom MCP server page again and click **Sign in**. ### The MCP server turned the saved sign-in away (HTTP 401). **What it means:** The server no longer accepts the token or headers. The connection shows **Reconnect needed**. **How to fix it:** Get a new token or key from the server, then [connect it again](#connect-it-again) with the same **Server address** and **Name**. ### The MCP server's sign-in expired or was revoked. **What it means:** The OAuth sign-in can't be renewed any more, for example because you signed Plugsight out at the server's end. **How to fix it:** [Connect it again](#connect-it-again) and sign in. ### Changes are off for "[connection]". Allow them under Connections first. **What it means:** The connection's switch is **Read-only**, so your AI can use only the tools the server marks read-only. **How to fix it:** On **Connections**, click the switch so it says **Can make changes**. ### Custom MCP server changes are paused (Permissions page). **What it means:** Changes through custom MCP servers and Custom APIs are paused for every connection. **How to fix it:** On **Permissions**, resume **Custom APIs and MCP servers**. See [Pause changes](/permissions/pause). ## Related articles - [How changes are allowed](/permissions/how-changes-are-allowed) - [Approvals in the chat](/permissions/approvals) - [Refresh the tools list](/ai-apps/refresh-tools) - [Custom API](/connectors/custom-api) - [Custom MCP server tools](/developers/custom-mcp-tools) - [Connectors](/connectors) --- # Use cases URL: https://docs.plugsight.app/use-cases How different people use Plugsight, with the connectors, MCP server setup, questions and weekly routine that suit each role. Plugsight connects your own accounts to Claude, ChatGPT and other AI apps. What you connect, and how you set up your MCP servers, depends on the work you do. Each article in this section covers one role or situation: - **Who it's for**, and what changes when you can ask your AI instead of opening each tool. - **Which connectors to set up**, with a link to each connector's own article. - **The MCP server setup** we recommend: how many servers, which accounts each reaches, and whether to tick **Allow changes**. - **Example questions** that work with the tools Plugsight gives your AI today. - **A typical week**: the questions people ask on Monday morning, mid-week and on Friday. - **Safety tips**: what to keep read-only, when approvals matter, and when to use **Pause**. ## Pick your situation | If you are… | Read | Main connectors | | --- | --- | --- | | An in-house marketer | [In-house marketers](/use-cases/in-house-marketers) | Google Ads, Microsoft Advertising, Search Console, GA4 | | An agency with many clients | [Agencies managing many clients](/use-cases/agencies) | Google Ads (manager accounts), GA4, Search Console, per-client servers | | A PPC specialist | [PPC specialists](/use-cases/ppc-specialists) | Google Ads, Microsoft Advertising, GA4 | | An SEO specialist | [SEO specialists](/use-cases/seo-specialists) | Search Console, PageSpeed Insights, GA4 | | A support team | [Support teams](/use-cases/support-teams) | Zendesk, shared inboxes | | An online store owner | [E-commerce store owners](/use-cases/ecommerce-store-owners) | WooCommerce, Magento, Merchant Center, Google Ads | | A founder or small business owner | [Founders and small business owners](/use-cases/founders-and-small-businesses) | Email, calendar, contacts, and whatever else you run | | In sales or account management | [Sales and account managers](/use-cases/sales-and-account-managers) | Email, calendar, contacts | | An email marketer | [Email marketers](/use-cases/email-marketers) | Mailchimp, GA4, your store | | A content or YouTube creator | [Content and YouTube creators](/use-cases/content-and-youtube-creators) | YouTube, Search Console, GA4 | | An analyst who builds reports | [Analysts and reporting](/use-cases/analysts-and-reporting) | Every marketing connector, deep dives, the developer API | | An executive assistant, or anyone with a busy inbox | [Executive assistants and busy inboxes](/use-cases/executive-assistants) | Several mailboxes, Outlook or iCloud Calendar, contacts | Most people fit more than one row. A founder who runs a shop might read both the founder and the store owner articles. Every combination works: one MCP server can reach any mix of accounts. ## Before you start - **Plans.** Email, Zendesk, calendars, contacts, Mailchimp, WooCommerce and Magento work on every plan. Marketing and analytics connectors (Google Ads, Microsoft Ads, Meta Ads, LinkedIn Ads, Search Console, GA4 and Bing Webmaster Tools) and all changes, such as sending email, need **Pro** or **Agency**. See [Plans](/get-started/plans). - **Coming soon.** Not in the **Connector catalog** until Google approves Plugsight's access: Google Drive, Google Tag Manager, YouTube, Google Merchant Center, Google Sheets, Google Docs, Google Forms, Google Meet. The articles below say where this matters. - **First steps.** If you haven't connected anything yet, start with the [Quick start](/get-started/quick-start). ## What every setup has in common - Your AI can always **read** the accounts its MCP server reaches, and write email drafts. - Marketing, analytics, e-commerce, email marketing, files and contacts are **read-only**: Plugsight never changes them. See [Read-only connectors](/permissions/read-only-connectors). - Sending email, Zendesk changes and calendar bookings need the account's switch on, **Allow changes** ticked on the server, nothing paused, a Pro or Agency plan, and your approval in the chat. See [How changes are allowed](/permissions/how-changes-are-allowed). - **Activity** lists everything your AI did, and **Pause everything** on **Permissions** stops all changes at once. See [Activity log](/permissions/activity) and [Pause changes](/permissions/pause). ## Related articles - [Questions to try first](/get-started/first-questions) - [Use several MCP servers](/mcp-servers/multiple-servers) - [All connectors](/connectors) --- # In-house marketers URL: https://docs.plugsight.app/use-cases/in-house-marketers Connect your ad accounts, Search Console and GA4 so your AI can answer marketing questions across paid, organic and analytics at once. ## Who it's for You look after marketing for one company or brand. You spend time in Google Ads, Microsoft Advertising, Search Console and Google Analytics 4, and you often need numbers from more than one of them to answer a single question: did the new campaign bring sales, or did organic traffic drop at the same time? With Plugsight, your AI reads all of them live. You ask in plain English, and it pulls the numbers, combines them and explains what changed. No CSV exports. You need the **Pro** or **Agency** plan for marketing and analytics connectors. ## Connectors to set up | Connector | What it adds | Notes | | --- | --- | --- | | [Google Ads](/connectors/google-ads) | Campaigns, keywords, search terms, conversions, impression share | Pro | | [Microsoft Advertising](/connectors/microsoft-advertising) | The same for Bing Ads, plus age, gender and audiences | Pro | | [Google Search Console](/connectors/google-search-console) | Organic clicks, impressions, CTR and position by query and page | Pro | | [Google Analytics 4](/connectors/google-analytics-4) | Sessions, channels, key events, revenue, funnels, realtime | Pro | | [PageSpeed Insights](/connectors/pagespeed-insights) | Page speed and Core Web Vitals for any public page | No connection needed | | Your work mailbox, for example [Gmail](/connectors/gmail) or [Outlook](/connectors/outlook) | Briefs, agency emails, invoices from ad platforms | Optional | | [Google Tag Manager](/connectors/google-tag-manager) | Audit tags and triggers | Coming soon | One Google sign-in reaches every Search Console site, GA4 property and Google Ads account that login can open, and counts as one connection per connector. See [What counts as a connection](/get-started/plans#what-counts-as-a-connection). > [!TIP] > If your Google login also reaches test sites or old properties, hide them under **Show sites & accounts** on **Connections**, so they don't creep into totals. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## Recommended MCP server setup One server is usually enough. - **Name:** "Marketing" - **Account access:** **All accounts**, or **Selected accounts** if you also connect a personal mailbox you'd rather keep out - **Allow changes:** ticked, if you connected a mailbox and want your AI to be able to send (each email still needs your approval). Marketing connectors are read-only either way. If you want to share a link with a colleague who only needs to read reports, create a second server with **Allow changes** unticked. See [Use several MCP servers](/mcp-servers/multiple-servers). ## Example questions - "Give me an overview of all my marketing accounts this month against last month." - "Which channels drove the most revenue this month vs last month?" - "Where are we paying for Google Ads clicks on queries we already rank top 3 for organically?" - "Which keywords convert below our average CPA but lose impression share to budget?" - "Which landing pages lost the most organic clicks since last month?" - "Which search terms cost us money last month without converting? Suggest negative keywords." - "How did Microsoft Ads perform last month compared with Google Ads?" - "Build a funnel from product page to purchase and show where mobile users drop off." - "What counts as a conversion in our GA4 property, and how many happened last week?" - "Do our top five landing pages pass Core Web Vitals on mobile?" For more, see [How your AI analyses marketing data](/connectors/marketing-data). ## A typical week **Monday: the overview.** Ask for an account overview against the previous week or month. It covers spend, conversions, CPA, ROAS, organic clicks, sessions and revenue for every connected platform in one answer. Ask what moved most, and why. **Tuesday: paid search housekeeping.** Run a wasted-spend check and a search-term-winners check on Google Ads and Microsoft Advertising. Your AI lists negative-keyword candidates and converting search terms you haven't added as keywords. You make the changes yourself in Google Ads or Microsoft Advertising: Plugsight only reads. **Wednesday: organic.** Ask for SEO opportunities: queries just off page one, page-one results with low CTR, and pages losing clicks. Check the speed of any page that dropped. **Thursday: analytics.** Look at channels and landing pages in GA4, or build a funnel for a journey you're working on. **Friday: the summary.** Ask your AI to write a short summary of the week for your manager, with the three biggest changes and what you did about them. If you connected a mailbox, ask it to save the summary as a draft. ## Safety tips - **Ads can't be changed through Plugsight.** Campaigns, bids, budgets and keywords are never touched. Your AI recommends; you decide and make the change in the ad platform. - **Drafts first.** If you connected a mailbox, leave its switch on **Drafts only** until you're comfortable. Your AI can still write every email; you send it yourself. See [Sending, drafts and the daily email limit](/connectors/email-safety). - **Name the account** when one login reaches several: "for the UK GA4 property", "on the brand Google Ads account". - **Watch for currency notes.** If your ad accounts use different currencies, ask your AI to split by account so money isn't added across currencies. - **Check Activity** now and then to see what your AI read and did. See [Activity log](/permissions/activity). ## Related articles - [PPC specialists](/use-cases/ppc-specialists) - [SEO specialists](/use-cases/seo-specialists) - [Analysts and reporting](/use-cases/analysts-and-reporting) - [How your AI analyses marketing data](/connectors/marketing-data) --- # Agencies managing many clients URL: https://docs.plugsight.app/use-cases/agencies Set up Plugsight for an agency - manager accounts, one MCP server per client, cross-client checks, and how to keep each client's data apart. ## Who it's for You run or work at an agency and look after marketing, search or support for several clients. Each client has their own Google Ads, Analytics and Search Console, sometimes a store, a Mailchimp account or a Zendesk. You need to see every client at once for health checks, and one client at a time for their reports. The **Agency** plan is made for this: 50 connections and unlimited MCP servers. **Pro** (10 connections, 5 MCP servers) works for a handful of clients. See [Plans](/get-started/plans). ## Connectors to set up | Connector | How agencies use it | | --- | --- | | [Google Ads](/connectors/google-ads) | Sign in with the Google account that has your manager (MCC) account. Plugsight finds every client underneath, as one connection. | | [Microsoft Advertising](/connectors/microsoft-advertising) | Sign in with the Microsoft login that reaches your clients' ad accounts. | | [Google Search Console](/connectors/google-search-console) | Every client site your Google login can open. | | [Google Analytics 4](/connectors/google-analytics-4) | Every client property your Google login can open. | | [PageSpeed Insights](/connectors/pagespeed-insights) | Speed checks for any client page. No connection needed. | | [Zendesk](/connectors/zendesk), [WooCommerce](/connectors/woocommerce), [Magento](/connectors/magento), [Shopify](/connectors/shopify), [Mailchimp](/connectors/mailchimp) | Per-client accounts, when you run support, stores or newsletters for them. Each is its own connection. | | Your agency mailbox, for example [Gmail](/connectors/gmail) or [Outlook](/connectors/outlook) | Client emails, briefs and report drafts. | Name each connection clearly on **Connections**, for example "Acme Zendesk" or "Bright Dental Mailchimp". Your AI and **Activity** use those names. ## How connections and client separation work This is the most important part of an agency setup, so read it before you create servers. - **An MCP server picks connections, not individual ad accounts.** If one Google sign-in reaches all your clients' Google Ads accounts, that is one connection. A server that includes it can reach every client that login can see. - **Hiding is per connection, on every server.** Hiding a site or ad account under **Show sites & accounts** hides it from your AI everywhere, not just on one server. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). - **Client-specific connections separate cleanly.** A client's own Zendesk, store or Mailchimp is a separate connection, so you can put it in that client's server only. So in practice: - Use your manager logins for **cross-client work** on an all-clients server. - Use **per-client servers** for each client's own connections, and, if you need a strict wall for ads and analytics too, connect that client with a Google or Microsoft login that only reaches that client. ## Recommended MCP server setup ### 1. An all-clients server for your team - **Name:** "Agency (all clients)" - **Account access:** **All accounts** - **Allow changes:** ticked if your team sends client emails through it, otherwise unticked Use it for portfolio checks across every client at once. ### 2. One server per client - **Name:** the client's name, for example "Acme (client)" - **Account access:** **Selected accounts**, ticking only that client's connections - **Allow changes:** your choice. Untick it if the server is only for reporting. In a chat that uses this server, your AI can only reach that client's connections, so another client's tickets or orders can't come up by mistake. Remember to tick new connections in the right server: **Selected accounts** don't grow by themselves. See [Edit an MCP server](/mcp-servers/edit). ### 3. A read-only server if a client uses it If a client will use a link themselves, make it read-only: **Selected accounts** with only their connections, and **Allow changes** unticked. The badge then shows **Read & draft only**. > [!IMPORTANT] > Each AI app has to sign in to **your** Plugsight account and click **Allow access** to use one of your servers, and anyone with a server's API key can use it. Share access only with people you trust, and revoke a key when it's no longer needed. See [API keys](/mcp-servers/api-keys) and [Use several MCP servers](/mcp-servers/multiple-servers). ## Example questions On the all-clients server: - "Which clients' CPA rose more than 20% this month, and why?" - "Across all client accounts, which ones spent more than 20% over last month?" - "List wasted spend across all clients and the top negative keywords for each." (Ask your AI to split by account, so each client gets its own list.) - "Give me an account overview of every connected platform this month against last month, per client." - "Which client sites lost the most organic clicks compared with last month?" On a client's server: - "Prepare a one-page performance summary for Acme vs last quarter." - "Which of Acme's campaigns are losing impression share to budget?" - "Which of Acme's keywords have a quality score of 5 or less, and what's dragging them down?" - "Where is Acme paying for clicks on queries they already rank top 3 for?" - "Do Acme's top landing pages pass Core Web Vitals on mobile?" - "What were Acme's most common Zendesk ticket reasons this month?" ## A typical week **Monday: portfolio check.** On the all-clients server, ask which accounts moved most against last week: spend, CPA and conversions per account. Note the clients that need attention. **Tuesday to Thursday: client work.** Open a chat on each client's server. Run the wasted-spend, scale-opportunities or SEO-opportunities deep dives, and drill into anything they surface. Make changes in Google Ads or Microsoft Advertising yourself: Plugsight only reads ads. **Friday: reports.** On each client's server, ask for a summary against last week or last month, in plain language for the client. If your agency mailbox is connected, ask your AI to save it as a draft to the client's contact, so you can check and send it. ## Safety tips - **Name the client in every question** on the all-clients server, or open the client's own server. The cross-client server can see everyone. - **Split by account.** When you ask about several clients, rows with the same values are added together. Ask your AI to "show it per account" to keep each client's numbers apart, and to keep currencies apart. - **Keep client-facing links read-only.** Untick **Allow changes** on any server someone outside your team uses. - **Client emails go through approval.** Every email your AI sends shows you the recipients, subject and body first. Keep the [daily email limit](/permissions/daily-email-limit) at a level that fits your team. - **Use Pause before handovers.** If someone else will use your chat, or something in **Activity** looks wrong, click **Pause everything** on **Permissions**. Reading keeps working. See [Pause changes](/permissions/pause). - **Remove a client's access when they leave.** Delete their server and remove their connections. See [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete) and [Remove access](/security/remove-access). ## Related articles - [Use several MCP servers](/mcp-servers/multiple-servers) - [MCP server limits on each plan](/mcp-servers/plan-limits) - [PPC specialists](/use-cases/ppc-specialists) - [Analysts and reporting](/use-cases/analysts-and-reporting) --- # PPC specialists URL: https://docs.plugsight.app/use-cases/ppc-specialists Use Plugsight with Google Ads and Microsoft Advertising to find wasted spend, new keywords, budget-limited winners and quality score problems. ## Who it's for You manage paid search and shopping campaigns in Google Ads, Microsoft Advertising or both. You know what to look for; what takes time is pulling the search-term report, the keyword report and the impression-share columns, then lining them up. Your AI does the pulling. It reads search terms, keywords, quality score, impression share, conversions and settings live, across one account or many, and answers in a table you can act on. It doesn't change anything: you make the edits in the ad platform. You need the **Pro** or **Agency** plan. ## Connectors to set up | Connector | What it adds | | --- | --- | | [Google Ads](/connectors/google-ads) | Campaigns, ad groups, keywords with match type and quality score components, search terms, ads, products, locations, devices, hours, conversions, impression share, and any read-only GAQL query | | [Microsoft Advertising](/connectors/microsoft-advertising) | The same kinds of data for Bing Ads, plus age, gender, audiences, Shopping products and Performance Max asset groups, and campaign settings (status, type, budget, bidding strategy) | | [Google Analytics 4](/connectors/google-analytics-4) | What paid visitors did on the site: landing page conversion rates, funnels, revenue by channel | | [Google Search Console](/connectors/google-search-console) | Organic rankings, for paid-vs-organic checks | | [PageSpeed Insights](/connectors/pagespeed-insights) | Landing page speed. No connection needed | | [Google Merchant Center](/connectors/google-merchant-center) | Shopping feed health and disapproved products. Coming soon | If you manage client accounts, sign in to Google Ads with the account that reaches your manager (MCC) account: Plugsight finds every client underneath. ## Recommended MCP server setup - **In-house:** one server with **All accounts**. Ads are read-only, so **Allow changes** only matters if you also connected a mailbox. - **Managing clients:** an all-accounts server for cross-account checks, plus one server per client for client-specific work. See [Agencies managing many clients](/use-cases/agencies) for how connections and client separation work. ## Example questions - "Which search terms cost us money last month without converting? Suggest negative keywords." - "Which converting search terms aren't keywords yet?" - "Which keywords convert below our average CPA but lose impression share to budget?" - "Which keywords have a quality score of 5 or less, and is expected CTR, ad relevance or the landing page the problem?" - "Compare CPA and ROAS by campaign this month vs last month." - "Which campaigns are losing impression share to budget, and which to rank?" - "Which hours of the day and age groups convert best on Bing?" - "Show cost and conversions by campaign per week for the last quarter, Google and Microsoft side by side." - "Which landing pages have the highest conversion rate from paid search in GA4?" - "Where are we paying for clicks on queries we already rank top 3 for organically?" - "What bidding strategy and daily budget does each Microsoft Advertising campaign use?" - "Run a GAQL query for ad group names and their final URLs in the Brand campaign." ## Deep dives worth knowing Your AI can run these ready-made analyses in one step. Each returns findings plus tables, for the last 30 days against the previous period unless you say otherwise. | Ask for | What you get | | --- | --- | | "a wasted spend report" | Non-converting search terms and keywords, the share of budget wasted, and negative-keyword candidates | | "search term winners" | Converting search terms that aren't keywords yet | | "scale opportunities" | Campaigns and keywords at or below average CPA that lose impression share to budget or rank | | "a quality score audit" | Spend by quality score, and which component drags low scores down | | "paid vs organic" | Paid clicks on queries you rank top 3 for, paid winners with weak SEO, organic queries worth testing in paid | Deep dives use Google Ads unless you ask for Microsoft Advertising. See [How your AI analyses marketing data](/connectors/marketing-data). ## A typical week **Monday: performance check.** Ask for this week against last week by campaign: cost, conversions, CPA and ROAS. Ask what drove the biggest changes. **Tuesday: search terms.** Run the wasted-spend and search-term-winners deep dives. Add the negatives and new keywords you agree with in the ad platform. **Wednesday: budgets and bids.** Run scale opportunities. Look at campaigns losing impression share to budget with a CPA below average. **Thursday: quality.** Run the quality score audit and check the speed of the landing pages behind low landing-page scores. **Friday: report.** Ask for a short summary of the week's results and the changes you made, for your manager or client. ## Safety tips - **Plugsight never changes your ad accounts.** It doesn't create, edit or pause campaigns, bids, budgets or keywords, even though Google Ads only offers a permission that includes edit rights. See [Permissions Plugsight asks Google and Microsoft for](/security/provider-permissions). - **Check the data notes.** Google hides low-volume search terms for privacy, so their cost is in campaign totals but not in search-term rows. Your AI passes on notes like this when they affect an answer. - **Keep currencies apart.** When several accounts use different currencies, ask your AI to split by account. - **Manager accounts don't report their own metrics.** Ask about the client accounts under them. - **Hide accounts you don't manage any more** under **Show sites & accounts**, so they don't show up in "all accounts" totals. ## Related articles - [Google Ads](/connectors/google-ads) - [Microsoft Advertising](/connectors/microsoft-advertising) - [In-house marketers](/use-cases/in-house-marketers) - [Agencies managing many clients](/use-cases/agencies) --- # SEO specialists URL: https://docs.plugsight.app/use-cases/seo-specialists Use Search Console, PageSpeed Insights and GA4 through your AI to find ranking opportunities, indexing problems and slow pages. ## Who it's for You look after organic search for your own site or for clients. Your week is Search Console performance reports, URL inspection, sitemaps, Core Web Vitals and checking what organic visitors do once they arrive. With Plugsight, your AI reads Search Console and GA4 live, inspects URLs, checks sitemaps and runs PageSpeed Insights on any public page. Ask "which pages lost clicks since last month, and are they still indexed?" and it pulls the numbers, inspects the pages and explains. Search Console and GA4 need the **Pro** or **Agency** plan. PageSpeed Insights works on every plan. ## Connectors to set up | Connector | What it adds | | --- | --- | | [Google Search Console](/connectors/google-search-console) | Clicks, impressions, CTR and average position by query, page, country, device, date and search appearance; web, image, video, news and Discover results; URL inspection; sitemaps | | [PageSpeed Insights](/connectors/pagespeed-insights) | Performance, SEO, accessibility and best-practice scores, real-user Core Web Vitals (LCP, INP, CLS) and the fixes that save the most time. No connection needed | | [Google Analytics 4](/connectors/google-analytics-4) | Organic sessions, engagement, key events and revenue by landing page | | [Google Ads](/connectors/google-ads) | Optional: for paid-vs-organic checks | | [Google Tag Manager](/connectors/google-tag-manager) | Optional: tag audits. Coming soon | If you work on several sites, one Google sign-in reaches every Search Console property that login can open. Hide test or staging properties under **Show sites & accounts**. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## Recommended MCP server setup - **One site:** one server, **All accounts**. Search Console, GA4 and PageSpeed are read-only, so **Allow changes** doesn't affect them. - **Several clients:** one server per client where their connections are separate. See [Agencies managing many clients](/use-cases/agencies). ## Example questions - "Which queries rank in positions 4–20 with the most impressions?" - "Which page-one results get much lower CTR than expected for their position?" - "Which pages lost the most clicks compared with last month?" - "Compare organic clicks and impressions by page with the same month last year." - "Is https://example.com/pricing indexed, and if not, why? What canonical did Google choose?" - "Do our sitemaps have errors, and how many submitted URLs are indexed?" - "Which queries bring us clicks from Discover or image search?" - "How do our clicks and CTR on mobile compare with desktop by country?" - "Check the speed of our five most-clicked pages on mobile. Which ones fail Core Web Vitals?" - "What are the three changes that would make our home page load fastest?" - "Which organic landing pages in GA4 have the highest key event rate?" - "Where are we paying for Google Ads clicks on queries we already rank top 3 for?" ## A typical week **Monday: what moved.** Ask for a period comparison of clicks and impressions by page, this week against last week. Ask your AI to list the biggest drops and gains. **Tuesday: opportunities.** Ask for the SEO opportunities deep dive: striking-distance queries, page-one results with low CTR and pages losing clicks. Pick the pages to work on. **Wednesday: technical checks.** Inspect the URLs that dropped, and check sitemaps for errors. Run PageSpeed Insights on the key templates. Each check takes 10 to 40 seconds. **Thursday: behaviour.** Look at the organic landing pages in GA4: engagement, key events and revenue. **Friday: report.** Ask for a short summary of the week, with what changed and what you're working on next. > [!NOTE] > Search Console data becomes final about 2–3 days after the date, so the most recent days may still grow. Rare queries are hidden by Google; your AI tells you what share of clicks that is when it matters. ## Safety tips - **Nothing changes in Search Console or GA4.** Plugsight only reads. URL inspection shows what Google sees; it doesn't request indexing. - **Name the property** when a login reaches several, for example "for the domain property of example.com". A domain property covers every subdomain and both http and https. - **PageSpeed checks public pages only.** Pages behind a login can't be checked. - **Use Activity** to see what was read. See [Activity log](/permissions/activity). ## Related articles - [Google Search Console](/connectors/google-search-console) - [PageSpeed Insights](/connectors/pagespeed-insights) - [Google Analytics 4](/connectors/google-analytics-4) - [Content and YouTube creators](/use-cases/content-and-youtube-creators) --- # Support teams URL: https://docs.plugsight.app/use-cases/support-teams Connect Zendesk and your support inboxes so your AI can find ticket history, spot trends and draft replies that you approve. ## Who it's for You answer customers in Zendesk, a shared support inbox, or both. You need the full history before you reply, you want to know what customers are raising this week, and you write many similar replies. With Plugsight, your AI searches and reads tickets and emails, counts tickets for any period, and drafts replies and internal notes. Nothing goes to a customer without your approval in the chat. Reading Zendesk and email works on every plan. Replies, notes, ticket updates, macros and sending email need **Pro** or **Agency**. ## Connectors to set up | Connector | What it adds | | --- | --- | | [Zendesk](/connectors/zendesk) | Search tickets with Zendesk search syntax, read full conversations including internal notes, find users, ticket counts, macros; with your approval: replies, internal notes, ticket updates, new tickets and macros | | Your support mailbox, for example [Gmail](/connectors/gmail), [Outlook](/connectors/outlook) or [another provider](/connectors/connect-any-email) | Search and read customer emails and attachments, draft replies; with your approval: send, archive, label and mark | | [Mailchimp](/connectors/mailchimp) | Optional: check whether a customer is subscribed, and when they joined | | [WooCommerce](/connectors/woocommerce) or [Magento](/connectors/magento) | Optional: look up a customer's orders while you answer them | Connect Zendesk with your own agent or admin login. Zendesk then applies your agent's permissions to everything your AI does, and records replies and changes under your name. ## Recommended MCP server setup - **Name:** "Support" - **Account access:** **Selected accounts**: your Zendesk, the support mailbox, and the store if you connected one. Leave personal mailboxes out. - **Allow changes:** ticked, so your AI can reply and update tickets after your approval. Then, on **Connections**, decide each account's switch: | Account | Start with | Turn on when | | --- | --- | --- | | Zendesk | **Read-only** | You're happy with the notes and drafts your AI writes. The switch then shows **Can reply & update**. | | Support mailbox | **Drafts only** | You want your AI to send approved replies itself. The switch then shows **Can send**. | If a team lead only needs to look at trends, give them a server with **Allow changes** unticked. See [Use several MCP servers](/mcp-servers/multiple-servers). ## Example questions - "What are the top five reasons for tickets this week?" - "Which urgent tickets have had no reply for more than a day?" - "Summarise everything this customer has raised in the last 90 days, in Zendesk and by email." - "Find tickets tagged 'refund' that are still open." - "How many tickets did we solve last week compared with the week before?" - "How many tickets are new, open, pending and on hold in the Billing group right now?" - "Draft an internal note on ticket 4821 summarising the issue and what we've tried." - "Draft a reply to ticket 4821 using our refund policy email." - "Which macros do we have for shipping delays? Preview what 'Delay apology' would do to ticket 4821." - "Set ticket 4821 to pending, assign it to Sam and add the tag 'carrier-issue'." - "Summarise this week's customer enquiries in the support inbox and draft replies to the three oldest." - "What did the PDF attached to the customer's last email say about the damage?" ## A typical week **Monday: the queue.** Ask for ticket counts (new, open, pending, on hold, unsolved) and the urgent tickets with no reply. Ask for the top reasons for tickets created over the weekend. **Every day: first replies.** For each ticket you pick up, ask your AI for the customer's history and a draft reply or note. Read it, edit it in the chat, then approve it. With macros, your AI previews exactly what the macro changes before you say yes. **Wednesday: follow-ups.** Ask for pending tickets that haven't been updated in a few days, and for support emails you haven't answered. **Friday: trends.** Compare tickets created and solved this week against last week, and ask what customers raised most. Share the summary with your team or product manager. ## Safety tips - **Approve every customer-facing message.** Your AI shows you the reply, the ticket and any status change before it acts. Plugsight refuses changes the AI hasn't marked as approved. See [Approvals in the chat](/permissions/approvals). - **Prefer internal notes while you build trust.** Notes are seen only by agents. A new ticket's first message is an internal note by default, so the customer isn't emailed unless you ask. - **Keep the email limit sensible.** Your AI can send at most the [daily email limit](/permissions/daily-email-limit) from each mailbox in 24 hours (20 by default). - **Pause in a hurry.** If a reply goes out that shouldn't have, or someone else is using your chat, click **Pause** on the Helpdesk or Email row on **Permissions**, or **Pause everything**. Your AI keeps reading. See [Pause changes](/permissions/pause). - **Review Activity.** Every reply, note and update is listed, with blocked attempts and their reasons. See [Activity log](/permissions/activity). ## Related articles - [Zendesk](/connectors/zendesk) - [What your AI can do with email](/connectors/email-tools) - [How changes are allowed](/permissions/how-changes-are-allowed) - [Executive assistants and busy inboxes](/use-cases/executive-assistants) --- # E-commerce store owners URL: https://docs.plugsight.app/use-cases/ecommerce-store-owners Connect WooCommerce or Magento, your ads and analytics so your AI can report sales, find orders, watch stock and check product feeds. ## Who it's for You run an online store on WooCommerce or Magento / Adobe Commerce. You want to know how the shop did, which products sell, what's running low, and whether your ads pay for themselves, without opening five dashboards. You also answer customers who ask "where's my order?". With Plugsight, your AI reads your store's orders, products, customers and sales live, and can put them next to your Google Ads, GA4 and Mailchimp numbers in one answer. It never changes anything in your store. WooCommerce, Magento, Mailchimp and email work on every plan. Google Ads, GA4 and Search Console need **Pro** or **Agency**, and so will Merchant Center once Google approves it. ## Connectors to set up | Connector | What it adds | | --- | --- | | [WooCommerce](/connectors/woocommerce) | Sales for any period (gross and net, orders, items, average order, tax, shipping, refunds, discounts), best sellers, orders, products with stock and total sales, customers with order count and total spent | | [Magento / Adobe Commerce](/connectors/magento) | Sales for any period with a per-day breakdown, best sellers, orders, products by name or SKU, low-stock products, customers | | [Shopify](/connectors/shopify) | Sales for any period with a per-day breakdown, best sellers, orders with tracking, low-stock variants, stock by location, customers; several stores at once | | [Google Analytics 4](/connectors/google-analytics-4) | Channels, landing pages, ecommerce events and checkout funnels | | [Google Ads](/connectors/google-ads) and [Microsoft Advertising](/connectors/microsoft-advertising) | Ad spend, conversions and ROAS, including Shopping products | | [Google Merchant Center](/connectors/google-merchant-center) | Feed health, disapproved products and Shopping performance. Coming soon | | [Mailchimp](/connectors/mailchimp) | Newsletter results, with orders and revenue when your store is connected to Mailchimp | | Your store's mailbox, for example [Gmail](/connectors/gmail) or [Outlook](/connectors/outlook) | Customer emails, supplier invoices, drafts | | [Zendesk](/connectors/zendesk) | If you answer customers in Zendesk | ## Recommended MCP server setup One server for the business is usually right. - **Name:** "Shop" - **Account access:** **All accounts** - **Allow changes:** ticked if you want your AI to send approved customer emails; the store connectors are read-only either way. On the Free plan you have 2 connections, for example your store and your mailbox. Adding ads and analytics needs Pro. See [Plans](/get-started/plans). ## Example questions - "How did the shop do last month compared with the month before?" - "Which products sold best this week, and are any of them running low on stock?" - "Which products are out of stock or on backorder?" (WooCommerce) - "List products with 5 or fewer in stock." (Magento) - "Find order 1042 and tell me what was bought and where it's shipping." - "Show every order from ann@example.com this year." - "How many orders has ann@example.com placed, and how much has she spent in total?" (WooCommerce) - "Compare Google Ads spend last month with store revenue for the same days." - "Which products were added to cart most but bought least?" - "Build a funnel from product view to purchase and show where mobile users drop off." - "How did our last newsletter do, and how much revenue did it bring?" - "Draft a reply to the customer asking where order 1042 is, using the shipping details from the order." ## A typical week **Monday: last week's sales.** Ask for the sales report for last week against the week before: revenue, orders, average order, refunds and best sellers. **Tuesday: stock.** Ask which best sellers are running low, and which products are out of stock or on backorder. **Wednesday: marketing.** Compare ad spend with store revenue for the same days, and look at GA4 channels and the checkout funnel. When Merchant Center is available, check the feed for disapproved products. **Every day: customer questions.** Look up orders by number or email while you answer customers, and ask your AI to draft the reply. **Friday: the month so far.** Ask for month-to-date sales against the same days last month. ## Safety tips - **Your store is read-only.** Plugsight never changes orders, products, prices, customers or settings. WooCommerce connects with read-only access; for Magento, give the integration read-only resources. - **Revoke access in the store** if you ever need to: delete the REST API key in WooCommerce settings, or the integration in your Magento admin. - **Guest checkouts** appear in orders, not in the customer list. Ask by order or email for those. - **Magento dates use UTC**, and a Magento sales report counts paid orders only. On a very busy store it can stop early and says how far it got: ask for a shorter period. - **Customer emails need your approval.** Keep your mailbox on **Drafts only** until you're ready to let your AI send approved replies. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Related articles - [WooCommerce](/connectors/woocommerce) - [Magento / Adobe Commerce](/connectors/magento) - [Email marketers](/use-cases/email-marketers) - [Founders and small business owners](/use-cases/founders-and-small-businesses) --- # Founders and small business owners URL: https://docs.plugsight.app/use-cases/founders-and-small-businesses Connect your email, calendar, contacts and the tools you run the business on, so your AI can catch you up and handle the admin with you. ## Who it's for You run a small business, often alone or with a small team. Your inbox has customers, suppliers, invoices and your accountant in it. Your calendar is full. You may also have a store, a newsletter, ads or a helpdesk, and no time to look at each one. With Plugsight, one AI chat reaches all of it. Ask "what needs my attention today?" and your AI reads your inboxes and calendar. Ask "how did we do last month?" and it reads your store, ads and newsletter. It drafts emails, finds attachments and, when you allow it, sends and books with your approval. ## Connectors to set up Start with the two that save the most time, then add more as you need them. | Connector | What it adds | Plan | | --- | --- | --- | | Your main mailbox: [Gmail](/connectors/gmail), [Outlook](/connectors/outlook), [iCloud Mail](/connectors/icloud-mail) or [any other provider](/connectors/connect-any-email) | Search, read, attachments as text, drafts; with approval: send, archive, label | All plans | | Your calendar: [Outlook Calendar](/connectors/outlook-calendar), [iCloud Calendar](/connectors/icloud-calendar) or [Google Calendar](/connectors/google-calendar) | Events and free time; Outlook and iCloud can also book, move and cancel with your approval. Google Calendar is read-only for now | All plans | | Your contacts: [Google](/connectors/google-contacts), [Outlook](/connectors/outlook-contacts) or [iCloud Contacts](/connectors/icloud-contacts) | Look people up by name, email, phone or company | All plans | | Your store: [WooCommerce](/connectors/woocommerce) or [Magento](/connectors/magento) | Sales, orders, products, customers | All plans | | [Mailchimp](/connectors/mailchimp) | Newsletter results and subscribers | All plans | | [Zendesk](/connectors/zendesk) | If you answer customers there | All plans | | [Google Ads](/connectors/google-ads), [GA4](/connectors/google-analytics-4), [Search Console](/connectors/google-search-console) | Ads, website traffic and search | Pro | The Free plan includes 2 connections and 1 MCP server, which is enough for a mailbox and a calendar. Pro gives you 10 connections, marketing connectors and sending. See [Plans](/get-started/plans). ## Recommended MCP server setup - **Name:** "Business" - **Account access:** **All accounts**, so anything you connect later is included automatically - **Allow changes:** ticked (on Pro or Agency) Then on **Connections**, turn on each account's switch only when you want your AI to act there: **Can send** for the mailbox, **Can book & change** for the calendar. Until then, your AI reads and drafts. If you hire an assistant or a freelancer, give them their own server with **Selected accounts** and, if they should only read, **Allow changes** unticked. See [Use several MCP servers](/mcp-servers/multiple-servers). ## Example questions - "Summarise my unread email from customers today, and tell me which ones need a reply." - "What does my week look like, and which meetings could be an email?" - "Find every invoice we received from suppliers this quarter and list the totals." - "What did the contract PDF attached to Sarah's email say about payment terms?" - "Which emails from last week am I still waiting on a reply to?" - "Find my accountant's email and draft them a note about this year's receipts." - "Find a free hour on Wednesday and book a call with sam@example.com." (Outlook or iCloud Calendar) - "How did the shop do last month compared with the month before?" - "Is our newsletter list growing? Show new subscribers and unsubscribes by month." - "Give me an overview of my ads, website and search traffic this month against last month." - "Archive every newsletter in my inbox and label the receipts 'Expenses'." ## A typical week **Monday morning: catch up.** Ask for a summary of unread email since Friday, grouped by customers, suppliers and everything else, and your calendar for the week. **Every morning: today.** "What's on today, and what do I need to prepare?" Ask your AI to draft replies to anything urgent; read and approve them in the chat. **Wednesday: numbers.** Ask how sales, ads and the newsletter are doing this month so far. **Friday: tidy up.** Ask your AI to archive newsletters and label receipts, list emails still waiting on a reply, and draft follow-ups. Before moving to trash, or changing more than 10 emails, it asks first. **Month end: admin.** Find invoices and receipts for your accountant, and ask for the month's sales summary. ## Safety tips - **Start on drafts.** Leave the mailbox on **Drafts only** for the first week. Your AI writes every email into your Drafts folder; you send it. Turn on **Can send** when you trust the drafts. - **Every send waits for you.** Your AI shows the recipients, subject and body, and sends only after your yes. See [Approvals in the chat](/permissions/approvals). - **The daily email limit** caps sends per mailbox at 20 in 24 hours by default. You can change it from 1 to 500 on **Permissions**. See [Daily email limit](/permissions/daily-email-limit). - **Store, ads, newsletter and contacts are read-only.** Plugsight never changes them. - **Use Pause** if you lend your laptop, demo your AI, or see something odd in **Activity**. **Pause everything** stops all sending and changes; reading keeps working. See [Pause changes](/permissions/pause). ## Related articles - [Questions to try first](/get-started/first-questions) - [E-commerce store owners](/use-cases/ecommerce-store-owners) - [Executive assistants and busy inboxes](/use-cases/executive-assistants) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # Sales and account managers URL: https://docs.plugsight.app/use-cases/sales-and-account-managers Connect your email, calendar and contacts so your AI can prepare you for meetings, find what was agreed, and draft and book follow-ups. ## Who it's for You sell, or you look after existing customers. Your relationships live in your inbox, your calendar and your address book: who you spoke to, what you promised, when you meet next. Before a call you dig through threads; after it you write follow-ups and find a time for the next one. With Plugsight, your AI reads your email, calendar and contacts live. It prepares you for a meeting from the full email history, finds what was agreed, drafts the follow-up, and, with Outlook or iCloud Calendar, books the next meeting after your approval. Everything here works on every plan. Sending email and booking events need **Pro** or **Agency**. ## Connectors to set up | Connector | What it adds | | --- | --- | | Your work mailbox: [Outlook](/connectors/outlook), [Gmail](/connectors/gmail) or [another provider](/connectors/connect-any-email) | Search every folder, full threads, attachments read as text (proposals, contracts, price lists), drafts; with approval: send, archive, label | | Your calendar: [Outlook Calendar](/connectors/outlook-calendar) or [iCloud Calendar](/connectors/icloud-calendar) | Events, free time, and with approval: book, move and cancel events and invite guests | | [Google Calendar](/connectors/google-calendar) | Events and free time. Read-only for now, so your AI can suggest times but not book them | | Your contacts: [Outlook](/connectors/outlook-contacts), [Google](/connectors/google-contacts) or [iCloud Contacts](/connectors/icloud-contacts) | Names, emails, phones, companies and notes. Google also finds people you've emailed who aren't saved | | [Zendesk](/connectors/zendesk) | Optional, for account managers: a customer's open tickets before a review | | [WooCommerce](/connectors/woocommerce) or [Magento](/connectors/magento) | Optional: a customer's orders | ## Recommended MCP server setup - **Name:** "Sales" - **Account access:** **Selected accounts**: your work mailbox, calendar and contacts. Leave personal accounts out. - **Allow changes:** ticked On **Connections**, start with the mailbox on **Drafts only** and the calendar **Read-only**. Turn on **Can send** and **Can book & change** once you've seen a few drafts and suggested bookings. If your Outlook Calendar or Outlook account shows **Read-only** with a lock, it was connected without the permission to send or book: click it and reconnect, ticking the extra permission. See [Read-only connectors](/permissions/read-only-connectors). ## Example questions - "I'm meeting Contoso tomorrow. Summarise every email with them in the last three months, and list open questions." - "What did I promise anyone by email this week?" - "Find the latest version of the proposal we sent to Contoso, and summarise the pricing section." - "Who do I know at Northwind, and what are their job titles?" - "What's the mobile number for Priya at Northwind?" - "When did I last meet Priya, and what was it about?" - "Which emails from last week am I still waiting on a reply to? Draft polite follow-ups." - "Find a 30-minute slot on Thursday afternoon and book a call with sam@example.com." (Outlook or iCloud Calendar) - "Move Friday's review with Acme to Monday at the same time and let everyone know." - "Draft a thank-you email to everyone who was in today's 2pm meeting, with the next steps we agreed." - "How many hours of customer meetings did I have this month?" - "Before my renewal call with Acme, list their open Zendesk tickets." (with Zendesk) ## A typical week **Monday: plan.** Ask for your meetings this week, who's in each one, and the last email exchange with each company. Ask which deals have gone quiet: threads where you sent the last email more than a week ago. **Before each meeting: brief.** "Summarise my history with this customer and anything they've asked that I haven't answered." **After each meeting: follow up.** Ask for a follow-up email with the next steps, and a time for the next meeting. Approve the email and the booking in the chat. **Friday: loose ends.** Ask what you promised this week, which emails are still waiting on a reply, and draft the follow-ups. ## Safety tips - **Approve every email and booking.** Your AI shows you the recipients, subject and body, or the event's time, title and guests, before it acts. See [Approvals in the chat](/permissions/approvals). - **Cancelling emails guests.** When your AI cancels an event, guests get a cancellation by default. For a repeating event, iCloud cancels the whole series, so check before you approve. - **Keep the daily email limit low for outreach.** The [daily email limit](/permissions/daily-email-limit) caps sends from each mailbox in 24 hours. Your email provider also has its own limits. - **Contacts are read-only.** Your AI can look people up but not add or edit contacts. - **Hide calendars you don't want read**, such as a personal calendar, under **Show calendars** on **Connections**. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## Related articles - [What your AI can do with email](/connectors/email-tools) - [What your AI can do with calendars](/connectors/calendar-tools) - [Executive assistants and busy inboxes](/use-cases/executive-assistants) - [Founders and small business owners](/use-cases/founders-and-small-businesses) --- # Email marketers URL: https://docs.plugsight.app/use-cases/email-marketers Connect Mailchimp, GA4 and your store so your AI can compare campaigns, track list growth, look up subscribers and tie emails to sales. ## Who it's for You plan and send newsletters and campaigns, usually in Mailchimp. You want to know which subject lines and content work, whether the list is growing, and whether emails bring sales. You also get questions like "is this customer still subscribed?". With Plugsight, your AI reads Mailchimp campaign reports, audiences and subscribers live, and can put them next to GA4 and store numbers. It compares campaigns with your audience average and your industry, and finds patterns across a quarter of sends. Mailchimp works on every plan. GA4 needs **Pro** or **Agency**. ## Connectors to set up | Connector | What it adds | | --- | --- | | [Mailchimp](/connectors/mailchimp) | Audiences with subscribers, unsubscribes and average engagement; campaigns with subject, audience, sends, open and click rates, orders and revenue; full campaign reports with bounces, unsubscribes, spam complaints, most-clicked links and comparison with your audience and industry; month-by-month audience growth; subscriber look-up | | [Google Analytics 4](/connectors/google-analytics-4) | What email visitors did on the site: sessions, key events and revenue by source, medium and campaign | | [WooCommerce](/connectors/woocommerce) or [Magento](/connectors/magento) | Store sales for the days after a send | | Your mailbox, for example [Gmail](/connectors/gmail) or [Outlook](/connectors/outlook) | Replies to your newsletter, and drafts of the next one | Mailchimp connects with an API key. Orders and revenue only appear in Mailchimp results when your online store is connected to Mailchimp. ## Recommended MCP server setup - **Name:** "Email marketing" - **Account access:** **Selected accounts**: Mailchimp, GA4 and your store - **Allow changes:** unticked is fine. Mailchimp, GA4 and stores are read-only, so a read-only server loses nothing. Tick it only if you also add a mailbox and want your AI to send approved emails. ## Example questions - "Which of last quarter's campaigns had the best click rate, and what did their subject lines have in common?" - "How does our latest newsletter compare with our audience average and the industry?" - "Is our list growing? Show new subscribers and unsubscribes by month for the last year." - "Which links got the most clicks in last week's campaign?" - "Which campaigns this year had the highest unsubscribe or spam complaint rates?" - "Compare open and click rates for each of our audiences." - "Which campaigns brought the most orders and revenue this quarter?" - "Is jane@example.com still subscribed, and when did she join? What tags does she have?" - "In GA4, how many sessions and key events came from email last month, by campaign?" - "Compare store sales in the three days after each of last month's newsletters with the three days before." - "Draft next week's newsletter intro based on the topics that got the most clicks this quarter." ## A typical week **Monday: last week's sends.** Ask for every campaign sent last week with opens, clicks, unsubscribes and revenue, and how each compares with your audience average. **Tuesday: what worked.** Ask for the most-clicked links in the best campaign, and what the best-performing subject lines this quarter had in common. **Wednesday: planning.** Ask your AI to suggest topics and subject lines for the next send, based on what got clicks. If you connected a mailbox, ask for a draft. **Friday: list health.** Check audience growth this month, and look up any subscriber questions that came in. **Month end: impact.** Compare email sessions and revenue in GA4 and your store with the month before. ## Safety tips - **Mailchimp is read-only.** Plugsight never sends, schedules, edits or deletes campaigns, audiences or contacts. You send campaigns in Mailchimp. - **Your newsletter isn't sent through Plugsight.** If your AI drafts a newsletter in your mailbox, it's a draft for you to copy into Mailchimp. Don't use a connected mailbox for bulk sends: the [daily email limit](/permissions/daily-email-limit) caps it at 500 per account in 24 hours at most, and your email provider has its own limits. - **Treat subscriber data with care.** Subscriber look-ups show email addresses, status and tags. Keep the Mailchimp connection out of servers you share with people who shouldn't see them. - **Revoke the API key** in Mailchimp if you stop using Plugsight, and remove the connection on **Connections**. See [Remove access](/security/remove-access). ## Related articles - [Mailchimp](/connectors/mailchimp) - [E-commerce store owners](/use-cases/ecommerce-store-owners) - [Analysts and reporting](/use-cases/analysts-and-reporting) --- # Content and YouTube creators URL: https://docs.plugsight.app/use-cases/content-and-youtube-creators Use YouTube Analytics, Search Console, GA4 and your inbox through your AI to see what content works, where viewers come from and who's emailing you. ## Who it's for You make videos, write a blog, run a podcast site or a newsletter. You want to know which pieces get watched and read, where your audience comes from, and what to make next. Your inbox is full of sponsor offers and collaboration requests. With Plugsight, your AI reads your channel and site analytics live and answers in plain language: top videos by watch time, traffic sources, subscribers gained and lost, search queries that bring readers. It can also sort your inbox and draft replies to sponsors. > [!NOTE] > **YouTube is coming soon.** Google is reviewing its permissions for Plugsight. Until Google approves it, YouTube isn't listed in the **Connector catalog**. Search Console, GA4, PageSpeed, Mailchimp and email work today. See [YouTube](/connectors/youtube). Search Console and GA4 need **Pro** or **Agency**, and so will YouTube once Google approves it. Email and Mailchimp work on every plan. ## Connectors to set up | Connector | What it adds | | --- | --- | | [YouTube](/connectors/youtube) | Channels with subscribers, total views and video count; reports on views, watch time, average view duration, subscribers gained and lost, likes, comments and shares, split by day, month, video, country, device, traffic source, playback location, subscribed status or age and gender; your uploads with views, likes and comments. Coming soon | | [Google Search Console](/connectors/google-search-console) | The searches that bring readers to your site, including video and Discover results | | [Google Analytics 4](/connectors/google-analytics-4) | Visitors, engagement, key events and where they come from | | [PageSpeed Insights](/connectors/pagespeed-insights) | Speed and SEO scores for your pages. No connection needed | | [Mailchimp](/connectors/mailchimp) | Newsletter results and subscriber growth | | Your mailbox, for example [Gmail](/connectors/gmail) or [Outlook](/connectors/outlook) | Sponsor and collaboration emails, drafts of replies | ## Recommended MCP server setup - **Name:** "Creator" - **Account access:** **All accounts** - **Allow changes:** ticked if you want your AI to send approved replies from your mailbox. Analytics connectors are read-only either way. If you work with an editor or manager who should see the numbers but not your inbox, give them a server with **Selected accounts** (analytics only) and **Allow changes** unticked. See [Use several MCP servers](/mcp-servers/multiple-servers). ## Example questions With YouTube (coming soon): - "How did my channel do last month compared with the month before?" - "Which ten videos got the most watch time in the last 90 days?" - "Where do my viewers come from: search, suggested videos or outside YouTube?" - "How many subscribers did I gain and lose each month this year?" - "What share of my viewers are 25–34, and which countries watch most?" - "List my latest uploads and how many views, likes and comments each has." Working today: - "Which blog posts got the most organic clicks this month, and which lost clicks since last month?" - "Which search queries rank in positions 4–20 for my site? Which posts could I update?" - "Check the speed and SEO score of my latest article on mobile." - "Which pages do newsletter readers visit, and how long do they stay?" - "Is my newsletter list growing? Show new subscribers and unsubscribes by month." - "List sponsor emails from the last two weeks I haven't replied to, and draft polite replies asking for their budget." ## A typical week **Monday: last week.** Ask how last week's uploads and posts did against the week before: views, watch time, organic clicks, new subscribers. **Tuesday: ideas.** Ask which topics brought the most watch time and search clicks this quarter, and which search queries you nearly rank for. Use the answer to plan the next pieces. **Thursday: inbox.** Ask for sponsor and collaboration emails, sorted by how promising they look, and draft replies. Approve the ones you want to send. **Month end: the big picture.** Subscribers gained and lost by month, top videos and posts, and where your audience comes from. ## Safety tips - **Your channel and site can't be changed.** YouTube, Search Console and GA4 are read-only: Plugsight never uploads, edits or deletes videos, or changes settings. - **Pick the channel.** If your login reaches several channels, say which one, or hide the others under **Show sites & accounts**. - **Sponsor replies wait for you.** Your AI shows each email before it sends, and only sends with the mailbox's switch on **Can send**. Start on **Drafts only**. See [Sending, drafts and the daily email limit](/connectors/email-safety). - **Some YouTube splits only show some numbers.** Traffic source, device and playback location show views and watch time; the age and gender split shows the share of viewers. ## Related articles - [YouTube](/connectors/youtube) - [SEO specialists](/use-cases/seo-specialists) - [Email marketers](/use-cases/email-marketers) --- # Analysts and reporting URL: https://docs.plugsight.app/use-cases/analysts-and-reporting Use Plugsight for marketing and business reporting - cross-account tables, period comparisons, funnels, custom GA4 fields and the developer API. ## Who it's for You build reports: weekly performance updates, monthly reviews, client decks, or answers to "why did this number drop?". You know the data well, and you spend too long exporting it, joining it and checking the joins. With Plugsight, your AI pulls exactly the dimensions and metrics you ask for, from one account or all of them, and returns a table with totals. Rates such as CTR, CPA and ROAS are recalculated after rows are combined, so totals across accounts stay correct. For dashboards and scheduled jobs in your own systems, the [developer API](/developers) runs the same tools over HTTPS. Marketing and analytics connectors and the developer API need **Pro** or **Agency**. ## Connectors to set up | Connector | What it adds | | --- | --- | | [Google Analytics 4](/connectors/google-analytics-4) | Any GA4 dimension or metric, including your custom definitions; key events; funnels of 2–10 steps; realtime | | [Google Ads](/connectors/google-ads) | Every standard report, plus any read-only Google Ads Query Language (GAQL) query | | [Microsoft Advertising](/connectors/microsoft-advertising) | Performance reports and campaign settings | | [Google Search Console](/connectors/google-search-console) | Organic performance by query, page, country, device, date and search appearance | | [WooCommerce](/connectors/woocommerce) or [Magento](/connectors/magento) | Sales reports with daily breakdowns and best sellers | | [Mailchimp](/connectors/mailchimp) | Campaign results and audience growth | | [Zendesk](/connectors/zendesk) | Ticket counts for any period, narrowed by tag, group or assignee | | [Google Sheets](/connectors/google-sheets), [Google Forms](/connectors/google-forms) | Read spreadsheets by link, and form responses with per-question totals. Coming soon | ## Recommended MCP server setup - **For your own analysis:** one server, **All accounts**, **Allow changes** unticked. Everything you report on is read-only, and a read-only server makes sure nothing is sent or changed. - **For a dashboard or script:** a separate server per system, with **Selected accounts** limited to what that system needs, and its own API key. See [Developer API](/developers) and [API keys](/mcp-servers/api-keys). - **For client reporting:** one server per client. See [Agencies managing many clients](/use-cases/agencies). ## Example questions - "Compare spend, conversions and CPA by platform for the last 90 days." - "Show sessions and key events by week for the last quarter, by default channel group." - "Give me cost, conversions, CPA and ROAS by campaign for each Google Ads account, split by account." - "Compare organic clicks by page this month with the same month last year. List the biggest gains and drops." - "List every dimension and metric our GA4 property has, including custom ones." - "Build a closed funnel: view_item, add_to_cart, begin_checkout, purchase, broken down by device category." - "What counts as a key event in this GA4 property, and what's the key event rate for each one last month?" - "Run a GAQL query for campaign name, advertising channel type and budget for all enabled campaigns." - "Show daily store revenue next to daily Google Ads cost for last month, and the correlation." - "How many Zendesk tickets were created and solved in each of the last six weeks?" - "Which numbers in this answer were affected by sampling, thresholds or hidden rows?" ## A typical week **Monday: the weekly report.** Ask for the account overview deep dive against the previous week. Then drill into each platform with exact fields and filters. Ask your AI to write the commentary under each table. **Mid-week: questions from colleagues.** When someone asks "why did conversions drop on Tuesday?", ask for the metric by day, then split by channel, device or campaign until the change shows up. **Thursday: checks.** Compare the same metric from two sources (for example Google Ads conversions and GA4 key events from paid search) and ask your AI to explain the gap. **Month end: the review.** Period comparisons against last month and last year, with the biggest movers, and a written summary. ## Getting reliable numbers - **Give exact dates.** "Last 30 days" means the 30 full days before today, in UTC. For month-end reports, name the month. - **Read the data notes.** Plugsight tells your AI when Google or Microsoft held data back: hidden low-volume search terms, rare Search Console queries, GA4 thresholds or sampling, Search Console data that isn't final yet (about 2–3 days), or a report that stopped at the row limit. - **Split by account** when accounts use different currencies, or when you need each account's own numbers. - **Row limits.** Tables return 500 rows by default, up to 50,000. Ask for more rows, or narrow with filters. - **Fields from different reports** can't always be combined (for example search terms and quality score). Ask in two questions. See [How your AI analyses marketing data](/connectors/marketing-data) for every setting. ## Safety tips - **Keep reporting servers read-only.** Untick **Allow changes** on any server used for reports, dashboards or scripts. - **Protect API keys.** Anyone with a key can read everything its server reaches. Keep keys on a server, never in a web page, and revoke them when a project ends. See [API keys](/mcp-servers/api-keys). - **Hide what shouldn't be counted.** Test properties, old sites and paused client accounts can be hidden under **Show sites & accounts**, so they never enter "all accounts" totals. - **Check Activity** to see which server and app each request came from. See [Activity log](/permissions/activity). ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Developer API](/developers) - [In-house marketers](/use-cases/in-house-marketers) - [Agencies managing many clients](/use-cases/agencies) --- # Executive assistants and busy inboxes URL: https://docs.plugsight.app/use-cases/executive-assistants Connect several mailboxes, a calendar and contacts so your AI can triage email, find what matters, draft replies and book meetings with approval. ## Who it's for You handle a lot of email: as an executive assistant, an office manager, or anyone whose inbox runs their day. You triage, chase replies, find the one attachment someone needs, and fit meetings into a full calendar. With Plugsight, your AI searches every connected mailbox at once, reads threads and attachments, tidies the inbox in bulk, drafts replies, finds free time and, with Outlook or iCloud Calendar, books and moves meetings. Every email and booking waits for your yes. Reading and drafting work on every plan. Sending, booking and archiving or labelling need **Pro** or **Agency**. ## Connectors to set up | Connector | What it adds | | --- | --- | | Each mailbox you handle: [Outlook](/connectors/outlook), [Gmail](/connectors/gmail), [iCloud Mail](/connectors/icloud-mail) or [another provider](/connectors/connect-any-email) | Live search across the whole mailbox, threads, attachments read as text; drafts; with approval: send, archive, label, move and mark | | [Outlook Calendar](/connectors/outlook-calendar) or [iCloud Calendar](/connectors/icloud-calendar) | Events, free time, and with approval: book, move and cancel events and invite guests | | [Google Calendar](/connectors/google-calendar) | Events and free time. Read-only for now | | [Outlook](/connectors/outlook-contacts), [Google](/connectors/google-contacts) or [iCloud Contacts](/connectors/icloud-contacts) | Find people's emails, phones and companies | Each mailbox is its own connection, and you connect it by signing in to that account. Give each one a clear name on **Connections**, such as "Work" or "Office inbox", so you can say which one you mean. See [Several accounts per service](/ai-apps/multiple-accounts). ## Recommended MCP server setup - **Name:** "Inbox" - **Account access:** **Selected accounts**: the mailboxes, calendar and contacts you handle - **Allow changes:** ticked On **Connections**: - Mailboxes start on **Drafts only**. Turn on **Can send** for a mailbox when you want your AI to send approved replies from it. You can leave some mailboxes on drafts and let others send. - Calendars start **Read-only**. Turn on **Can book & change** when you want your AI to book with your approval. Archiving, labelling and marking emails don't need the mailbox's switch: they work on Pro and Agency whenever email isn't paused. See [How changes are allowed](/permissions/how-changes-are-allowed). ## Example questions - "What came in overnight across all my inboxes? Group it by urgent, needs a reply, and FYI." - "Which emails from last week am I still waiting on a reply to? Draft polite follow-ups." - "Find the latest version of the board pack sent by finance, and summarise the attachment." - "List all emails with Excel attachments from the last 30 days." - "What are the open questions in the thread with legal about the NDA?" - "Archive every newsletter in the inbox and label the receipts 'Expenses'." - "Mark everything from the automated reports sender as read." - "What does next week look like, and where is there a free afternoon?" - "Find three 45-minute slots next week, and book the first one with sam@example.com and priya@example.com." (Outlook or iCloud Calendar) - "Move Friday's team review to Monday at the same time and let everyone know." - "What's the mobile number for Priya at Northwind?" - "Draft a reply to the conference organiser declining politely, in the Work inbox." ## A typical week **Every morning: triage.** Ask what came in since yesterday across every inbox, what's urgent, and what's on the calendar today. Ask for drafts of the replies that are needed. **Monday: the week ahead.** List next week's meetings with their guests, flag clashes, and find time for anything that still needs booking. **Mid-week: chasing.** Ask which emails are still waiting on a reply, and draft follow-ups. Find documents people are asking for. **Friday: inbox zero.** Ask your AI to archive newsletters and notifications, label receipts and mark FYI emails read. It asks first before moving anything to the trash, or changing more than 10 emails, and can change up to 100 at once. ## Safety tips - **Approve every send and booking.** Your AI shows the email's recipients, subject and body, or the event's details, and acts only after your yes. See [Approvals in the chat](/permissions/approvals). - **Name the mailbox.** With several inboxes, say which one to send from: "reply from the Office inbox". The approval shows the account it will use. - **Keep sending limits in place.** The [daily email limit](/permissions/daily-email-limit) (20 per mailbox in 24 hours by default) protects against mistakes. Drafts never count. - **Cancelling notifies guests.** Cancelled events email guests a cancellation by default, and on iCloud a repeating event is cancelled as a whole series. - **Pause when someone else uses your chat**, or when something looks wrong in **Activity**: **Pause everything** on **Permissions** stops sending, booking and inbox changes, and reading keeps working. See [Pause changes](/permissions/pause). - **Check Activity** at the end of the day to see every email sent and change made. See [Activity log](/permissions/activity). ## Related articles - [What your AI can do with email](/connectors/email-tools) - [What your AI can do with calendars](/connectors/calendar-tools) - [Sending, drafts and the daily email limit](/connectors/email-safety) - [Founders and small business owners](/use-cases/founders-and-small-businesses) - [Sales and account managers](/use-cases/sales-and-account-managers) --- # Recipes URL: https://docs.plugsight.app/recipes Copy-paste questions for Claude, ChatGPT and other AI apps, grouped by the job you want done, with what each one needs and does. A recipe is a question you can copy into your AI app, with everything around it: what you'll get back, which accounts it needs, what your AI does to answer it, and whether anything is changed. ## How to use a recipe 1. Check the accounts listed under **What you need** are connected in Plugsight and included in the MCP server your AI app uses. See [Connectors](/connectors) and [Create an MCP server](/mcp-servers/create). 2. Open a new chat in Claude, ChatGPT or another AI app that has your Plugsight MCP server added. See [Connect AI apps](/ai-apps). 3. Copy the question from the grey box and paste it into the chat. 4. Change the names, dates and numbers to match your own accounts. 5. Send it. The first time your AI uses a Plugsight tool, your AI app may ask your permission. See [Approvals in your AI app](/ai-apps/approvals). If your AI answers from general knowledge instead of your data, check the Plugsight connector is switched on in the chat. [Questions to try first](/get-started/first-questions#tips-for-better-answers) shows where to find it in Claude and ChatGPT. ## Tips for phrasing - **Start with "Using Plugsight".** It tells your AI to use your connected accounts rather than answer from memory. The recipes include it. - **Say what you want back.** "A table with campaign, cost and conversions", "the top 10", "three bullet points". Your AI shapes the answer to match. - **Ask one job at a time, then follow up.** "Now only for mobile", "show it per account", "explain the biggest drop". Your AI keeps what it already found. - **Ask for the reasoning.** "Explain how you worked this out" shows which data your AI used. ## Date ranges - **Name the period**: "yesterday", "last 7 days", "last month", "this year", or exact dates such as "1 to 31 October 2026". - **"Last 30 days" means the 30 full days before today** in the marketing tools, not including today. The same goes for 7, 14, 28, 90, 180 and 365 days. - **For a calendar week or month, give the dates.** "Monday 9 to Sunday 15 November" is clearer than "last week" if your week starts on a Monday. - **Marketing dates use UTC.** Store reports from Magento also use UTC. If you're far from UTC, the edges of a day can differ a little from what Google or your store shows. - **Search Console's last 2–3 days are not final yet** and may still grow. For comparisons, leave them out: "up to three days ago". - **To compare**, say with what: "compared with the previous 30 days" or "compared with the same month last year". ## Naming an account When your MCP server reaches several accounts of one type, name the one you mean: - "In my work Gmail…", "From the support@ inbox…" - "For Bright Dental's Google Ads…", "On the shop's GA4 property…" - "In our UK Zendesk…", "For the WooCommerce store…" Without a name, your AI usually looks across all of them. Clear names on **Connections** make this easier. See [Several accounts per service](/ai-apps/multiple-accounts). ## Recipes that change things Most recipes only read. A few send email, reply to tickets or book meetings. For those, your AI always shows you the exact change first and waits for your yes, and a few settings must allow it. Each of those recipes says what it needs. See [How changes are allowed](/permissions/how-changes-are-allowed). ## Paid search (Google Ads and Microsoft Advertising) - [Find wasted Google Ads spend](/recipes/find-wasted-ad-spend) - [Search terms to add as negatives](/recipes/negative-keywords) - [Weekly Google Ads performance summary](/recipes/weekly-google-ads-summary) - [Search terms to add as keywords](/recipes/search-terms-to-add-as-keywords) - [Quality score check](/recipes/quality-score-check) - [Campaigns and keywords worth more budget](/recipes/campaigns-worth-more-budget) - [Google Ads vs Microsoft Advertising](/recipes/google-vs-microsoft-ads) - [Spend check across client accounts](/recipes/client-accounts-spend-check) ## SEO (Google Search Console) - [Pages losing Google clicks](/recipes/pages-losing-google-clicks) - [Keywords you almost rank for](/recipes/keywords-you-almost-rank-for) - [Page-one results with low clicks](/recipes/low-ctr-results) - [Check if a page is indexed](/recipes/check-page-indexed) - [Ads on searches you already rank for](/recipes/paid-vs-organic) ## Website analytics (Google Analytics 4) - [Traffic by channel last week](/recipes/traffic-by-channel) - [Landing pages with high bounce](/recipes/landing-pages-high-bounce) - [Where shoppers drop out of checkout](/recipes/checkout-funnel) - [What counts as a conversion](/recipes/key-events-check) - [Who's on the site right now](/recipes/realtime-visitors) ## Website health - [Core Web Vitals check for key pages](/recipes/core-web-vitals-check) - [Tag Manager container audit](/recipes/tag-manager-audit) ## YouTube and Shopping - [YouTube video performance](/recipes/youtube-video-performance) - [Merchant Center products with problems](/recipes/merchant-center-problems) ## Reports across services - [Monthly marketing report across Ads, Analytics and Search Console](/recipes/monthly-marketing-report) - [Did last week's campaign drive store sales?](/recipes/campaign-store-sales) ## Email - [Triage today's inbox](/recipes/triage-inbox) - [Find and summarise invoices](/recipes/find-invoices) - [Draft replies to customer emails](/recipes/draft-customer-replies) - [Clean up newsletters (archive and label)](/recipes/clean-up-newsletters) - [Follow up on emails without a reply](/recipes/follow-up-no-reply) ## Calendar, meetings and contacts - [Prepare for tomorrow's meetings](/recipes/prepare-for-meetings) - [Find a free slot and book a meeting](/recipes/book-a-meeting) - [Summarise a Google Meet](/recipes/summarise-google-meet) - [Look up a contact's details](/recipes/look-up-a-contact) ## Customer support (Zendesk) - [This week's Zendesk themes](/recipes/zendesk-weekly-themes) - [Draft a ticket reply and add an internal note](/recipes/zendesk-reply-and-note) - [Apply a macro to similar tickets](/recipes/zendesk-apply-macro) - [Support volume this week vs last](/recipes/zendesk-ticket-counts) ## Online stores (WooCommerce and Magento) - [Store sales this month vs last](/recipes/store-sales-month-vs-month) - [Best-selling products](/recipes/best-selling-products) - [Customers who haven't reordered](/recipes/customers-not-reordered) - [Products running low on stock](/recipes/low-stock-products) ## Email marketing (Mailchimp) - [Mailchimp campaign performance](/recipes/mailchimp-campaign-performance) - [Mailchimp audience growth](/recipes/mailchimp-audience-growth) ## Docs and files - [Read and analyse a Google Sheet](/recipes/analyse-google-sheet) - [Summarise a Google Doc](/recipes/summarise-google-doc) - [Form responses summary](/recipes/form-responses-summary) ## Related articles - [Questions to try first](/get-started/first-questions) - [How your AI analyses marketing data](/connectors/marketing-data) - [Approvals in your AI app](/ai-apps/approvals) --- # Find wasted Google Ads spend URL: https://docs.plugsight.app/recipes/find-wasted-ad-spend See which search terms and keywords cost money without a single conversion, and what share of your Google Ads budget they took. Find out how much of your ad budget went to searches that never converted, and which terms and keywords were responsible. ## What you'll get - The share of your spend that went to search terms with no conversions, as a percentage and an amount. - The most expensive non-converting search terms, with the keyword and campaign that triggered each, clicks and cost. - Keywords that spent money without converting, with match type, campaign and ad group. - A short list of words that only ever appear in non-converting searches: candidates for negative keywords. See [Search terms to add as negatives](/recipes/negative-keywords) for more on those. ## What you need - [Google Ads](/connectors/google-ads) connected, on the **Pro** or **Agency** plan. [Microsoft Advertising](/connectors/microsoft-advertising) works the same way. - The Google Ads account must have conversion tracking set up. Without it, every term looks wasted. ## Ask this ```text Using Plugsight, find wasted spend in my Google Ads account over the last 30 days. Show what share of the budget went to search terms with no conversions, the 15 most expensive of those terms, and any keywords that spent money without converting. ``` ## Variations - **Another period:** "…over last month" or "…over the last 90 days". - **A higher bar:** "Only list search terms that spent at least 50 each." The default is 10 in the account's currency. - **One account:** "For Bright Dental's Google Ads, find wasted spend last month." - **Microsoft Advertising:** "Do the same for my Microsoft Advertising account." - **One campaign:** "Only for the Brand campaign: which search terms spent money without converting?" - **Per account:** "Rank my client accounts by money spent on search terms with no conversions." ## What your AI does behind the scenes 1. Lists your marketing accounts to find the right Google Ads account (`list_marketing_accounts`). 2. Runs the ready-made **wasted spend** analysis (`marketing_deep_dive`). It pulls your total spend, every search term with spend and no conversions, the search terms that did convert, and keywords that spent at least the threshold without converting. 3. Works out the negative-keyword candidates: words from the wasted search terms that never appear in a converting search. 4. For a single campaign, or a split by account, it pulls the rows directly instead (`get_marketing_data`), for example search term, keyword, cost, clicks and conversions where conversions are 0. Two things your AI may mention: - **Hidden search terms.** Google hides low-volume search terms for privacy. Their cost is in the account total but not in the search-term list. - **All conversions.** The table includes "all conversions", which counts secondary actions such as calls. A term with no main conversions may still drive those. ## Does it change anything? No. Google Ads is read-only in Plugsight. Your AI can suggest what to pause or exclude, but you make the change in Google Ads. See [Read-only connectors](/permissions/read-only-connectors). ## Related articles - [Search terms to add as negatives](/recipes/negative-keywords) - [Search terms to add as keywords](/recipes/search-terms-to-add-as-keywords) - [How your AI analyses marketing data](/connectors/marketing-data) --- # Search terms to add as negatives URL: https://docs.plugsight.app/recipes/negative-keywords Get a list of negative-keyword candidates from your Google Ads search terms, with the spend behind each word and the searches it appears in. Build a negative-keyword list from what people actually searched, based on words that cost you money and never led to a conversion. ## What you'll get - Words that appear only in search terms with no conversions, ranked by how much they cost. - For each word: total cost, clicks and how many different search terms contain it. - The full search terms behind any word you want to check. - Your AI's suggestion of which to add, and at what level (campaign or account), as a list you can paste into Google Ads. ## What you need - [Google Ads](/connectors/google-ads) or [Microsoft Advertising](/connectors/microsoft-advertising) connected, on the **Pro** or **Agency** plan. - Conversion tracking set up in the ad account. ## Ask this ```text Using Plugsight, look at my Google Ads search terms from the last 90 days and suggest negative keywords. Only include words that never appear in a converting search and that cost at least 20 in total. For each one, show the cost, clicks and three example search terms. Then give me a clean list I can paste into Google Ads. ``` ## Variations - **Check a word first:** "Which search terms containing 'free' did we pay for last month, and did any convert?" - **One campaign:** "Suggest negatives for the Generic campaign only." - **Lower the bar:** "Include words that cost at least 5." - **Microsoft Advertising:** "Do the same for Microsoft Advertising." ## What your AI does behind the scenes 1. Runs the **wasted spend** analysis (`marketing_deep_dive`) with the spend threshold you gave. It splits every non-converting search term into words, drops short and common words, numbers and any word that also appears in a converting search, and adds up cost and clicks per word. 2. Pulls the search terms that contain a given word, to show examples or check a word (`get_marketing_data` with fields such as search term, cost, clicks and conversions, and a "contains" filter). 3. Writes the suggestions. Matching is on the exact search text, so your AI may suggest a phrase rather than a single word where that's safer. > [!WARNING] > Check each suggestion before adding it. A word can be wasted in one campaign and valuable in another, and Google hides low-volume search terms, so the list never covers every search. ## Does it change anything? No. Your AI can't add negative keywords: Google Ads and Microsoft Advertising are read-only in Plugsight. Paste the list into the ad platform yourself. See [Read-only connectors](/permissions/read-only-connectors). ## Related articles - [Find wasted Google Ads spend](/recipes/find-wasted-ad-spend) - [Search terms to add as keywords](/recipes/search-terms-to-add-as-keywords) - [Google Ads](/connectors/google-ads) --- # Weekly Google Ads performance summary URL: https://docs.plugsight.app/recipes/weekly-google-ads-summary A short weekly report on Google Ads spend, clicks, conversions, CPA and ROAS by campaign, compared with the week before. Get the numbers you'd put in a Monday update: what you spent, what it brought in, and which campaigns moved. ## What you'll get - Totals for the week: cost, clicks, conversions, cost per conversion (CPA), conversion value and return on ad spend (ROAS). - The change against the previous 7 days, in percent. - A table by campaign, with the biggest gains and drops. - A few sentences on what changed and what to look at. ## What you need - [Google Ads](/connectors/google-ads) connected, on the **Pro** or **Agency** plan. ## Ask this ```text Using Plugsight, give me a weekly Google Ads summary for the last 7 days compared with the 7 days before. Show totals for cost, clicks, conversions, CPA, conversion value and ROAS, then a table by campaign, then three bullet points on what changed and why it might have. ``` ## Variations - **A calendar week:** "…for Monday 9 to Sunday 15 November, compared with the week before." "Last 7 days" means the 7 full days before today, so give dates if your week runs Monday to Sunday. - **Against last year:** "…compared with the same week last year." - **By day:** "Show cost and conversions per day for the last 14 days." - **By device:** "Split last week's conversions and CPA by device." - **For a client:** "Write it as a short email to the client, in plain words." Add "save it as a draft" if an email account is connected: see [Draft replies to customer emails](/recipes/draft-customer-replies). ## What your AI does behind the scenes 1. Lists your marketing accounts (`list_marketing_accounts`). 2. Runs a **period comparison** (`marketing_deep_dive`) with fields such as campaign, cost, clicks, conversions, CPA, conversion value and ROAS, for the last 7 days against the previous 7. It returns totals, the change for each metric and the campaigns with the biggest gains and drops. 3. For a per-day or per-device split, it pulls the rows directly (`get_marketing_data` with date or device as a field). CPA, ROAS, CTR and conversion rate are recalculated from the added-up totals, so they stay correct across campaigns and accounts. ## Does it change anything? No. This recipe only reads. Saving the summary as an email draft writes a draft in your mailbox, which is never sent without your approval. ## Related articles - [Monthly marketing report across Ads, Analytics and Search Console](/recipes/monthly-marketing-report) - [Spend check across client accounts](/recipes/client-accounts-spend-check) - [How your AI analyses marketing data](/connectors/marketing-data) --- # Search terms to add as keywords URL: https://docs.plugsight.app/recipes/search-terms-to-add-as-keywords Find search terms that already convert in Google Ads but aren't keywords yet, so you can add them and control their bids and ads. Some of your best searches arrive through broad or phrase match. Adding them as their own keywords lets you set bids and write ads for them. ## What you'll get - Search terms with at least one conversion that aren't keywords yet, ranked by conversions. - For each: the keyword and match type that triggered it, campaign, ad group, clicks, cost, conversions, CPA and conversion value. - The total conversions these terms brought in. - Your AI's suggestion of which to add as exact-match keywords first. ## What you need - [Google Ads](/connectors/google-ads) or [Microsoft Advertising](/connectors/microsoft-advertising) connected, on the **Pro** or **Agency** plan. ## Ask this ```text Using Plugsight, which search terms converted in Google Ads over the last 90 days but aren't keywords yet? Show the top 20 by conversions, with the keyword that triggered each, cost and CPA, and say which you'd add as exact-match keywords first. ``` ## Variations - **Stronger winners only:** "Only include search terms with at least 3 conversions." The default is 1. - **One campaign:** "…in the Generic campaign only." - **Microsoft Advertising:** "Do the same for Microsoft Advertising." - **Ad copy ideas:** "For the top five, suggest a headline that uses the search term." ## What your AI does behind the scenes 1. Runs the ready-made **search term winners** analysis (`marketing_deep_dive`). It pulls search terms with at least the number of conversions you set, and leaves out terms that are already keywords. On Google Ads it also uses each search term's status, so terms you've already added or excluded are left out. 2. For a single campaign or a closer look, it pulls the rows directly (`get_marketing_data`). ## Does it change anything? No. Your AI can't add keywords: the ad platforms are read-only in Plugsight. Add them in Google Ads or Microsoft Advertising yourself. See [Read-only connectors](/permissions/read-only-connectors). ## Related articles - [Find wasted Google Ads spend](/recipes/find-wasted-ad-spend) - [Campaigns and keywords worth more budget](/recipes/campaigns-worth-more-budget) - [Google Ads](/connectors/google-ads) --- # Quality score check URL: https://docs.plugsight.app/recipes/quality-score-check See how much of your Google Ads spend goes to low quality score keywords, and whether expected CTR, ad relevance or the landing page is to blame. Low quality scores make clicks cost more. This recipe shows where your spend sits by quality score and which part of the score to fix. ## What you'll get - Spend, keywords and conversions grouped by quality score (1 to 10, plus keywords with no score yet). - Which of the three parts (expected click-through rate, ad relevance, landing page experience) is most often below average for low-scoring keywords. - The most expensive low-scoring keywords, with campaign, ad group and each part's rating. - Your AI's suggestions on what to change first. ## What you need - [Google Ads](/connectors/google-ads) or [Microsoft Advertising](/connectors/microsoft-advertising) connected, on the **Pro** or **Agency** plan. ## Ask this ```text Using Plugsight, audit quality scores in my Google Ads account for the last 30 days. How much did we spend on keywords with a quality score of 5 or less, and which part is usually the problem: expected CTR, ad relevance or landing page experience? List the 15 most expensive low-scoring keywords. ``` ## Variations - **One campaign:** "…for the Generic campaign only." - **Landing pages:** "Which landing pages do the keywords with a below-average landing page experience point to?" Then check those pages with [Core Web Vitals check for key pages](/recipes/core-web-vitals-check). - **Microsoft Advertising:** "Do the same for Microsoft Advertising." ## What your AI does behind the scenes 1. Runs the ready-made **quality score audit** (`marketing_deep_dive`). It pulls every keyword with impressions in the period, with its quality score, the three parts, impressions, clicks, cost, conversions and CPA, and groups spend by score. 2. For landing pages or a closer look, it pulls the rows directly (`get_marketing_data` with fields such as keyword, landing page and landing page experience). ## Does it change anything? No. Google Ads is read-only in Plugsight. You make the changes in Google Ads. See [Read-only connectors](/permissions/read-only-connectors). ## Related articles - [Core Web Vitals check for key pages](/recipes/core-web-vitals-check) - [How your AI analyses marketing data](/connectors/marketing-data) --- # Campaigns and keywords worth more budget URL: https://docs.plugsight.app/recipes/campaigns-worth-more-budget Find Google Ads campaigns and keywords that convert at or below your average CPA but miss impressions because of budget or ad rank. Find where more money would most likely bring more conversions at a cost you already accept. ## What you'll get - Your account's average cost per conversion (CPA). - Campaigns that convert at or below that average but lose impression share, with how much is lost to budget and how much to rank, and a suggested action for each. - Keywords in the same position, with their CPA compared with the average. - A rough estimate of the extra conversions if the lost share were won back at a similar CPA. Treat it as a guide: it assumes conversions grow in line with impressions. ## What you need - [Google Ads](/connectors/google-ads) or [Microsoft Advertising](/connectors/microsoft-advertising) connected, on the **Pro** or **Agency** plan. ## Ask this ```text Using Plugsight, which Google Ads campaigns and keywords converted at or below our average CPA over the last 30 days but lost impression share to budget or rank? Show what each one loses, what you'd change, and roughly how many extra conversions we could get. ``` ## Variations - **Stronger performers only:** "Only include campaigns with at least 5 conversions." The default is 1. - **Budget only:** "Which campaigns are limited by budget, and by how much?" - **Longer period:** "…over the last 90 days", for accounts with fewer conversions. - **Microsoft Advertising:** "Do the same for Microsoft Advertising." ## What your AI does behind the scenes 1. Runs the ready-made **scale opportunities** analysis (`marketing_deep_dive`). It pulls the average CPA per account, then campaigns and keywords with at least the conversions you set, with their impression share and the share lost to budget and to rank. 2. Keeps the ones at or below the average CPA that lose at least 5% to budget or 10% to rank, and labels each with "raise budget" or "raise bid / improve quality score". 3. Keywords take their campaign's budget figure, because budget is set per campaign. ## Does it change anything? No. Your AI can't change budgets or bids: the ad platforms are read-only in Plugsight. See [Read-only connectors](/permissions/read-only-connectors). ## Related articles - [Quality score check](/recipes/quality-score-check) - [Find wasted Google Ads spend](/recipes/find-wasted-ad-spend) - [How your AI analyses marketing data](/connectors/marketing-data) --- # Google Ads vs Microsoft Advertising URL: https://docs.plugsight.app/recipes/google-vs-microsoft-ads Compare spend, clicks, conversions, CPA and ROAS between Google Ads and Microsoft Advertising for the same period, side by side. See which ad platform gives you more for your money, in one table. ## What you'll get - A side-by-side table for each platform: cost, clicks, conversions, CPA, conversion value and ROAS. - The change for each against the previous period. - Optionally, the same by campaign or by device on each platform. - A short view on where to shift budget, with the reasons. ## What you need - [Google Ads](/connectors/google-ads) and [Microsoft Advertising](/connectors/microsoft-advertising) both connected, on the **Pro** or **Agency** plan. ## Ask this ```text Using Plugsight, compare Google Ads and Microsoft Advertising for last month: cost, clicks, conversions, CPA, conversion value and ROAS for each, side by side, and how each changed from the month before. Where would you move budget, and why? ``` ## Variations - **By campaign:** "Show the same for each campaign on both platforms." - **By device:** "Compare CPA by device on Google Ads and Microsoft Advertising." - **Longer view:** "…for the last 90 days, by month." ## What your AI does behind the scenes 1. Lists your marketing accounts (`list_marketing_accounts`). 2. Runs the **account overview** (`marketing_deep_dive`), which covers every connected platform this period against the previous one, or a **period comparison** for each platform with the fields you asked for. 3. For splits by campaign, device or month, it pulls each platform's rows directly (`get_marketing_data`) and puts them side by side. If your accounts use different currencies, your AI is told the money is added as-is. Ask it to keep currencies apart. ## Does it change anything? No. Both ad platforms are read-only in Plugsight. ## Related articles - [Monthly marketing report across Ads, Analytics and Search Console](/recipes/monthly-marketing-report) - [How your AI analyses marketing data](/connectors/marketing-data) --- # Spend check across client accounts URL: https://docs.plugsight.app/recipes/client-accounts-spend-check For agencies, one table of every client's ad spend, conversions and CPA this month against last month, with the accounts that moved most. When you manage many Google Ads accounts, see them all in one table and spot the ones that need attention. ## What you'll get - One row per ad account: cost, conversions, CPA and ROAS this period, and the change from the previous period. - The accounts with the biggest rises and drops in spend. - Accounts whose CPA got noticeably worse. ## What you need - [Google Ads](/connectors/google-ads) connected with the Google account that can open your manager (MCC) account, so every client account is included. [Microsoft Advertising](/connectors/microsoft-advertising) works the same way. - The **Pro** or **Agency** plan. - The client accounts visible. Hidden accounts are left out: see [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## Ask this ```text Using Plugsight, for every Google Ads account I can see, compare this month so far with the same days last month: cost, conversions, CPA and ROAS per account. Sort by the biggest change in spend, and flag any account whose CPA rose by more than 20%. ``` ## Variations - **Last full month:** "…for last month compared with the month before." - **Over budget:** "Which accounts spent more than 20% more than last month?" - **One client in detail:** "Now break Bright Dental's account down by campaign." - **Both platforms:** "Do the same across Google Ads and Microsoft Advertising." ## What your AI does behind the scenes 1. Lists every marketing account the MCP server reaches (`list_marketing_accounts`), including client accounts under a manager account. 2. Runs a **period comparison** (`marketing_deep_dive`) with fields such as account name, cost, conversions, CPA and ROAS. Including the account name keeps each account on its own row; without it, the rows are added together. 3. For one client in detail, it pulls that account's rows by campaign (`get_marketing_data`). > [!TIP] > Give each client's connection a clear name on **Connections**, and keep one MCP server per client if you share chats with them. See [Several accounts per service](/ai-apps/multiple-accounts). ## Does it change anything? No. This recipe only reads. ## Related articles - [Weekly Google Ads performance summary](/recipes/weekly-google-ads-summary) - [Several accounts per service](/ai-apps/multiple-accounts) --- # Pages losing Google clicks URL: https://docs.plugsight.app/recipes/pages-losing-google-clicks Find the pages on your site that lost the most clicks from Google search compared with the previous period, and the queries behind the drop. Spot pages whose Google traffic is falling, before it shows up in your leads or sales. ## What you'll get - Pages that lost clicks, biggest drop first: clicks now, clicks before, the change, and average position now and before. - Pages that got clicks before but none now. - For any page you pick, the queries that lost the most clicks, so you can see whether it dropped in ranking or lost interest. - Your AI's view on likely causes and what to check. ## What you need - [Google Search Console](/connectors/google-search-console) connected, on the **Pro** or **Agency** plan. ## Ask this ```text Using Plugsight, which pages on my site lost the most Google clicks in the last 28 days compared with the 28 days before? Show the top 15 with clicks before and after and the change in average position. For the three biggest drops, show which queries lost clicks. ``` ## Variations - **Against last year:** "…compared with the same 28 days last year." This removes seasonal swings. - **One site:** "For example.com only…" when you have several sites. - **Leave out fresh data:** "…up to three days ago." Search Console's latest 2–3 days aren't final yet. - **Mobile only:** "…for mobile searches only." - **Check a page:** "Is the top page still indexed?" See [Check if a page is indexed](/recipes/check-page-indexed). ## What your AI does behind the scenes 1. Lists your Search Console sites (`list_marketing_accounts`). 2. Runs the ready-made **SEO opportunities** analysis (`marketing_deep_dive`). Its "declining pages" table compares each page's clicks and position with the previous period, or the same period last year. 3. For the queries behind a page, it pulls query rows filtered to that page for both periods (`get_marketing_data` with fields such as query, page, clicks, impressions and position), or runs a **period comparison** on them. Search Console hides rare queries for privacy. When that matters, your AI is told what share of clicks and impressions is missing. ## Does it change anything? No. Search Console is read-only in Plugsight. ## Related articles - [Keywords you almost rank for](/recipes/keywords-you-almost-rank-for) - [Check if a page is indexed](/recipes/check-page-indexed) - [Google Search Console](/connectors/google-search-console) --- # Keywords you almost rank for URL: https://docs.plugsight.app/recipes/keywords-you-almost-rank-for List the search queries where your site sits near the top of Google, in positions 4 to 20, and the extra clicks a better rank could bring. Queries in positions 4 to 20 already get seen. Moving them up a few places is often the quickest SEO win. ## What you'll get - Queries ranking between position 4 and 20 with at least 100 impressions (you can change this). - For each: average position, impressions, clicks, click-through rate and an estimate of the extra clicks at position 3. - The page that ranks for each query, if you ask. - Suggestions on what to improve on those pages. ## What you need - [Google Search Console](/connectors/google-search-console) connected, on the **Pro** or **Agency** plan. ## Ask this ```text Using Plugsight, which search queries rank in positions 4 to 20 for my site over the last 28 days, with the most impressions? Show the top 20 with position, impressions, clicks and how many extra clicks we might get at position 3, and which page ranks for each. ``` ## Variations - **More volume only:** "Only include queries with at least 500 impressions." - **One section of the site:** "…only for pages under /blog/." - **Page two only:** "Which queries sit on page two, positions 11 to 20?" - **Where ads could help:** see [Ads on searches you already rank for](/recipes/paid-vs-organic). ## What your AI does behind the scenes 1. Runs the ready-made **SEO opportunities** analysis (`marketing_deep_dive`). Its "striking distance" table lists queries in positions 4 to 20 with at least the impressions you set, and estimates the extra clicks at position 3 from typical click-through rates. 2. To show which page ranks for each query, or to limit it to part of the site, it pulls query and page rows directly (`get_marketing_data`, with a filter such as page contains "/blog/"). The extra-clicks estimate uses industry average click-through rates. Brand queries and rich results can make it higher or lower. ## Does it change anything? No. Search Console is read-only in Plugsight. ## Related articles - [Page-one results with low clicks](/recipes/low-ctr-results) - [Pages losing Google clicks](/recipes/pages-losing-google-clicks) - [Google Search Console](/connectors/google-search-console) --- # Page-one results with low clicks URL: https://docs.plugsight.app/recipes/low-ctr-results Find queries where you rank on Google's first page but get far fewer clicks than usual for that position, so you can rewrite titles and descriptions. When a page ranks well but few people click it, the title or description shown in Google is often the problem. ## What you'll get - Queries where you rank in the top 10 but get less than half the usual click-through rate for that position. - For each: position, impressions, your click-through rate, the typical rate and the estimated extra clicks. - The page shown for each query, if you ask. - New title and meta description ideas for the worst ones. ## What you need - [Google Search Console](/connectors/google-search-console) connected, on the **Pro** or **Agency** plan. ## Ask this ```text Using Plugsight, which queries rank on page one for my site in the last 28 days but get less than half the usual click-through rate for their position? List the top 15 with the page shown, and suggest a better title and meta description for the five with the most missed clicks. ``` ## Variations - **Mobile only:** "…for mobile searches only." - **One country:** "…for searches from the United Kingdom only." - **Check the live title:** "Fetch the speed and SEO score of the top page too." See [Core Web Vitals check for key pages](/recipes/core-web-vitals-check). ## What your AI does behind the scenes 1. Runs the ready-made **SEO opportunities** analysis (`marketing_deep_dive`). Its "low CTR" table compares each page-one query's click-through rate with an industry average for its position. 2. Pulls the query and page rows (`get_marketing_data`) to show which page appears for each query. 3. Writes title and description ideas itself. Plugsight doesn't read the page's current title from your site, so give your AI the current wording if you want it compared. Brand queries and results with extras such as review stars can have a higher or lower usual rate than average. ## Does it change anything? No. Search Console is read-only in Plugsight. You change titles and descriptions on your site. ## Related articles - [Keywords you almost rank for](/recipes/keywords-you-almost-rank-for) - [Google Search Console](/connectors/google-search-console) --- # Check if a page is indexed URL: https://docs.plugsight.app/recipes/check-page-indexed Ask whether Google has indexed a page, when it last crawled it, which canonical it chose, and whether your sitemaps have errors. Find out how Google sees a page, without opening Search Console's URL inspection yourself. ## What you'll get - Whether the page is indexed, and if not, Google's reason. - When Google last crawled it, and the canonical address Google chose compared with yours. - Mobile usability and rich result findings, where Google reports them. - Optionally, your submitted sitemaps with how many pages each submitted and how many are indexed, plus errors and warnings. ## What you need - [Google Search Console](/connectors/google-search-console) connected, on the **Pro** or **Agency** plan. - The page must be on a site in your Search Console. ## Ask this ```text Using Plugsight, is https://example.com/pricing indexed by Google? If not, why not? Tell me when it was last crawled and which canonical Google picked. ``` ## Variations - **Several pages:** "Check these five URLs and tell me which aren't indexed: …" - **Sitemaps:** "List the sitemaps for example.com with submitted and indexed counts, and any errors." - **After a drop:** "Check whether the three pages that lost the most clicks last month are still indexed." See [Pages losing Google clicks](/recipes/pages-losing-google-clicks). ## What your AI does behind the scenes 1. Finds the Search Console site that contains the address (`list_marketing_accounts`). 2. Inspects the address as Google sees it (`search_console_inspect_url`): coverage, last crawl, canonical, mobile usability and rich results. It does this once per address. 3. For sitemaps, lists them with their counts, errors and warnings (`search_console_sitemaps`). ## Does it change anything? No. Inspecting a page doesn't ask Google to crawl or index it. To request indexing, use Search Console. ## Related articles - [Pages losing Google clicks](/recipes/pages-losing-google-clicks) - [Google Search Console](/connectors/google-search-console) --- # Ads on searches you already rank for URL: https://docs.plugsight.app/recipes/paid-vs-organic Compare Google Ads search terms with Search Console queries to find ad spend on searches where you already rank top 3, and SEO gaps. Check whether you're paying for clicks you might get for free, and which paid winners deserve better organic content. ## What you'll get - Search terms you pay for where your site already ranks in the top 3 organically, with the ad cost and organic position. - The share of search-term spend that goes to those terms. - Terms that convert in ads but rank below page one organically, or not at all: content ideas. - Organic queries with plenty of impressions beyond page one that you don't advertise on: candidates for a paid test. ## What you need - [Google Ads](/connectors/google-ads) or [Microsoft Advertising](/connectors/microsoft-advertising), and [Google Search Console](/connectors/google-search-console), on the **Pro** or **Agency** plan. ## Ask this ```text Using Plugsight, compare my Google Ads search terms with my Search Console queries for the last 90 days. Where are we paying for clicks on searches we already rank top 3 for, and how much did that cost? Which terms convert in ads but rank badly organically? ``` ## Variations - **One site:** "…using example.com in Search Console" when you have several sites. - **Leave brand out:** "Ignore searches containing our brand name, Acme." - **Microsoft Advertising:** "Do the same with Microsoft Advertising." ## What your AI does behind the scenes 1. Runs the ready-made **paid vs organic** analysis (`marketing_deep_dive`). It pulls ad search terms with clicks, cost, conversions and value, and Search Console queries with clicks, impressions and position, then matches them on the exact search text. 2. Splits the matches into three tables: paying while ranking top 3, paid winners with weak SEO, and organic queries worth a paid test. > [!NOTE] > Matching is on the exact search text, and both Google Ads and Search Console hide low-volume searches, so the overlap is a minimum. Before cutting bids on your brand name, check whether competitors bid on it. ## Does it change anything? No. Both services are read-only in Plugsight. ## Related articles - [Keywords you almost rank for](/recipes/keywords-you-almost-rank-for) - [Find wasted Google Ads spend](/recipes/find-wasted-ad-spend) --- # Traffic by channel last week URL: https://docs.plugsight.app/recipes/traffic-by-channel See last week's website sessions, engagement, conversions and revenue by channel in Google Analytics 4, compared with the week before. Find out where last week's visitors came from (search, ads, email, social, direct) and which channels brought results. ## What you'll get - A table by channel (the default channel group in GA4): sessions, users, engagement rate, key events (conversions) and revenue. - The change for each against the previous week. - The channels that grew or fell the most. ## What you need - [Google Analytics 4](/connectors/google-analytics-4) connected, on the **Pro** or **Agency** plan. ## Ask this ```text Using Plugsight, show my GA4 traffic by channel for the last 7 days compared with the 7 days before: sessions, users, engagement rate, conversions and revenue for each channel, with the change in percent. Which channels moved most? ``` ## Variations - **By source and medium:** "Break the Paid Search and Email channels down by source / medium." - **By campaign:** "Which campaigns brought the most sessions and conversions last week?" - **New visitors:** "How many new users did each channel bring?" - **One property:** "On the shop's GA4 property…" when you have several. - **A calendar week:** give the dates, for example "Monday 9 to Sunday 15 November". ## What your AI does behind the scenes 1. Lists your GA4 properties (`list_marketing_accounts`). 2. Runs a **period comparison** (`marketing_deep_dive`) with fields such as channel, sessions, users, engagement rate, conversions and revenue, for the last 7 days against the previous 7. 3. For source, medium or campaign splits, it pulls the rows directly (`get_marketing_data`). "Conversions" here means GA4 key events. To see which events count, use [What counts as a conversion](/recipes/key-events-check). GA4 may sometimes sample results or group rare values into "(other)"; your AI is told when it does. ## Does it change anything? No. Google Analytics is read-only in Plugsight. ## Related articles - [Landing pages with high bounce](/recipes/landing-pages-high-bounce) - [Monthly marketing report across Ads, Analytics and Search Console](/recipes/monthly-marketing-report) - [Google Analytics 4](/connectors/google-analytics-4) --- # Landing pages with high bounce URL: https://docs.plugsight.app/recipes/landing-pages-high-bounce Find the landing pages in Google Analytics 4 where most visits leave without engaging, ranked by how many sessions they lose. Find the pages where visitors arrive and leave without doing anything, weighted by how much traffic each gets. ## What you'll get - Landing pages with at least a minimum number of sessions, sorted by bounce rate or by sessions lost. - For each: sessions, bounce rate, engagement rate, average session duration and conversions. - The same pages split by device or channel, if you ask, to see whether the problem is on mobile or from one source. - Suggestions on what to check on each page. ## What you need - [Google Analytics 4](/connectors/google-analytics-4) connected, on the **Pro** or **Agency** plan. In GA4, bounce rate is the share of sessions that weren't engaged sessions. ## Ask this ```text Using Plugsight, which landing pages in GA4 had the highest bounce rate over the last 30 days, counting only pages with at least 200 sessions? Show sessions, bounce rate, engagement rate, average session duration and conversions for the top 15, and split the worst five by device. ``` ## Variations - **Paid traffic only:** "…for sessions from the Paid Search channel only." - **Most sessions lost:** "Rank them by the number of bounced sessions, not the rate." - **Compare:** "How did the bounce rate of these pages change from the previous 30 days?" - **Check speed:** "Check the three worst pages with PageSpeed." See [Core Web Vitals check for key pages](/recipes/core-web-vitals-check). ## What your AI does behind the scenes 1. Lists your GA4 properties (`list_marketing_accounts`). 2. Pulls landing page rows (`get_marketing_data`) with fields such as landing page, sessions, bounce rate, engagement rate, average session duration and conversions, filtered to pages with at least the sessions you set, and sorted as you asked. 3. Pulls the same with device or channel added for the pages you pick. 4. For a change over time, runs a **period comparison** (`marketing_deep_dive`). ## Does it change anything? No. Google Analytics is read-only in Plugsight. ## Related articles - [Core Web Vitals check for key pages](/recipes/core-web-vitals-check) - [Traffic by channel last week](/recipes/traffic-by-channel) --- # Where shoppers drop out of checkout URL: https://docs.plugsight.app/recipes/checkout-funnel Build a GA4 funnel from product view to purchase and see how many users reach each step and where they leave, by device or channel. See how many shoppers make it from looking at a product to buying it, and at which step most of them give up. ## What you'll get - A funnel of your steps, for example product view, add to cart, begin checkout and purchase. - For each step: users who reached it, the completion rate to the next step and the drop-off. - The same funnel split by device or channel, if you ask. - Your AI's view on the weakest step and what to check. ## What you need - [Google Analytics 4](/connectors/google-analytics-4) connected, on the **Pro** or **Agency** plan. - The events for each step tracked in GA4. Online stores often send view_item, add_to_cart, begin_checkout and purchase. A step can also be a page visit, such as any page whose address contains /checkout. ## Ask this ```text Using Plugsight, build a GA4 funnel for the last 28 days: view_item, add_to_cart, begin_checkout, purchase. Show how many users reach each step and the drop-off between steps, split by device. Where do mobile users drop out most compared with desktop? ``` ## Variations - **Page steps:** "Build a funnel: pages containing /pricing, then /signup, then /welcome." - **By channel:** "Split the funnel by channel instead of device." - **Open funnel:** "Let users enter at any step." By default users must start at step 1. - **Another period:** "…for last month." - **Check the events exist first:** "Which events does this GA4 property record?" ## What your AI does behind the scenes 1. Lists your GA4 properties (`list_marketing_accounts`). 2. If it isn't sure of your event names, checks what the property offers (`analytics_metadata`) or which events count as key events (`analytics_key_events`). 3. Builds the funnel (`analytics_funnel`) with 2 to 10 steps, each an event or a page visit, closed unless you ask for an open funnel, and with the breakdown you asked for. The period is the last 28 days unless you give another. Rates come back as fractions (0.25 means 25%); your AI turns them into percentages. ## Does it change anything? No. Google Analytics is read-only in Plugsight. ## Related articles - [What counts as a conversion](/recipes/key-events-check) - [Google Analytics 4](/connectors/google-analytics-4) --- # What counts as a conversion URL: https://docs.plugsight.app/recipes/key-events-check List the events your GA4 property counts as key events (conversions), how often each happened, and how they're counted. Before you trust a conversion number, check what GA4 is counting. ## What you'll get - Every event marked as a key event in the property. - For each: how many times it happened in the period, how many users triggered it, and whether it counts once per session or every time. - When each was set up as a key event. - A note if the property has no key events at all. ## What you need - [Google Analytics 4](/connectors/google-analytics-4) connected, on the **Pro** or **Agency** plan. ## Ask this ```text Using Plugsight, what counts as a conversion in my GA4 property? List the key events, how many of each happened in the last 28 days, how many users triggered them, and whether each is counted once per session or every time. ``` ## Variations - **By channel:** "Which channels drove the purchase key event last month?" - **By page:** "Which landing pages led to the most generate_lead events?" - **Spot problems:** "Are any key events firing far more than sessions would suggest?" Then see [Tag Manager container audit](/recipes/tag-manager-audit) to look for duplicate tags. ## What your AI does behind the scenes 1. Lists your GA4 properties (`list_marketing_accounts`). 2. Reads the property's key events and their counts for the period (`analytics_key_events`). The period is the last 28 days up to yesterday unless you give another. 3. For a split by channel or page, pulls conversions with that field (`get_marketing_data`). If the property has no key events, your AI is told to mark events as key events in GA4: **Admin → Data display → Events**. ## Does it change anything? No. Google Analytics is read-only in Plugsight. Key events are set in GA4. ## Related articles - [Tag Manager container audit](/recipes/tag-manager-audit) - [Where shoppers drop out of checkout](/recipes/checkout-funnel) --- # Who's on the site right now URL: https://docs.plugsight.app/recipes/realtime-visitors See how many people are on your website in the last 30 minutes, by country, page or event, from Google Analytics 4 realtime data. Check live activity, for example during a launch, a sale or right after an email goes out. ## What you'll get - Active users in the last 30 minutes. - Split by country, page or screen, or event, as you ask. - A quick read on whether a launch or campaign is landing. ## What you need - [Google Analytics 4](/connectors/google-analytics-4) connected, on the **Pro** or **Agency** plan. ## Ask this ```text Using Plugsight, how many people are on my site right now according to GA4? Break it down by country and by page. ``` ## Variations - **Events:** "Which events happened in the last 30 minutes, and how many of each?" - **After a send:** "We sent our newsletter 10 minutes ago. Which pages are people on now?" - **One property:** "On the shop's GA4 property…" ## What your AI does behind the scenes 1. Lists your GA4 properties (`list_marketing_accounts`). 2. Runs a realtime report (`analytics_realtime`) with active users and the dimensions you asked for, such as country, page or screen name (unifiedScreenName) or event name. Realtime covers the last 30 minutes only. ## Does it change anything? No. Google Analytics is read-only in Plugsight. ## Related articles - [Traffic by channel last week](/recipes/traffic-by-channel) - [Google Analytics 4](/connectors/google-analytics-4) --- # Core Web Vitals check for key pages URL: https://docs.plugsight.app/recipes/core-web-vitals-check Check your most important pages with Google PageSpeed Insights, see which pass Core Web Vitals on mobile, and get the fixes that save the most time. Check whether your key pages pass Google's Core Web Vitals, and what would make them faster. ## What you'll get - For each page: performance, SEO, accessibility and best-practice scores out of 100. - Real-user Core Web Vitals (Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift) for the page and for the whole site, from Chrome users, as Google Search uses them. - Lab timings from one test run. - The changes that would save the most time, with how much each would save. - A summary table across all the pages you checked. ## What you need - Nothing to connect. PageSpeed Insights works on every plan and every MCP server. See [PageSpeed Insights](/connectors/pagespeed-insights). - The pages must be public. Pages behind a login can't be checked. - Optional: [Google Search Console](/connectors/google-search-console) or [Google Analytics 4](/connectors/google-analytics-4) (Pro or Agency), if you want your AI to pick the pages with the most traffic. ## Ask this ```text Using Plugsight, run a PageSpeed check on mobile for these pages: https://example.com/, https://example.com/pricing, https://example.com/blog/. For each, tell me whether it passes Core Web Vitals, its performance score, and the top three fixes. Finish with a table across all pages. ``` ## Variations - **Pick the pages for me:** "Find my five landing pages with the most Google clicks last month in Search Console, then check each with PageSpeed on mobile." - **Desktop:** "…on desktop." Mobile is checked unless you ask; it's what Google ranks on. - **Only SEO and accessibility:** "Check only the SEO and accessibility scores of https://example.com/blog/latest." - **Compare:** "Compare the mobile and desktop scores of our home page." ## What your AI does behind the scenes 1. If you asked it to pick pages, pulls your top pages by clicks (`get_marketing_data` on Search Console) or sessions (on GA4). 2. Checks each page with PageSpeed Insights (`pagespeed_check`), one page at a time. Each check takes 10 to 40 seconds, so several pages take a few minutes. 3. Puts the results side by side. A quiet page or new site may not have enough Chrome visits for real-user data; your AI is told, and the lab scores still work. Lab results come from one test run and can vary a little between checks. ## Does it change anything? No. A check only loads the page, the way a visitor would. ## Related articles - [Landing pages with high bounce](/recipes/landing-pages-high-bounce) - [PageSpeed Insights](/connectors/pagespeed-insights) --- # Tag Manager container audit URL: https://docs.plugsight.app/recipes/tag-manager-audit Audit your Google Tag Manager container for tags that never fire, retired Universal Analytics tags, duplicates, unused triggers and unpublished changes. Find tracking problems in your live Tag Manager container, ranked by how much they matter. ## What you'll get - Problems found in the published (live) version: - tags with no firing trigger, which never run (high) - Universal Analytics tags, which collect nothing since Google retired UA (high) - paused tags (medium) - possible duplicates: tags of the same type with the same id, which can double-count (medium) - triggers no tag uses, and variables nothing refers to (low) - Custom HTML tags, to check they're still needed - Changes waiting unpublished in workspaces. - A fix-first list in plain words. ## What you need - [Google Tag Manager](/connectors/google-tag-manager) connected, on the **Pro** or **Agency** plan, once Google approves it (it's being reviewed). ## Ask this ```text Using Plugsight, audit my Google Tag Manager container. List the problems by severity, explain each in plain words, and tell me what to fix first. Are there unpublished changes waiting in any workspace? ``` ## Variations - **Several containers:** "Audit GTM-ABC123." When the MCP server reaches more than one container, name it. - **One tag:** "Which GA4 measurement id does the GA4 config tag send to, and on which triggers?" - **Double counting:** "Are any of our conversion tags firing twice?" - **History:** "How many tags, triggers and variables did each of the last five published versions have?" ## What your AI does behind the scenes 1. Lists the containers the MCP server reaches (`tag_manager_list_containers`). 2. Audits the live version of the container (`tag_manager_audit`). 3. For detail, reads the container's tags, triggers and variables (`tag_manager_container`), or one tag in full (`tag_manager_get_tag`). 4. For history, lists the published versions (`tag_manager_versions`). ## Does it change anything? No. Tag Manager is read-only in Plugsight: your AI can't edit, publish or delete anything. Make the fixes in Tag Manager. ## Related articles - [What counts as a conversion](/recipes/key-events-check) - [Google Tag Manager](/connectors/google-tag-manager) --- # YouTube video performance URL: https://docs.plugsight.app/recipes/youtube-video-performance See which YouTube videos got the most views and watch time in a period, how subscribers changed, and where viewers came from. Find your best and weakest videos, and what drives your channel's views. ## What you'll get - Your top videos in the period by views or watch time, with titles, average view duration, likes, comments, shares and subscribers gained. - Channel totals: views, watch time, subscribers gained and lost. - Optionally, where views came from (search, suggested videos, outside YouTube), devices, countries, or a trend by day or month. ## What you need - [YouTube](/connectors/youtube) connected, on the **Pro** or **Agency** plan, once Google approves it (it's being reviewed). ## Ask this ```text Using Plugsight, which of my YouTube videos got the most watch time in the last 90 days? Show the top 10 with views, watch time, average view duration and subscribers gained, then tell me what the best ones have in common. ``` ## Variations - **Latest uploads:** "List my last 10 uploads with views, likes and comments." - **Traffic sources:** "Where do my viewers come from: search, suggested videos or outside YouTube?" - **Subscriber trend:** "How many subscribers did I gain and lose each month this year?" - **Audience:** "What share of my viewers are 25–34, and which countries watch most?" - **Subscribers vs not:** "How much of my watch time comes from subscribers?" - **One channel:** "For the Acme Tutorials channel…" when the MCP server reaches more than one. ## What your AI does behind the scenes 1. Lists the channels the MCP server reaches (`youtube_list_channels`). 2. Runs a channel report (`youtube_report`) for the period, split by video for top videos. The same report splits by day, month, country, device, traffic source, playback location, subscribed status or age and gender. Without a period it covers the last 28 days. 3. For recent uploads, lists the channel's videos newest first (`youtube_list_videos`). ## Does it change anything? No. YouTube is read-only in Plugsight: your AI can't upload, edit or delete videos, comments or settings. ## Related articles - [YouTube](/connectors/youtube) - [Monthly marketing report across Ads, Analytics and Search Console](/recipes/monthly-marketing-report) --- # Merchant Center products with problems URL: https://docs.plugsight.app/recipes/merchant-center-problems Check your Google Merchant Center feed for disapproved and limited products, the most common issues, and how your Shopping listings perform. Find the products Google won't show, why, and how many products each issue affects. ## What you'll get - How many products are approved, limited (disapproved in some countries), pending or disapproved. - The most common issues, with how many products each affects, examples and Google's help link. - The disapproved products themselves, with price, availability, link and issues. - Optionally, Shopping performance (free listings and Shopping ads): impressions, clicks, click-through rate, conversions and conversion value by product or by day. ## What you need - [Google Merchant Center](/connectors/google-merchant-center) connected, on the **Pro** or **Agency** plan, once Google approves it (it's being reviewed). ## Ask this ```text Using Plugsight, how healthy is our Google Merchant Center feed? Show how many products are approved, limited, pending and disapproved, the top issues with how many products each affects, and the disapproved products with what to fix on each. ``` ## Variations - **One product:** "Is the blue running shoe approved, and does it have any issues?" - **Limited products:** "List products that are limited, and in which countries." - **Performance:** "Which products got the most Shopping clicks in the last 30 days?" - **Trend:** "Show Shopping clicks and conversions per day for last month." - **Fix the costly ones first:** "Which of the disapproved products had the most Shopping clicks last month?" ## What your AI does behind the scenes 1. Lists the Merchant Center accounts the MCP server reaches (`merchant_center_list_accounts`). 2. Checks feed health (`merchant_center_product_health`): counts by status and the top issues (15 by default). 3. Lists products filtered by status or by text in the title or offer id (`merchant_center_list_products`), up to 500 at a time. 4. For performance, pulls Shopping results by product, by day or in total (`merchant_center_performance`). Without a period it covers the last 28 days. ## Does it change anything? No. Merchant Center is read-only in Plugsight: your AI can't change products, feeds or settings. ## Related articles - [Google Merchant Center](/connectors/google-merchant-center) - [Best-selling products](/recipes/best-selling-products) --- # Monthly marketing report across Ads, Analytics and Search Console URL: https://docs.plugsight.app/recipes/monthly-marketing-report One report for last month across Google Ads, Microsoft Advertising, GA4 and Search Console, compared with the month before, ready to share. Pull every marketing platform into one monthly report, with the comparisons and commentary you'd normally build by hand. ## What you'll get - **Paid search:** cost, clicks, conversions, CPA, conversion value and ROAS per ad account, with the change from the previous month. - **Website:** sessions, conversions, revenue and engagement rate per GA4 property. - **Organic search:** clicks, impressions, click-through rate and average position per Search Console site. - Headline findings across all of them, then the biggest movers by campaign, channel and page. - A plain-language summary you can paste into an email or slide. ## What you need On the **Pro** or **Agency** plan, any of these (the report covers whatever is connected): - [Google Ads](/connectors/google-ads) and [Microsoft Advertising](/connectors/microsoft-advertising) - [Google Analytics 4](/connectors/google-analytics-4) - [Google Search Console](/connectors/google-search-console) ## Ask this ```text Using Plugsight, build my monthly marketing report for last month compared with the month before. Start with an overview of every connected platform and account. Then show Google Ads by campaign, GA4 by channel, and Search Console's top 10 pages by clicks, each with the change. End with five bullet points: what went well, what didn't, and what to do next month. ``` ## Variations - **Against last year:** "…compared with the same month last year." - **One client:** "Only for Bright Dental: their Google Ads, GA4 property and website in Search Console." Name the accounts when the MCP server reaches several clients. - **Add other channels:** "Add YouTube views and watch time, and Merchant Center Shopping clicks." This works once Google approves YouTube and Merchant Center (they're being reviewed). See [YouTube video performance](/recipes/youtube-video-performance) and [Merchant Center products with problems](/recipes/merchant-center-problems). - **Add store sales:** "Add WooCommerce revenue and orders for the same month." See [Store sales this month vs last](/recipes/store-sales-month-vs-month). - **As an email draft:** "Write it as an email to the client and save it as a draft in my work Gmail." ## What your AI does behind the scenes 1. Lists every marketing account the MCP server reaches (`list_marketing_accounts`). 2. Runs the **account overview** (`marketing_deep_dive`): each connected platform and account, this period against the previous period or last year. Platforms that aren't connected are skipped; if one fails, the others still come back with the error noted. 3. Runs a **period comparison** for each breakdown you asked for: campaigns on Google Ads, channels on GA4, pages on Search Console. 4. With other connectors added, uses their own tools, for example the store's sales report. 5. For a draft, saves it in your mailbox (`create_draft`). Search Console's last 2–3 days aren't final, so a report run on the 1st or 2nd of the month may show slightly lower organic numbers for the end of last month. ## Does it change anything? No, apart from an optional email draft, which is saved in your Drafts folder and never sent without your approval. See [Approvals in your AI app](/ai-apps/approvals). ## Related articles - [Weekly Google Ads performance summary](/recipes/weekly-google-ads-summary) - [Did last week's campaign drive store sales?](/recipes/campaign-store-sales) - [How your AI analyses marketing data](/connectors/marketing-data) --- # Did last week's campaign drive store sales? URL: https://docs.plugsight.app/recipes/campaign-store-sales Line up a campaign's dates with daily store revenue from WooCommerce or Magento, ad spend, GA4 revenue and Mailchimp orders to see if sales moved. Check whether a campaign, email or promotion actually showed up in your store's sales, by putting the numbers for the same days side by side. ## What you'll get - Daily store sales (revenue and orders) for the campaign week and the week before. - What the campaign spent and brought in on the same days: ad cost and conversions, or the email's clicks, orders and revenue. - GA4 sessions and revenue for the campaign, if it was tagged. - A comparison of the two weeks, and your AI's view on whether the campaign likely made a difference, with the caveats. ## What you need At least one store and one source of campaign data: - A store: [WooCommerce](/connectors/woocommerce) or [Magento](/connectors/magento) (any plan). - Campaign data, one or more of: [Google Ads](/connectors/google-ads) or [Microsoft Advertising](/connectors/microsoft-advertising), [Google Analytics 4](/connectors/google-analytics-4) (these need **Pro** or **Agency**), or [Mailchimp](/connectors/mailchimp) (any plan). ## Ask this ```text Using Plugsight, our "Winter Sale" Google Ads campaign ran from 9 to 15 November. Show WooCommerce revenue and orders per day for those days and the 7 days before, next to the campaign's daily cost and conversions. Did store sales rise during the campaign, and by how much compared with the extra ad spend? ``` ## Variations - **An email campaign:** "Our 'Black Friday preview' Mailchimp campaign went out on 12 November. Show its clicks, orders and revenue, and WooCommerce sales per day from 12 to 18 November against the week before." - **Using GA4:** "Add GA4 sessions, purchases and revenue for the winter_sale campaign on the same days." - **Magento:** "Use our Magento store instead of WooCommerce." - **Products:** "Which products sold more during the campaign week than the week before?" ## What your AI does behind the scenes 1. Pulls store sales per day for both weeks (`woocommerce_sales_report` or `magento_sales_report`), with the best-selling products. 2. For ads, pulls the campaign's cost and conversions per day (`get_marketing_data` with date and campaign as fields, filtered to the campaign). 3. For GA4, pulls sessions, purchases and revenue for the campaign by day (`get_marketing_data` with campaign and date). 4. For Mailchimp, finds the campaign (`mailchimp_list_campaigns`) and reads its full report (`mailchimp_campaign_report`), which includes orders and revenue when your store is connected to Mailchimp. 5. Lines the days up and compares. > [!NOTE] > This shows whether sales moved at the same time, not proof that the campaign caused it. Other things (seasons, other promotions, stock) can move sales too, and your AI should say so. Magento reports use UTC dates. ## Does it change anything? No. Stores, ad platforms, GA4 and Mailchimp are all read-only in Plugsight. ## Related articles - [Store sales this month vs last](/recipes/store-sales-month-vs-month) - [Mailchimp campaign performance](/recipes/mailchimp-campaign-performance) - [Monthly marketing report across Ads, Analytics and Search Console](/recipes/monthly-marketing-report) --- # Triage today's inbox URL: https://docs.plugsight.app/recipes/triage-inbox Get today's unread email sorted into what needs a reply, what needs reading and what can wait, across all your inboxes, and optionally flag the urgent ones. Start the day with a sorted list instead of a full inbox. ## What you'll get - Today's unread emails across every inbox the MCP server reaches, grouped into: needs a reply, needs reading, and can wait or archive. - One line per email: who it's from, what it's about and what they want. - Deadlines and requests pulled out of the emails. - Optionally, the urgent ones flagged in your mailbox. ## What you need - At least one email account connected, such as [Gmail](/connectors/gmail), [Outlook](/connectors/outlook) or [iCloud Mail](/connectors/icloud-mail). Reading works on every plan. - To flag, label or mark emails: the **Pro** or **Agency** plan. The account's sending switch doesn't matter for this. ## Ask this ```text Using Plugsight, triage my unread email from today across all my inboxes. Group it into "needs a reply", "needs reading" and "can wait", with one line per email saying who it's from and what they want. Pull out any deadlines. Don't change anything yet. ``` Then, if you want: ```text Flag the emails in "needs a reply" and mark the ones in "can wait" as read. ``` ## Variations - **One inbox:** "…in my work Gmail only." - **Since yesterday evening:** "…unread email since 6pm yesterday." - **Only people:** "Leave out newsletters and automatic notifications." - **With context:** "For anything from a customer, read the earlier emails in the conversation first." - **Clean up after:** see [Clean up newsletters (archive and label)](/recipes/clean-up-newsletters). ## What your AI does behind the scenes 1. Lists the accounts the MCP server reaches (`list_accounts`). 2. Searches every inbox for unread emails since today (`search_emails` with unread and a date). It pages through if there are more than 100. 3. Opens the ones it needs to read in full (`get_email`), and the earlier emails in a conversation when useful (`get_thread`). Reading an email doesn't mark it as read. 4. If you ask, flags or marks emails (`organize_emails`, up to 100 at a time). ## Does it change anything? Only if you ask in the follow-up. Flagging and marking emails read can be undone, so they work differently from sending: - They need the **Pro** or **Agency** plan, and stop if email changes are paused on **Permissions**. - For a handful of emails, your AI does it and tells you what changed. For more than 10 emails, or before moving anything to the trash, it tells you what will happen and asks first. See [Archiving, labelling and marking emails](/permissions/how-changes-are-allowed#archiving-labelling-and-marking-emails). ## Related articles - [Draft replies to customer emails](/recipes/draft-customer-replies) - [What your AI can do with email](/connectors/email-tools) --- # Find and summarise invoices URL: https://docs.plugsight.app/recipes/find-invoices Find invoices and receipts in your email for a period, read the PDF attachments, and get one table of suppliers, dates, numbers and totals. Collect every invoice from your inbox into one table, ready for your bookkeeping. ## What you'll get - Every email in the period that looks like an invoice or receipt, across all your inboxes or one. - For each: supplier, invoice number, date, due date, amount, currency and tax, read from the attached PDF, Word or Excel file, or from the email body. - A total per supplier and overall. - Emails your AI couldn't read clearly, listed separately so you can check them. ## What you need - At least one email account connected, such as [Gmail](/connectors/gmail) or [Outlook](/connectors/outlook). Any plan. ## Ask this ```text Using Plugsight, find every invoice and receipt we received by email in October 2026, across all my inboxes. Open the attachments and give me a table with supplier, invoice number, invoice date, due date, amount, tax and currency, then totals per supplier. List anything you couldn't read separately. ``` ## Variations - **One supplier:** "Find every invoice from Northwind this year and total them." - **Unpaid ones:** "Which invoices from last month mention a due date that has passed?" - **Only PDFs:** "Only emails with PDF attachments." - **Forward to your accountant as a draft:** "Draft an email to accounts@example.com forwarding the Northwind invoices." See [Draft replies to customer emails](/recipes/draft-customer-replies) for how drafts work. ## What your AI does behind the scenes 1. Searches your inboxes for the period (`search_emails`), using words such as "invoice" and "receipt", and attachment filters such as attachment type pdf or "has attachment". On Gmail and Outlook it can also use their own search syntax. It pages through until no more results come back. 2. Opens each email (`get_email`) to see its attachments. 3. Reads each attachment as text (`get_attachment`): PDF, Word, Excel, PowerPoint, CSV and other text files. Attachments inside a forwarded email can be read too. 4. Builds the table and totals. If an attachment's text can't be read, your AI lists that email for you to check. ## Does it change anything? No. This recipe only reads. A forward saved as a draft stays in your Drafts folder until you send it. ## Related articles - [What your AI can do with email](/connectors/email-tools) - [Read and analyse a Google Sheet](/recipes/analyse-google-sheet) --- # Draft replies to customer emails URL: https://docs.plugsight.app/recipes/draft-customer-replies Have your AI read customer emails and write reply drafts in your mailbox, in your tone, ready for you to check and send. Let your AI write first drafts of your replies. They wait in your Drafts folder until you send them. ## What you'll get - A reply draft for each customer email you pick, saved in the right mailbox, threaded with the original and quoting it below. - Replies that use the facts from the conversation, and from other sources you name (an order, a ticket, a document). - A list of what each draft says and anything your AI wasn't sure about. ## What you need - At least one email account connected, such as [Gmail](/connectors/gmail) or [Outlook](/connectors/outlook). Drafts work on every plan, with sending off, and on MCP servers set to read and draft only. - Optional, for facts: a store such as [WooCommerce](/connectors/woocommerce), or [Zendesk](/connectors/zendesk), in the same MCP server. ## Ask this ```text Using Plugsight, find unanswered emails from customers in my support@ inbox from the last 3 days. For each one, read the whole conversation and write a reply draft: friendly, short, and answering every question they asked. Save them as drafts and give me a list of what each one says. Don't send anything. ``` ## Variations - **One email:** "Draft a reply to the latest email from Acme about the delayed order." - **With order details:** "Look up their WooCommerce order first and include the order status and items." - **Reply all:** "Draft a reply-all to Sam's thread about the launch date." - **Your tone:** "Match the tone of my last five sent replies." - **Send one:** "Send the draft to Acme." See below: sending needs more than a draft. ## What your AI does behind the scenes 1. Searches the inbox for recent emails you haven't replied to (`search_emails` with "not replied", a date and, if you like, the sender's domain). 2. Reads each conversation (`get_thread`), and any attachments it needs (`get_attachment`). 3. If you asked, looks up facts in other connected accounts, for example an order (`woocommerce_list_orders`, `woocommerce_get_order`) or a ticket (`zendesk_search_tickets`). 4. Saves each reply as a draft (`create_draft`), linked to the original so it stays in the same conversation. ## Does it change anything? It writes drafts in your Drafts folder. Drafts are never sent on their own and don't count toward the [daily email limit](/permissions/daily-email-limit). To have your AI **send** a draft (`send_draft`) or send a reply directly (`send_email`), all of these must be true: - The **Pro** or **Agency** plan. - The account's switch on **Connections** shows **Can send**. - **Allow changes** is ticked on the MCP server. - Email sending isn't paused on **Permissions**. - The account has sends left under its daily limit (20 in a rolling 24 hours by default). - You approve that exact email in the chat. Your AI must show you the account it sends from, To, Cc, Bcc, subject, full text and attachment names first. See [Sending, drafts and the daily email limit](/connectors/email-safety). ## Related articles - [Follow up on emails without a reply](/recipes/follow-up-no-reply) - [Approvals in your AI app](/ai-apps/approvals) --- # Clean up newsletters (archive and label) URL: https://docs.plugsight.app/recipes/clean-up-newsletters Find newsletters and promotional emails in your inbox, label them and archive them in batches, after you've seen the list. Clear newsletters out of your inbox without losing them: label them so you can find them later, then archive. ## What you'll get - A list of the newsletters and promotional senders in your inbox, with how many emails each sent. - After your yes: those emails labelled (for example "Newsletters") and moved out of the inbox to the archive. - A summary of what changed. ## What you need - An email account connected, such as [Gmail](/connectors/gmail) or [Outlook](/connectors/outlook). - The **Pro** or **Agency** plan. Archiving and labelling don't need the account's sending switch or the MCP server's **Allow changes**. - Labels are Gmail labels or Outlook categories. Other mailboxes don't have labels, so your AI moves the emails to a folder instead. ## Ask this ```text Using Plugsight, find newsletters and promotional emails in my Gmail inbox from the last 60 days. List the senders with how many emails each sent, and leave out anything from people or customers. Wait for my yes, then label them "Newsletters" and archive them. ``` ## Variations - **Receipts too:** "Label receipts 'Expenses' and leave them in the inbox." - **Mark read only:** "Mark all of yesterday's notifications as read." - **A folder instead:** "Move them to the Newsletters folder." (For mailboxes without labels.) - **Keep some:** "Keep anything from the Financial Times in the inbox." - **Unsubscribe links:** "Which of these have an unsubscribe link?" Your AI can find the link; you click it yourself. ## What your AI does behind the scenes 1. Searches the inbox for the period (`search_emails`), and looks at senders and subjects. To be sure an email is a newsletter, it can read its headers, such as List-Unsubscribe (`get_email` with headers). 2. Shows you the list and waits for your yes. 3. Labels and archives the emails in batches of up to 100 (`organize_emails` with a label to add and "archive" as the place to move to). New labels are created. ## Does it change anything? Yes: it labels and moves emails. These changes can be undone (the emails are in the archive, not deleted), so they don't need your sending switch, but: - They need the **Pro** or **Agency** plan. - They stop if email changes are paused on **Permissions**. - Before changing more than 10 emails, or moving anything to the trash, your AI tells you what will happen and asks first. - They don't count toward the daily email limit. See [How changes are allowed](/permissions/how-changes-are-allowed#archiving-labelling-and-marking-emails). ## Related articles - [Triage today's inbox](/recipes/triage-inbox) - [What your AI can do with email](/connectors/email-tools) --- # Follow up on emails without a reply URL: https://docs.plugsight.app/recipes/follow-up-no-reply Find emails you sent that never got an answer, see what you were waiting for, and get polite follow-up drafts ready to send. Find the conversations where you're still waiting on someone, and nudge them. ## What you'll get - Emails you sent in the period where the other person hasn't replied since. - For each: who, when you sent it, and what you were asking for. - Optionally, a short follow-up draft for each, in the same conversation. ## What you need - At least one email account connected, such as [Gmail](/connectors/gmail) or [Outlook](/connectors/outlook). Any plan. ## Ask this ```text Using Plugsight, look at the emails I sent in the last 14 days from my work Gmail and find the ones where the other person hasn't replied since. List who, when, and what I was waiting for. Then draft a short, polite follow-up for each one that's older than 3 days. Don't send anything. ``` ## Variations - **Only external people:** "Leave out anyone at our own domain, acme.com." - **Only questions:** "Only include emails where I asked a question or asked for something." - **Meeting requests:** "Draft follow-ups to everyone who hasn't replied to my meeting request." - **All inboxes:** "…across all my inboxes." ## What your AI does behind the scenes 1. Searches your sent folder for the period (`search_emails` with folder "sent"). 2. Reads each conversation (`get_thread`) to see whether anyone replied after your last email. 3. Saves a follow-up as a reply draft in the same conversation (`create_draft`). For a long list, your AI may need several steps; ask it to carry on if it stops part-way. ## Does it change anything? Only drafts, saved in your Drafts folder. Nothing is sent. Sending a follow-up needs your **Can send** switch, the Pro or Agency plan and your yes for each email: see [Draft replies to customer emails](/recipes/draft-customer-replies#does-it-change-anything). ## Related articles - [Draft replies to customer emails](/recipes/draft-customer-replies) - [Sending, drafts and the daily email limit](/connectors/email-safety) --- # Prepare for tomorrow's meetings URL: https://docs.plugsight.app/recipes/prepare-for-meetings Get a briefing for each of tomorrow's meetings: who's coming, what you last discussed by email, open questions and what to bring. Walk into each meeting knowing who's there and where things stand. ## What you'll get - Tomorrow's meetings in order, with time, place or video link, and guests. - For each guest you've emailed: their details and a short summary of your recent emails. - Open questions, promises and documents mentioned in those emails. - A short "what to prepare" list per meeting. ## What you need - A calendar connected: [Google Calendar](/connectors/google-calendar), [Outlook Calendar](/connectors/outlook-calendar) or [iCloud Calendar](/connectors/icloud-calendar). Any plan. - For email history: an email account such as [Gmail](/connectors/gmail) or [Outlook](/connectors/outlook) in the same MCP server. - Optional: contacts such as [Google Contacts](/connectors/google-contacts), for phone numbers and companies. ## Ask this ```text Using Plugsight, brief me on tomorrow's meetings. For each one, list the time, guests and link, then summarise my emails with those guests from the last 30 days: what we discussed, any open questions or promises, and what I should prepare. Keep each meeting to a few lines. ``` ## Variations - **The whole week:** "Brief me on every external meeting this week." - **One meeting:** "Prepare me for my 2pm with Acme." - **Last time you met:** "When did I last meet Priya, and what was it about?" - **Free time too:** "Also tell me where I have gaps of 30 minutes or more tomorrow." - **With meeting notes:** "Include the action items from our last Google Meet with them." This works once Google approves Google Meet (it's being reviewed). See [Summarise a Google Meet](/recipes/summarise-google-meet). ## What your AI does behind the scenes 1. Lists tomorrow's events across your visible calendars (`calendar_list_events`). Repeating events are listed one by one. 2. For each guest, searches your email for recent messages to or from them (`search_emails`), and reads the relevant conversations (`get_thread`). 3. If contacts are connected, looks up each guest (`contacts_search`, `contacts_get`). 4. For gaps, checks free time (`calendar_find_free_time`). Calendars you've hidden in Plugsight are never read. ## Does it change anything? No. This recipe only reads. ## Related articles - [Find a free slot and book a meeting](/recipes/book-a-meeting) - [What your AI can do with calendars](/connectors/calendar-tools) --- # Find a free slot and book a meeting URL: https://docs.plugsight.app/recipes/book-a-meeting Ask your AI to find a free time in your calendar and book a meeting with guests, after you've checked the details. Outlook and iCloud calendars. Find a time that works and get the invitation out without leaving the chat. ## What you'll get - Free slots of the length you need, in the days and hours you choose. - After your yes: the event booked in your calendar, with guests invited by email. - The booked event's details back in the chat. ## What you need - [Outlook Calendar](/connectors/outlook-calendar) or [iCloud Calendar](/connectors/icloud-calendar). [Google Calendar](/connectors/google-calendar) can show free time but can't book yet. - To book, all of these: - The **Pro** or **Agency** plan. - The calendar connection's switch on **Connections** set to **Can book & change**, with **Ready** shown under it. - **Allow changes** ticked on the MCP server. - Calendar changes not paused on **Permissions**. Finding free time works on every plan, with any of the three calendars. ## Ask this ```text Using Plugsight, find three 45-minute slots next week when I'm free between 10am and 4pm. Then, once I pick one, book a call called "Acme quarterly review" with sam@example.com and priya@example.com, and show me the details before you book. ``` ## Variations - **Book straight away:** "Find a free hour on Wednesday afternoon and book a call with sam@example.com." Your AI still shows you the details and waits for your yes. - **With a location or agenda:** "Add the office address as the location and this agenda in the description: …" - **Without invitations:** "Book it in my calendar without emailing the guests." Outlook always emails invitations to guests; iCloud can skip them. - **Move a meeting:** "Move Friday's team review to Monday at the same time and let everyone know." - **Cancel:** "Cancel my 4pm on Thursday." ## What your AI does behind the scenes 1. Checks your busy times across your visible calendars and finds gaps of the length you asked for (`calendar_find_free_time`). 2. Shows you the calendar, title, date, start and end time with time zone, location and every guest, and waits for your yes. 3. Books the event (`calendar_create_event`) on your main calendar, or the one you name. To move or cancel, it uses `calendar_update_event` or `calendar_cancel_event`, also after your yes. ## Does it change anything? Yes: it adds an event to your calendar and, by default, emails the guests. Plugsight refuses a booking your AI hasn't marked as approved by you. Each booking is recorded in **Activity**. Things to know: - Google Meet links can only be added on Google calendars, which can't be booked yet. For Outlook or iCloud, put a video link in the description. - Calendars you can only view can't have events added. - For a repeating event, Outlook changes or cancels only that occurrence; iCloud changes or cancels the whole series. See [What your AI can do with calendars](/connectors/calendar-tools#what-changes-need) and [Approvals in your AI app](/ai-apps/approvals). ## Related articles - [Prepare for tomorrow's meetings](/recipes/prepare-for-meetings) - [How changes are allowed](/permissions/how-changes-are-allowed) --- # Summarise a Google Meet URL: https://docs.plugsight.app/recipes/summarise-google-meet Turn a Google Meet transcript into a summary with decisions and action items, and draft the follow-up email to everyone who joined. Get the decisions and to-dos from a meeting without re-reading the whole transcript. ## What you'll get - A short summary of the meeting. - Decisions made, and action items with who owns each and any dates mentioned. - Open questions left for next time. - Optionally, a follow-up email draft to the people who joined. ## What you need - [Google Meet](/connectors/google-meet) connected. Any plan, once Google approves it (it's being reviewed). - Transcription turned on in the meeting. Only meetings with a transcript can be summarised. - The meeting must be one **you organised**. Meetings you were only invited to aren't listed. - For the follow-up draft: an email account such as [Gmail](/connectors/gmail) in the same MCP server. ## Ask this ```text Using Plugsight, summarise yesterday's Google Meet with Acme. Give me a five-line summary, the decisions, and the action items with who owns each and any dates. Then draft a follow-up email to everyone who joined with the decisions and action items. Don't send it. ``` ## Variations - **Which meetings:** "Which meetings did I run this week, who joined each, and which have transcripts?" - **One question:** "What did Priya say about the launch date in Tuesday's call?" - **A longer period:** "List my meetings from last month." - **Compare meetings:** "What changed between our last two weekly reviews?" ## What your AI does behind the scenes 1. Lists the meetings you organised in the period (`meet_list_meetings`): start, length, who joined, and whether a transcript exists. Without a period it covers the last 7 days. 2. Reads the transcript of the meeting you mean (`meet_get_transcript`), as "Name: words" lines. Very long transcripts are cut at 80,000 characters unless your AI asks for more. 3. Writes the summary and action items. 4. For the follow-up, saves a draft (`create_draft`) addressed to the people who joined. If the meeting had no transcript, your AI tells you to turn on transcription next time (in Meet: **Activities → Transcripts**). ## Does it change anything? Only the optional draft, saved in your Drafts folder. Google Meet is read-only in Plugsight: your AI never starts, joins or records meetings. Sending the draft needs your **Can send** switch, the Pro or Agency plan and your yes: see [Approvals in your AI app](/ai-apps/approvals). ## Related articles - [Google Meet](/connectors/google-meet) - [Prepare for tomorrow's meetings](/recipes/prepare-for-meetings) --- # Look up a contact's details URL: https://docs.plugsight.app/recipes/look-up-a-contact Find someone's email, phone number, company and address from your contacts, plus when you last emailed them, by name or company. Find someone's details without opening your address book. ## What you'll get - The people who match a name, email, phone number or company. - For the one you mean: emails, phone numbers, organisation, addresses, notes, birthday and links. - Optionally, your last emails with them. ## What you need - A contacts connection: [Google Contacts](/connectors/google-contacts), [Outlook Contacts](/connectors/outlook-contacts) or [iCloud Contacts](/connectors/icloud-contacts). Any plan. - For email history: an email account in the same MCP server. With Google Contacts, searches also cover "other contacts" (people you've emailed but never saved), if you allowed it when connecting. ## Ask this ```text Using Plugsight, what's the mobile number and email for Priya at Northwind? Also tell me when I last emailed her and what it was about. ``` ## Variations - **Everyone at a company:** "Who do I know at Acme?" - **By domain:** "Find everyone in my contacts with an @example.gov.uk address." - **Then write:** "Find my accountant's email and draft them a note about this year's receipts." - **Recent contacts:** "List the 20 contacts I changed most recently." (Google Contacts.) ## What your AI does behind the scenes 1. Searches your contacts by name, email, phone or company (`contacts_search`), up to 60 results. 2. Reads the full record of the right person (`contacts_get`). 3. For email history, searches your inboxes for messages from or to their address (`search_emails`). 4. For a draft, saves one in your mailbox (`create_draft`). ## Does it change anything? No. Contacts are read-only in Plugsight: your AI never adds, changes or deletes contacts. A draft, if you ask for one, waits in your Drafts folder. ## Related articles - [Prepare for tomorrow's meetings](/recipes/prepare-for-meetings) - [Google Contacts](/connectors/google-contacts) --- # This week's Zendesk themes URL: https://docs.plugsight.app/recipes/zendesk-weekly-themes Group this week's Zendesk tickets into themes, with how many tickets each has, example tickets and what's driving them. Find out what customers are contacting you about this week, and what's new or growing. ## What you'll get - The main themes in tickets created this week, with a ticket count for each and links to examples. - Themes that are new or bigger than last week. - How many tickets were created and solved, and how many are still unsolved or urgent. - Suggestions: a help article to write, a macro to add, or a product issue to raise. ## What you need - [Zendesk](/connectors/zendesk) connected with an agent or admin login. Any plan for reading. ## Ask this ```text Using Plugsight, look at all Zendesk tickets created from Monday 9 to Sunday 15 November. Group them into the top themes, with a count and two example ticket links for each. Compare with the week before: which themes are new or growing? Also give me the created, solved and unsolved counts. ``` ## Variations - **One group or tag:** "…only tickets in the Billing group" or "…tagged refund." - **Top five reasons:** "What are the top five reasons for tickets this week?" - **One customer:** "Summarise everything Acme has raised in the last 90 days." - **Urgent first:** "Which urgent tickets have had no reply for more than a day?" - **Two helpdesks:** "Compare refund requests across our UK and US Zendesk." ## What your AI does behind the scenes 1. Searches for tickets created in the period (`zendesk_search_tickets` with a Zendesk search such as `created>=2026-11-09 created<=2026-11-15`), up to 100 at a time, paging through for more. 2. Reads the tickets it needs in detail (`zendesk_get_ticket`), including the conversation. 3. Gets the counts for each week (`zendesk_ticket_stats`): new, open, pending, on hold, unsolved and urgent right now, and created and solved in the period. It runs once per week to compare. 4. Groups the tickets into themes from their subjects, tags and conversations. Your AI sees what your Zendesk role can see, and nothing more. ## Does it change anything? No. This recipe only reads. ## Related articles - [Support volume this week vs last](/recipes/zendesk-ticket-counts) - [Zendesk](/connectors/zendesk) --- # Draft a ticket reply and add an internal note URL: https://docs.plugsight.app/recipes/zendesk-reply-and-note Have your AI read a Zendesk ticket, write the public reply and an internal note for your team, then post both after your approval. Let your AI read the whole ticket, write the reply to the customer and a note for your colleagues, and post them when you say yes. ## What you'll get - A summary of the ticket and what the customer needs. - A public reply written for the customer, shown to you first. - An internal note for agents only, for example a summary and next steps. - After your yes: both posted on the ticket, and the status changed if you asked. ## What you need - [Zendesk](/connectors/zendesk) connected with an agent or admin login. - To post on tickets, all of these: - The **Pro** or **Agency** plan. - The Zendesk connection's switch on **Connections** set to **Can reply & update**. - **Allow changes** ticked on the MCP server. - Helpdesk changes not paused on **Permissions**. - Your Zendesk role allowed to do it in Zendesk. Without these, your AI can still read the ticket and write the text in the chat for you to paste. ## Ask this ```text Using Plugsight, read Zendesk ticket 4821 in full. Write a public reply to the customer that answers their question, and an internal note for the team summarising the issue and next steps. Show me both and wait for my yes before posting. After posting the reply, set the ticket to pending. ``` ## Variations - **Note only:** "Add an internal note on ticket 4821 summarising the conversation so far." - **With order details:** "Check their WooCommerce order before you write the reply." Needs a store in the same MCP server. - **Solve it:** "Post the reply and set the ticket to solved." - **Tags and priority:** "Also add the tag 'shipping-delay' and set priority to high." - **New ticket:** "Open a ticket for jane@example.com about her broken order, as an internal note." See [Zendesk](/connectors/zendesk). ## What your AI does behind the scenes 1. Reads the ticket with the requester, assignee, custom fields and every reply and note (`zendesk_get_ticket`). 2. Writes the reply and the note, and shows you both with the ticket number. 3. After your yes, posts each one (`zendesk_add_comment`): the public reply, which Zendesk emails to the customer, and the internal note, which only agents see. A status change (open, pending, on hold or solved) can go with either. 4. For tags, priority, type or assignee, updates the ticket (`zendesk_update_ticket`), also after your yes. ## Does it change anything? Yes, after your approval. Plugsight refuses a reply, note or update your AI hasn't marked as approved by you, and every change is recorded in **Activity**. A public reply is emailed to the customer by Zendesk, so read it carefully before you say yes. See [Approvals in your AI app](/ai-apps/approvals) and [How changes are allowed](/permissions/how-changes-are-allowed). ## Related articles - [Apply a macro to similar tickets](/recipes/zendesk-apply-macro) - [Zendesk](/connectors/zendesk) --- # Apply a macro to similar tickets URL: https://docs.plugsight.app/recipes/zendesk-apply-macro Find Zendesk tickets about the same issue, preview what a macro will change on them, and apply it to each one after your approval. When many tickets are about the same thing, find them all and apply the right macro, checking what it does first. ## What you'll get - The open tickets that match the issue you describe. - The macro that fits, and a preview of exactly what it will change: reply text, status, tags and other fields. - After your yes: the macro applied to each ticket, with a list of what changed. ## What you need - [Zendesk](/connectors/zendesk) connected with an agent or admin login, and a macro that already exists in Zendesk. - To apply macros, all of these: - The **Pro** or **Agency** plan. - The Zendesk connection's switch set to **Can reply & update**. - **Allow changes** ticked on the MCP server. - Helpdesk changes not paused on **Permissions**. ## Ask this ```text Using Plugsight, find open Zendesk tickets from the last 7 days about the delivery delay to Scotland. List them. Then find our macro for shipping delays, preview what it would change on the first ticket, and wait for my yes before applying it to each of them. ``` ## Variations - **By tag:** "Apply the 'Refund approved' macro to open tickets tagged refund-ok." - **Find a macro:** "Which macros do we have about passwords?" - **One ticket:** "Apply the 'Close and thank' macro to ticket 4821." - **Check first:** "Preview the macro on every ticket before you apply any." ## What your AI does behind the scenes 1. Searches for matching tickets (`zendesk_search_tickets`), with words, tags or dates. 2. Finds the macro by words in its title (`zendesk_list_macros`). 3. Previews the macro on a ticket (`zendesk_apply_macro` with preview on), which changes nothing, and shows you the result. 4. After your yes, applies it to each ticket (`zendesk_apply_macro` with your approval). A macro can work out differently on different tickets, for example if it inserts the customer's name. Ask for a preview on each ticket if that matters. ## Does it change anything? Yes, after your approval. If the macro includes a public reply, Zendesk emails it to the customer. Plugsight refuses to apply a macro your AI hasn't marked as approved, and each change is recorded in **Activity**. See [Approvals in your AI app](/ai-apps/approvals). ## Related articles - [Draft a ticket reply and add an internal note](/recipes/zendesk-reply-and-note) - [This week's Zendesk themes](/recipes/zendesk-weekly-themes) --- # Support volume this week vs last URL: https://docs.plugsight.app/recipes/zendesk-ticket-counts Count Zendesk tickets created and solved this week and last week, plus how many are open, pending, on hold and urgent right now. Get the support numbers for a weekly update in one question. ## What you'll get - Tickets created and solved in each week, and the change. - Right now: new, open, pending, on hold, unsolved and urgent unsolved tickets. - The same numbers for a group, tag or agent, if you ask. - A short trend over several weeks, if you ask. ## What you need - [Zendesk](/connectors/zendesk) connected with an agent or admin login. Any plan. ## Ask this ```text Using Plugsight, how many Zendesk tickets were created and solved from Monday 9 to Sunday 15 November, compared with the week before? Also show how many are new, open, pending, on hold and urgent right now. ``` ## Variations - **One group:** "…for the Billing group only." - **One tag:** "…for tickets tagged refund." - **Your own:** "…for tickets assigned to me." - **A trend:** "Show created and solved tickets for each of the last 8 weeks." ## What your AI does behind the scenes 1. Counts tickets for each period (`zendesk_ticket_stats`), narrowed by a Zendesk search such as `group:Billing`, `tags:refund` or `assignee:me` if you asked. It runs once per week to compare or build a trend. 2. Lays the counts out side by side. "Right now" counts are the same for every period you ask about: they describe the tickets as they are today. ## Does it change anything? No. This recipe only reads. ## Related articles - [This week's Zendesk themes](/recipes/zendesk-weekly-themes) - [Zendesk](/connectors/zendesk) --- # Store sales this month vs last URL: https://docs.plugsight.app/recipes/store-sales-month-vs-month Compare this month's WooCommerce or Magento sales with last month's: revenue, orders, average order, refunds, discounts and best sellers. See how the shop is doing against last month, on the same number of days. ## What you'll get - For each period: revenue, orders, items sold, average order value, discounts, shipping, tax and refunds. - The change between the two, in amount and percent. - A day-by-day view, to spot the days that made the difference. - The best-selling products in each period. ## What you need - [WooCommerce](/connectors/woocommerce) or [Magento](/connectors/magento) connected. Any plan. ## Ask this ```text Using Plugsight, compare my store's sales from 1 to 17 November with 1 to 17 October: revenue, orders, average order, discounts and refunds, with the change in percent. Show the five best-selling products in each period and point out the days that made the biggest difference. ``` Comparing the same days of each month keeps it fair while this month is still running. ## Variations - **Full months:** "Compare last month with the month before." - **Against last year:** "Compare this November so far with the same days last year." - **Several stores:** "Do this for both the UK and US stores." Name each store when you have more than one. - **With ad spend:** "Add Google Ads spend for the same days and work out revenue per unit of ad spend." Needs Google Ads on the Pro or Agency plan. ## What your AI does behind the scenes 1. Runs the store's sales report for each period (`woocommerce_sales_report` or `magento_sales_report`), with the best-selling products (10 by default, up to 50). 2. Compares the totals and the day-by-day figures. On WooCommerce, the report gives gross and net sales; long periods are broken down by month instead of by day. On Magento, sales are added up from paid orders only: unpaid, on-hold and cancelled orders are listed separately. On a very busy store the report can stop early and says how far it got; ask for a shorter period then. Dates are UTC. ## Does it change anything? No. Stores are read-only in Plugsight. ## Related articles - [Best-selling products](/recipes/best-selling-products) - [Did last week's campaign drive store sales?](/recipes/campaign-store-sales) --- # Best-selling products URL: https://docs.plugsight.app/recipes/best-selling-products Find your best-selling products for any period in WooCommerce or Magento, with units, revenue and stock left, plus all-time best sellers. Find what's selling, and whether you have enough of it. ## What you'll get - The best-selling products in the period, with units sold and revenue. - How much stock each has left, so you can spot best sellers running low. - On WooCommerce, the all-time best sellers too. - A comparison with the previous period, if you ask. ## What you need - [WooCommerce](/connectors/woocommerce) or [Magento](/connectors/magento) connected. Any plan. ## Ask this ```text Using Plugsight, what were my 20 best-selling products in the last 30 days, by units and by revenue? For each, show how much stock is left and flag any that could run out soon. ``` ## Variations - **This week:** "Which products sold best this week?" - **All time:** "What are my best sellers of all time?" (WooCommerce.) - **Rising products:** "Which products sold more this month than last month?" - **With Shopping data:** "Which of these get the most Google Shopping clicks?" See [Merchant Center products with problems](/recipes/merchant-center-problems). ## What your AI does behind the scenes 1. Runs the sales report for the period with up to 50 best-selling products (`woocommerce_sales_report` or `magento_sales_report`). 2. Looks up each product's stock (`woocommerce_search_products` by name or SKU, or `magento_search_products`). 3. For all-time best sellers on WooCommerce, lists products sorted by popularity (`woocommerce_search_products`). ## Does it change anything? No. Stores are read-only in Plugsight. ## Related articles - [Products running low on stock](/recipes/low-stock-products) - [Store sales this month vs last](/recipes/store-sales-month-vs-month) --- # Customers who haven't reordered URL: https://docs.plugsight.app/recipes/customers-not-reordered Find customers who bought once and never came back, or who haven't ordered in months, from your WooCommerce or Magento store. Build a list of customers to win back: people who bought before but haven't returned. ## What you'll get - Customers who placed exactly one order, or none since a date you choose. - For each: name, email, when they joined, how many orders and how much they spent, and their last order date when your AI checks it. - Your AI's suggestions for a win-back message. ## What you need - [WooCommerce](/connectors/woocommerce) or [Magento](/connectors/magento) connected. Any plan. ## Ask this For WooCommerce: ```text Using Plugsight, find WooCommerce customers who have placed only one order. For the 30 who spent the most, show their email, total spent and the date of that order. Then suggest a short win-back email. ``` For Magento: ```text Using Plugsight, list my Magento orders from January to June 2026 and find the customers who ordered then but haven't ordered since 1 July. Show their email, number of orders and last order date. ``` ## Variations - **Big spenders gone quiet:** "Which of my top 50 customers by total spent haven't ordered in the last 90 days?" - **Draft the message:** "Write a win-back email I can send from Mailchimp." Mailchimp is read-only in Plugsight, so you send it there yourself. - **Check one person:** "Show every order from ann@example.com." ## What your AI does behind the scenes On WooCommerce: 1. Lists registered customers with how many orders each placed and how much they spent (`woocommerce_search_customers`), 100 at a time, paging through. 2. Picks those with one order (or the ones you asked for) and checks their orders and dates (`woocommerce_list_orders` with a search for their email). On Magento: 1. Lists orders in the periods you named (`magento_list_orders`), 100 at a time, paging through, and groups them by customer email. 2. Compares the two periods to find who stopped ordering. > [!NOTE] > WooCommerce's customer list covers registered customers only. Guest checkouts appear in orders, not in the customer list. For a big store this takes many pages: name a period, or ask for the top customers by spend. ## Does it change anything? No. Stores are read-only in Plugsight. ## Related articles - [Best-selling products](/recipes/best-selling-products) - [Mailchimp audience growth](/recipes/mailchimp-audience-growth) --- # Products running low on stock URL: https://docs.plugsight.app/recipes/low-stock-products List the products that are out of stock, on backorder or below a stock level you choose, with how fast they're selling. Find products you're about to run out of, before customers notice. ## What you'll get - Products out of stock or on backorder (WooCommerce), or at or below a stock level you choose (Magento). - For each: name, SKU, price and stock left. - How many of each sold recently, so you can see which to reorder first. ## What you need - [WooCommerce](/connectors/woocommerce) or [Magento](/connectors/magento) connected. Any plan. ## Ask this For WooCommerce: ```text Using Plugsight, which WooCommerce products are out of stock or on backorder? Then check how many of each sold in the last 30 days, and list the ones I should reorder first. ``` For Magento: ```text Using Plugsight, list Magento products with 5 or fewer in stock, and how many of each sold in the last 30 days. Which should I reorder first? ``` ## Variations - **Best sellers only:** "Which of my top 20 sellers this month have fewer than 10 left?" - **One product:** "How many of SKU TSHIRT-BLUE-M do we have left?" - **Ads still running:** "Are we still advertising any out-of-stock products in Google Ads?" Needs Google Ads on the Pro or Agency plan. ## What your AI does behind the scenes 1. On WooCommerce, lists products by stock status, out of stock or on backorder (`woocommerce_search_products`). On Magento, lists products at or below the stock level you gave (`magento_search_products`). 2. Runs the sales report for the recent period (`woocommerce_sales_report` or `magento_sales_report`) to see how fast each sells. 3. For ads, pulls Google Ads product rows (`get_marketing_data` with product title and cost) and matches them by name. ## Does it change anything? No. Stores are read-only in Plugsight: your AI can't change stock, prices or products. ## Related articles - [Best-selling products](/recipes/best-selling-products) - [WooCommerce](/connectors/woocommerce) --- # Mailchimp campaign performance URL: https://docs.plugsight.app/recipes/mailchimp-campaign-performance Rank your sent Mailchimp campaigns by opens, clicks and revenue, compare them with your audience and industry, and see which links got clicked. Find which emails worked, and what the best ones had in common. ## What you'll get - Your sent campaigns in the period, with subject, audience, emails sent, open rate, click rate, and orders and revenue when your store is connected to Mailchimp. - The best and worst by the measure you choose. - For any one campaign: opens, clicks, bounces, unsubscribes, spam complaints, how it compares with your audience's average and your industry, and the most-clicked links. - What the best subject lines and content had in common. ## What you need - [Mailchimp](/connectors/mailchimp) connected. Any plan. ## Ask this ```text Using Plugsight, rank my Mailchimp campaigns sent from July to September 2026 by click rate. Show subject, emails sent, open rate, click rate and revenue for each. For the best and worst, show how they compare with our audience average and the industry, and their most-clicked links. What did the best subject lines have in common? ``` ## Variations - **Last campaign:** "How did last week's newsletter do, and which links got the most clicks?" - **Revenue:** "Which campaigns this year brought the most orders and revenue?" - **One audience:** "…only campaigns sent to the Customers audience." - **Drafts and scheduled:** "Which campaigns are scheduled to go out?" - **A subscriber:** "Is jane@example.com still subscribed, and when did she join?" ## What your AI does behind the scenes 1. Lists your audiences if it needs their ids (`mailchimp_list_audiences`). 2. Lists the campaigns sent in the period (`mailchimp_list_campaigns`), up to 100 at a time, paging through for more. 3. Reads the full report for the campaigns you want in detail (`mailchimp_campaign_report`), with up to 50 most-clicked links (10 by default). 4. For one person, looks them up across audiences (`mailchimp_find_subscriber`). Orders and revenue only appear when your online store is connected to Mailchimp. ## Does it change anything? No. Mailchimp is read-only in Plugsight: your AI can't create, edit or send campaigns. ## Related articles - [Mailchimp audience growth](/recipes/mailchimp-audience-growth) - [Did last week's campaign drive store sales?](/recipes/campaign-store-sales) - [Mailchimp](/connectors/mailchimp) --- # Mailchimp audience growth URL: https://docs.plugsight.app/recipes/mailchimp-audience-growth See month by month how your Mailchimp audience grew: new subscribers, imports, unsubscribes, cleaned addresses and the total at month end. Find out whether your list is growing, and what's making it shrink. ## What you'll get - For each month: new subscribers (opt-ins and imports), unsubscribes, cleaned addresses and the total at the end of the month. - Net growth per month and over the whole period. - The months with unusual drops or jumps, and what may explain them. - Your audiences side by side, if you have several. ## What you need - [Mailchimp](/connectors/mailchimp) connected. Any plan. ## Ask this ```text Using Plugsight, is my main Mailchimp audience growing? Show new subscribers, imports, unsubscribes, cleaned addresses and the month-end total for each of the last 12 months, and point out any month with an unusual drop. ``` ## Variations - **Longer view:** "…for the last 3 years." Up to 60 months. - **All audiences:** "Compare growth across all my audiences this year." - **Link drops to campaigns:** "In the months with the most unsubscribes, which campaigns went out?" - **Overview:** "List my audiences with subscribers, unsubscribes and average open and click rates." ## What your AI does behind the scenes 1. Lists your audiences with their totals and average rates (`mailchimp_list_audiences`). 2. Reads month-by-month growth for each audience you ask about (`mailchimp_audience_growth`), 12 months unless you ask for more. 3. To link drops to sends, lists the campaigns sent in those months (`mailchimp_list_campaigns`). ## Does it change anything? No. Mailchimp is read-only in Plugsight. ## Related articles - [Mailchimp campaign performance](/recipes/mailchimp-campaign-performance) - [Mailchimp](/connectors/mailchimp) --- # Read and analyse a Google Sheet URL: https://docs.plugsight.app/recipes/analyse-google-sheet Give your AI a Google Sheets link and ask questions about the data: totals, trends, outliers and comparisons, without copying anything out. Ask questions about a spreadsheet in plain words, by pasting its link. ## What you'll get - The spreadsheet's tabs and their sizes, so you can pick the right one. - Answers worked out from the values: totals, averages, groupings, trends and outliers. - Tables you can paste back into the sheet or into a report. ## What you need - [Google Sheets](/connectors/google-sheets) connected, with a Google account that can open the spreadsheet. Any plan, once Google approves it (it's being reviewed). - The spreadsheet's link from your browser's address bar. Your AI can't browse or search your Drive for spreadsheets. ## Ask this ```text Using Plugsight, here's our budget sheet: https://docs.google.com/spreadsheets/d/… First tell me what tabs it has. Then, from the "2026" tab, total the Actual column by category and month, and list the categories that are more than 10% over budget this quarter. ``` ## Variations - **One range:** "Read Sales!A1:F500 and total the Amount column by month." - **Filter rows:** "Read the Leads tab and list everyone from London." - **No header row:** "The first row isn't a header; the data starts at A1." - **Compare with live data:** "Compare the monthly targets in this sheet with actual Google Ads spend." Needs Google Ads on the Pro or Agency plan. - **A sheet sent by email:** "Add up the totals on the spreadsheet attached to the supplier's last email." That reads the email attachment instead: see [Find and summarise invoices](/recipes/find-invoices). ## What your AI does behind the scenes 1. Reads the spreadsheet's details (`sheets_get_info`): title, tabs with their size, and named ranges. 2. Reads the values from a tab, a range such as "Sales!A1:F200", or a named range (`sheets_read`), as they're shown in Google Sheets. The first row becomes the column names unless you say otherwise. Without a range, the first tab is read. 3. Works out the answer from the values. Up to 5,000 rows are read at a time (500 by default). For bigger sheets, ask for a range, or let your AI read it in parts. ## Does it change anything? No. Google Sheets is read-only in Plugsight: your AI can't edit cells, tabs or files. ## Related articles - [Google Sheets](/connectors/google-sheets) - [Summarise a Google Doc](/recipes/summarise-google-doc) --- # Summarise a Google Doc URL: https://docs.plugsight.app/recipes/summarise-google-doc Paste a Google Docs link and get a summary, the action items, or answers to specific questions, with headings, lists and tables taken into account. Get the gist of a long document, or pull specific facts out of it, by pasting its link. ## What you'll get - A summary at the length you ask for. - Action items, decisions, dates or figures from the document. - Answers to specific questions, with the section they came from. - Comparisons between documents, if you give several links. ## What you need - [Google Docs](/connectors/google-docs) connected, with a Google account that can open the document. Any plan, once Google approves it (it's being reviewed). - The document's link from your browser's address bar. Your AI can't browse or search your Drive. ## Ask this ```text Using Plugsight, summarise this proposal in five bullet points: https://docs.google.com/document/d/… Then list every date, price and commitment it mentions, and any open questions. ``` ## Variations - **Meeting notes:** "What are the action items in our meeting notes doc, and who owns each?" - **Compare two:** "Compare the pricing sections of these two documents: … and …" - **Use it in a reply:** "Draft a reply to Sarah's email using the figures in this doc." Needs an email account in the same MCP server; the reply is saved as a draft. - **A long document:** "Read all of it, even if it's long." ## What your AI does behind the scenes 1. Reads the document as text (`docs_read`), keeping headings, bullet lists and tables. Documents with several tabs are read in full. 2. Documents longer than 60,000 characters are cut, and your AI is told; it can ask for up to 500,000. 3. For a reply, reads the email (`search_emails`, `get_thread`) and saves a draft (`create_draft`). ## Does it change anything? No. Google Docs is read-only in Plugsight: your AI can't edit, comment on or delete documents. A reply draft, if you ask for one, waits in your Drafts folder. ## Related articles - [Google Docs](/connectors/google-docs) - [Read and analyse a Google Sheet](/recipes/analyse-google-sheet) --- # Form responses summary URL: https://docs.plugsight.app/recipes/form-responses-summary Total the answers to a Google Form, read the written answers for common themes, and list respondents who need a follow-up. Turn a form's responses into numbers and themes: survey results, event sign-ups, leads or bookings. ## What you'll get - For each choice, scale and rating question: how many chose each option. - For written answers: the common themes, with example quotes. - Responses since a date you choose, newest first, with the respondent's email when the form collects it. - A list of respondents to follow up, if you ask. ## What you need - [Google Forms](/connectors/google-forms) connected, with a Google account that can edit the form. Any plan, once Google approves it (it's being reviewed). - The form's **edit link** (the address when you're editing it in Google Forms). The link people use to fill it in doesn't work. ## Ask this ```text Using Plugsight, summarise the responses to our customer survey since 1 October 2026: https://docs.google.com/forms/d/…/edit. Give me the totals for each multiple-choice and rating question, the average rating, and the three most common themes in the written comments, with a quote for each. ``` ## Variations - **Leads:** "List everyone who asked for a quote since Monday, with their email and what they need." - **Sign-ups:** "How many people chose each session in the event sign-up form?" - **The questions:** "What questions does this form ask, and what are the options?" - **Follow up:** "Draft a thank-you email to everyone who gave a rating of 2 or less." Needs an email account in the same MCP server; the emails are saved as drafts. ## What your AI does behind the scenes 1. Reads the form's questions and options (`forms_get`). 2. Totals the answers per question (`forms_summary`), optionally only since a date. 3. Reads the responses as a table (`forms_responses`), newest first, up to 5,000 at a time (200 by default), for written answers and respondents' emails. 4. For follow-ups, saves drafts in your mailbox (`create_draft`). ## Does it change anything? No. Google Forms is read-only in Plugsight: your AI can't edit forms or responses. Follow-up drafts wait in your Drafts folder until you send them. ## Related articles - [Google Forms](/connectors/google-forms) - [Read and analyse a Google Sheet](/recipes/analyse-google-sheet) --- # Guides and best practices URL: https://docs.plugsight.app/guides Step-by-step walkthroughs for real jobs, from client reports to support tickets, plus habits that keep your AI safe and accurate. The other sections of these docs explain each part of Plugsight on its own. The guides here put the parts together: each one starts with the set-up you need and ends with a finished result, such as a client report, an answered ticket or a working dashboard. You don't need to read them in order. Pick the job you want to do. ## Workflow guides ### Agencies and marketing - [Set up Plugsight for a new client](/guides/new-client-setup): connect the client's accounts, give them their own MCP server and check what your AI can see. - [Build a monthly client marketing report](/guides/monthly-client-report): pull this month against last month across Google Ads, GA4 and Search Console, then draft the email. - [Run a Google Ads account audit](/guides/google-ads-audit): wasted spend, quality score, impression share and search terms, in one sitting. - [Run an SEO health check](/guides/seo-health-check): Search Console opportunities, indexing, sitemaps and page speed. - [Check your conversion tracking](/guides/tracking-check): audit Tag Manager, confirm GA4 key events and watch a test conversion arrive. ### Email, meetings and support - [Daily inbox triage routine](/guides/daily-inbox-triage): a ten-minute morning routine for one inbox or several. - [Prepare for meetings and follow up](/guides/meeting-prep-and-follow-up): brief yourself before a call, then turn the transcript into a follow-up. - [Weekly support ticket review](/guides/weekly-support-review): volumes, trends and the tickets that need attention. - [Handle a support ticket end to end](/guides/support-ticket-with-approval): from reading the ticket to an approved reply and status change. ### Stores - [Review your store's sales](/guides/store-sales-review): sales, best sellers, stock and customers for WooCommerce or Magento, next to your ad spend. ### Your account and set-up - [Onboard a teammate](/guides/onboard-a-teammate): bring a teammate into your workspace, or give someone outside the team a read-only server. - [Move from Free to Pro without losing anything](/guides/free-to-pro): what stays, what unlocks and what to switch on afterwards. - [Connect several Google accounts](/guides/several-google-accounts): work and personal logins, client logins and how each counts. - [Build a dashboard with Claude Code and the developer API](/guides/developer-dashboard): explore your data in Claude Code, then build a page that shows it. - [Switch AI apps](/guides/switch-ai-apps): move between Claude and ChatGPT, or use both, with the same accounts. ## Best practices - [Give your AI the least access it needs](/guides/least-privilege): read-only servers, **Selected accounts** and hidden items. - [One MCP server per client or purpose](/guides/one-server-per-purpose): how to split servers and name them. - [When to use Pause](/guides/when-to-pause): the moments that call for the emergency stop, and when the account switch is better. - [Keep app passwords and API keys safe](/guides/keep-credentials-safe): where they belong, and what to do if one leaks. - [Review Activity regularly](/guides/review-activity): a short weekly check of what your AI did. - [Write better questions](/guides/better-questions): date ranges, naming accounts and asking for tables. - [Get accurate numbers from marketing data](/guides/accurate-marketing-numbers): date ranges, UTC, currencies and fair comparisons. - [Stay within your limits](/guides/stay-within-limits): the daily email limit, plan limits and provider limits. > [!TIP] > New to Plugsight? Start with the [quick start](/get-started/quick-start), then come back here. --- # Set up Plugsight for a new client URL: https://docs.plugsight.app/guides/new-client-setup An agency walkthrough - connect a new client's accounts, give them their own MCP server, check what your AI can see and run a first report. This guide takes you from "we've signed a new client" to your AI answering questions about that client's accounts, and only that client's accounts. It takes about 15 minutes. ## What you need - A **Pro** or **Agency** plan. Free includes only 1 marketing connection and 25 marketing tool calls a month, to try them. Agencies with many clients usually need Agency, for its 50 connections and unlimited MCP servers. See [Plans](/get-started/plans). - A Google login (or Microsoft login, for Microsoft Advertising) that can open the client's accounts. This is usually your own agency login after the client has given it access, or a login the client created for you. - An AI app that supports remote MCP servers, such as Claude or ChatGPT. See [Connect AI apps](/ai-apps). ## Step 1: decide how the client's data reaches Plugsight An MCP server picks **whole connections**, not individual ad accounts or sites inside them. That matters for agencies: | How you reach the client | What happens | | --- | --- | | Through your manager (MCC) account, or an agency Google login that sees many clients | You already have one connection that reaches every client. A new client appears in it automatically. You can't give this client a server that reaches only their Google Ads account through that connection. | | A separate login that only sees this client | Connecting it creates a new connection that reaches only this client. You can give the client a server of their own. | > [!IMPORTANT] > Hiding an ad account, site or property with **Show sites & accounts** hides it from **every** MCP server, not one. It's for keeping things out of all answers (a test site, a closed client), not for splitting clients between servers. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). Connecting the same Google login to the same service a second time doesn't add a new connection: it replaces the sign-in of the one you already have. ## Step 2: connect the client's accounts For each service the client uses: 1. In the Plugsight app, open **Connections** and click **Add connection**. 2. Choose the service, for example **Google Ads**, **Google Analytics 4** or **Google Search Console**. 3. Read **What happens next** and click **Continue to Google**. 4. Choose the Google account that can see the client's data. 5. Tick the permission box Google shows, and continue. 6. Back on **Connections**, check the message, for example "Connected you@example.com: 12 Google Ads accounts." Each Google service is its own connection, even from the same Google login. A client with Google Ads, GA4 and Search Console on a new login uses three connections. If you hit your plan's limit, see [Stay within your limits](/guides/stay-within-limits). The full steps and fixes for each service are on its connector page: [Google Ads](/connectors/google-ads), [Google Analytics 4](/connectors/google-analytics-4), [Google Search Console](/connectors/google-search-console), [Microsoft Advertising](/connectors/microsoft-advertising), [Google Tag Manager](/connectors/google-tag-manager) and [Google Merchant Center](/connectors/google-merchant-center). If you're using an existing agency connection (your MCC, say) and the client's account doesn't show yet, click **Refresh list** next to that connection. ## Step 3: check which items are visible 1. On **Connections**, click **Show sites & accounts** next to each new connection. 2. Check every site, property and ad account you want your AI to use shows **Visible**. 3. Switch anything you never want in answers to **Hidden**, for example a staging site. ## Step 4: create the client's MCP server 1. Open **MCP servers** and click **Create MCP server**. 2. **Name**: the client's name, for example "Acme (client)". Your AI app shows this name, and so does **Activity**. 3. **Account access**: choose **Selected accounts** and tick only this client's connections. 4. **Allow changes**: untick it if this server only needs to read, which is the case for marketing work. Marketing connectors are read-only anyway. 5. Click **Create server**. If the client is only reachable through a shared agency connection (Step 1), you have two choices: keep using your main server and name the client in every question, or ask for a separate login that only reaches this client. See [One MCP server per client or purpose](/guides/one-server-per-purpose). ## Step 5: add the server to your AI app 1. On the new server's page, under **Connect an AI app**, open the steps for your AI app. 2. Copy the **Server URL** and add it to your AI app as a connector. 3. When the Plugsight window opens, check the server under **MCP server** is the client's, then click **Allow access**. Full steps for each app: [Claude](/ai-apps/claude), [ChatGPT](/ai-apps/chatgpt), [Claude Code](/ai-apps/claude-code) and [others](/ai-apps). If this is the first marketing connection on the account, [refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. ## Step 6: check what your AI can see In a new chat with the client's server switched on, ask: - "List my Plugsight accounts." - "List my marketing accounts." The answer should name only the client's connections and the client's sites, properties and ad accounts. If something is missing, see [Your AI can't see an account](/troubleshooting/ai-cant-see-account). ## Step 7: run a first report A good first question for a new client: - "Give me an overview of all marketing accounts on this server for the last 30 days compared with the 30 days before." This runs the **account overview** deep dive: spend, conversions, CPA, ROAS, organic clicks, sessions and revenue for each platform. Use it as your baseline. Next, try the [Google Ads audit](/guides/google-ads-audit) and the [SEO health check](/guides/seo-health-check). ## When the client leaves 1. Open the client's server and use **Delete server** under **Danger zone**. Its link stops working in every AI app. 2. On **Connections**, click **Remove** next to any connection used only for this client. 3. If the client was reached through a shared agency connection, hide their accounts with **Show sites & accounts** so they stop appearing in answers. ## Related articles - [Use several MCP servers](/mcp-servers/multiple-servers) - [Several accounts per service](/ai-apps/multiple-accounts) - [Build a monthly client marketing report](/guides/monthly-client-report) --- # Build a monthly client marketing report URL: https://docs.plugsight.app/guides/monthly-client-report Pull last month against the month before across Google Ads, GA4 and Search Console, check the numbers, then draft the email to your client. This guide builds a monthly marketing report for one client in your AI chat: headline numbers, what changed, why, and what to do next. You finish with a draft email in your mailbox, ready to check and send. It takes about 20 minutes the first time and less once you reuse your questions. ## What you need - A **Pro** or **Agency** plan (Free's 25 marketing tool calls a month won't cover a report for several clients). - The client's marketing accounts connected and in an MCP server: see [Set up Plugsight for a new client](/guides/new-client-setup). - Optional: an email account connected, if you want your AI to save the report as a draft. ## Step 1: open a chat with the right server 1. Start a new chat in your AI app. 2. Switch on the client's MCP server (in Claude: **+** → **Connectors**; in ChatGPT: **+** next to the message box). 3. Ask "List my marketing accounts" and check the client's accounts are there. If you use one server for several clients, name the client's accounts in every question below, for example "for Acme's Google Ads account". ## Step 2: get the headline numbers Ask for last month as a whole calendar month: - "Give me an account overview for last month compared with the month before, for every platform." This runs the **account overview** deep dive: spend, conversions, CPA, ROAS, organic clicks, sessions and revenue, for this period and the previous one. > [!NOTE] > "Last month" means the 1st to the last day of the previous calendar month, worked out in UTC. Run the report after the month has ended, and, for Search Console, a few days later: its data becomes final 2–3 days after each date. See [Get accurate numbers from marketing data](/guides/accurate-marketing-numbers). ## Step 3: find out what changed Ask for a period comparison on the platforms that matter to this client: - "Compare cost, conversions and CPA by campaign in Google Ads, last month against the month before. Show the biggest gains and drops." - "Compare sessions, key events and revenue by channel in GA4, last month against the month before." - "Compare organic clicks and impressions by page in Search Console, last month against the month before. Which pages lost the most clicks?" For a year-on-year view, ask for "the same month last year" instead of "the month before". ## Step 4: add the why Pick the questions that explain the changes: - "Which search terms cost money last month without converting?" (the **wasted spend** deep dive) - "Which campaigns lost impression share to budget last month?" - "Which queries are close to page one in Search Console?" (the **SEO opportunities** deep dive) ## Step 5: check the numbers Before anything goes to a client: 1. Ask "Were any data notes returned for these reports?" Plugsight adds notes when Google holds data back (hidden low-volume search terms, GA4 thresholds or sampling, Search Console data that isn't final yet). 2. If the client has ad accounts in more than one currency, ask for results "split by account" so money isn't added across currencies. 3. Spot-check one or two totals against the Google Ads or GA4 interface for the same dates. ## Step 6: turn it into a report Ask your AI to write it up: - "Write this as a client report with these sections: headline numbers (a table, last month vs the month before, with % change), what went well, what didn't, and three recommendations for this month. Keep it under 400 words." Ask for changes until you're happy with it. ## Step 7: save it as a draft email If an email account is in the same MCP server: - "Save this report as a draft email to jane@acme.com from my work inbox, subject 'Acme marketing report: October'." Your AI saves it in the account's **Drafts** folder. Nothing is sent. Drafts work on every plan, even when the account's switch is off or the server is read-only. Open the draft in your mail app, check it and send it yourself. Or, if your plan includes changes and the account's switch is on **Can send**, ask your AI to send it: it shows you the final email and waits for your yes. See [Approvals in the chat](/permissions/approvals). ## Make it faster next month - Keep your questions from this month in a note and paste them in next month. - Ask the same questions in the same order, so reports stay comparable. - Use exact dates if you need a period that isn't a calendar month, for example "from 2026-10-01 to 2026-10-31". ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Write better questions](/guides/better-questions) - [Run a Google Ads account audit](/guides/google-ads-audit) --- # Run a Google Ads account audit URL: https://docs.plugsight.app/guides/google-ads-audit Audit a Google Ads account with your AI - wasted spend, quality score, impression share, search term winners and paid vs organic overlap. This guide walks through a full Google Ads audit in one chat, using Plugsight's ready-made deep dives. You finish with a list of findings and a prioritised action plan. The same steps work for Microsoft Advertising: add "in Microsoft Advertising" to each question. Plugsight only reads Google Ads. Your AI can recommend changes, but you make them in Google Ads yourself. ## What you need - A **Pro** or **Agency** plan. - A [Google Ads](/connectors/google-ads) connection that reaches the account, in the MCP server you'll use. - Optional: a [Google Search Console](/connectors/google-search-console) connection for the same site, for the paid vs organic step. - Optional: a [Google Tag Manager](/connectors/google-tag-manager) connection, to check tracking. ## Step 1: pick the account and period 1. Start a new chat with the right MCP server switched on. 2. Ask "List my Google Ads accounts" and note the exact name of the one you're auditing. 3. Choose a period long enough to be fair. The deep dives default to the last 30 days; for low-volume accounts, ask for the last 90 days. Name the account in every question, for example "in the Acme Shop Google Ads account". ## Step 2: check tracking first An audit built on broken conversion tracking gives wrong answers. Ask: - "Which conversion actions does this account have, and how many conversions did each record in the last 30 days?" If conversions look wrong (zero, or far too many), check tracking before going on. See [Check your conversion tracking](/guides/tracking-check). ## Step 3: the account overview - "Give me an account overview for this account, last 30 days against the previous 30." You get spend, conversions, CPA and ROAS against the previous period. Write down the CPA: the next steps compare against it. ## Step 4: wasted spend - "Run a wasted spend report for the last 90 days. Which search terms and keywords cost money without converting, and what share of the budget is that?" The **wasted spend** deep dive lists search terms and keywords with at least 10 in spend and no conversions, and suggests negative-keyword candidates. Ask for a lower threshold on small accounts, for example "at least 5 in spend". > [!NOTE] > Google hides low-volume search terms for privacy. Their cost is in campaign totals but not in the search-term rows, so search-term waste is always a little understated. Your AI is told when this applies. ## Step 5: scale opportunities - "Which campaigns and keywords convert at or below our average CPA but lose impression share to budget or rank?" This is the **scale opportunities** deep dive: the places where more budget or better bids are most likely to pay back. ## Step 6: search term winners - "Which converting search terms aren't keywords yet?" The **search term winners** deep dive. Each one is a candidate to add as a keyword. ## Step 7: quality score - "Run a quality score audit. How much spend sits on keywords with a quality score of 5 or less, and is expected CTR, ad relevance or the landing page the main problem?" ## Step 8: paid vs organic (needs Search Console) - "Run a paid vs organic report for this account and the shop's Search Console site." It shows where you pay for clicks on queries you already rank top 3 for, paid winners with weak SEO, and organic queries worth a paid test. ## Step 9: anything else For questions the deep dives don't cover, your AI can run a read-only Google Ads Query Language (GAQL) query. Ask in plain English, for example: - "Which ads in this account are disapproved or limited?" - "List every campaign with its bidding strategy and daily budget." Only SELECT queries are allowed, so nothing can be changed this way. ## Step 10: the action plan - "Summarise the audit as a table: finding, evidence (with numbers), estimated monthly impact, and the change to make in Google Ads. Order it by impact." Save it as an email draft if you want to share it ("save this as a draft to me"). ## Tips - **Audit one account at a time.** For an MCC with many clients, you can rank them first: "Across all client accounts, which ones had the highest share of wasted spend last month?" - **Mind currencies.** Accounts in different currencies are added as-is. Ask for results per account. - **Removed campaigns** are included, because they spent money in the period. Ask your AI to leave them out if you don't want them. ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Get accurate numbers from marketing data](/guides/accurate-marketing-numbers) - [Build a monthly client marketing report](/guides/monthly-client-report) --- # Run an SEO health check URL: https://docs.plugsight.app/guides/seo-health-check Check a site's organic search health with your AI - traffic trends, quick-win queries, indexing, sitemaps and page speed - and get a fix list. This guide runs a complete SEO health check on one site: how organic traffic is trending, which queries are close to paying off, whether Google can index the important pages, and how fast they load. You finish with a prioritised fix list. Plugsight only reads. It can't change your site, submit sitemaps or request indexing; your AI tells you what to change. ## What you need - A **Pro** or **Agency** plan, for Search Console. - A [Google Search Console](/connectors/google-search-console) connection that reaches the site, in your MCP server. - Optional: a [Google Analytics 4](/connectors/google-analytics-4) connection for the same site, to see what organic visitors do. - Page speed checks need nothing: [PageSpeed Insights](/connectors/pagespeed-insights) works on every plan and every server. ## Step 1: pick the site 1. Start a new chat with the right MCP server switched on. 2. Ask "List my Search Console sites." 3. Name the site in every question, for example "for https://www.example.com/" or "for the example.com domain property". ## Step 2: the traffic trend - "Compare organic clicks, impressions, CTR and average position for this site, last 28 days against the 28 days before." - "Which pages lost the most clicks compared with the previous period?" > [!NOTE] > Search Console data becomes final about 2–3 days after each date, and Plugsight includes the fresh, not-yet-final days by default. If the latest days look low, ask again for a range that ends 3 days ago. See [Get accurate numbers from marketing data](/guides/accurate-marketing-numbers). ## Step 3: quick wins - "Run an SEO opportunities report for this site." The **SEO opportunities** deep dive returns: - Queries close to page one (worth a content refresh or more internal links). - Page-one results with low CTR for their position (worth a better title and description). - Pages losing clicks. It only looks at queries with at least 100 impressions, unless you ask for a different threshold. ## Step 4: indexing For the pages that matter most (home page, top products or services, pages that lost clicks): - "Is https://www.example.com/pricing indexed? If not, why?" This uses URL inspection: whether the page is indexed, when Google last crawled it, the canonical Google chose, mobile usability and rich results. Ask about one page at a time. Then check the sitemaps: - "Which sitemaps are submitted for this site? How many URLs are submitted and indexed, and are there errors or warnings?" ## Step 5: page speed - "Check the speed of https://www.example.com/ on mobile. Does it pass Core Web Vitals, and what are the three biggest fixes?" - "Check the same page on desktop." Each check takes 10 to 40 seconds. Real-user Core Web Vitals need enough Chrome visits; for a quiet page your AI is told there isn't enough data, and the lab scores still work. ## Step 6: what organic visitors do (needs GA4) - "In GA4, how many sessions, key events and how much revenue came from organic search last month compared with the month before?" - "Which landing pages from organic search have the lowest engagement rate?" ## Step 7: the fix list - "Summarise the health check as a table: issue, page or query, evidence, and the fix. Put indexing problems first, then speed, then content opportunities." ## Run it regularly A monthly check catches problems early. Ask the same questions each time, with the same date ranges, so you can compare. A shorter version for busy months: Steps 2, 3 and the sitemap question in Step 4. ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Run a Google Ads account audit](/guides/google-ads-audit): includes the paid vs organic report. - [Write better questions](/guides/better-questions) --- # Check your conversion tracking URL: https://docs.plugsight.app/guides/tracking-check Audit Google Tag Manager, confirm which GA4 events count as conversions, and watch a test visit arrive in realtime, with your AI. Every marketing report depends on tracking that works. This guide checks it from end to end: the tags in Tag Manager, the key events GA4 counts, the conversions Google Ads records, and a live test. Run it when you take on a new site, after a site change, or when conversions suddenly drop. Plugsight only reads. Your AI finds problems and tells you what to fix; you change Tag Manager, GA4 or Google Ads yourself. ## What you need - A **Pro** or **Agency** plan. - A [Google Analytics 4](/connectors/google-analytics-4) connection that reaches the property. - Optional: a [Google Tag Manager](/connectors/google-tag-manager) connection. Google is still reviewing its permission, so it may not appear in your **Connector catalog** yet. Skip Step 1 if you can't connect it. - Optional: a [Google Ads](/connectors/google-ads) connection, for Step 4. ## Step 1: audit the Tag Manager container 1. Ask "List my Tag Manager containers" and note the GTM id (GTM-…) of the site's container. 2. Ask "Audit container GTM-XXXXXXX and tell me what to fix first." The audit checks the live (published) version for: - tags with no firing trigger, which never run - Universal Analytics tags, which collect nothing since Google retired UA - paused tags - possible duplicates that can double-count - triggers and variables nothing uses - Custom HTML tags, to check they're still needed It also lists changes waiting unpublished in workspaces. A conversion tag fixed in a workspace but never published still isn't live. Follow-up questions: - "Which GA4 measurement id does the GA4 config tag send to?" Check it matches the GA4 property you report on. - "Are any of our conversion tags firing twice?" ## Step 2: check what GA4 counts as a conversion - "Which events does this GA4 property count as key events, and how many of each happened in the last 7 days?" Look for key events with zero counts (tracking broken, or the event was renamed) and for events that shouldn't be key events at all (such as page views). ## Step 3: check the funnel - "Build a funnel from viewing a product page to adding to cart to purchase for the last 30 days. Where do users drop off? Split it by device." A funnel has 2 to 10 steps, each an event or a page visit. A step where almost everyone drops off, on one device only, often points to a tracking problem rather than a real one. ## Step 4: compare with Google Ads - "List the conversion actions in this Google Ads account with conversions recorded in the last 30 days." - "Compare Google Ads conversions last week with GA4 key events from Google Ads traffic for the same days." The two won't match exactly (they count differently), but a large or sudden gap is worth checking. ## Step 5: a live test 1. Ask: "How many people are on the site right now, by page?" This reads GA4 activity from the last 30 minutes. 2. Visit the site yourself and complete a test action, for example a form submission. 3. A minute later, ask: "Did a generate_lead event (or your event name) happen in the last 30 minutes?" ## Step 6: write it up - "Summarise the tracking check as a table: problem, where (GTM, GA4 or Google Ads), evidence, and the fix. Highest impact first." ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Run a Google Ads account audit](/guides/google-ads-audit) - [Get accurate numbers from marketing data](/guides/accurate-marketing-numbers) --- # Daily inbox triage routine URL: https://docs.plugsight.app/guides/daily-inbox-triage A ten-minute morning routine with your AI - summarise new mail, find what needs a reply, draft answers and tidy up, in one inbox or several. This routine gets you from a full inbox to a short list of what needs you, with replies drafted, in about ten minutes. It works with any email account you've connected: Gmail, Outlook, iCloud, Yahoo or any other mailbox, and across several at once. ## What you need - At least one [email account](/connectors/email-tools) connected and in your MCP server. - **Any plan** for reading, summarising and drafts. - **Pro or Agency** for the tidy-up step (archiving, labelling and marking as read) and for sending from the chat. ## One-time set-up 1. Decide which inboxes the routine covers. If you have a work and a personal inbox, both can be in the same MCP server; you'll name the one you mean. 2. Leave each email account's switch on **Drafts only** for now. Drafting is all this routine needs. You can turn on **Can send** later if you want your AI to send after your approval. See [How changes are allowed](/permissions/how-changes-are-allowed). 3. Write your routine down as a note you can paste. The questions below are a starting point. ## The routine ### 1. Summarise what's new - "Summarise my unread emails from the last 24 hours in my work inbox. Group them as: needs a reply from me, for information, and newsletters or notifications. Show it as a table with sender, subject and one line on what it's about." Your AI searches live and doesn't mark anything as read by reading it. ### 2. Find what's waiting on you - "Which emails from the last 7 days that I haven't replied to ask me a question or for a decision?" - "Is anything from my manager, or from clients, still unanswered from this week?" ### 3. Read what matters in full For anything important, ask for the whole conversation: - "Read the full thread with Northwind about the delivery date and tell me what they're asking for." - "What does the PDF attached to Sarah's last email say about payment terms?" ### 4. Draft the replies - "Draft a reply to Northwind saying we can deliver on the 14th, and ask them to confirm the address." - "Draft short replies to the other two emails that need me. Keep them under 80 words." Drafts land in the account's **Drafts** folder, as replies in the same conversation. Nothing is sent. Open them in your mail app, edit if needed, and send. If the account's switch is on **Can send** (Pro or Agency) and you'd rather send from the chat, ask your AI to send a draft. It shows you the final email, with recipients, subject and body, and waits for your yes. See [Approvals in the chat](/permissions/approvals). ### 5. Tidy up (Pro and Agency) - "Mark the newsletters from today as read and archive them." - "Label the Northwind emails 'Clients'." These don't need the account's switch, and they don't count toward the daily email limit. Before moving emails to the trash, or changing more than 10 emails at once, your AI tells you what will happen and asks first. Pausing email changes on **Permissions** stops them too. ## Several inboxes Ask across all of them at once, or one by name: - "What arrived overnight in any of my inboxes that needs a reply today?" - "In my personal Gmail, anything from the school this week?" Each result says which account it came from. If your AI picks the wrong inbox, use the short name shown under the account on **Connections**. See [Several accounts per service](/ai-apps/multiple-accounts). ## Search tips - Your AI can search by sender, subject, date range, unread or flagged, has attachments and attachment type, and folder. - On Gmail it also understands Gmail search syntax, such as `from:amazon newer_than:7d`. On Outlook, Outlook search syntax. - Results come up to 100 at a time; ask for more if you need them. ## Related articles - [What your AI can do with email](/connectors/email-tools) - [Sending, drafts and the daily email limit](/connectors/email-safety) - [Write better questions](/guides/better-questions) --- # Weekly support ticket review URL: https://docs.plugsight.app/guides/weekly-support-review Review a week of Zendesk tickets with your AI - volumes against last week, top reasons, stuck and urgent tickets - and share a summary. This guide is a weekly review of your Zendesk helpdesk: how many tickets came in and were solved, what customers contacted you about, and which tickets need attention. It only reads, so it works on every plan and with the Zendesk connection's switch on **Read-only**. It takes about 15 minutes. ## What you need - A [Zendesk](/connectors/zendesk) connection in your MCP server. Any plan. - A Zendesk login with the agent or admin role. Your AI sees only what that login can see in Zendesk. - Optional: an email account in the same server, to save the summary as a draft. ## Step 1: the numbers Use exact dates so this week and last week line up. For example, for the week of Monday 9 to Sunday 15 November: - "Give me Zendesk ticket counts for 2026-11-09 to 2026-11-15, and for 2026-11-02 to 2026-11-08. Show a table with created, solved, and the change." Ticket counts also show how many tickets are new, open, pending, on hold, unsolved and urgent **right now**, whatever dates you ask for. To narrow the counts, add a Zendesk search, for example: - "…only for tickets tagged refund." - "…only for the Billing group." ## Step 2: what customers contacted you about - "Read the tickets created last week and group them by reason. Show the top five reasons with the number of tickets and one example ticket number each." - "Which reasons grew the most compared with the week before?" For large weeks, your AI searches up to 100 tickets at a time and may page through more. Narrowing by tag or group gives more reliable groupings than asking about everything. ## Step 3: tickets that need attention - "Which urgent tickets have had no reply for more than a day?" - "Which open tickets haven't been updated for more than 5 days?" - "Which customers opened more than two tickets last week, and what about?" Ask for each ticket's number, so you can open it in Zendesk. ## Step 4: macros and repeat questions - "Which macros do we have about refunds?" - "Which questions came up three or more times last week that no macro answers?" The second answer is a good list of macros or help articles to write. ## Step 5: share the summary - "Write a weekly support summary: a table of created and solved against last week, the top five reasons, three tickets that need attention, and one suggestion. Under 300 words." - "Save it as a draft email to support-team@example.com from my work inbox." The draft lands in your **Drafts** folder. Nothing is sent. ## Going further To act on what you found, for example adding an internal note to a stuck ticket, follow [Handle a support ticket end to end](/guides/support-ticket-with-approval). Changes need the Pro or Agency plan and the Zendesk switch on **Can reply & update**. ## Related articles - [Zendesk](/connectors/zendesk) - [Write better questions](/guides/better-questions) - [Review Activity regularly](/guides/review-activity) --- # Handle a support ticket end to end URL: https://docs.plugsight.app/guides/support-ticket-with-approval Let your AI read a Zendesk ticket and the customer's history, draft a reply, and post it and update the ticket only after your approval. This guide handles one Zendesk ticket from start to finish in your AI chat: read it, check the customer's history, write the reply, and post it with a status change. Every change waits for your yes. You finish with the ticket answered and a record of it on **Activity**. ## What you need - A **Pro** or **Agency** plan. Replies and ticket updates are changes, which aren't on Free. - A [Zendesk](/connectors/zendesk) connection, signed in with an agent or admin login. Changes appear in Zendesk as made by you. ## One-time set-up: allow changes 1. On **Connections**, click the Zendesk connection's switch so it says **Can reply & update**. 2. On **MCP servers**, open the server your AI app uses. If its badge says **Read & draft only**, click **Edit configuration**, tick **Allow changes** and save. 3. On **Permissions**, check nothing is paused: neither **Pause everything** nor the **Helpdesk** row. 4. Back on **Connections**, check the line under the Zendesk switch says **Ready**. If it names something else, follow [Switch states under each account](/permissions/switch-states). The full list of checks is in [How changes are allowed](/permissions/how-changes-are-allowed). > [!TIP] > Want to try this without any risk of a reply reaching a customer? Ask only for internal notes, which customers never see, until you're comfortable. ## Step 1: read the ticket - "Read Zendesk ticket 4821 and summarise it: who it's from, what they want, what's been said so far, and what's still open." Your AI reads the whole conversation, public replies and internal notes, oldest first. It can also open attachments and pasted screenshots. ## Step 2: check the customer's history - "What else has this customer raised in the last 90 days? Anything still open?" - "Find the customer's other tickets about refunds." ## Step 3: check for a macro - "Is there a macro for this kind of request?" If there is, your AI can apply it in Step 5. Before applying a macro, it previews exactly what the macro will change (reply text, status, tags and other fields) and shows you. ## Step 4: write the reply - "Draft a public reply to ticket 4821: apologise for the delay, confirm the refund of the second item, and say it takes 5 working days. Friendly, under 120 words. Don't post it yet." Ask for changes until you're happy with the text. Nothing is posted while you're editing. ## Step 5: post it and update the ticket - "Post that reply and set the ticket to pending." Your AI shows you the ticket and the exact text, and the status change, then waits. Read it, then say yes. Only then is the reply posted. A public reply is emailed to the requester by Zendesk. Or, with a macro: - "Apply the 'Refund approved' macro to ticket 4821." Your AI shows the preview, then applies it after your yes. Other changes your AI can make the same way, each after your yes: - **Internal note**: "Add an internal note to 4821: refund approved by Sam, ref R-2231." - **Update**: status, priority, type, assignee, and adding or removing tags. "Tag 4821 'refund' and assign it to me." - **New ticket**: "Open a ticket for jane@acme.com about the missing invoice." Its first message is an internal note unless you ask for it to go to the customer. ## Step 6: check it worked 1. Open the ticket in Zendesk: the reply and changes are there, made by you. 2. In Plugsight, open **Activity** and filter by **AI apps**. Each change is listed with its result. ## If the change is refused Your AI passes on Plugsight's reason. The common ones: | Message | Fix | | --- | --- | | Changes are off for "…". Allow them under Connections first. | Turn the Zendesk switch to **Can reply & update**. | | The "…" MCP is read-only. Allow changes on the MCP server first (MCP servers page). | Tick **Allow changes** on the server. | | Helpdesk replies and updates are paused (Permissions page). | Click **Resume** next to **Helpdesk** on **Permissions**. | | Zendesk refused this action for that agent (…). | Your Zendesk role doesn't allow it. Ask a Zendesk admin. | Every message is explained in [Your AI can't send or change anything](/troubleshooting/ai-cant-send-or-change). ## Related articles - [Approvals in the chat](/permissions/approvals) - [Weekly support ticket review](/guides/weekly-support-review) - [When to use Pause](/guides/when-to-pause) --- # Review your store's sales URL: https://docs.plugsight.app/guides/store-sales-review A weekly or monthly store review with your AI - sales against the last period, best sellers, low stock, stuck orders and top customers. This guide reviews how your online store is doing: sales against the previous period, what sold, what's running out, which orders need attention, and who your best customers are. With Google Ads or GA4 connected too, you can put ad spend and traffic next to revenue. Plugsight only reads your store. It can't change orders, products, prices or stock. ## What you need - A [WooCommerce](/connectors/woocommerce), [Magento / Adobe Commerce](/connectors/magento) or [Shopify](/connectors/shopify) connection in your MCP server. Stores work on **any plan**. - Optional, on **Pro** or **Agency**: [Google Ads](/connectors/google-ads), [Google Analytics 4](/connectors/google-analytics-4) or [Google Merchant Center](/connectors/google-merchant-center) (once Google approves it), for Step 6. If you have more than one store, name the store in every question. ## Step 1: sales against the last period - "How did the shop do last month compared with the month before? Show a table with sales, orders, average order, refunds and discounts, and the % change." The sales report gives gross and net sales (WooCommerce) or revenue (Magento), orders, items sold, average order, tax, shipping, refunds and discounts, with a day-by-day breakdown. > [!NOTE] > Magento sales reports use UTC dates and count only paid orders (cancelled, unpaid and on-hold orders are listed separately). On very busy stores a report can stop early; your AI is then told how far it got: ask for a shorter period, such as one week at a time. ## Step 2: best sellers - "What were the 20 best-selling products last month, with quantity sold?" Sales reports list up to 50 best sellers (10 unless you ask for more). ## Step 3: stock - WooCommerce: "Which products are out of stock or on backorder?" - Magento: "List products with 5 or fewer in stock." Then put the two together: - "Which of last month's 20 best sellers are low on stock?" ## Step 4: orders that need attention - "Which orders are on hold or still processing from more than 3 days ago?" - "Find order 1042 and tell me what was bought, how it was paid and where it's shipping." Order lists come up to 100 at a time, newest first. ## Step 5: customers - "Who are my ten biggest customers by total spent?" (WooCommerce) - "Show every order from ann@example.com this year." WooCommerce's customer search covers registered customers; guest checkouts appear in orders only. ## Step 6: marketing next to sales (Pro and Agency) With marketing connectors in the same MCP server: - "Compare Google Ads spend last month with WooCommerce revenue for the same days, by week." - "In GA4, which channels brought the most revenue last month?" - "Which Merchant Center products are disapproved, and are any of them best sellers?" Store and ad platform figures are counted differently (for example, refunds, tax and conversion windows), so expect them to differ a little. ## Step 7: the summary - "Write a one-page store review: a table of the headline numbers against the last period, best sellers, stock risks, orders needing attention, and three actions for next month." ## Make it a routine Run the same questions at the same point each week or month (for example every Monday for the previous Monday to Sunday) with exact dates, so periods line up. See [Write better questions](/guides/better-questions). ## Related articles - [WooCommerce](/connectors/woocommerce) - [Magento / Adobe Commerce](/connectors/magento) - [Shopify](/connectors/shopify) - [Get accurate numbers from marketing data](/guides/accurate-marketing-numbers) --- # Prepare for meetings and follow up URL: https://docs.plugsight.app/guides/meeting-prep-and-follow-up Brief yourself before a meeting from your calendar, email and contacts, then turn the Meet transcript into notes, a follow-up email and a booking. This guide covers both ends of a meeting. Before it, your AI pulls together who's coming, what you last discussed and what's still open. After it, your AI turns the transcript into decisions and action items, drafts the follow-up email and, if you want, books the next meeting. ## What you need | For | Connect | Plan | | --- | --- | --- | | Your schedule and free time | A calendar: [Google Calendar](/connectors/google-calendar), [Outlook Calendar](/connectors/outlook-calendar) or [iCloud Calendar](/connectors/icloud-calendar) | Any | | Past conversations | An [email account](/connectors/email-tools) | Any | | Who people are | [Google Contacts](/connectors/google-contacts), [Outlook Contacts](/connectors/outlook-contacts) or [iCloud Contacts](/connectors/icloud-contacts) (optional) | Any | | Transcripts | [Google Meet](/connectors/google-meet) (optional) | Any | | Booking from the chat | Outlook or iCloud Calendar, with its switch on **Can book & change** | Pro or Agency | Put them all in the MCP server you use. Google Meet is still waiting for Google's approval and may not appear in your **Connector catalog** yet. Google Calendar is read-only today, so booking from the chat needs Outlook or iCloud Calendar. ## Before the meeting ### 1. See what's coming up - "What meetings do I have tomorrow? For each one, list the time, the title and who's invited." Each calendar has its own time zone, which your AI can see. If you work across time zones, say which one you mean, for example "tomorrow, London time". ### 2. Brief yourself on one meeting - "Brief me for my 2pm with Acme: who's coming and what they do, the last three email threads with them, and anything I promised and haven't done." Your AI can look up each guest in your contacts, search your email for recent threads with them, and read the threads in full. ### 3. Check the past meetings - "When did I last meet Priya, and what was it about?" - With Google Meet: "Summarise the last meeting I ran with Acme and list the action items with owners." Google Meet only lists meetings **you organised**, and transcripts only exist when transcription was turned on in the meeting. ### 4. Ask for a one-page brief - "Put that together as a one-page brief: purpose, attendees, history, open points, and three questions I should ask." ## After the meeting ### 5. Get the notes from the transcript - "Read the transcript of today's Acme meeting. List the decisions, the action items with owners and dates, and any open questions." Your AI reads the transcript as "Name: words" lines, so it can say who committed to what. ### 6. Draft the follow-up email - "Draft a follow-up email to everyone who joined, with the decisions and action items as a list. Friendly, under 200 words." It's saved in your **Drafts** folder. Nothing is sent until you send it, or ask your AI to send it and approve the final email (Pro or Agency, with the account's switch on **Can send**). ### 7. Book the next meeting (Pro and Agency, Outlook or iCloud) - "Find three 45-minute slots next week when I'm free in the afternoon." - "Book the Tuesday 3pm slot with jane@acme.com and sam@acme.com, titled 'Acme: next steps'." Before booking, your AI shows the calendar, title, date, start and end time with time zone, location and every guest, and waits for your yes. Guests get an invitation by email; Outlook always sends invitations. To book from the chat, the calendar connection's switch must say **Can book & change**, the server must have **Allow changes** ticked, and nothing can be paused. See [What your AI can do with calendars](/connectors/calendar-tools). ## Related articles - [What your AI can do with calendars](/connectors/calendar-tools) - [Google Meet](/connectors/google-meet) - [Daily inbox triage routine](/guides/daily-inbox-triage) --- # Onboard a teammate URL: https://docs.plugsight.app/guides/onboard-a-teammate Bring a teammate into your workspace on Agency, or give someone outside the team a read-only MCP server. Each person signs in as themselves. On the Agency plan, teammates work in your Plugsight workspace with you: they use its MCP servers from their own AI apps, each signed in as themselves, and every action shows in **Activity** with who did it (actions through an API key show as the person who created the key). Agency includes 5 team members, you included. Free and Pro are for one person. See [Team members](/account/team) for everything about roles and seats. This guide walks through bringing a teammate in, and what to do for someone who isn't part of the team, such as a client. > [!IMPORTANT] > Don't share your Plugsight password. Each person signs in to Plugsight with their own account, so **Activity** shows who did what, and removing someone from the team takes their access away straight away. ## Step 1: choose their role - **Member**: uses the workspace's MCP servers from their own AI apps and sees connections, MCP servers and **Permissions**, but can't change them. **Activity** shows them only what they did. - **Admin**: everything a Member can do, plus adding connections, managing MCP servers and API keys, setting permissions and inviting people. Start with **Member** unless they'll help manage the workspace. You can change it later. The full table is in [Team members](/account/team#roles). ## Step 2: invite them 1. Open **Team**. 2. Under **Invite someone**, enter their work email address and choose **Member** or **Admin**. 3. Click **Send invitation**. The link in their email works once and expires after 7 days. Each invitation takes a seat until it's accepted, revoked or expires. See [Invite someone](/account/team#invite-someone). ## Step 3: they accept and sign in as themselves 1. They open the link in the email. 2. They sign in with the address the invitation was sent to, or click **Create an account** and sign up with it. See [Sign in to Plugsight](/account/sign-in). 3. They click **Accept invitation**. They're now working in your workspace. Their own workspace stays as it was, and the menu at the top of the app switches between the two. ## Step 4: they add an MCP server to their AI app They open **MCP servers**, copy the **Server URL** of the server they should use, and add it to their own AI app (their own Claude or ChatGPT login). When the sign-in window opens, they sign in as themselves and click **Allow access**. See [Connect an AI app](/mcp-servers/connect-ai-app). Your connections stay where they are: nobody gets a copy, and Members never see a password, sign-in or API key stored for a connection. ## Step 5: agree on safe defaults - Keep **Allow changes** unticked on any server they only use for reporting. - Keep account switches off (**Drafts only** or **Read-only**) unless an account needs changes. New connections start that way. - Check **Activity** once a week. See [Review Activity regularly](/guides/review-activity). Share these guides with them: [Questions to try first](/get-started/first-questions) and [Write better questions](/guides/better-questions). ## Someone outside the team For a client or a freelancer who only needs to read some of your data, you don't have to give them a seat. Make a read-only MCP server for them instead: 1. Create an MCP server with **Selected accounts**, ticking only what they should see, and untick **Allow changes**. See [A read-only server to share](/mcp-servers/multiple-servers#a-read-only-server-to-share). 2. On the server's page, under **API key**, click **Create API key**. Give them the key and the server's **Server URL**: their AI app or script needs both. See [API keys](/mcp-servers/api-keys). With **Allow changes** unticked, the server can't send email, update tickets or book events. It can still archive, label and mark emails in the mailboxes it reaches, so leave mailboxes out of it unless they need them. > [!WARNING] > An API key works for anyone who has it, and what's done with it shows in **Activity** as the person who created the key. Give it only to people you trust, and click **Revoke key** when they no longer need it. An AI app that connects with a sign-in window has to sign in to a Plugsight account that's in your workspace. If someone outside the team adds your server's link and signs in as themselves, they see "This connector points at an MCP server that isn't in your account." ## When a teammate leaves 1. Open **Team** and click **Remove** next to their name. They lose access straight away: their AI apps are signed out of the workspace's MCP servers, and any API key they created stops working. What they set up, and their activity, stays. 2. Remove their access in the shared tools themselves (Zendesk, Google Ads, GA4 and so on), as you would for any leaver. 3. Removing someone stops only the API keys they created. If an Owner or Admin created a key for them to use, or gave one to someone outside the team, click **Revoke key** on that server's page. ## Related articles - [Team members](/account/team) - [Use several MCP servers](/mcp-servers/multiple-servers) - [API keys](/mcp-servers/api-keys) - [Remove Plugsight's access](/security/remove-access) - [Give your AI the least access it needs](/guides/least-privilege) --- # Move from Free to Pro without losing anything URL: https://docs.plugsight.app/guides/free-to-pro What stays when you upgrade, what unlocks straight away, and the switches to turn on afterwards so your AI can use the new features. Upgrading keeps everything you've set up. Your connections, MCP servers, AI app connections, settings and **Activity** all stay exactly as they are, and nothing needs reconnecting. This guide covers the upgrade itself and the few things to do afterwards. ## What stays | | After upgrading | | --- | --- | | Connections | All stay, with their switches as they were. | | MCP servers | All stay, with the same **Server URL**, accounts and settings. | | AI apps | Stay connected. You don't add the connector again. | | API keys | Keep working, and now also work with the developer API. | | Activity | Kept, as before. | | Daily email limit and pauses | Unchanged. | ## What unlocks straight away - **Marketing and analytics connectors**: Google Ads, Microsoft Ads, Meta Ads, LinkedIn Ads, Search Console, GA4 and Bing Webmaster Tools, plus Tag Manager, YouTube and Merchant Center once Google approves them. - **Changes**: sending email, Zendesk replies and updates and calendar bookings, each needing your approval; and archiving, labelling or marking emails (your AI asks first only before moving emails to the trash or changing more than 10). - **Higher limits**: 10 connections and 5 MCP servers on Pro; 50 connections and unlimited servers on Agency. - **The developer API.** See [Plans](/get-started/plans) for the full comparison. ## Step 1: upgrade 1. Open **Billing**. 2. Under **Plans**, choose **Monthly** or **Yearly · 2 months free**. 3. Click **Upgrade to Pro** (or **Upgrade to Agency**). 4. Pay on the Stripe checkout page. 5. Back on **Billing**, wait for "Thanks! Your subscription is active." Refresh the page if your plan doesn't show yet. Details and errors: [Upgrade your plan](/account/upgrade). ## Step 2: turn on what you want to change Upgrading doesn't turn on sending or changes by itself. For each account you want your AI to change: 1. Open **Connections**. 2. Click the account's switch under **Write access**. It changes to **Can send** (email), **Can reply & update** (Zendesk) or **Can book & change** (calendars). 3. Read the line under the switch. **Ready** means changes can happen, after your approval in the chat. Leave the others off. You can turn any switch on later. ## Step 3: check your MCP server allows changes On Free, the **Allow changes** box on the server form is greyed out. After upgrading: 1. Open **MCP servers** and look at the server's badge. 2. If it says **Read & draft only** and you want changes through this server, open it, click **Edit configuration**, tick **Allow changes** and save. 3. If it already says **Can make changes**, there's nothing to do. If the line under an account's switch says **Not yet**, this is the step it's waiting for. ## Step 4: connect marketing accounts (if you want them) 1. On **Connections**, click **Add connection** and choose the service. 2. Add the new connection to your MCP server, or use a server set to **All accounts**. 3. [Refresh the tools list](/ai-apps/refresh-tools) in your AI app and start a new chat. Your AI app needs this once, after the first account of a new type. ## Step 5: test it In a new chat: - "List my Plugsight accounts and which ones can send." Accounts you switched on show sending as on. - For marketing: "List my marketing accounts." ## If you go back to Free later Nothing is deleted. Marketing connectors stop working in your AI (they stay on **Connections**), your AI can't send or make changes (it can still read and draft), and the developer API stops. You keep the connections and servers you have, but can't add more beyond Free's limits. See [Cancel your plan](/account/cancel). ## Related articles - [How changes are allowed](/permissions/how-changes-are-allowed) - [Switch states under each account](/permissions/switch-states) - [Stay within your limits](/guides/stay-within-limits) --- # Connect several Google accounts URL: https://docs.plugsight.app/guides/several-google-accounts Connect work, personal and client Google logins side by side, see how each one counts toward your plan, and ask about the right one. You can connect as many Google logins as your plan's connection limit allows: a work and a personal login, or one for each client. This guide explains how Google connections are counted, how to add a second login, and how to make sure your AI uses the right one. ## How Google connections count Each Google service you connect is its own connection, holding only that service's permission: | You connect | Connections used | | --- | --- | | Google Ads with your work login | 1 | | Google Ads, GA4 and Search Console with your work login | 3 (one per service) | | GA4 with your work login and GA4 with a client's login | 2 | | Gmail (work) and Gmail (personal) | 2 | What one connection reaches depends on the service. A Google Ads, GA4, Search Console, Tag Manager, YouTube or Merchant Center connection reaches **every** account, property, site or container that login can open. So one Google Ads connection through a manager (MCC) login brings in every client under it. Connecting the **same** login to the **same** service again doesn't add a connection: it replaces the sign-in of the one you have. That's how you fix a connection that needs reconnecting, too. Your plan sets the total: Free 2, Pro 10, Agency 50. Marketing services (Google Ads, Microsoft Ads, Meta Ads, LinkedIn Ads, Search Console, GA4 and Bing Webmaster Tools) need Pro or Agency, apart from the 1 Free includes to try. See [Plans](/get-started/plans). ## Step 1: add the second login 1. Open **Connector catalog** (or **Connections** → **Add connection**). 2. Click the service. A service you already use shows **Add another account** on its tile. 3. Read **What happens next** and click **Continue to Google**. 4. On Google's screen, choose the **other** Google account. If your browser is signed in to only one Google account, add the second one in Google's account chooser. 5. Tick the permission box and continue. On **Connections**, the new connection appears under the same service, labelled with its Google address. You can also click **Add** next to a service on **Connections** to connect another account of it. Gmail connects differently, with a Google app password rather than Google sign-in. Each Gmail inbox is its own connection, with its own app password. See [Gmail and Google Workspace](/connectors/gmail). ## Step 2: check what each login reaches 1. On **Connections**, click **Show sites & accounts** next to each Google connection. 2. Check the lists, and hide anything you never want in answers. Where two logins reach the same site, property or ad account, it's only counted once when your AI adds accounts together. Hiding applies to every MCP server. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## Step 3: put each login in the right MCP server - **One server for everything** (**All accounts**): your AI sees both logins and can answer across them. - **Separate servers**: for example "Work" with the work connections and "Personal" with the personal ones, each set to **Selected accounts**. See [One MCP server per client or purpose](/guides/one-server-per-purpose). If a server uses **Selected accounts**, new connections aren't added to it by themselves: open the server, click **Edit configuration** and tick them. The first time you add a service you didn't have before (your first GA4, say), [refresh the tools list](/ai-apps/refresh-tools) in your AI app. A second login for a service you already have needs no refresh. ## Step 4: ask about the right one Each connection has a short name, shown in code text under its label on **Connections**. Your AI uses it to tell accounts apart. - "List my Plugsight accounts" shows every connection the server reaches. - "List my marketing accounts" shows every site, property and ad account, with the connection it comes through. Then name what you mean: - "In my personal Gmail, find the booking confirmation from the hotel." - "For the Bright Dental GA4 property, sessions by channel last month." - "Compare organic clicks across all my Search Console sites, per site." ## Troubleshooting ### My AI uses the wrong login Name the account, site or property in your question, or use the connection's short name. To keep two logins apart for good, put them in different MCP servers. ### I hit my connection limit Each Google service per login is one connection. Remove connections you don't use, or upgrade. See [Stay within your limits](/guides/stay-within-limits). ## Related articles - [Several accounts per service](/ai-apps/multiple-accounts) - [Your AI can't see an account](/troubleshooting/ai-cant-see-account) - [Reconnect needed](/troubleshooting/reconnect-needed) --- # Build a dashboard with Claude Code and the developer API URL: https://docs.plugsight.app/guides/developer-dashboard Explore your data in Claude Code through your MCP server, then have it build a small dashboard that reads live numbers from the developer API. This guide goes from an idea ("a page with this month's sessions, ad spend and open tickets") to a working dashboard. You use Claude Code twice: first through your Plugsight MCP server, to explore what data you have; then as a coding assistant, to write a small server that calls Plugsight's developer API and shows the numbers. You need to be comfortable running commands in a terminal. If you only want answers in a chat, you don't need any of this. ## What you need - A **Pro** or **Agency** plan. The developer API isn't on Free. - The accounts the dashboard should show, connected on **Connections**. - [Claude Code](/ai-apps/claude-code) installed (the `claude` command). - Somewhere to run server-side code, such as your own server or a serverless platform. The API key must never reach a web browser. ## Step 1: create an MCP server for the dashboard Give the dashboard its own server, so its key reaches only what it needs. 1. Open **MCP servers** and click **Create MCP server**. 2. **Name**: where it will be used, for example "Company dashboard". 3. **Account access**: **Selected accounts**, ticking only the accounts the dashboard shows. 4. Untick **Allow changes**. A dashboard only reads, and this way its key can't send email, update tickets or book events, even by mistake. 5. Click **Create server**. ## Step 2: explore the data in Claude Code Connect Claude Code to the new server with a browser sign-in, which needs no key: 1. Run, with your server's name and **Server URL**: ``` claude mcp add --transport http company-dashboard https://app.plugsight.app/mcp/YOUR_SERVER_ID ``` 2. Start `claude`, type `/mcp`, choose the server, then **Authenticate**, and click **Allow access** in the browser. Now ask Claude Code what's there, the same way you'd ask in a chat: - "List my marketing accounts and their ids." - "Which fields can I get from GA4? I want sessions, users and key events by day." - "Show me last month's Google Ads cost and conversions by campaign." - "Give me today's Zendesk ticket counts." Note the tool names, arguments and account ids Claude Code uses. Those are the same calls your dashboard will make. ## Step 3: create the API key 1. Open the server's page in Plugsight. 2. Under **API key**, click **Create API key**. 3. Copy the key straight away. It's shown only once. 4. Store it as an environment variable where the dashboard will run, never in your code: ```bash export PLUGSIGHT_API_KEY="mcpk_…" ``` Check it works: ```bash curl https://app.plugsight.app/v1/tools \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" ``` ## Step 4: have Claude Code build the dashboard In your project folder, ask Claude Code to write it, describing the calls you found in Step 2. For example: > Build a small Node.js server for a dashboard. It reads the key from the PLUGSIGHT_API_KEY environment variable and calls the Plugsight developer API (`POST https://app.plugsight.app/v1/tools/{tool}`, JSON body, Bearer key, result under "data"). Make a route /api/stats that calls get_marketing_data for GA4 sessions and users by day for the last 30 days, get_marketing_data for Google Ads cost and conversions by campaign for this month, and zendesk_ticket_stats for this month. Cache the combined result for 10 minutes. Serve one HTML page that fetches /api/stats and shows three tables. Never send the key to the page. Point Claude Code at [Calling tools](/developers/calling-tools), which has request and answer examples, and the tool reference for the tools you use, such as [Marketing and analytics tools](/developers/marketing-tools) and [Zendesk tools](/developers/zendesk-tools). Check what it writes against these rules: - **The key stays on the server.** The web page calls your own route; your server calls Plugsight. The API sends no CORS headers, so a browser can't call it directly anyway. - **Results are cached.** Each API call reads live from the provider. Up to 120 requests a minute per MCP server are allowed, and providers have their own limits. A few minutes of caching keeps you well clear. - **Errors are handled.** A failed call returns `{ "error", "message", "docs" }`. Show "data unavailable" for that panel rather than breaking the page. See [Errors](/developers/errors). ## Step 5: run it and check 1. Run the server and open the page. 2. Compare one or two numbers with the same question asked in a chat, or in Google Ads or GA4 for the same dates. 3. In Plugsight, open **Activity**: each call shows with "Developer API" under **Who**. ## Keep it running - **Dates**: presets such as `last_30d` and `this_month` are worked out in UTC. See [Get accurate numbers from marketing data](/guides/accurate-marketing-numbers). - **If the key leaks**: on the server's page, click **Regenerate key**, then **Replace key**, and update the environment variable. The old key stops working at once. - **If your plan changes to Free**, every request is refused with `403 plan_required`. - **New accounts**: with **Selected accounts**, tick new connections on the server before the dashboard can use them. ## Related articles - [Developer API](/developers) - [Authentication](/developers/authentication) - [Keep app passwords and API keys safe](/guides/keep-credentials-safe) --- # Switch AI apps URL: https://docs.plugsight.app/guides/switch-ai-apps Move from Claude to ChatGPT or back, or use both, with the same Plugsight accounts and servers. Nothing in Plugsight needs setting up again. Your accounts, MCP servers and safety settings live in Plugsight, not in your AI app. So switching from Claude to ChatGPT, or the other way, means adding the same MCP server to the new app. You don't reconnect any accounts. You can also use both at once: one MCP server can be added to several AI apps. ## What moves with you, and what doesn't | | Switching AI apps | | --- | --- | | Connections, MCP servers, switches, pauses, daily email limit | Stay in Plugsight. Nothing to redo. | | **Activity** | Stays in Plugsight, and shows each AI app by name under **Who**. | | Your chats and chat history | Stay in the old AI app. Plugsight doesn't store them. | | Anything the AI app remembers about you | Stays in the old AI app. | ## Before you switch: check the new app's plan | AI app | What you need | | --- | --- | | Claude | Any Claude plan. The free plan allows one custom connector. On Team and Enterprise, an Owner adds the connector first. | | ChatGPT | chatgpt.com in a web browser, on Business, Enterprise or Edu (an admin may need to allow **Create custom MCP servers**). ChatGPT Pro can connect, but read-only. The free plan isn't eligible. | Full details: [Connect AI apps](/ai-apps). > [!NOTE] > On ChatGPT Pro (OpenAI's plan, not Plugsight's), your AI can read your accounts but can't send or change anything, whatever your Plugsight settings say. ## Step 1: copy your server's link 1. In Plugsight, open **MCP servers** and click the server. 2. Under **Server URL**, click **Copy URL**. ## Step 2: add it to the new AI app **Moving to ChatGPT:** 1. On chatgpt.com, open chatgpt.com/plugins. 2. Click **Add** and choose **Create custom MCP server** (on some accounts, **Create MCP App**). 3. Enter the server's name, paste the URL as **Server URL**, and choose **OAuth** for **Authentication**. 4. Select **I understand and want to continue**, then **Create as a plugin**. 5. In the Plugsight window, check the server and click **Allow access**. Full steps: [ChatGPT](/ai-apps/chatgpt). **Moving to Claude:** 1. On claude.ai, go to **Customize** → **Connectors**. 2. Click **+ Add** → **Add custom connector**. 3. Enter the server's name and paste the URL as the **Remote MCP server URL**. 4. Click **Continue**, keep the sign-in settings Claude detects, click **Continue** again, then **Add**. 5. Click **Connect** next to the new connector, check the server and click **Allow access**. Full steps: [Claude](/ai-apps/claude). The Claude desktop and phone apps use the connector you add on claude.ai. ## Step 3: check it works In a new chat in the new app, switch the connector on and ask: - "List my Plugsight accounts." On the server's page in Plugsight, **AI apps connected** goes up by one. ## Step 4: bring your routines across Prompts you used in the old app work in the new one. Copy over the questions you reuse, such as your [inbox triage](/guides/daily-inbox-triage) or [monthly report](/guides/monthly-client-report) questions. Approvals look different in each app: both ask before a change, but the wording and buttons are the app's own. See [Approvals in your AI app](/ai-apps/approvals). ## Step 5: remove the old app (optional) If you've stopped using the old app, remove the Plugsight connector there. In Claude: [claude.ai/customize/connectors](https://claude.ai/customize/connectors), click the server, then **Disconnect**. In ChatGPT: remove it in the app's connector settings. To be certain the old app can't use the server any more, use **Disconnect all AI apps** on the server's page in Plugsight, then reconnect the new app (it asks you to sign in and click **Allow access** again). See [Disconnect an AI app](/ai-apps/disconnect). ## Use both Many people keep both. Some set-ups that work well: - **Same server in both apps**: the simplest. Both apps see the same accounts. - **One server per app**, for example "Claude" and "ChatGPT": **Disconnect all AI apps** on one doesn't affect the other, and **Activity** shows which server each request came through. See [One MCP server per client or purpose](/guides/one-server-per-purpose). ## Related articles - [Connect an AI app to your server](/mcp-servers/connect-ai-app) - [Refresh the tools list](/ai-apps/refresh-tools) - [AI app problems](/troubleshooting/ai-app-problems) --- # Give your AI the least access it needs URL: https://docs.plugsight.app/guides/least-privilege Set up Plugsight so each AI app reaches only the accounts it needs and can change only what you mean it to, using the controls you already have. The safest set-up gives each AI app exactly what its job needs and nothing more. Plugsight gives you five layers to do that. Use them from the outside in: first which accounts, then which items inside them, then what may change. ## 1. Connect only what you'll use Each connection is a login Plugsight keeps for you. If you don't need an account, don't connect it, and remove connections you've stopped using (**Connections** → **Remove**). Removing a connection deletes its stored login straight away and takes it out of every MCP server. ## 2. Choose Selected accounts on each MCP server **All accounts** is convenient for your own everyday server, but it grows by itself: every account you connect later is added. For anything else, choose **Selected accounts** and tick only what that server needs. - A server for client reporting: only that client's marketing connections. - A server for a dashboard or script: only the accounts it shows. - A server for support work: only the helpdesk and the support inbox. To check what a server reaches, ask your AI "List my Plugsight accounts" in a chat that uses it. See [Create an MCP server](/mcp-servers/create). ## 3. Hide items you never want in answers One Google or Microsoft login often reaches many sites, properties, ad accounts, calendars or drives. On **Connections**, click **Show sites & accounts** (or **Show drives**, **Show calendars**) and switch off anything your AI should never use: test sites, closed clients, a private calendar. Hidden items are hidden on **every** MCP server, even if your AI asks for them by name. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## 4. Make servers read-only where you can Untick **Allow changes** on any server that only needs to read. Its badge then says **Read & draft only**: through it, your AI can read and write email drafts, but can't send email, update tickets or book events, whatever the account switches say. Archiving, labelling and marking emails still work; to stop those, pause email changes on **Permissions**. Good candidates: - Reporting and analysis servers. - Servers used by scripts and dashboards, so their API key can't make changes. - A server you're using to test new prompts. ## 5. Turn on changes one account at a time Every account's switch on **Connections** starts off: **Drafts only** for email, **Read-only** for helpdesk and calendars. Turn on only the accounts you need your AI to change, for example your work inbox but not your personal one. Even with everything on, each change still waits for your approval in the chat. See [How changes are allowed](/permissions/how-changes-are-allowed). ## Some connectors only read Marketing and analytics, contacts, files, stores and email marketing are read-only in Plugsight: your AI can never change them, whatever your settings. Google Ads and Merchant Center ask Google for broader permissions because Google offers no read-only option, but Plugsight only reads them. See [Read-only connectors](/permissions/read-only-connectors) and [Permissions Plugsight asks Google and Microsoft for](/security/provider-permissions). ## Check your set-up A quick review, every few months or when something changes: - [ ] Every connection on **Connections** is still needed. - [ ] Servers other than your own everyday one use **Selected accounts**. - [ ] Servers that only read have **Allow changes** unticked. - [ ] Only the accounts that need it have their switch on. - [ ] Every API key is still in use. Revoke the rest. See [Keep app passwords and API keys safe](/guides/keep-credentials-safe). - [ ] **AI apps connected** on each server matches the apps you actually use. If not, use **Disconnect all AI apps** and reconnect the ones you use. ## Related articles - [One MCP server per client or purpose](/guides/one-server-per-purpose) - [Review Activity regularly](/guides/review-activity) - [Use several MCP servers](/mcp-servers/multiple-servers) --- # One MCP server per client or purpose URL: https://docs.plugsight.app/guides/one-server-per-purpose When to split your accounts across several MCP servers, how to name and set each one up, and the limits of what a separate server can separate. One MCP server with **All accounts** is fine when you're the only person and every account is yours. Once you work with clients, share data with scripts, or want some AI apps to only read, separate servers keep things apart. ## Why split - **No mix-ups.** In a chat that uses a client's server, your AI can't see another client's accounts, so it can't mention them by mistake. - **Different permissions.** One server can allow changes while another is read-only. - **Separate off switches.** **Disconnect all AI apps**, **Regenerate key** and **Delete server** affect one server only. - **Clearer Activity.** Every entry shows the server it came through, "via [server name]". ## Ways to split | Split by | Example servers | Typical settings | | --- | --- | --- | | Client | "Acme (client)", "Bright Dental (client)" | **Selected accounts**: only that client's connections. **Allow changes** usually unticked. | | Purpose | "Reporting", "Support", "Inbox" | **Selected accounts** per purpose. Changes only where needed, for example on "Support". | | AI app | "Claude", "ChatGPT", "Claude Code" | Often **All accounts**. Lets you cut off one app without touching the others. | | Script or system | "Company dashboard", "Website stats" | **Selected accounts**, **Allow changes** unticked, an API key. One server per system. | Mixing is fine: for example, "Me" with everything, plus one read-only server per client. ## Name servers clearly The name is what your AI app shows for the connector, and what **Activity** shows under **Who**. Name each server after who or what it's for: "Acme (client)", "Support desk", "Website dashboard". Up to 60 characters. ## What a separate server can't separate A server picks **whole connections**. It can't pick some ad accounts or sites inside a connection and leave out others. - One Google Ads connection through your manager (MCC) login reaches every client under it, so a server with that connection reaches every client. - Hiding an item with **Show sites & accounts** hides it from **every** server, not one. To give a client a server that reaches only their ad account, you need a connection that reaches only that client: a Google login with access to their account and no others. See [Set up Plugsight for a new client](/guides/new-client-setup). ## How many servers you can have Free 1, Pro 5, Agency unlimited. See [MCP server limits on each plan](/mcp-servers/plan-limits). On Pro, a common pattern is one server for yourself, one read-only reporting server and up to three client or system servers. ## Keep them tidy - **Selected accounts don't grow by themselves.** When you connect a new account, tick it on each server that should reach it. - **One account can be in many servers.** Connect it once, tick it wherever it's needed. - **Delete servers you no longer use**, for example when a client leaves. The link stops working in every AI app and any API key is deleted. Your connections aren't touched. ## Several servers in one AI app If your AI app allows several connectors, you can add more than one server, for example "Me" and "Acme (client)". Each shows under its own name. Switch on only the one you need for a chat, so answers don't mix. ## Related articles - [Use several MCP servers](/mcp-servers/multiple-servers) - [Give your AI the least access it needs](/guides/least-privilege) - [Edit an MCP server](/mcp-servers/edit) --- # When to use Pause URL: https://docs.plugsight.app/guides/when-to-pause The moments that call for Pause or Pause everything, when an account switch or a read-only server is the better tool, and how to resume safely. **Pause** on the **Permissions** page is an emergency stop for changes. It takes effect at once, overrides every account switch of its type, and leaves reading and drafting working. **Resume** puts everything back exactly as it was. It's not meant for every day. Day to day, each account's switch on **Connections** decides what your AI may change. Use Pause for the moments below. How it works, step by step: [Pause changes](/permissions/pause). ## Pause everything when - **Something in Activity looks wrong.** An email you don't remember approving, a ticket update you didn't ask for, or many attempts in a row. Pause first, then look. See [Review Activity regularly](/guides/review-activity). - **You think a device, an AI chat or an API key is in the wrong hands.** Pause everything straight away, then use **Disconnect all AI apps** or **Regenerate key** on the server. See [Keep app passwords and API keys safe](/guides/keep-credentials-safe). - **Someone else is using your AI chat**, for example in a demo or a screen share. - **You're away**, and want to be certain nothing goes out while you can't check. ## Pause one type when - **You're testing new prompts for one kind of account.** For example, pause **Email** while you work out a new triage routine; drafts still work, so you can see exactly what your AI would send. - **One service is behaving oddly.** For example, pause **Helpdesk** while you check a run of Zendesk updates, and keep email working. ## Use something else when | You want | Better choice | | --- | --- | | One inbox to send and another not to | The account switches on **Connections**. | | A server that never sends email, updates tickets or books events | Untick **Allow changes** on that server. | | To stop one AI app using Plugsight at all | Remove the connector in that app, or **Disconnect all AI apps** on the server. | | Fewer emails per day | Lower the daily email limit on **Permissions**. See [Stay within your limits](/guides/stay-within-limits). | ## What Pause doesn't do - It doesn't undo anything already sent or changed. **Activity** lists what was done. - It doesn't stop reading. Your AI can still search and read everything, and write email drafts. - It doesn't disconnect AI apps or revoke API keys. - It has nothing to pause for read-only types (marketing, contacts, files, stores, email marketing). ## Resume with care Before clicking **Resume** or **Resume all**: 1. Check **Activity**, filtered to **AI apps** and **Blocked**, for anything that tried to happen while paused. 2. If you paused because of a possible leak, make sure you've disconnected AI apps or replaced keys first. 3. Then resume. Each account goes back to the switch setting it had before. While anything is paused, a red notice at the top of every page reminds you, with a **Resume** button. If you resume and your AI still can't change something, read the line under the account's switch on **Connections**. See [Switch states under each account](/permissions/switch-states). ## Related articles - [Pause changes](/permissions/pause) - [How changes are allowed](/permissions/how-changes-are-allowed) - [Remove Plugsight's access](/security/remove-access) --- # Keep app passwords and API keys safe URL: https://docs.plugsight.app/guides/keep-credentials-safe Where app passwords, API keys and server links belong, habits that keep them safe, and exactly what to do if one leaks. Plugsight uses three kinds of secret. Each one gives access to something different, so each needs its own care. | Secret | What it is | What someone with it could do | | --- | --- | --- | | **App password** | A password you create at your email provider (Gmail, iCloud, Yahoo, AOL, Zoho and others) for Plugsight to use. | Sign in to that mailbox by itself, outside Plugsight. | | **API key** (starts `mcpk_`) | The key for one MCP server, for Claude Code, scripts or the developer API. | Use everything that MCP server reaches, and make changes if the server and accounts allow them. | | **Your Plugsight sign-in** | Your password, sign-in link or Google or Microsoft login. | Everything in your Plugsight account. | A **Server URL** on its own isn't enough to get in: an AI app that uses it must sign in to your Plugsight account and click **Allow access**. There's still no reason to share it. ## App passwords - **Make an app password only for Plugsight**, and name it so you'll recognise it later, for example "Plugsight". Don't reuse it anywhere else. - **Paste it straight into Plugsight**, then close the provider's page. Some providers, including Google, show it only once; you don't need to keep a copy. If you ever need to reconnect, make a new one. - **Never paste it into an AI chat**, an email or a shared document. - **Delete it at your provider** when you remove that mailbox from Plugsight. Your normal password isn't affected. Plugsight encrypts app passwords with AES-256-GCM before saving them, decrypts them only on its own servers when a request needs them, and never sends them to your AI app. See [How credentials are stored](/security/credentials). Problems creating one: [App password problems](/troubleshooting/app-passwords). ## API keys - **Most AI apps don't need a key.** Claude, ChatGPT and most others sign in through a window. Create a key only for tools that can't, such as Claude Code on a server, scripts or the developer API. - **One server per key holder.** Each server has at most one key. Give each script or system its own server with **Selected accounts**, so each key reaches the least it can. - **Untick Allow changes** on servers whose key only needs to read. Then the key can't send email, update tickets or book events (it can still archive, label and mark emails unless email changes are paused). - **Keep keys on servers, in environment variables** or your platform's secret settings. Never put one in web page code, a mobile app, a public repository or a chat. - **Don't share a key with a teammate** so they can use your accounts. Everything done with it shows in **Activity** as the person who created it. On Agency, invite them to your team instead, so they sign in as themselves. See [Onboard a teammate](/guides/onboard-a-teammate). - **Revoke keys you no longer use**: on the server's page, **API key** → **Revoke key**. Plugsight shows a key once and stores only a hash of it, so nobody, including Plugsight, can show it to you again. If you lose it, regenerate it. See [API keys](/mcp-servers/api-keys). ## Your Plugsight sign-in - Use a password of at least 10 characters that you don't use anywhere else, or sign in with Google or Microsoft. - Don't share your login. Plugsight has no shared or team accounts. - Check **Activity**, filtered to **Sign-ins**, now and then for sign-ins you don't recognise. See [Change or reset your password](/account/password). ## If a secret leaks Act in this order. Each step takes effect straight away. 1. **Stop changes.** On **Permissions**, click **Pause everything**. Your AI can still read, but nothing can be sent or changed. 2. **Close the leaked door:** - **API key**: on the server's page, **Regenerate key** → **Replace key** (or **Revoke key**). The old key stops working at once. Then update the places that use it. - **App password**: delete it at your email provider. Then make a new one and reconnect the mailbox on **Connections**. - **Plugsight sign-in**: change your password. Then, on each MCP server, use **Disconnect all AI apps**, and reconnect your own apps. 3. **Check what happened.** On **Activity**, filter to **AI apps** and look for anything you didn't do. Calls made with an API key show as "Developer API" or the app's name, with "via [server name]". 4. **Resume.** Once you're sure, click **Resume all** on **Permissions**. 5. **Tell us** if you think someone got into your account: email info@plugsight.app. See [Security issues and the privacy policy](/security/contact-security). ## Related articles - [Remove Plugsight's access](/security/remove-access) - [When to use Pause](/guides/when-to-pause) - [Review Activity regularly](/guides/review-activity) --- # Review Activity regularly URL: https://docs.plugsight.app/guides/review-activity A five-minute weekly check of the Activity page - what your AI did, what was blocked or failed, and sign-ins - with what to do when something looks wrong. **Activity** lists everything on your account: sign-ins, changes you made in the app, and every read and write your AI apps made. A short look once a week tells you whether everything is as you expect, and catches problems while they're small. Entries are kept for one year. How the page works, column by column: [Activity log](/permissions/activity). ## The weekly check About five minutes. Use the filters at the top of the page; they combine. ### 1. What your AI changed 1. Click the **AI apps** chip. 2. Set **Result** to **Succeeded**. 3. Scan for sends and changes, such as "Sent an email…" or ticket updates. Each one should be something you approved in a chat. To find one thing, type in **Search what happened…**, for example a recipient's address or "Sent". ### 2. What was stopped 1. Keep **AI apps**, and set **Result** to **Blocked**. **Blocked** means one of your own safety settings stopped it and nothing happened: an account switch was off, the server was read-only, something was paused, the daily email limit was reached, or the change wasn't approved. The reason is under the badge. A few blocked entries are normal. Many in a row, or blocked attempts you don't recognise, are worth a closer look. ### 3. What failed 1. Set **Result** to **Failed**. **Failed** means the service refused or didn't answer, for example an expired sign-in or a ticket that no longer exists. If the reason says to reconnect, do that on **Connections**. See [Reconnect needed](/troubleshooting/reconnect-needed). ### 4. Sign-ins 1. Click the **Sign-ins** chip and set **Result** to **Any result**. 2. Check the times and IP addresses (shown under the time). Hover over a time to see it in UTC. ### 5. Settings changes 1. Click the **Connections**, **MCP servers** and **Settings** chips in turn. 2. Check that every switch turned on, server created or edited, API key created and limit changed was you. ## What to look for | You see | It may mean | Do this | | --- | --- | --- | | A send or change you don't remember approving | An AI app or key used in a way you didn't expect | **Pause everything**, then see [Keep app passwords and API keys safe](/guides/keep-credentials-safe). | | "Developer API" entries you don't expect | An API key in use somewhere | Find which server ("via …"), then revoke or regenerate its key. | | An AI app name you don't use | An app you once connected is still allowed | **Disconnect all AI apps** on that server, then reconnect your own. | | Sign-ins from times or places you don't recognise | Someone may know your sign-in | Change your password and **Pause everything**. Email info@plugsight.app. | | Many blocked sends at the daily limit | A routine sending more than you expected | Check the routine; adjust the limit if it's right. See [Stay within your limits](/guides/stay-within-limits). | | Repeated failures for one account | A sign-in that has expired | Reconnect the account on **Connections**. | ## Make it easier - **Name servers clearly**, so "via Acme (client)" tells you at once where a request came from. - **One server per AI app or script**, so each source shows up under its own name. See [One MCP server per client or purpose](/guides/one-server-per-purpose). - **Remember what Activity doesn't keep**: email bodies, attachments and report contents are never recorded. It shows what was done, not the content. ## Related articles - [Activity log](/permissions/activity) - [When a change is blocked](/permissions/blocked-changes) - [When to use Pause](/guides/when-to-pause) --- # Write better questions URL: https://docs.plugsight.app/guides/better-questions How to ask your AI questions that get precise answers from your accounts - exact dates, naming the account, asking for tables, and checking the result. Your AI reads your accounts live through Plugsight, but it still has to work out what you mean. The more precise the question, the fewer guesses it makes. These habits help most. ## Say which data to use AI apps sometimes answer from general knowledge instead of your accounts. Make it clear: - "Using Plugsight, show last week's Google Ads spend." - "From my Zendesk, how many tickets were created yesterday?" Also check the Plugsight connector is switched on in that chat (in Claude: **+** → **Connectors**; in ChatGPT: **+** next to the message box). ## Give a date range Without one, your AI picks its own, and marketing tools default to the last 30 days. | Vague | Precise | | --- | --- | | "recently" | "in the last 7 days" | | "this month vs last" | "this month to date, compared with the same days last month" | | "last quarter" | "from 2026-07-01 to 2026-09-30" | | "this week" | "Monday 9 November to Sunday 15 November 2026" | Exact dates (YYYY-MM-DD) are the most reliable, especially when you'll repeat the report. For how presets like "last 30 days" are worked out, see [Get accurate numbers from marketing data](/guides/accurate-marketing-numbers). ## Name the account When the server reaches more than one account of a kind, say which one: - "In my **work Gmail**, find the latest invoice from Northwind." - "For **Bright Dental's Google Ads** account, which search terms wasted money?" - "On the **shop's GA4 property**, sessions by channel last month." Each connection also has a short name, shown under its label on **Connections**, which you can use too, for example "check [short name] for new messages". Not sure what's there? Ask "List my Plugsight accounts" or "List my marketing accounts". Or ask across everything on purpose: "in any of my inboxes", "across all client accounts". ## Ask for the shape you want Tell your AI how to lay out the answer: - "Show it as a table with columns: campaign, cost, conversions, CPA, change vs last month." - "Top 10 only, sorted by cost, highest first." - "One row per account." (keeps accounts and currencies apart) - "Under 150 words, as bullet points." - "Include the ticket numbers" or "include the order numbers", so you can check them. ## One job per question Big questions are easier to check in steps: 1. "List my Google Ads accounts." 2. "For the Acme account, cost and conversions by campaign last month." 3. "Now the same for the month before, and show the change." 4. "Which of these campaigns had the biggest drop, and why might that be?" Some data can't be combined in one request anyway, for example Google Ads search terms with quality score. Your AI is told when that happens and splits the question. ## Use the ready-made analyses For marketing, Plugsight has deep dives that run several queries at once. Ask for them by name: - "Run a **wasted spend** report." - "Run an **SEO opportunities** report for this site." - "Give me an **account overview**, this month against last month." - "Run a **period comparison** of cost and conversions by campaign against the same period last year." See [How your AI analyses marketing data](/connectors/marketing-data) for the full list. ## Be exact about changes For anything that sends or changes, say exactly what you want, and read the preview before you say yes: - "Draft a reply to Sam, from my work inbox, saying Thursday 2pm works. Don't send it yet." - "Set ticket 4821 to pending and tag it 'refund'." Your AI shows the final email, ticket change or booking and waits for your approval. See [Approvals in the chat](/permissions/approvals). ## Check the answer - Ask "Which accounts and dates did you use?" Every result says where it came from. - Ask "Were there any data notes?" Plugsight adds notes when providers hold data back. - Spot-check one number in the provider's own interface. ## Save questions that work Keep the questions you reuse in a note: your morning [inbox triage](/guides/daily-inbox-triage), your [monthly report](/guides/monthly-client-report), your [support review](/guides/weekly-support-review). Same questions, same order, comparable answers. ## Related articles - [Questions to try first](/get-started/first-questions) - [Get accurate numbers from marketing data](/guides/accurate-marketing-numbers) - [Several accounts per service](/ai-apps/multiple-accounts) --- # Get accurate numbers from marketing data URL: https://docs.plugsight.app/guides/accurate-marketing-numbers How date ranges are worked out (in UTC), how currencies and several accounts are combined, and how to compare periods fairly and check the result. Your AI reads Google Ads, Microsoft Advertising, Search Console and GA4 live, through the same tools every time. Most differences between "what the AI said" and "what Google says" come down to four things: which dates, which accounts, which currency, and data the platform holds back. This article explains each one and how to control it. ## Dates ### How presets are worked out When you say "last 30 days" or "last month", your AI uses one of Plugsight's date presets. Plugsight turns each preset into calendar dates, using **today's date in UTC**: | Preset | From | To | | --- | --- | --- | | Today | today | today | | Yesterday | yesterday | yesterday | | Last 7, 14, 28, 30, 90, 180 or 365 days | that many days ago | **yesterday** (today isn't included) | | This month | the 1st of this month | today | | Last month | the 1st of last month | the last day of last month | | This year | 1 January | today | | Last year | 1 January last year | 31 December last year | With no date range at all, the marketing tools use the last 30 days. > [!NOTE] > "Today" is the date in UTC. Early in the morning in the Americas, or late in the evening in Asia and Australia, the UTC date can differ from yours. If it matters, give exact dates. ### Use exact dates for anything you'll repeat Exact dates in YYYY-MM-DD form remove all doubt: "from 2026-10-01 to 2026-10-31". Both ends are included. Your AI can also use relative dates such as "28daysAgo", "yesterday" and "today". ### Partial days and late data - **"This month" and "today" include today**, which isn't over. Compare complete days, or compare "this month to date" with the same number of days last month. - **Search Console** data becomes final about 2–3 days after each date, and Plugsight includes the fresh, not-yet-final days by default. For a fair comparison, end your range 3 days ago, or ask your AI to leave out fresh data. - **Conversions** in ad platforms can keep arriving for days after a click. Recent days may still grow. ### Time zones Plugsight sends the ad platforms and GA4 whole calendar days. Each platform counts a day in its own reporting time zone. For Google Ads, ask "List my Google Ads accounts": the list shows each account's time zone, as well as its currency. If two accounts are in different time zones, their "same day" covers different hours. ## Several accounts in one answer When you ask about several accounts, properties or sites at once, Plugsight adds rows with the same values together. The same search term in two ad accounts becomes one row. The same account reached through two logins is only counted once. - To see each account separately, ask for it "per account" or "split by account". - **Ratios stay correct.** CTR, CPC, CPM, CPA, ROAS and conversion rate are recalculated after rows are combined, not averaged. - **Manager (MCC) accounts** don't report their own metrics; the clients under them do. - **Hidden accounts** are left out of every answer. ## Currencies Money is added up as it is, in each account's own currency. If the accounts in one answer use different currencies, your AI is told so (for example "Accounts use different currencies (GBP, USD); money is summed as-is"). - Ask for results "split by account" or "split by currency" whenever accounts may differ. - Plugsight doesn't convert currencies. If you ask your AI to convert, check which exchange rate it used. - Store connectors show each order's currency; [Magento](/connectors/magento) sales reports use the store's base currency. ## Comparing periods For "this month against last month" questions, ask for a **period comparison**. It compares any metrics with either: - **the previous period** of the same length (the default), or - **the same period last year**. It lists the biggest gains and drops. Tips for a fair comparison: - Compare periods of the same length. "Last 28 days against the 28 days before" has the same weekdays in each; calendar months don't. - For seasonal businesses, compare with the same period last year. - Use the same accounts in both periods. An account added or hidden in between changes the totals. ## Data the platforms hold back Plugsight adds a note to the answer when this affects it, and your AI can pass it on. Ask "were there any data notes?" if you're not sure. | Platform | What's held back | | --- | --- | | Google Ads | Low-volume search terms are hidden for privacy. Their cost is in campaign totals but not in search-term rows. | | Search Console | Rare queries are hidden. The note says what share of clicks and impressions that is. | | GA4 | Data thresholds (for example with age and gender), sampling, and rare values grouped into "(other)". | | Any | A report that stopped at the per-account row limit. | Removed Google Ads campaigns are included, because they spent money in the period. Ask your AI to leave them out if you don't want them. ## Check before you share 1. Ask "Which accounts and dates did you use?" 2. Ask "Were there any data notes?" 3. Check one total against the platform's own interface, for the same dates and accounts. 4. If a number is far off, see [Errors from your AI's tools](/troubleshooting/tool-errors). ## Related articles - [How your AI analyses marketing data](/connectors/marketing-data) - [Write better questions](/guides/better-questions) - [Build a monthly client marketing report](/guides/monthly-client-report) --- # Stay within your limits URL: https://docs.plugsight.app/guides/stay-within-limits Plan your use around the daily email limit, your plan's connection and server limits, the developer API rate limit and providers' own limits. Plugsight has a few limits, each there for a reason: the daily email limit protects you from runaway sending, plan limits set what you pay for, and providers like Google have their own rules. This article explains how to plan around each one, so you don't hit them at a bad moment. ## The daily email limit Your AI apps can send up to **20 emails per email account in any 24 hours** unless you change it. You can set any whole number from 1 to 500 on **Permissions** → **Daily email limit**. The same limit applies to every email account. - The 24 hours roll: each email counts for 24 hours after it's sent, then frees up a send. There's no fixed reset time. - **Drafts never count**, and neither do archiving, labelling, marking emails, Zendesk replies or calendar bookings. - Blocked and failed attempts don't count. How to work with it: - **Check before a batch.** Under **Used in the last 24 hours** on **Permissions**, each account shows a count such as **7 of 20 sent** and when the next send frees up. - **Use drafts for big batches.** Ask your AI to save the emails as drafts; drafts have no limit. Review and send them from your mail app. - **Raise the limit only as far as you need.** If you regularly need 40, set 40, not 500. A lower limit caps the damage if something goes wrong. - **Mind your provider's limit too.** Gmail allows about 500 emails a day; Google Workspace and Microsoft 365 allow more. Going near it can get the account temporarily blocked by the provider. When the limit is reached, your AI is told and suggests a draft instead. See [Daily email limit](/permissions/daily-email-limit). ## Plan limits | | Free | Pro | Agency | | --- | --- | --- | --- | | Connections | 2 | 10 | 50 | | MCP servers | 1 | 5 | Unlimited | | Marketing and analytics connectors | No | Yes | Yes | | Sending and changes | No | Yes | Yes | | Developer API | No | Yes | Yes | **Billing** shows how many connections and MCP servers you're using against your plan, with a bar for each. ### Make connections go further - **Each Google service per login is one connection.** Google Ads, GA4 and Search Console from the same login are three. Connect only the services you'll use. - **One marketing connection reaches many accounts.** A Google Ads connection through a manager (MCC) login brings in every client under it, for one connection. The same goes for every GA4 property, Search Console site or Microsoft Advertising account one login can open. - **Remove what you don't use.** On **Connections**, click **Remove** next to it. You can connect it again later. - [PageSpeed Insights](/connectors/pagespeed-insights) needs no connection at all. See [Connect several Google accounts](/guides/several-google-accounts). ### Make servers go further - One server can reach any number of accounts. A server per client is tidy, but not required: on Pro, a common set-up is one server for yourself, one read-only reporting server, and up to three for clients or systems. - Delete servers you no longer use. When you reach a limit, the app tells you, for example "Your Pro plan includes 10 connections. Upgrade to Agency for 50." Nothing you already have is switched off. See [Plans and limits](/troubleshooting/plan-limits). ## Developer API - Up to **120 requests a minute** per MCP server. Over that, requests get `429 rate_limited`. - Every call reads live from the provider, and Plugsight doesn't cache results, so cache them on your side, for a few minutes or more. - Need more? Spread the work over a second MCP server, or cache longer. See [Developer API](/developers). ## Providers' own limits Google, Microsoft, Zendesk and stores set their own limits. When one says "slow down", your AI is told. Ways to stay clear: - **Ask for shorter date ranges** when a report is slow or stops. Microsoft Advertising builds reports on request; a long range can still be pending after 2 minutes. - **Ask for fewer rows.** Marketing data returns up to 500 rows unless you ask for more (up to 50,000). A top 50 is usually enough to decide. - **Watch for the GA4 quota note.** Plugsight tells your AI when the GA4 property's daily API quota is running low. Save the rest for tomorrow. - **Big store reports:** on very busy stores, a Magento sales report can stop early, and the answer says how far it got. Ask for a week at a time. - **Big searches:** email and ticket searches return up to 100 results at a time; your AI pages through more when it needs to. ## AI app access An AI app stays connected while it keeps using your server. If it hasn't used the server for 90 days, it has to sign in and click **Allow access** again. That's not a limit to plan around, but it explains a sudden sign-in prompt in an app you rarely use. ## Related articles - [Plans](/get-started/plans) - [Daily email limit](/permissions/daily-email-limit) - [Plans and limits](/troubleshooting/plan-limits) --- # MCP servers URL: https://docs.plugsight.app/mcp-servers What an MCP server is, which accounts it reaches, what it may do, and how to create, share, secure and delete one. An **MCP server** is your private AI link: a web address you add to Claude, ChatGPT, Cursor or another AI app as a connector. Through it, the AI app can use only the accounts you chose for that server, and nothing else. You create and manage them on the **MCP servers** page of the Plugsight app. ## What an MCP server decides Each MCP server has three settings: | Setting | What it controls | | --- | --- | | **Name** | The name your AI app shows for the connector, for example "Work" or "Acme (client)". | | **Account access** | **All accounts** (every connected account, including ones you add later) or **Selected accounts** (only the ones you tick). | | **Allow changes** | Whether the AI may send email, update tickets or book events through this server. Untick it for a read-only server. | Every MCP server can always read the accounts it reaches and write email drafts. Drafts are never sent without you. ## How an AI app gets access 1. You copy the server's link (its **Server URL**) and add it to your AI app. 2. The AI app opens a Plugsight window. You sign in and click **Allow access**. 3. From then on, the AI app can use the server's accounts until you disconnect it or delete the server. Tools that can't open a sign-in window, such as Claude Code in a terminal or your own scripts, use an **API key** instead. ## Why have more than one? To give different AI apps or people different access. For example, one server with all your accounts for you, and a read-only server with only one client's ad account for that client. See [Use several MCP servers](/mcp-servers/multiple-servers). ## In this section - [Create an MCP server](/mcp-servers/create): every field on the form, explained. - [Edit an MCP server](/mcp-servers/edit): change its name, accounts or permissions, and read its details. - [Connect an AI app to your server](/mcp-servers/connect-ai-app): the server link, the approval screen and the **AI apps connected** count. - [API keys](/mcp-servers/api-keys): create, regenerate and revoke a key, and what each one breaks or keeps. - [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete): cut off every AI app, or remove a server for good. - [Use several MCP servers](/mcp-servers/multiple-servers): one per client, read-only servers and other set-ups. - [MCP server limits on each plan](/mcp-servers/plan-limits): how many servers you can have. > [!TIP] > New to Plugsight? The [quick start](/get-started/quick-start) walks you through your first server in about five minutes. --- # Create an MCP server URL: https://docs.plugsight.app/mcp-servers/create Step by step, with every field explained - the name, All accounts or Selected accounts, the permissions and Allow changes. An MCP server is the private link your AI app uses to reach your accounts. Creating one takes about a minute. ## Before you start Connect at least one account first, on **Connections** → **Add connection**. A server only reaches accounts you've connected, so with none it can't do anything yet. If you open the form with no accounts connected, Plugsight shows **Connect an account first.** with a link to add one. ## Create the server 1. In the Plugsight app, open **MCP servers**. 2. Click **Create MCP server**. 3. Fill in **Name**, **Account access** and **Permissions** (each is explained below). 4. Click **Create server**. Plugsight opens the new server's page with the message "Server created. Now connect your AI app below." and scrolls to **Connect an AI app**. Next, follow [Connect an AI app to your server](/mcp-servers/connect-ai-app). To leave without creating anything, click **Cancel**. ## The fields ### Name The name your AI app (Claude, ChatGPT, Cursor and others) shows for the connector, for example "Work" or "Acme (client)". - Required. - Up to 60 characters. Choose a name that tells you which accounts it reaches. When you have more than one server, the name is how you tell them apart in your AI app and in **Activity**. ### Account access Which of your connected accounts this server can reach. Choose one: | Option | What it means | | --- | --- | | **All accounts** | Every connected account, including ones you add later. This is the default. | | **Selected accounts** | Only the accounts you tick. Accounts you connect later are not added: you tick them here. | When you choose **Selected accounts**, a list of your connected accounts appears with a tick box next to each one. Tick at least one. If you click **Create server** with none ticked, the form shows **Tick at least one account, or choose All accounts.** > [!NOTE] > With **Selected accounts**, a new account you connect later stays out of this server until you tick it in [Edit configuration](/mcp-servers/edit). This is the most common reason an AI can't see a newly added account. ### Permissions Three tick boxes. The first two are always ticked and can't be changed: | Permission | Can you change it? | What it allows | | --- | --- | --- | | **Read your connected data: email, tickets, ads, analytics, files, calendars and contacts** | No, always on | The AI can search and read the accounts this server reaches. | | **Create email drafts** | No, always on | The AI can save emails in your Drafts folder. Drafts never send without you. | | **Allow changes** | Yes | The AI may send email, update helpdesk tickets or book calendar events through this server. | Why are two boxes always ticked? Reading and drafting are what make a server useful, and drafts never send without you. To limit what a server reads, choose **Selected accounts**. To stop it sending or changing anything, untick **Allow changes**. #### Allow changes **Allow changes** is ticked by default for a new server. Plugsight recommends leaving it ticked: with it on, each account's own switch on **Connections** still decides whether that account can make changes, and you approve every change in the chat. Untick it to make a **read-only server**. A read-only server never sends email, updates tickets or books events, whatever the account switches say. It can still archive, label and mark emails, which can be undone. Its badge on **MCP servers** reads **Read & draft only** instead of **Can make changes**. On the Free plan, **Allow changes** is greyed out and shows **(on the Pro plan. See plans)**, because sending email and making changes are part of the Pro and Agency plans. For the full list of what has to be true before your AI can make a change, see [How changes are allowed](/permissions/how-changes-are-allowed). ## Errors when creating a server ### Give the server a name. **What it means:** the **Name** box is empty. **How to fix it:** type a name, then click **Create server** again. ### Use at most 60 characters. **What it means:** the name is longer than 60 characters. **How to fix it:** shorten it. ### Your Free plan includes 1 MCP server. Upgrade to Pro for 5. **What it means:** you already have as many MCP servers as your plan allows. On Pro the message reads "Your Pro plan includes 5 MCP servers. Upgrade to Agency for unlimited." **How to fix it:** delete a server you no longer use, or upgrade under **Billing**. See [MCP server limits on each plan](/mcp-servers/plan-limits). ## Related articles - [Edit an MCP server](/mcp-servers/edit) - [Connect an AI app to your server](/mcp-servers/connect-ai-app) - [Use several MCP servers](/mcp-servers/multiple-servers) - [How changes are allowed](/permissions/how-changes-are-allowed) --- # Edit an MCP server URL: https://docs.plugsight.app/mcp-servers/edit Change a server's name, accounts or Allow changes, and understand everything shown on the server's page. You can change an MCP server's settings at any time. AI apps already connected to it keep their access; they don't need to sign in again. ## Open a server 1. Open **MCP servers**. 2. Click the server's name, or **Manage** on its row. The list on **MCP servers** shows each server's **Name**, **Accounts** (for example "All accounts (4)" or "2 selected"), **Permissions** (**Can make changes** or **Read & draft only**) and **Server URL**, with a copy button. ## Change the configuration 1. On the server's page, click **Edit** (top right), or scroll to **Edit configuration**. 2. Change any of the fields. They are the same as when you created the server: **Name**, **Account access** (**All accounts** or **Selected accounts**) and **Permissions** (**Allow changes**). See [Create an MCP server](/mcp-servers/create) for what each one means. 3. Click **Save changes**. Plugsight shows **Changes saved.** The change applies to the next thing your AI does; you don't need to reconnect your AI app. Every change to a server is recorded in **Activity**, for example "Changed MCP server "Work"". > [!NOTE] > Adding or removing accounts can change the list of actions your AI app sees, for example when the server gains its first helpdesk account. When that happens, Plugsight shows a notice at the top of **MCP servers** naming each AI app that needs a refresh, with its steps. The notice goes away by itself once the app has the new list. See [Refresh the tools list](/ai-apps/refresh-tools). ## What the server's page shows ### Server URL The link you paste into your AI app, with a **Copy URL** button. See [Connect an AI app to your server](/mcp-servers/connect-ai-app). ### Details | Item | What it tells you | | --- | --- | | **Permissions** | **Can make changes** (Allow changes is ticked) or **Read & draft only** (it isn't). | | **Account access** | **All accounts** or **Selected accounts**. | | **AI apps connected** | How many AI apps have clicked **Allow** for this server and can use it now. 0 means none yet. | | **API key** | **Active** if the server has an API key, **None** if it doesn't. None is normal: most AI apps don't need one. | | **Server ID** | An internal reference. You only need it if Plugsight support asks for it. | The page description also shows when the server was created. ### Accounts The accounts this server reaches, with the number in the heading, for example **Accounts (3)**. If it reaches none, it shows **No accounts** and "This server can't do anything yet." Tick accounts in **Edit configuration**, or connect an account first. ### Other sections - **Connect an AI app**: setup steps for Claude, ChatGPT, Claude Code, Cursor and other apps. - **API key**: see [API keys](/mcp-servers/api-keys). - **Developer API**: for pulling the same data into your own website or system. - **Having trouble?**: common problems with this server and their fixes. - **Danger zone**: see [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete). ## Common changes ### Add a newly connected account If the server uses **Selected accounts**, accounts you connect later aren't included. 1. Open the server and go to **Edit configuration**. 2. Tick the new account, or choose **All accounts**. 3. Click **Save changes**. If it's the first account of a new type (your first Zendesk, say), your AI app may also need to reload its list of actions. Follow the refresh notice on **MCP servers**. ### Make a server read-only 1. Open the server and go to **Edit configuration**. 2. Untick **Allow changes**. 3. Click **Save changes**. The badge changes to **Read & draft only**. The AI can still read the server's accounts and write email drafts, but can't send email, update tickets or book events, whatever the account switches say. It can still archive, label and mark emails. ### Let a server make changes again Tick **Allow changes** and click **Save changes**. Each account's own switch on **Connections** still decides what that account may change, and you still approve every change in the chat. See [How changes are allowed](/permissions/how-changes-are-allowed). ## Troubleshooting ### The AI says an account is unknown **What it means:** that account isn't in this server. **How to fix it:** in **Edit configuration**, choose **All accounts** or tick the account, then **Save changes**. ### The AI can't send emails or update tickets **What it means:** one of the conditions for changes isn't met. **How to fix it:** check that **Allow changes** is ticked here, that the account's switch on **Connections** is on and says **Ready** underneath, and that nothing is paused on **Permissions**. See [Switch states under each account](/permissions/switch-states). ### That MCP server doesn't exist. **What it means:** the server was deleted, possibly in another browser tab. **How to fix it:** go back to **MCP servers** and refresh the page. ## Related articles - [Create an MCP server](/mcp-servers/create) - [Connect an AI app to your server](/mcp-servers/connect-ai-app) - [How changes are allowed](/permissions/how-changes-are-allowed) --- # Connect an AI app to your server URL: https://docs.plugsight.app/mcp-servers/connect-ai-app Where to find your server link, what the Plugsight approval screen shows, and how the AI apps connected count works. To use an MCP server, you add its link to your AI app, then approve the app once on a Plugsight screen. ## Find your server link 1. Open **MCP servers**. 2. Copy the link in the **Server URL** column, or open the server and click **Copy URL** under **Server URL**. The link ends in `/mcp/` followed by the server's ID. Treat it as private: it only works for someone who can sign in to your Plugsight account and click **Allow access**, but there's no reason to share it. ## Add it to your AI app Each server's page has a **Connect an AI app** section with step-by-step instructions for Claude, ChatGPT, Claude Code, Cursor and other apps. It takes about 2 minutes. On **MCP servers**, **Show setup steps** opens the same instructions. For example, in Claude (claude.ai in a web browser): 1. Go to **Customize** → **Connectors** (claude.ai/customize/connectors). 2. Click **+ Add** → **Add custom connector**. 3. Enter the server's name and paste the server URL as the **Remote MCP server URL**. 4. Click **Continue**, keep the sign-in settings Claude detects, click **Continue** again, then **Add**. 5. Click **Connect** next to the new connector. The Plugsight approval screen opens. ## The approval screen When an AI app connects, a Plugsight window opens with the heading **[AI app name] wants access**, for example "Claude wants access to this MCP server on Plugsight". 1. If you aren't signed in to Plugsight, sign in first. If your email isn't confirmed yet, Plugsight asks you to confirm it before you can continue. 2. Read what the app will be able to do: - **Search and read**: everything in the accounts of the MCP server you choose, and nothing outside it. - **Draft, send and change**: write email drafts. Send, update tickets or book events only if that server allows changes and the account's switch is on, and only after you approve each one in the chat. 3. Check the server shown under **MCP server**. Each server lists what it **Reaches**: the accounts (or "all your accounts") and either "changes follow account switches" or "read & draft only". 4. Click **Allow access**. The window sends you back to the AI app, whose web address is shown at the bottom of the screen. The connector now shows as connected in your AI app. If the AI app doesn't say which server it is connecting to, the screen shows **Choose an MCP server** with all your servers instead. Pick one before clicking **Allow access**. To refuse, click **Cancel**. The AI app gets no access, and you can close its window. The bottom of the screen shows which Plugsight account you're signed in with, and a **Switch account** link. Each approval is recorded in **Activity**, for example "Allowed "Claude" to use "Work"". ## AI apps connected The server's **Details** panel shows **AI apps connected**: how many AI apps have clicked **Allow** for this server and can use it now. - **0** means none yet. Follow **Connect an AI app** on the server's page. - The count goes up each time a different AI app is approved. - It goes back to 0 when you use **Disconnect all AI apps**. See [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete). - Tools that use an API key aren't counted here; the **API key** item shows whether the server has one. An AI app stays connected while it keeps using the server. If it hasn't used the server for 90 days, it has to sign in and click **Allow access** again. ## Troubleshooting ### This connector points at an MCP server that isn't in your account. **What it means:** you're signed in to Plugsight with a different account from the one that created this server, often a work and a personal login in the same browser. **How to fix it:** click **Switch account** at the bottom of the approval screen and sign in with the account that owns the server. Or use the URL of one of your own servers. ### You don't have an MCP server yet. **What it means:** your Plugsight account has no MCP servers, so there's nothing to approve. **How to fix it:** click **Create one**, pick the accounts it should reach, then go back to your AI app and connect again. ### This AI app isn't registered. Start the connection again from your AI app. **What it means:** Plugsight doesn't recognise the app that opened the window. **How to fix it:** close the window and click **Connect** again in your AI app. ### This AI app's connection is out of date. Remove the Plugsight connector in your AI app and add it again. **What it means:** the AI app's saved details no longer match. **How to fix it:** remove the connector in your AI app, then add it again with the same server URL. Your accounts and server settings in Plugsight aren't affected. ### The sign-in window doesn't open, or closes with an error **How to fix it:** allow pop-ups for the AI app, make sure you're signed in to Plugsight in the same browser, then remove the connector in the AI app and add it again. ### My AI app asks me to sign in to Plugsight again **What it means:** its access ended. This happens when the server was deleted, you used **Disconnect all AI apps**, or the app hadn't used the server for 90 days. **How to fix it:** click the sign-in prompt, sign in to the same Plugsight account, check the server name and click **Allow access**. ## Related articles - [Connect AI apps](/ai-apps): full steps for each AI app. - [API keys](/mcp-servers/api-keys): for tools that can't open a sign-in window. - [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete) - [Approvals in the chat](/permissions/approvals) --- # API keys URL: https://docs.plugsight.app/mcp-servers/api-keys When an MCP server needs an API key, and exactly what creating, regenerating or revoking one breaks and keeps working. Most people never need an API key. Claude, ChatGPT and most AI apps connect by opening a sign-in window, where you click **Allow access**. No key needed. An API key is for tools that can't show a sign-in window, such as Claude Code in a terminal or your own scripts. They send the key with every request instead. Each MCP server can have one API key. The key reaches exactly the accounts its server reaches, with the same permissions. > [!WARNING] > Anyone with the key can use this MCP server's accounts. Plugsight shows a new key only once. Keep it on your own computer or server, never in a web page or an app people can download. If it leaks, regenerate or revoke it. ## Create an API key 1. Open **MCP servers** and click the server. 2. Scroll to **API key**. 3. Click **Create API key**. 4. Copy the key from the **API key created.** box. Copy it now: it won't be shown again. The box also shows a ready-made Claude Code command with your key filled in: ``` claude mcp add --transport http --header "Authorization: Bearer " ``` The server's **Details** panel now shows **API key: Active**. The event is recorded in **Activity**. Plugsight stores only a scrambled form (a hash) of the key, so nobody, including Plugsight, can show it to you again. If you lose it, regenerate it. ## Regenerate the key Use this when the key may have leaked, or you lost it. 1. On the server's page, under **API key**, click **Regenerate key**. 2. Read the **Replace the API key?** box, then click **Replace key**. 3. Copy the new key from the **API key created.** box. | | | | --- | --- | | **What happens** | You get a new key, and the current one stops working straight away. | | **What breaks until you update it** | Anything using the current key, such as Claude Code or a script, gets refused until you paste in the new key. | | **What keeps working** | Claude, ChatGPT and other apps that signed in with the browser aren't affected. | ## Revoke the key Use this when you no longer need a key at all. 1. On the server's page, under **API key**, click **Revoke key**. 2. Read the **Revoke the API key?** box, then click **Revoke key**. | | | | --- | --- | | **What happens** | The key stops working straight away, and this server has no key until you create a new one. | | **What stops** | Anything using the key, such as Claude Code or a script, is refused. | | **What keeps working** | Claude, ChatGPT and other apps that signed in with the browser aren't affected. | The **Details** panel then shows **API key: None**. ## How API keys relate to other controls - **Disconnect all AI apps** doesn't affect the API key. The key keeps working until you revoke it. See [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete). - **Deleting the server** deletes its API key too. - Calls made with the key show in **Activity** like any other AI app, and all your safety settings apply: account switches, **Allow changes**, Pause, the daily email limit and approval. - The same key also works with Plugsight's Developer API, on the Pro and Agency plans. Every Developer API call shows in **Activity** as "Developer API". See [Developer API](/developers). ## Related articles - [Connect an AI app to your server](/mcp-servers/connect-ai-app) - [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete) - [How credentials are stored](/security/credentials) - [Team members](/account/team) --- # Disconnect AI apps or delete a server URL: https://docs.plugsight.app/mcp-servers/disconnect-and-delete Cut off every AI app using a server right now, or delete the server for good, and what stays or stops in each case. Both actions are in the **Danger zone** at the bottom of a server's page. Each one asks you to confirm first. ## Disconnect all AI apps Cuts off every AI app using this server right now. Each one must click **Allow** again to come back. **When to use it:** a device was lost, someone else had access, or you want a clean start. 1. Open **MCP servers** and click the server. 2. Scroll to **Danger zone**. 3. Click **Disconnect all AI apps**. 4. In **Disconnect all AI apps?**, click **Disconnect all**. Plugsight shows **Every AI app was disconnected from this server.** and the server's **AI apps connected** count goes back to 0. | | | | --- | --- | | **What stops** | Every AI app using the server (Claude, ChatGPT and others) loses access straight away. | | **What stays** | The server, its link, its accounts and settings. Each AI app can come back by signing in and clicking **Allow access** again. | | **What isn't affected** | The server's API key, if it has one, keeps working. Revoke it separately under **API key**. | To get an AI app back, open it and connect again; it shows the Plugsight sign-in and approval screen. See [Connect an AI app to your server](/mcp-servers/connect-ai-app). > [!TIP] > To cut off one specific AI app only, remove the Plugsight connector in that app. **Disconnect all AI apps** always disconnects every app on the server. ## Delete a server Removes the server for good. This can't be undone. 1. Open **MCP servers** and click the server. 2. Scroll to **Danger zone**. 3. Click **Delete server**. 4. In **Delete [server name]?**, click **Delete server**. Plugsight goes back to **MCP servers** and shows **MCP server deleted.** | | | | --- | --- | | **What stops** | Its link stops working in every AI app, and its API key, if any, is deleted. | | **What stays** | Your connected accounts aren't touched. Other MCP servers keep working. Past entries in **Activity** stay. | | **To undo** | You can't. Create a new server and add it to your AI apps again. The new server gets a new link. | After deleting, also remove the connector from your AI apps, so they stop trying to use the old link. ## Which one should I use? | You want to | Use | | --- | --- | | Lock out every AI app now, but keep the server | **Disconnect all AI apps** (and **Revoke key** if it has an API key) | | Stop a key-based tool, such as Claude Code or a script | **Revoke key** or **Regenerate key** under **API key** | | Stop all changes for a while, but keep reading | **Pause everything** on **Permissions**. See [Pause changes](/permissions/pause) | | Make the server read-only | Untick **Allow changes** in [Edit configuration](/mcp-servers/edit) | | Remove the server for good | **Delete server** | Both actions are recorded in **Activity**. ## Related articles - [API keys](/mcp-servers/api-keys) - [Pause changes](/permissions/pause) - [Remove Plugsight's access](/security/remove-access) --- # Use several MCP servers URL: https://docs.plugsight.app/mcp-servers/multiple-servers Set up one server per client, a read-only server to share, or separate servers per AI app, and keep data apart. Each MCP server is a separate link with its own accounts, its own **Allow changes** setting, its own connected AI apps and its own API key. Having several lets you give different AI apps or people different access. How many servers you can have depends on your plan: 1 on Free, 5 on Pro, unlimited on Agency. See [MCP server limits on each plan](/mcp-servers/plan-limits). ## Common set-ups ### One for you, with everything - **Account access:** **All accounts** - **Allow changes:** ticked Your everyday link. New accounts you connect are included automatically. Changes still depend on each account's switch and your approval in the chat. ### One per client - **Name:** the client's name, for example "Acme (client)" - **Account access:** **Selected accounts**, ticking only that client's accounts (their Google Ads, Analytics, Zendesk and so on) - **Allow changes:** your choice In a chat that uses this link, the AI can only see that client's connections, so another client's data can't come up by mistake. > [!IMPORTANT] > A server chooses whole connections, not single ad accounts inside them. If one Google login (for example a Google Ads manager account) reaches several clients, every server that includes that connection reaches all of them. Hiding an ad account under **Show sites & accounts** hides it on every server, not just one. To keep clients fully apart, connect each client with its own login (for example an access grant on the client's own account) and put only that connection in their server. See [Agencies](/use-cases/agencies). ### A read-only server to share - **Account access:** **Selected accounts**, ticking only what the other person should see - **Allow changes:** unticked The badge shows **Read & draft only**. Whoever uses this link can read those accounts and write email drafts, but can't send email, update tickets or book events, whatever the account switches say. It can still archive, label and mark emails in the mailboxes it reaches. This suits a server you share with a client or colleague. > [!IMPORTANT] > Each AI app must sign in to **your** Plugsight account and click **Allow access** before it can use a server. A server with an API key can also be used by anyone who has the key, so share a key only with people you trust, and revoke it when they no longer need it. See [API keys](/mcp-servers/api-keys). ### One per AI app For example, "Claude" and "Cursor". Then **Disconnect all AI apps** on one server doesn't affect the other, and **Activity** shows which server each request came through. ## Tips - **Name servers clearly.** The name is what your AI app shows for the connector, and what **Activity** shows under **Who** ("via Work"). - **Selected accounts don't grow by themselves.** When you connect a new account, tick it in each server that should reach it. - **One account can be in many servers.** Connecting an account once is enough; add it to as many servers as you like. - **Check what a link reaches.** Ask your AI "list my Plugsight accounts" to see exactly what the server it's using can reach. - **Account switches apply everywhere.** The switch on **Connections** belongs to the account, not the server. A server with **Allow changes** unticked never makes changes, but a server with it ticked follows each account's switch. ## Related articles - [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts): keep individual sites or ad accounts away from your AI. - [Create an MCP server](/mcp-servers/create) - [Edit an MCP server](/mcp-servers/edit) - [Read-only connectors](/permissions/read-only-connectors) --- # MCP server limits on each plan URL: https://docs.plugsight.app/mcp-servers/plan-limits How many MCP servers each Plugsight plan includes, what happens at the limit, and what happens after a downgrade. | Plan | MCP servers | Connections | Allow changes on a server | | --- | --- | --- | --- | | **Free** | 1 | 2 | Not available (on the Pro plan) | | **Pro** | 5 | 10 | Available | | **Agency** | Unlimited | 50 | Available | You can see how many you're using on **Billing**, under **Your plan**: for example "MCP servers 1 of 5", with a bar that fills up as you approach the limit. ## At the limit When you already have as many servers as your plan allows, creating another shows a message such as: - "Your Free plan includes 1 MCP server. Upgrade to Pro for 5." - "Your Pro plan includes 5 MCP servers. Upgrade to Agency for unlimited." Everything you already have keeps working; nothing is switched off when you reach the limit. To add another server, delete one you no longer use, or upgrade under **Billing**. See [Upgrade your plan](/account/upgrade). ## Allow changes on the Free plan On Free, the **Allow changes** box on the server form is greyed out and shows **(on the Pro plan. See plans)**. Your AI can read every account the server reaches and write email drafts, but can't send email, update helpdesk tickets or book events. ## After a downgrade or cancellation If you move to a plan with fewer servers, for example when a paid plan ends and you're back on Free: - Servers you already have stay, with their links and settings. - You can't create more until you're below the new limit. - Sending email and other changes stop working in your AI, because they're part of the Pro and Agency plans. - Marketing and analytics connectors work within Free's allowance: 25 marketing tool calls a month, and no more than 1 marketing connection added. Ready-made deep dives need Pro or Agency. See [Cancel your plan](/account/cancel). ## Related articles - [Plans and billing](/account/plans-and-billing) - [Use several MCP servers](/mcp-servers/multiple-servers) --- # Permissions & safety URL: https://docs.plugsight.app/permissions How Plugsight keeps your AI to reading until you allow more, and every control you have over what it may change. Your AI can always **read** the accounts an MCP server reaches, and write email drafts. Sending email, changing helpdesk tickets and booking calendar events are off until you allow them, and each one then waits for your yes in the chat. ## The controls at a glance | Control | Where | What it does | | --- | --- | --- | | **Account switch** | **Connections**, under **Write access** | The everyday setting: may the AI change things with this one account? Starts off for every account. | | **Allow changes** | **MCP servers** → a server → **Edit configuration** | Untick it to make a server read-only, whatever the account switches say. | | **Approval in the chat** | Your AI app | The AI shows you the exact email or change and waits for your yes. | | **Pause** and **Pause everything** | **Permissions** | An emergency stop for one type of change, or all of them at once. | | **Daily email limit** | **Permissions** → **Daily email limit** | How many emails each account may send in a rolling 24 hours. 20 by default. | | **Your plan** | **Billing** | Sending and other changes are part of the Pro and Agency plans. | | **Activity** | **Activity** | A record of every sign-in, settings change, read and write, kept for one year. | ## In this section - [How changes are allowed](/permissions/how-changes-are-allowed): every condition that must be met before your AI can send or change anything. - [Switch states under each account](/permissions/switch-states): what **Ready**, **Paused**, **Off**, **Not in any MCP server** and **Not yet** mean. - [Pause changes](/permissions/pause): the emergency stop, the red notice and **Resume**. - [Read-only connectors](/permissions/read-only-connectors): the types of account your AI can never change. - [Daily email limit](/permissions/daily-email-limit): how the rolling 24-hour limit works and how to change it. - [Approvals in the chat](/permissions/approvals): how your AI asks before each change. - [When a change is blocked](/permissions/blocked-changes): the exact messages your AI receives, and the fix for each. - [Activity log](/permissions/activity): what's recorded, the filters, and what **Succeeded**, **Blocked** and **Failed** mean. --- # How changes are allowed URL: https://docs.plugsight.app/permissions/how-changes-are-allowed Everything that must be true before your AI can send an email, update a ticket or book an event, and where to set each one. Your AI can always read, and write email drafts. Before it can **send or change** anything, all of these must be true: 1. **Your plan includes changes.** Sending email, helpdesk changes and calendar bookings are on the Pro and Agency plans. 2. **The account's switch is on**, on **Connections**. 3. **The MCP server allows changes**: **Allow changes** is ticked on the server your AI app uses. 4. **Nothing is paused** on **Permissions**. 5. **You approve the change in the chat.** For email, one more: the account must have sends left under its [daily email limit](/permissions/daily-email-limit). If any one of these isn't met, the change is blocked, nothing is sent or changed, and the attempt shows as **Blocked** in **Activity**. > [!TIP] > You don't need to check all of these yourself. On **Connections**, the line under each account's switch says **Ready** when changes can happen, or names the one thing still stopping them. See [Switch states under each account](/permissions/switch-states). ## 1. Your plan Changes are part of the Pro and Agency plans. On Free: - Your AI can read what you connect and write email drafts. Marketing and analytics connectors work within Free's allowance: 1 marketing connection and 25 marketing tool calls a month. - The account switch on **Connections** shows a lock and **Upgrade**, for example **Drafts only · Upgrade**. - **Allow changes** on the server form is greyed out with **(on the Pro plan. See plans)**. - On **Permissions**, the types that can make changes show **On the Pro plan**. See [Plans and billing](/account/plans-and-billing). ## 2. The account's switch Every account that can make changes has a switch under **Write access** on **Connections**. It starts off for every account you connect. It's the main, everyday control: one switch per account. | Type of account | Switch off | Switch on | | --- | --- | --- | | Email | **Drafts only** | **Can send** | | Helpdesk (Zendesk) | **Read-only** | **Can reply & update** | | Calendar | **Read-only** | **Can book & change** | | [Custom API](/connectors/custom-api) | **Read-only** | **Can make changes** | | [Custom MCP server](/connectors/custom-mcp) | **Read-only** | **Can make changes** | To turn it on, click the switch. Turning it on or off is recorded in **Activity**. Accounts that can never make changes show a fixed **Read-only** label with a lock instead of a switch. That has two possible reasons: - **The service only reads.** Marketing and analytics, email marketing, e-commerce, docs and files, and contacts. Google Calendar is read-only too until Google approves its booking permission; Outlook and iCloud calendars can book. See [Read-only connectors](/permissions/read-only-connectors). - **The account was connected with read access only.** For example, an Outlook account connected before sending was allowed, or a calendar where the extra permission wasn't ticked. Click **Read-only** to see how to allow changes: reconnect it and tick the extra permission when the provider asks. Nothing is lost; your settings stay. ## 3. The MCP server's Allow changes Each MCP server has an **Allow changes** box. It's ticked by default for new servers. - **Ticked** (badge **Can make changes**): the AI may make changes through this server, with accounts whose switch is on, after you approve each one. - **Unticked** (badge **Read & draft only**): the AI can read the server's accounts and write email drafts, but can't send email, update tickets or book events through this server, whatever the account switches say. Archiving, labelling and marking emails still work (see below). Change it in **MCP servers** → the server → **Edit configuration**. See [Edit an MCP server](/mcp-servers/edit). ## 4. Nothing paused **Pause** on the **Permissions** page is an emergency stop. It overrides every account switch of its type. While anything is paused, every page in the app shows a red notice with **Resume**. See [Pause changes](/permissions/pause). ## 5. Your approval in the chat Before each change, your AI shows you exactly what it's about to do (the email with its recipients, subject and body, the ticket reply, the event details) and waits for your yes. Plugsight refuses a send or change that the AI hasn't marked as approved by you. See [Approvals in the chat](/permissions/approvals). ## Archiving, labelling and marking emails Archiving, labelling, moving and marking emails read or unread, and flagging them, can be undone, so they work differently: - They need a plan that includes changes (Pro or Agency). - They don't need the account's switch or the server's **Allow changes**. - They stop when email changes, or everything, are paused on **Permissions**. - They don't count towards the daily email limit. Your AI does a handful of these when you ask. Before moving emails to the trash, or changing more than 10 emails, it tells you what will happen and asks first. ## Related articles - [Switch states under each account](/permissions/switch-states) - [Pause changes](/permissions/pause) - [When a change is blocked](/permissions/blocked-changes) - [Approvals in the chat](/permissions/approvals) --- # Switch states under each account URL: https://docs.plugsight.app/permissions/switch-states What Ready, Paused, Off, Not in any MCP server and Not yet mean under an account's switch on Connections, and how to fix each. On **Connections**, each account that can make changes has a switch in the **Write access** column. The line under the switch says plainly whether your AI can make changes with that account now, and if not, the one thing to fix next. ## The states ### Ready > Ready: your AI asks you in the chat before each change. **What it means:** everything is in place. The switch is on, the account is in at least one MCP server that allows changes, and nothing is paused. Your AI can send or make changes with this account, after you approve each one in the chat. **What to do:** nothing. To stop changes for this account, click the switch to turn it off. ### Off > Off: your AI can read and write drafts, but can't change anything. (For helpdesk and calendar accounts: "Off: your AI can read, but can't change anything.") **What it means:** the account's switch is off. The switch shows **Drafts only** for email and **Read-only** for helpdesk and calendar accounts. This is how every account starts. **How to allow changes:** click the switch. It changes to **Can send**, **Can reply & update** or **Can book & change**. ### Not in any MCP server > Not in any MCP server yet. Add it to one on MCP servers. **What it means:** the switch is on, but no MCP server includes this account, so no AI app can reach it at all. **How to fix it:** open **MCP servers**, then either set a server to **All accounts**, or open a server's **Edit configuration**, tick this account under **Selected accounts** and click **Save changes**. ### Not yet > Not yet: the MCP servers with this account are read-only. To allow changes, open one on MCP servers → Edit configuration → tick Allow changes. **What it means:** the switch is on and the account is in one or more MCP servers, but every one of those servers has **Allow changes** unticked. **How to fix it:** open one of those servers on **MCP servers**, go to **Edit configuration**, tick **Allow changes** and click **Save changes**. If you made the server read-only on purpose (for example, one you share with a client), leave it, and use a different server for changes. ### Paused The switch itself shows **Paused**, greyed out. **What it means:** this type of change, or every change, is paused on the **Permissions** page. A pause is an emergency stop: while it's on, your AI can't make these changes with any account, whatever the switch says. Your AI can still read and search the account, and write drafts for email. **How to fix it:** click the greyed-out switch. A box explains the pause and offers **Resume** (or **Resume all** when everything is paused) and **Keep paused**. When you resume, the account goes back to exactly the switch setting you left it on. You can also resume on **Permissions**, or from the red notice at the top of every page. See [Pause changes](/permissions/pause). > [!NOTE] > Turning the switch off and on doesn't undo a pause. Only **Resume** does. ## Labels without a switch ### Read-only (with a lock) The account can't make changes, so there's no switch. Click **Read-only** to see why: - **"Why is this read-only?"** Plugsight only reads this service. See [Read-only connectors](/permissions/read-only-connectors). - **"How to allow changes"** The account was connected with read access only. Reconnect it and tick the extra permission when the provider asks. The box has a **Reconnect** button. Nothing is lost; your settings stay. ### Drafts only · Upgrade (or Read-only · Upgrade) Your plan doesn't include changes. Your AI can read the account (and write drafts, for email). Click it and choose **See plans** to upgrade. See [Plans and billing](/account/plans-and-billing). ## Still can't make a change when it says Ready? - Make sure your AI app is using an MCP server that includes the account. With several servers, the account must be in the one your AI app is connected to. - For email, check the account has sends left under the [daily email limit](/permissions/daily-email-limit). - Every change waits for your yes in the chat. See [Approvals in the chat](/permissions/approvals). - Your AI's message names what's missing. See [When a change is blocked](/permissions/blocked-changes). Fixing any of these works straight away. You don't need to refresh your AI app. ## Related articles - [How changes are allowed](/permissions/how-changes-are-allowed) - [Pause changes](/permissions/pause) - [Edit an MCP server](/mcp-servers/edit) --- # Pause changes URL: https://docs.plugsight.app/permissions/pause Use Pause or Pause everything as an emergency stop for sending and changes, what keeps working, and how to Resume. **Pause** is an emergency stop. From the moment you confirm, your AI can't make the paused changes, even for accounts whose switch on **Connections** is on. Your AI keeps reading, and one tap on **Resume** puts everything back. Day to day you don't need it: each account's switch on **Connections** decides what your AI may change. Pause is for the moment you want changes to stop right now, without touching any of those switches. ## When to pause - Something in **Activity** looks wrong. - You're testing prompts and want to be sure nothing goes out. - Someone else is using your AI chat. - You're away and want everything held. ## The Emergency stop panel Open **Permissions**. The **Emergency stop** panel lists each type of account with: | Column | What it shows | | --- | --- | | **Connector type** | Email, Helpdesk, Calendar, and the read-only types. | | **What it covers** | The changes this type can make, for example "Send emails and drafts; archive, label and mark emails". | | **Your accounts** | For example "1 of 2 can make changes", or **None connected**. | | **Status** | **Active**, **Paused**, **Read-only**, **Allowed once connected**, **On the Pro plan** or **Not available yet**. | What each status means: | Status | Meaning | | --- | --- | | **Active** | Changes of this type can happen, for accounts whose switch is on. | | **Paused** | This type, or everything, is paused. | | **Read-only** | This type only reads, so there's nothing to pause. | | **Allowed once connected** | You haven't connected an account of this type yet. When you do, its switch on **Connections** starts off. | | **On the Pro plan** | Your plan doesn't include changes, so there's nothing to pause. | | **Not available yet** | Changes of this type are switched off on Plugsight for everyone right now. Your AI can still read these accounts. | ## Pause one type 1. Open **Permissions**. 2. In the **Emergency stop** panel, click **Pause** on the type's row (Email, Helpdesk or Calendar). 3. Read the box that opens, then click **Pause**. ## Pause everything 1. Open **Permissions**. 2. Click **Pause everything** at the top of the **Emergency stop** panel. 3. Read the **Pause all changes?** box, then click **Pause everything**. The panel then shows **Everything is paused.** No connector can send or make changes until you resume. While everything is paused, the per-type buttons are held; tapping one explains that you need to click **Resume all** first. ## What the pause box tells you Before anything is paused, Plugsight shows what the pause will do: - **What stops**: each type covered, with the changes it makes. - **Accounts affected**: every account of those types that can make changes. If none are connected, any you add later are paused too, until you resume. - **What keeps working**: - Your AI can still read and search everything, and write email drafts. - Your account switches and MCP servers stay exactly as they are. - Nothing already sent or changed is undone. - **How to undo**: click **Resume**, on **Permissions** or on the red notice. ## While a pause is on - **A red notice at the top of every page** says, for example, **All changes are paused.** or **Email changes are paused.**, followed by "Your AI can still read and write drafts, but can't send or change anything there, whatever the account switches say." It has a **Resume** (or **Resume all**) button and a **Manage** link to **Permissions**. - **On Connections**, the affected accounts' switches show **Paused**, greyed out. - **In your AI app**, any attempt to send or change something of that type is blocked with a message such as "All write actions are paused for this account (Permissions page)." Email sends suggest saving a draft instead. - **In Activity**, blocked attempts show as **Blocked**, and the pause itself is recorded, for example "Paused all writes". A pause also stops archiving, labelling and marking emails when email (or everything) is paused. ## Resume Any of these puts changes back straight away: - On **Permissions**, click **Resume all** (when everything is paused) or **Resume** on a type's row. - Click **Resume** or **Resume all** on the red notice at the top of any page. - On **Connections**, click a greyed-out **Paused** switch, then **Resume**. Each account goes back to exactly the switch setting it had before. Nothing else changes. ## Pause or the account switch? | Use | When | | --- | --- | | **The account switch** (on **Connections**) | Everyday choices, like letting one inbox send but not another. | | **Pause** (on **Permissions**) | Stopping everything of a type at once, for example while you check something that looks wrong, or before handing your AI to someone else. | A pause always wins over the account switch. Turning an account's switch on doesn't undo a pause; click **Resume**. ## Common questions ### Does pausing cancel anything already sent? No. It stops new changes from that moment on. Anything already sent or updated stays as it is. **Activity** lists every change your AI made. ### Why do some types have no Pause button? They only read. Marketing and analytics, contacts, files, stores and email marketing can't change anything in your accounts, so there's nothing to pause. Their row says "Nothing to pause: AI apps only read here". ### I resumed, but the AI still can't send or change anything Look under the account's switch on **Connections**: it says **Ready**, or names the one thing still stopping it. See [Switch states under each account](/permissions/switch-states). ## Related articles - [How changes are allowed](/permissions/how-changes-are-allowed) - [Switch states under each account](/permissions/switch-states) - [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete) --- # Read-only connectors URL: https://docs.plugsight.app/permissions/read-only-connectors Which types of connected account your AI can only read, never change, and how that differs from a read-only account or server. Some types of account only ever read. Your AI can search them and answer questions with their data, but Plugsight can't change anything in them. There's no switch to turn on and nothing to pause. ## Which types are read-only | Type | Examples | What your AI can do | | --- | --- | --- | | **Marketing & analytics** | Google Ads, Microsoft Advertising, Meta Ads, LinkedIn Ads, Google Search Console, Google Analytics 4, Google Tag Manager, YouTube, Google Merchant Center | Read reports and settings. Plugsight never creates, edits or pauses campaigns, bids or budgets. | | **Email marketing** | Mailchimp | Read audiences, campaigns and results. | | **E-commerce** | WooCommerce, Magento | Read orders, sales, products and customers. | | **Docs & files** | Google Drive, Google Sheets, Google Docs, Google Forms, Google Meet | Read documents, spreadsheets, forms and meeting transcripts. | | **Contacts** | Google Contacts, Outlook Contacts, iCloud Contacts | Look people up. | The types that can make changes are **Email** (send, plus archive, label and mark), **Helpdesk & support** (Zendesk replies, notes, new tickets, updates and macros), **Calendar** (book, move and cancel events; for Google Calendar, once Google approves the booking permission) and **Custom APIs and MCP servers** (POST, PUT, PATCH and DELETE requests to APIs you connected yourself, and the tools of your own MCP servers that the server doesn't mark read-only; reading is always allowed, and every change needs your approval in the chat). > [!NOTE] > Google Ads and Google Merchant Center only offer a permission that includes edit rights. Plugsight uses it for reading only and never creates, changes or deletes anything there. See [Permissions Plugsight asks Google and Microsoft for](/security/provider-permissions). ## Where you see it - **Connections**: these accounts show a fixed **Read-only** label with a lock instead of a switch. Clicking it explains: "Plugsight only reads [service] here, so there's no switch to turn on." - **Permissions**: these types show the status **Read-only** and "Reads only. AI apps can't change anything here." Their row says "Nothing to pause: AI apps only read here". ## Three different kinds of "read-only" | | What's read-only | How to change it | | --- | --- | --- | | **Read-only connector type** | Every account of that type, always | It can't be changed. | | **Account connected with read access only** | One account, for example an Outlook account or calendar connected without the permission to send or book | Click **Read-only** on **Connections** and reconnect, ticking the extra permission when the provider asks. | | **Read-only MCP server** | Everything reached through one server | Tick **Allow changes** in the server's **Edit configuration**. | A read-only MCP server still lets the AI write email drafts. See [Edit an MCP server](/mcp-servers/edit). ## Related articles - [How changes are allowed](/permissions/how-changes-are-allowed) - [Switch states under each account](/permissions/switch-states) - [Use several MCP servers](/mcp-servers/multiple-servers) --- # Daily email limit URL: https://docs.plugsight.app/permissions/daily-email-limit How many emails your AI may send from each account in a rolling 24 hours, how to change the limit, and how usage is shown. The daily email limit protects you from runaway sending. It sets how many emails your AI apps may send from **each** email account in 24 hours. - **Default:** 20 per account. - **Range:** 1 to 500. - **Drafts never count.** Your AI can always save drafts. - **Every send still needs your approval in the chat.** ## Change the limit 1. Open **Permissions**. 2. Scroll to **Daily email limit**. 3. In **Emails per account, per 24 hours**, type a whole number from 1 to 500. 4. Click **Save**. Plugsight shows, for example, **Saved: up to 50 emails per account per 24 hours.** The new limit applies to the next send. The change is recorded in **Activity**, for example "Changed the daily email limit from 20 to 50 per account". To go back to the default, click **Reset to 20** (shown when you've set your own number). Plugsight shows **Back to the default: 20 a day.** The limit is the same for every email account you connect; you can't set a different limit per account. > [!WARNING] > Your email provider has its own daily limits too. Gmail allows about 500 a day; Google Workspace and Microsoft 365 allow more. A very high number here can get an account temporarily blocked by the provider. ## How the 24 hours work The 24 hours roll: there's no fixed reset time. Each email counts for 24 hours after it's sent, then frees up a send. For example, with a limit of 20: if you sent 5 emails at 9:00 and 15 at 14:00, you're at 20 of 20. At 9:00 the next day, the first 5 stop counting and 5 sends free up. At 14:00, the other 15 do. Only emails that were actually sent count. Blocked or failed attempts don't. ## See how much you've used Under the limit, **Used in the last 24 hours** lists each email account with a meter and a count, such as **7 of 20 sent**. The line under each one says: | Message | What it means | | --- | --- | | None sent in the last 24 hours: all 20 available. | Nothing sent from this account in the last 24 hours. | | 13 left. The oldest send stops counting today at 3:42 PM (in 2 h 10 min). | Some sends used. When the oldest one is 24 hours old, it frees up. | | Limit reached. The next send frees up tomorrow at 9:10 AM (in 5 h 3 min). | No sends left. Your AI can save drafts until then. | | Sending is off for this account (drafts only). Turn it on under Connections. | The account's switch is off, so it can't send at all. | Times are shown in your own time zone. ## When the limit is reached Your AI gets this message, and the attempt shows as **Blocked** in **Activity**: > Daily limit reached: "[account]" sent 20 emails in the last 24 hours (limit 20, which you can change on the Permissions page). Save it as a draft instead. **How to fix it:** wait until the next send frees up (shown under **Used in the last 24 hours**), raise the limit on **Permissions**, or ask your AI to save the email as a draft and send it yourself. ## Errors when saving ### Enter a whole number from 1 to 500. **What it means:** the box holds a number outside 1 to 500, or one with decimals. **Save** stays greyed out until it's fixed. **How to fix it:** type a whole number from 1 to 500. ### The limit can be at most 500 emails a day per account. **What it means:** the number is above the maximum. **How to fix it:** enter 500 or less. ## What counts | Counts towards the limit | Doesn't count | | --- | --- | | Sending a new email, reply or forward | Saving a draft | | Sending an existing draft | Archiving, labelling, moving or marking emails | | | Helpdesk replies and calendar bookings | | | Blocked or failed attempts | ## Related articles - [How changes are allowed](/permissions/how-changes-are-allowed) - [Approvals in the chat](/permissions/approvals) - [Activity log](/permissions/activity) --- # Approvals in the chat URL: https://docs.plugsight.app/permissions/approvals How your AI asks for your yes before each email, ticket change or booking, and what Plugsight does if it doesn't. Every change your AI makes waits for your approval in the chat, even when everything else allows it. This is the last of the checks in [How changes are allowed](/permissions/how-changes-are-allowed). ## How it works 1. You ask your AI to do something, for example "Reply to Sam and say Thursday works." 2. Your AI prepares the change and shows it to you in the chat, then waits. 3. You check it and say yes (or ask for edits, or say no). 4. Only after your yes does the AI ask Plugsight to make the change. Plugsight checks every other safety setting, then sends it. Plugsight refuses a send or change that the AI hasn't marked as approved by you. If the AI tries anyway, nothing happens and the attempt shows as **Blocked** in **Activity**, with a message such as "Not sent: show the user the final email and set confirm: true only after they explicitly approve." ## What the AI must show you first | Change | What you see before you approve | | --- | --- | | Send an email (new, reply or forward) | The From account, To, Cc, Bcc, subject, full body and attachment names | | Send an existing draft | The draft | | Zendesk reply or internal note | The exact text and the ticket | | Zendesk ticket update | The exact changes (status, priority, assignee, tags and so on) | | Zendesk macro | A preview of what the macro will change | | New Zendesk ticket | The exact ticket details | | Book, move or cancel a calendar event | The exact event details or changes, or which event will be cancelled | The AI is told never to send or change anything on its own initiative. ## Archiving, labelling and marking emails For a handful of emails you asked about, your AI makes these changes and tells you what it did. Before moving emails to the trash, or changing more than 10 emails, it says what will happen and gets your yes first. ## Drafts Saving a draft doesn't need approval: nothing leaves your account. Drafts appear in the account's Drafts folder, and you can send them yourself, or ask your AI to send one (which then needs your approval). ## Your AI app's own permission prompt Separately, the first time your AI uses a Plugsight tool, your AI app may ask whether to allow it. Choose **Allow**. That prompt comes from your AI app, not Plugsight, and it doesn't replace your approval of each change. ## Tips - Read the whole message before saying yes, especially the recipients. - If you're testing prompts and want to be sure nothing goes out, use **Pause everything** on **Permissions**. See [Pause changes](/permissions/pause). - Every approved change, and every blocked attempt, is listed in [Activity](/permissions/activity). ## Related articles - [How changes are allowed](/permissions/how-changes-are-allowed) - [When a change is blocked](/permissions/blocked-changes) - [Daily email limit](/permissions/daily-email-limit) --- # When a change is blocked URL: https://docs.plugsight.app/permissions/blocked-changes The exact messages your AI receives when Plugsight blocks a send or change, what each one means and how to fix it. When one of your safety settings stops a send or change, nothing is sent or changed. Your AI receives a message naming the reason, and usually tells you. The attempt appears in **Activity** as **Blocked**, with the same message under the badge. Fixing the cause works straight away. You don't need to refresh your AI app; ask it to try again. In the messages below, `[account]` is the account's short name and `[server]` is the MCP server's name. ## Plan ### Sending email and changing helpdesk tickets are on the Pro plan. Upgrade under Billing to turn write access on. **What it means:** your plan doesn't include changes. The message ends with a link to **Billing**. **How to fix it:** upgrade to Pro or Agency under **Billing**. See [Upgrade your plan](/account/upgrade). Your AI can still read and write drafts on Free. ## Pause ### All write actions are paused for this account (Permissions page). **What it means:** **Pause everything** is on. For emails, the message adds "Save it as a draft instead." **How to fix it:** click **Resume all** on **Permissions**, or on the red notice at the top of any page. See [Pause changes](/permissions/pause). ### Email sending is paused (Permissions page). Save it as a draft instead. **What it means:** email changes are paused. **How to fix it:** click **Resume** on the Email row on **Permissions**, or on the red notice. ### Email changes are paused (Permissions page). **What it means:** email changes are paused, so archiving, labelling and marking emails is stopped too. **How to fix it:** click **Resume** on the Email row on **Permissions**. ### Helpdesk replies and updates are paused (Permissions page). **What it means:** helpdesk changes are paused. **How to fix it:** click **Resume** on the Helpdesk row on **Permissions**. ### Calendar changes are paused (Permissions page). **What it means:** calendar changes are paused. **How to fix it:** click **Resume** on the Calendar row on **Permissions**. ## MCP server ### The "[server]" MCP is set to drafts only. Save it as a draft instead. **What it means:** the MCP server your AI app uses has **Allow changes** unticked, so it can't send email. **How to fix it:** on **MCP servers**, open the server, go to **Edit configuration**, tick **Allow changes** and click **Save changes**. If the server is read-only on purpose, use a different server for sending. ### The "[server]" MCP is read-only. Allow changes on the MCP server first (MCP servers page). **What it means:** the same, for a helpdesk or calendar change. **How to fix it:** tick **Allow changes** on that server, as above. ## Account switch ### Sending is off for "[account]". Turn it on under Connections, or save it as a draft. **What it means:** the email account's switch is on **Drafts only**. **How to fix it:** on **Connections**, click the account's switch so it shows **Can send**. ### Changes are off for "[account]". Allow them under Connections first. **What it means:** the helpdesk or calendar account's switch is off. **How to fix it:** on **Connections**, click the account's switch so it shows **Can reply & update** or **Can book & change**. ## Daily email limit ### Daily limit reached: "[account]" sent 20 emails in the last 24 hours (limit 20, which you can change on the Permissions page). Save it as a draft instead. **What it means:** this account has used all its sends for the rolling 24 hours. **How to fix it:** wait for the next send to free up, or raise the limit. See [Daily email limit](/permissions/daily-email-limit). ## Approval ### Not sent: show the user the final email and set confirm: true only after they explicitly approve. **What it means:** the AI tried to send without marking it as approved by you. Similar messages start "Not sent", "Not posted", "Not updated", "Not applied", "Not created", "Not booked", "Not changed" or "Not cancelled". **How to fix it:** ask your AI to show you the email or change first, then say yes. See [Approvals in the chat](/permissions/approvals). ## Not available ### Sending is turned off on this server. Save it as a draft instead. **What it means:** sending email is switched off on Plugsight for everyone right now. **Permissions** shows **Not available yet** for Email. **How to fix it:** there's nothing for you to turn on. Save the email as a draft and send it from your email app. ## Related articles - [How changes are allowed](/permissions/how-changes-are-allowed) - [Switch states under each account](/permissions/switch-states) - [Activity log](/permissions/activity) --- # Activity log URL: https://docs.plugsight.app/permissions/activity What the Activity page records, how to search and filter it, and what Succeeded, Blocked and Failed mean. **Activity** lists everything on your account, newest first: sign-ins, changes you made, and every read and write AI apps made through your MCP servers. Entries are kept for one year. ## What's recorded - **Sign-ins**, including failed attempts and blocked attempts (too many tries), sign-in links and password reset requests, and signing out. - **Your changes** to connections, MCP servers, settings and your account: for example adding or removing an account, turning an account's switch on or off, creating or editing a server, creating or revoking an API key, disconnecting AI apps, pausing or resuming, changing the daily email limit, changing your password and starting checkout. - **Approvals**: each time you clicked **Allow access** for an AI app, for example "Allowed "Claude" to use "Work"". - **Every tool an AI app used**: searches, reads, drafts, sends, archiving and labelling, helpdesk updates, calendar bookings and report requests. For example "Searched email in "work" for "invoice"" or "Sent an email "Thursday" to sam@example.com in "work"". What isn't recorded: email bodies, attachments and report contents. Activity shows what was done, never the content. See [What Plugsight stores and logs](/security/data-handling). ## Read an entry | Column | What it shows | | --- | --- | | **Time** | When it happened, in your own time zone, for example "17 Nov 2026, 10:42". Hover over it to see the time in UTC. The IP address it came from is shown underneath, when there is one. | | **What happened** | A one-line summary. | | **Who** | **You** for things you did in the app (with the MCP server's name underneath when it was about a server), or the AI app's name, such as Claude or ChatGPT, with "via [server name]" underneath. Calls made with the Developer API show as "Developer API". | | **Result** | **Succeeded**, **Blocked** or **Failed**. | ## What the results mean | Result | Meaning | | --- | --- | | **Succeeded** | It worked: the read or change went through. | | **Blocked** | One of your own safety settings stopped it before anything happened: the account's switch was off, the MCP server is read-only, changes were paused, the daily email limit was reached, or the change wasn't approved. Nothing was sent or changed. | | **Failed** | The service refused it or didn't answer, for example an expired sign-in, a wrong recipient address or a ticket that no longer exists. Nothing was changed. | For **Blocked** and **Failed**, the reason is shown under the badge, and the **ⓘ** next to it explains the result. If a failure says to reconnect, do that on **Connections**. For the blocked messages and their fixes, see [When a change is blocked](/permissions/blocked-changes). ## Search and filter At the top of the page: - **Search what happened…**: type any words. It matches the summary, the kind of event and the MCP server's name. - **Result**: **Any result**, **Succeeded**, **Blocked** or **Failed**. - **Category chips**: **All**, **AI apps**, **Sign-ins**, **Connections**, **MCP servers**, **Settings** and **Account**. Filters combine: for example, **AI apps** with **Blocked** shows only what your safety settings stopped. If nothing matches, the page says **No matches**. Click **Clear filters** to see everything again. The page loads the newest entries first. Click **Load more** at the bottom for older ones. ## How long entries are kept One year. Older entries are deleted automatically. If you delete your Plugsight account, its activity entries are kept until they reach one year old, with only the email address the account had, for security. See [Delete your account](/account/delete-account). ## Ways to use it - **Check what your AI did** after a session, filtered to **AI apps**. - **Find out why something didn't happen**: filter to **Blocked** or **Failed** and read the reason under the badge. - **Spot sign-ins you don't recognise**: filter to **Sign-ins** and check the times and IP addresses. If something looks wrong, change your password and use **Pause everything**. ## Related articles - [When a change is blocked](/permissions/blocked-changes) - [Pause changes](/permissions/pause) - [What Plugsight stores and logs](/security/data-handling) --- # Account & billing URL: https://docs.plugsight.app/account Sign in, confirm your email, change your password or profile, delete your account, and manage your plan and invoices. Your Plugsight account holds your connections, MCP servers and settings. You manage it on two pages in the app: - **Settings** (shown as **Account settings**): your profile, password and deleting the account. - **Billing**: your plan, usage, upgrades, invoices and cancelling. ## Your account - [Sign in to Plugsight](/account/sign-in): password, email link, Google or Microsoft. - [Confirm your email](/account/verify-email): why and how, and what to do if the email doesn't arrive. - [Change or reset your password](/account/password): what it signs out, and what stays connected. - [Profile and email address](/account/profile): change your name, or the email you sign in with. - [Delete your account](/account/delete-account): what's deleted, and what happens to your plan. ## Plans and billing - [Plans and billing](/account/plans-and-billing): Free, Pro and Agency, and what each includes. - [Upgrade your plan](/account/upgrade): paying with Stripe Checkout, monthly or yearly. - [Team members](/account/team): invite people on Agency, with Owner, Admin and Member roles. - [Invoices, card and plan changes](/account/manage-billing): the Stripe billing portal. - [When a payment fails](/account/failed-payment): what keeps working while Stripe retries. - [Cancel your plan](/account/cancel): what happens at the end of the period. - [Emails Plugsight sends you](/account/emails): every account and billing email, and when it's sent. --- # Sign in to Plugsight URL: https://docs.plugsight.app/account/sign-in The four ways to sign in - password, emailed sign-in link, Google or Microsoft - and fixes for every sign-in error. Plugsight is at [app.plugsight.app](https://app.plugsight.app). You can sign in four ways, and use whichever is handiest each time. They all lead to the same account as long as the email address is the same. ## Ways to sign in ### Email and password 1. Open the **Sign in** page. 2. Enter your **Email** and **Password**. 3. Click **Sign in**. Signed up with Google, Microsoft or an email link and want a password too? Set one under **Settings** → **Set a password**. See [Change or reset your password](/account/password). ### Email me a sign-in link No password needed. 1. On the **Sign in** page, enter your **Email**. 2. Click **Email me a sign-in link**. 3. Open the email "Your Plugsight sign-in link" and click **Sign in**. The link works once and expires in **20 minutes**. If you click **Email me a sign-in link** without typing an email, Plugsight asks you to enter it first. If sign-ups are open and the address has no account yet, the link creates one. ### Continue with Google 1. On the **Sign in** or **Create your account** page, click **Continue with Google**. 2. Choose your Google account and continue. Plugsight only asks Google for your name, email address and a stable ID, to know who you are. Signing in with Google doesn't connect your Gmail or any other Google service; you connect those separately on **Connections**. ### Continue with Microsoft 1. Click **Continue with Microsoft**. 2. Choose your Microsoft account and continue. As with Google, this only tells Plugsight who you are. It doesn't connect Outlook. > [!NOTE] > Plugsight only trusts an email address that Google or Microsoft has verified. If you sign in with Google or Microsoft using the same email as an existing Plugsight account, you get into that account. ## Create an account 1. Open the **Create your account** page (**Create an account** on the **Sign in** page). 2. Either click **Continue with Google** or **Continue with Microsoft**, or fill in **Full name**, **Work or personal email** and **Password** (at least 10 characters), then click **Create account**. 3. If you used a password, confirm your email. See [Confirm your email](/account/verify-email). If sign-ups are closed, the page says so and asks you to email info@plugsight.app to be told when they open. ## Signing out and sessions A sign-in on a browser lasts up to 30 days, then you sign in again. Changing your password signs you out everywhere. Signing in to Plugsight is separate from your AI apps: they keep their own access to your MCP servers. ## Sign-in errors ### Wrong email or password. **What it means:** the email and password don't match an account. **How to fix it:** check for typos, or click **Forgot password?** to reset it. If you signed up with Google, Microsoft or an email link, you may not have a password: use that method instead, or use **Email me a sign-in link**. ### Too many attempts. Try again in 15 minutes. **What it means:** in the last 15 minutes there were too many sign-in attempts from your network, too many wrong passwords for this email from your network, or many wrong passwords for this email from all networks together. This protects your account from password guessing. A few wrong guesses from someone else's network don't block you; a large number spread across many networks blocks the email everywhere for 15 minutes. The blocked attempt is recorded in **Activity**. **How to fix it:** wait 15 minutes, or use **Email me a sign-in link**, **Continue with Google** or **Continue with Microsoft**. ### This sign-in was started in a different browser. Start it again here. **What it means:** a **Continue with Google** or **Continue with Microsoft** sign-in can only finish in the browser where you clicked it. This stops someone from sending you a link that signs you in to their account instead of yours. **How to fix it:** go to the sign-in page in the browser you want to use and click **Continue with Google** or **Continue with Microsoft** again. ### That login link is invalid or has expired. **What it means:** the sign-in link was already used, or is older than 20 minutes. **How to fix it:** ask for a new one with **Email me a sign-in link**. ### Sign-ups are closed right now. **What it means:** you tried to create a new account (with a password, a link, Google or Microsoft) while Plugsight isn't accepting new sign-ups. **How to fix it:** if you already have an account, sign in with the email address it uses. Otherwise, email info@plugsight.app to be told when sign-ups open. ### That email already has an account. Sign in or reset your password. **What it means:** you tried to create an account with an email that already has one. **How to fix it:** sign in instead, or click **Forgot password?**. ### Your Google account didn't share a verified email address. (Or "Your Microsoft account didn't share a verified email address.") **What it means:** Google or Microsoft didn't confirm the account's email address, so Plugsight can't tell whose account it is. **How to fix it:** use a different sign-in method, such as **Email me a sign-in link**. ### Too many sign-ups from your network. Try again later. **What it means:** too many accounts were created from your network in the last hour, or a great many sign-up forms were refused (a short password or a mistyped address). A few mistakes on the form don't count towards the limit. **How to fix it:** wait an hour and try again. ### I didn't get the sign-in link Check your spam folder. For security, Plugsight shows the same message whether or not the email has an account ("If [email] can sign in, a sign-in link is on its way."), so check you typed the address you signed up with. You can ask for up to 10 links per 15 minutes from one network. ## Related articles - [Confirm your email](/account/verify-email) - [Change or reset your password](/account/password) - [Activity log](/permissions/activity) - [Sign-in problems](/troubleshooting/sign-in-problems) --- # Confirm your email URL: https://docs.plugsight.app/account/verify-email Why Plugsight asks you to confirm your email after signing up with a password, how to do it, and what to do if the link fails. When you create an account with an email and password, Plugsight sends a confirmation link to that address. You need to confirm it before you can use the app or approve an AI app. Signing up with Google, Microsoft or an emailed sign-in link doesn't need this step: the email is already confirmed. ## Confirm your email 1. After **Create account**, Plugsight shows **Confirm your email**, with the address it sent the link to. 2. Open the email "Confirm your email for Plugsight". 3. Click **Confirm email**. You're taken into the app, and Plugsight sends a welcome email. The confirmation is recorded in **Activity**. The link expires in **2 days**. > [!IMPORTANT] > Open the link in the same browser where you're signed in to the account that signed up. Only the person who signed up (and knows the password) can confirm. This stops someone signing up with your address and waiting for you to click the link. ## The email didn't arrive 1. Wait a minute and check your spam folder. 2. On the **Confirm your email** page, click **Resend email**. Plugsight shows "Sent. Check your inbox and spam folder." 3. Wrong address? Click **Use a different account** and sign up again with the right one. You can resend up to 3 times in 15 minutes. ## Errors ### Sign in to confirm your email. **What it means:** you opened the link in a browser where you aren't signed in. **How to fix it:** sign in with the email and password you signed up with. Plugsight then confirms the email. ### That link is for a different account. Sign out and open it again. **What it means:** you're signed in to Plugsight with a different account from the one the link is for. **How to fix it:** sign out, sign in with the account that signed up, then open the link again. ### That link is invalid or has expired. We can send you a new one. **What it means:** the link was already used, or is more than 2 days old. **How to fix it:** sign in and click **Resend email** on the **Confirm your email** page. ## Someone else signed up with my email If an account was created with your address but never confirmed, you can take it over: sign in with **Email me a sign-in link**, **Continue with Google** or **Continue with Microsoft**. Proving you control the email removes the unconfirmed password and signs out any other sessions on that account. ## Related articles - [Sign in to Plugsight](/account/sign-in) - [Emails Plugsight sends you](/account/emails) --- # Change or reset your password URL: https://docs.plugsight.app/account/password Change, set or reset your Plugsight password, and what it signs out - your browser sessions end, your AI apps stay connected. ## Change your password 1. Open **Settings**. 2. Under **Password**, enter your **Current password**. 3. Enter a **New password** of at least 10 characters. 4. Click **Update password**. Plugsight signs you out and shows "Password saved. Sign in again." Sign in with the new password. ## What changing your password does | | | | --- | --- | | **Signed out** | Every browser session on Plugsight, on every device, including the one you're using. | | **Stays connected** | Your AI apps (Claude, ChatGPT and others). Their access to your MCP servers doesn't depend on your password. API keys keep working too. | | **Email** | Plugsight sends "Your Plugsight password was changed" to your address. | | **Activity** | Recorded as "Changed the password (other sessions signed out)". | > [!TIP] > If you're changing your password because you think someone else got in, also cut off AI apps: on each MCP server, use **Disconnect all AI apps**, and revoke or regenerate any API key. See [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete). ## Set a password If you signed up with Google, Microsoft or an email link, you don't have a password. You can add one, which is optional. 1. Open **Settings**. 2. Under **Set a password**, enter a **New password** of at least 10 characters. 3. Click **Update password**. You're signed out and sign in again, as with a change. ## Reset a forgotten password 1. On the **Sign in** page, click **Forgot password?**. 2. Enter your **Email** and click **Send reset link**. 3. Open the email "Reset your Plugsight password" and click **Choose a new password**. The link expires in **1 hour**. 4. Enter a **New password** of at least 10 characters and click **Save password**. You're signed in and see "Password changed." As with a change, every other browser session is signed out, your AI apps stay connected, and Plugsight emails you to say the password was changed. Resetting your password also confirms your email address, because you proved you can read it. For security, the reset page says the same thing whether or not the email has an account: "If [email] has an account, a reset link is on its way." ## Errors ### Current password is wrong. **What it means:** the **Current password** doesn't match. **How to fix it:** type it again, or sign out and use **Forgot password?** to reset it. ### Use at least 10 characters. **What it means:** the new password is too short. **How to fix it:** choose a longer one. A password can be up to 200 characters. ### That link is invalid or has expired. Ask for a new one. **What it means:** the reset link was already used, or is more than 1 hour old. **How to fix it:** click **Need a new link?** and ask for another. ### I got a "password was changed" email, but it wasn't me Click **It wasn't me: reset my password** in that email and choose a new password straight away, then email info@plugsight.app so we can help secure your account. Check **Activity** for sign-ins you don't recognise. ## Related articles - [Sign in to Plugsight](/account/sign-in) - [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete) - [Activity log](/permissions/activity) - [Profile and email address](/account/profile) --- # Profile and email address URL: https://docs.plugsight.app/account/profile Change the name on your Plugsight account, and how to change the email address you sign in with. ## Change your name 1. Open **Settings**. 2. Under **Profile**, change **Name** (up to 80 characters). 3. Click **Save profile**. Plugsight shows **Profile saved.** Your name is used to greet you in emails. The change is recorded in **Activity**. ## Change your email address The **Email** box under **Profile** shows the address you sign in with. You can't change it yourself. To change it, email [info@plugsight.app](mailto:info@plugsight.app) from your current address, and say which new address you'd like to use. > [!NOTE] > Your Plugsight email address is only how you sign in to Plugsight. It's separate from the email accounts you connect for your AI. To add or remove those, use **Connections**. ## Related articles - [Sign in to Plugsight](/account/sign-in) - [Change or reset your password](/account/password) - [Delete your account](/account/delete-account) --- # Delete your account URL: https://docs.plugsight.app/account/delete-account Permanently delete your Plugsight account - what's deleted, what happens to a paid plan, and what isn't touched. Deleting your account can't be undone. ## Delete your account 1. Open **Settings**. 2. Under **Delete account**, type your email address exactly as shown, in **Type [your email] to confirm**. 3. Click **Delete my account**. 4. Read the **Delete your account?** box, then click **Delete everything**. You're signed out and see "Your account and all its data were deleted." Plugsight sends a last email, "Your Plugsight account has been deleted", to the address. ## What happens | | | | --- | --- | | **Paid plan** | Cancelled straight away. You won't be charged again. | | **MCP servers** | Every server link stops working in your AI apps, and their API keys stop working. | | **Connected accounts** | All stored logins (sign-in tokens, app passwords, API tokens) are deleted. | | **Settings** | Your profile, switches, pauses, daily email limit and sign-in sessions are deleted. | | **Activity** | Your Activity page goes with the account. The underlying records are kept until they're one year old, with only the email address the account had, for security; then they're deleted automatically. | ## What isn't touched Your accounts themselves (Gmail, Zendesk, Google Ads and so on) aren't changed. Nothing is deleted from them. Plugsight's access ends when its stored logins are deleted. You may also want to remove Plugsight's access in each service's own settings, and delete any app passwords you made for it. See [Remove Plugsight's access](/security/remove-access). Remove the Plugsight connectors from your AI apps too, since their links no longer work. ## Errors ### Type your email exactly to confirm. **What it means:** the text in the confirmation box doesn't match your account's email. **How to fix it:** type the email address shown above the box. Capital letters don't matter. ## Before you delete - **Only want to stop paying?** Cancel your plan instead and keep using Free. See [Cancel your plan](/account/cancel). - **Only want to stop your AI making changes?** Use **Pause everything** on **Permissions**. See [Pause changes](/permissions/pause). - **Only want to cut off your AI apps?** Use **Disconnect all AI apps** on each MCP server, or delete the servers. See [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete). ## Related articles - [Cancel your plan](/account/cancel) - [Remove Plugsight's access](/security/remove-access) - [What Plugsight stores and logs](/security/data-handling) --- # Plans and billing URL: https://docs.plugsight.app/account/plans-and-billing What the Free, Pro and Agency plans include, their prices and limits, and where to see your plan and usage. Plugsight has three plans. Prices are in US dollars. | | **Free** | **Pro** | **Agency** | | --- | --- | --- | --- | | **Price, monthly** | $0, forever | $29 / month | $99 / month | | **Price, yearly** | $0 | $290 / year | $990 / year | | **Connections** (accounts you connect) | 2 | 10 | 50 | | **MCP servers** | 1 | 5 | Unlimited | | **Team members** (people working in your workspace, you included; see [Team members](/account/team)) | 1 | 1 | 5 | | **Marketing & analytics connectors** (Google Ads, Microsoft Ads, Meta Ads, LinkedIn Ads, Search Console, GA4 and Bing Webmaster Tools; Tag Manager, YouTube and Merchant Center once Google approves them) | To try: 1 connection, 25 tool calls a month | Yes | Yes | | **Approved sending & helpdesk updates** (sending email, Zendesk changes, calendar bookings) | No | Yes | Yes | | **Archiving, labelling and marking email** (no approval needed; your AI asks before trashing or changing more than 10) | No | Yes | Yes | | **Developer API** | No | Yes | Yes | Yearly billing costs the same as 10 months: 2 months free. ## What every plan includes - Reading your connected accounts through your AI: email, helpdesk, files, calendars, contacts, stores and email marketing. - Email drafts. - Approvals in the chat, Pause, the daily email limit and the **Activity** log. ## What Free doesn't include - **Unlimited marketing and analytics.** Free includes 1 marketing connection and 25 marketing tool calls a month, to try them. Once the month's calls are used, marketing tools answer with a note until the calls start again on the 1st (UTC). To add another marketing connection, remove the one you have or upgrade; the one you have keeps working. - **Changes.** Your AI can read and draft, but can't send email, update helpdesk tickets, book events, or archive and label email. Account switches show **Upgrade**, and **Allow changes** on servers is greyed out. ## See your plan and usage Open **Billing**. **Your plan** shows: - The plan name, with a badge: **Active**, **Trial — ends [date]**, **Cancelling** or **Payment failed**. - On a paid plan: **Price**, **Billing** (**Monthly** or **Yearly**) and **Renews on** (**Trial ends on** during a free trial, or **Ends on** if you've cancelled). - **Connections** and **MCP servers** used, for example "Connections 3 of 10", with a bar. On Agency, **Team members** too. - On Free, **Marketing connections** and **Marketing calls this month** too, with when the calls start again (the 1st of next month, UTC). ## At a limit When you reach your plan's limit of connections, MCP servers or team members, you can't add another until you remove one or upgrade. Invitations that are still open count as team members. Everything you already have keeps working; nothing is switched off when you reach it. The messages look like this: - "Your Free plan includes 2 connections. Upgrade to Pro for 10." - "Your Pro plan includes 5 MCP servers. Upgrade to Agency for unlimited." - "Your Agency plan includes 50 connections. Contact us for a higher limit." For a higher limit on Agency, email info@plugsight.app. ## A plan shows "Coming soon" That plan isn't open yet. Click **Coming soon** for details, and email info@plugsight.app if you'd like it as soon as it opens. ## A plan given to you Plugsight may give an account a plan free of charge. You then get the email "You've been given Plugsight [plan]", with the date it lasts until, if there is one. No card is needed and you won't be charged. ## Related articles - [Upgrade your plan](/account/upgrade) - [Invoices, card and plan changes](/account/manage-billing) - [Cancel your plan](/account/cancel) - [MCP server limits on each plan](/mcp-servers/plan-limits) - [Team members](/account/team) --- # Team members URL: https://docs.plugsight.app/account/team Invite people to work in your Plugsight workspace on the Agency plan: what Owners, Admins and Members can do, and how seats work. On the Agency plan, other people can work in your workspace with you: they use its MCP servers from their own AI apps, each signing in as themselves, and Admins help you manage it. Agency includes 5 team members, you included. Free and Pro are for one person. Your connections, MCP servers and settings stay yours. Nobody gets a copy: everyone works in the same workspace, and every action shows in **Activity** with who did it. ## Roles Every workspace has one **Owner**: the person who pays for the plan. Everyone else you invite is an **Admin** or a **Member**. | | **Owner** | **Admin** | **Member** | | ------------------------------------------------------------------------------------------- | --------- | ----------------------- | -------------- | | Use the workspace's MCP servers from their own AI apps | Yes | Yes | Yes | | See connections, MCP servers and Permissions | Yes | Yes | Yes | | Add, reconnect and remove connections, turn write access on or off, hide sites and accounts | Yes | Yes | No | | Create, change and delete MCP servers, and sign AI apps out of them | Yes | Yes | No | | Create and revoke API keys | Yes | Yes | No | | Pause changes and set the daily email limit | Yes | Yes | No | | See the whole workspace's **Activity** | Yes | Yes | Only their own | | Invite and remove people, and change roles | Yes | Yes (never the Owner's) | No | | See billing, change the plan, delete the team | Yes | No | No | Members never see an API key or anything stored for a connection, such as a password or a sign-in. To use an MCP server from an app that needs an API key, a Member asks an Owner or Admin to create one; the key then acts as the person who created it. The Owner's own sign-ins, profile, password and billing events stay in the Owner's **Activity** only. Admins see everything else that happens in the workspace. ## Invite someone 1. Open **Team**. 2. Under **Invite someone**, enter their email address and choose a role: **Member** or **Admin**. 3. Click **Send invitation**. They get the email "[name] invited you to [team] on Plugsight", with a link. The link works once and expires after 7 days. Until then the invitation is listed under **Invitations**, where you can: - Click **Resend** to email a new link. The old link stops working, and the new one lasts another 7 days. Use it for an invitation marked **Expired**, too. - Click **Revoke** to cancel it. The link stops working straight away. ## Accept an invitation 1. Open the link in the email. 2. Sign in with the address the invitation was sent to. If you don't have a Plugsight account yet, click **Create an account** and sign up with that address. If you sign up with a password, confirm your email first, then open the invitation link again. 3. Click **Accept invitation**. You start working in the team's workspace straight away. Your own workspace stays as it was: switch between the two with the menu at the top of the app. That menu only appears once you belong to a team. > [!NOTE] > An invitation only works for the address it was sent to. Signed in with another address, you're asked to sign out and switch account. ## Seats Each person in the team takes a seat: the Owner, every Admin and Member, and every invitation that hasn't been accepted, revoked or expired. **Team** shows how many are used, for example "3 of 5 seats used". When every seat is taken, you can't invite anyone else until you revoke an invitation or remove someone. An expired invitation frees its seat on its own. ## Name the team The team's name shows in the workspace menu at the top of the app and in invitation emails. Until you name it, it's "[Owner's name]'s team". To change it, an Owner or Admin opens **Team**, types a new name under **Team name** and clicks **Save name**. ## Remove someone or change their role On **Team**, an Owner or Admin can: - Change someone's role with the menu next to their name. - Click **Remove** to take them out of the team. When someone is removed, they lose access straight away: every AI app they signed in to the workspace's MCP servers is signed out, and any API key they created stops working. When an Admin becomes a Member, the API keys they created stop working too. What they set up, and their activity, stays in the workspace. Nobody can change or remove the Owner, and nobody can change their own role. ## Leave a team 1. Switch to the team's workspace with the menu at the top of the app. 2. Open **Team**. 3. Click **Leave team**, then **Leave team** again to confirm. You lose access straight away, and your AI apps are signed out of the team's MCP servers. To come back, ask an Owner or Admin to invite you again. If the team is paused because its Owner's plan no longer includes team members, you can't switch to it. Leave it from your own workspace instead: open **Team**, then click **Leave** next to the team under **Paused teams**. ## Billing stays with the Owner Only the Owner sees **Billing**, pays and changes the plan. Admins and Members don't see the team's payment details. In their own workspace, everyone still has their own account and plan. If the Owner moves to a plan without team members (or cancels and the plan ends), the people in the team can't use the workspace or its MCP servers until the Owner upgrades again. Nobody is removed, and nothing is deleted: everything works again as soon as the plan includes a team. ## Delete the team 1. Open **Team**. 2. Click **Delete team**, then **Delete team** again to confirm. Everyone else loses access straight away, with their AI apps and API keys, and open invitations stop working. Your connections, MCP servers, settings, plan and activity stay. ## Troubleshooting ### You're working in a different workspace now (switched in another tab, or your access to the team changed). Nothing was changed: check the page and try again. **What it means:** every tab you have open works in the same workspace. You switched workspace in another tab, or you were removed from the team, or the team was paused or deleted, while this page still showed the old workspace. Plugsight made no change, so nothing landed in the wrong workspace. **How to fix it:** check the workspace menu at the top of the app. Switch back if you want to, then try again. ### Too many invitations sent in the last hour. Try again later. **What it means:** your workspace sent a lot of invitation emails in the last hour, or several to the same address. **How to fix it:** wait an hour, then click **Resend** or invite them again. ### This invitation was sent to [address]. Sign out, then sign in or sign up with that address to accept it. **What it means:** you're signed in with a different email address from the one the invitation was sent to. **How to fix it:** sign out, then sign in, or create an account, with the address in the invitation email. ### This invitation has expired, was revoked or was already used. Ask for a new one. **What it means:** the link is more than 7 days old, the invitation was revoked, or someone already accepted it. **How to fix it:** ask an Owner or Admin of the team to click **Resend** on **Team**, or to invite you again. ### Team members are on the Agency plan. Upgrade under Billing to invite people. **What it means:** your plan is for one person. **How to fix it:** [upgrade](/account/upgrade) to Agency. ## Related articles - [Plans and billing](/account/plans-and-billing) - [Upgrade your plan](/account/upgrade) - [Connect an AI app](/mcp-servers/connect-ai-app) - [API keys](/mcp-servers/api-keys) - [Cancel your plan](/account/cancel) --- # Upgrade your plan URL: https://docs.plugsight.app/account/upgrade Upgrade to Pro or Agency with Stripe Checkout, choose monthly or yearly billing, and what changes straight away. Upgrades are paid through Stripe, our payment provider. Plugsight never sees or stores your card details. ## Upgrade from Free 1. Open **Billing**. 2. Under **Plans**, choose **Monthly** or **Yearly · 2 months free** at the top right. 3. Click **Upgrade to Pro** or **Upgrade to Agency**. 4. On the Stripe checkout page, enter your payment details and confirm. If you've never had a paid plan or a trial, the Pro checkout page shows its 7-day free trial before you confirm. If you have a promotion code, you can enter it there. 5. Stripe sends you back to **Billing**. Plugsight shows "Thanks! Your subscription is active. It can take a few seconds to show here; refresh if it doesn't." After starting a free trial it shows "Thanks! Your free trial has started. You aren't charged until it ends, and you can cancel before then." instead. You also get the email "You're on Plugsight [plan]" and a payment receipt (or, for a trial, "Your Plugsight Pro trial has started"). If you leave the Stripe page without paying, **Billing** shows "Checkout was cancelled. Nothing was charged." ## The free Pro trial If you've never had a paid plan or a trial, your first Pro subscription starts with a 7-day free trial: - Stripe asks for your card at checkout, but doesn't charge it until the trial ends. - During the trial you have everything in Pro. **Billing** shows the badge **Trial — ends [date]**, and **Trial ends on** with the date. - A few days before it ends, Plugsight emails "Your Plugsight Pro trial ends on [date]", with the amount it will charge (or just the date, when a discount changes the amount). - When it ends, your card is charged and Pro carries on, monthly or yearly as you chose. To stop it, cancel before the trial ends with **Invoices, card & cancel** on **Billing**: you aren't charged, and your account moves to Free when the trial ends. - There's one trial per account and email address. If you've had a paid plan or a trial before, even on an earlier account with the same email, Pro starts as a paid plan straight away. Agency has no trial. ## What changes straight away Upgrades apply straight away: - Marketing and analytics connectors can be connected and work in your AI. - Account switches on **Connections** can be turned on, and **Allow changes** on MCP servers becomes available. - Your connection and MCP server limits go up. - The Developer API works with your servers' API keys. > [!NOTE] > Upgrading doesn't turn on sending by itself. Each account's switch on **Connections** still starts off, and every change still needs your approval in the chat. See [How changes are allowed](/permissions/how-changes-are-allowed). ## Monthly or yearly | | Pro | Agency | | --- | --- | --- | | **Monthly** | $29 / month | $99 / month | | **Yearly** | $290 / year | $990 / year | Yearly costs the same as 10 months. Your plan renews automatically at the end of each month or year, and Plugsight emails you a reminder before each renewal. ## Already on a paid plan? To move from Pro to Agency, switch between monthly and yearly, or move to a cheaper plan, Plugsight sends you to the Stripe billing portal instead of a new checkout. See [Invoices, card and plan changes](/account/manage-billing). ## Errors ### That plan isn't available yet. **What it means:** the plan can't be bought right now. On **Billing** it shows **Coming soon**. **How to fix it:** email info@plugsight.app if you'd like it as soon as it opens. ### Billing isn't set up on this server. **What it means:** this copy of Plugsight doesn't take payments, so every feature is available without a plan. **Billing** says "Billing isn't set up on this server, so every feature is available." **How to fix it:** nothing to do. ## Related articles - [Plans and billing](/account/plans-and-billing) - [Invoices, card and plan changes](/account/manage-billing) - [Emails Plugsight sends you](/account/emails) - [Move from Free to Pro without losing anything](/guides/free-to-pro) --- # Invoices, card and plan changes URL: https://docs.plugsight.app/account/manage-billing Use the Stripe billing portal to download invoices, update your card, switch plan or billing period, or cancel. Invoices, your card and plan changes are handled in Stripe's billing portal. Open it from Plugsight. ## Open the billing portal 1. Open **Billing**. 2. Under **Your plan**, click **Invoices, card & cancel**. 3. Stripe's billing portal opens. When you're done, use its link back to Plugsight's **Billing** page. The button appears once you've started an upgrade at least once. ## What you can do there - **Download invoices** for every payment. - **Update your card** or other payment method. - **Change plan**: move between Pro and Agency. - **Switch between monthly and yearly** billing. - **Cancel** your plan. See [Cancel your plan](/account/cancel). - **Resume** a plan you cancelled, before it ends. ## When plan changes apply - **Upgrades** apply straight away. - **Moving to a cheaper plan** or **cancelling** takes effect at the end of the period you've paid for. You keep everything until then. Any difference in price is worked out by Stripe and shown on your next invoice. Plugsight emails you "Your Plugsight plan is now [plan]" when your plan changes. ## Receipts After every successful payment, Plugsight emails "Receipt for your Plugsight payment of [amount]", with a **View invoice** button. You can download all your invoices from the billing portal. ## Errors ### There's no billing account yet. Choose a plan first. **What it means:** you haven't started an upgrade yet, so there's nothing in Stripe to manage. **How to fix it:** upgrade first. See [Upgrade your plan](/account/upgrade). ## Related articles - [Plans and billing](/account/plans-and-billing) - [When a payment fails](/account/failed-payment) - [Cancel your plan](/account/cancel) --- # When a payment fails URL: https://docs.plugsight.app/account/failed-payment What happens when a renewal payment is declined - your plan keeps working while Stripe retries - and how to fix it. If Stripe can't charge your card for a renewal, your plan **keeps working** while Stripe tries again over the next few days. ## How you'll know - **Email:** "Action needed: your Plugsight payment didn't go through", with the amount and plan, and an **Update payment method** button. - **Billing:** your plan shows a red **Payment failed** badge. Click it to see what it means, with **Update card** and **Later** buttons. This usually means the card expired, was replaced, or the bank declined it. ## Fix it 1. Open **Billing**. 2. Click the **Payment failed** badge, then **Update card**. (Or click **Invoices, card & cancel**.) 3. In Stripe's billing portal, add or update your payment method. Stripe uses the new card for its next try. ## What happens meanwhile | | | | --- | --- | | **While Stripe retries** | Your plan keeps working as normal: marketing connectors, sending email and your limits. | | **If every retry fails** | Your account moves to the Free plan. Plugsight emails "Your Plugsight [plan] plan has ended". | | **On Free** | Marketing connectors work only within Free's 25 tool calls a month, and sending email stops working in your AI. Your connections, MCP servers and settings are kept. See [Cancel your plan](/account/cancel) for exactly what changes. | To get your plan back after it ended, upgrade again from **Billing**. ## Related articles - [Invoices, card and plan changes](/account/manage-billing) - [Cancel your plan](/account/cancel) - [Emails Plugsight sends you](/account/emails) --- # Cancel your plan URL: https://docs.plugsight.app/account/cancel Cancel Pro or Agency, keep your plan until the end of the period, the 14-day money-back guarantee on your first payment, and what changes on Free. You can cancel at any time. You keep your plan until the end of the period you've paid for, then your account moves to Free. Nothing is deleted. ## Cancel 1. Open **Billing**. 2. Click **Invoices, card & cancel**. 3. In Stripe's billing portal, cancel your plan. Back on **Billing**, your plan shows a **Cancelling** badge and **Ends on** with the date. Plugsight emails "Your Plugsight [plan] plan will end on [date]". ## Refunds Your first payment has a 14-day money-back guarantee. If Plugsight isn't right for you, email info@plugsight.app within 14 days of the first payment for your first paid plan and we refund it in full. After a free trial, that's the first charge, when the trial ends. Refunds are made by hand in Stripe, so there's no button for them in the app; we cancel the plan with the refund, so your account moves to Free. Later payments aren't refunded: cancelling doesn't give money back for the rest of the period, and there are no credits for unused time. Instead, you keep your plan until the end date and aren't charged again. If you were charged twice or after cancelling by mistake, email info@plugsight.app and we'll refund it. > [!TIP] > Cancelling during a free trial costs nothing: you aren't charged, and your account moves to Free when the trial ends. ## Until the end date Everything works as before. Nothing changes until the date shown under **Ends on**. ## Changed your mind? Before the end date, open **Invoices, card & cancel** and resume your plan in the billing portal. The **Resume my plan** button in the cancellation email takes you to **Billing**. Plugsight emails "Your Plugsight [plan] plan will continue". ## When the plan ends Your account moves to the Free plan, and Plugsight emails "Your Plugsight [plan] plan has ended". | | On Free | | --- | --- | | **Marketing and analytics connectors** | They keep working within Free's allowance: 25 marketing tool calls a month, and no more than 1 marketing connection added. Ready-made deep dives stop. They stay on **Connections**. | | **Sending email and changes** | Your AI can't send email, make helpdesk changes or book events. It can still read and draft. | | **Connections and MCP servers** | The ones you already have stay, with their settings. You can't add more beyond Free's limits (2 connections, 1 MCP server). | | **Developer API** | Stops working. | | **Team members** | They can't use your workspace or its MCP servers until you upgrade again. Nobody is removed. | | **Your data in Plugsight** | Nothing is deleted. | To get everything back, upgrade again from **Billing**. See [Upgrade your plan](/account/upgrade). ## Cancelling isn't deleting Cancelling only stops payment. To remove your account and everything in it, see [Delete your account](/account/delete-account). Deleting an account with a paid plan cancels the plan straight away. ## Related articles - [Plans and billing](/account/plans-and-billing) - [Invoices, card and plan changes](/account/manage-billing) - [MCP server limits on each plan](/mcp-servers/plan-limits) - [Team members](/account/team) --- # Emails Plugsight sends you URL: https://docs.plugsight.app/account/emails Every email Plugsight sends about your account, connections and billing, with its subject line and when it's sent. Plugsight only sends emails about your own account. They come to the email address you sign in with. ## Account | Email | Subject | When | | --- | --- | --- | | **Confirm email** | Confirm your email for Plugsight | You sign up with a password. The link expires in 2 days. | | **Welcome** | Welcome to Plugsight | You confirm your email, or sign in for the first time with Google, Microsoft or an email link. | | **Sign-in link** | Your Plugsight sign-in link | You click **Email me a sign-in link**. Works once, expires in 20 minutes. | | **Reset password** | Reset your Plugsight password | You click **Forgot password?**. The link expires in 1 hour. | | **Password changed** | Your Plugsight password was changed | You change, set or reset your password. Every device was signed out, including the one you changed it on, so you sign in again. After a reset, you're signed in again on the device you used. | | **Account deleted** | Your Plugsight account has been deleted | You delete your account. | ## Connections | Email | Subject | When | | --- | --- | --- | | **Connection needs reconnecting** | Reconnect [account] to keep using it with your AI | An account stops accepting Plugsight's login, usually after a password change or when access was removed at the provider. At most once a day per account. Click **Reconnect it** to fix it. | ## Plans and billing | Email | Subject | When | | --- | --- | --- | | **Subscription started** | You're on Plugsight [plan] | You pay for a plan. | | **Trial started** | Your Plugsight Pro trial has started | Your first Pro subscription starts its free trial (if you've never had a paid plan or a trial). | | **Trial ending** | Your Plugsight Pro trial ends on [date] | A few days before the trial ends (when Stripe tells us), with the first payment's amount unless a discount changes it. Not sent if you've cancelled. | | **Plan changed** | Your Plugsight plan is now [plan] | You upgrade, move to a cheaper plan, or switch between monthly and yearly. | | **Renewal reminder** | Your Plugsight [plan] plan renews on [date] | Before each monthly or yearly renewal, with the amount. | | **Payment receipt** | Receipt for your Plugsight payment of [amount] | Every successful payment, with a link to the invoice. | | **Payment failed** | Action needed: your Plugsight payment didn't go through | A renewal payment is declined. See [When a payment fails](/account/failed-payment). | | **Cancellation scheduled** | Your Plugsight [plan] plan will end on [date] | You cancel. The plan runs to the end of the period. | | **Plan resumed** | Your Plugsight [plan] plan will continue | You undo a cancellation. | | **Plan ended** | Your Plugsight [plan] plan has ended | A paid plan ends and your account moves to Free. | | **Plan given to you** | You've been given Plugsight [plan] | Plugsight gives your account a plan free of charge. | > [!WARNING] > Plugsight's emails never ask for your password. Sign-in, reset and confirmation links go to app.plugsight.app. If you get an email you didn't expect, such as a password change you didn't make, reset your password and contact info@plugsight.app. ## Not getting emails? Check your spam folder, and that you're looking at the address shown under **Settings** → **Profile** → **Email**. ## Related articles - [Sign in to Plugsight](/account/sign-in) - [Change or reset your password](/account/password) - [Plans and billing](/account/plans-and-billing) --- # Troubleshooting URL: https://docs.plugsight.app/troubleshooting How to find out why something isn't working, where Plugsight shows the reason, and every error message explained by symptom. When your AI can't see an account, can't send, or shows an error, Plugsight almost always says why in one of four places. Check them in this order. ## 1. The account's row on Connections Open **Connections** and find the account. - **Status** shows **Connected** or **Reconnect needed**. With **Reconnect needed**, the line underneath gives the reason, such as "Google sign-in was revoked or has expired." Click **Reconnect** on the row. See [Reconnect needed](/troubleshooting/reconnect-needed). - **The line under the account's name** says which MCP servers it's in. "not in any MCP server" means your AI can't use it yet. See [Your AI can't see an account](/troubleshooting/ai-cant-see-account). - **The line under the account's switch** (in **Write access**) says whether your AI can make changes with it, and if not, the one thing stopping it: | Line under the switch | What it means | | --- | --- | | Ready: your AI asks you in the chat before each change. | Changes can happen, after your yes in the chat. | | Off: your AI can read, but can't change anything. | The switch is off. Click it to turn it on. Email accounts say "can read and write drafts". | | Not in any MCP server yet. Add it to one on MCP servers. | Put the account in an MCP server first. | | Not yet: the MCP servers with this account are read-only. | Open the MCP server, click **Edit configuration** and tick **Allow changes**. | Instead of a switch, you may see: - **Read-only** with a lock: the service only reads, or the account was connected with read access only. Click it for the reason. - **Drafts only · Upgrade** or **Read-only · Upgrade**: changes are on the Pro plan. See [Plans and limits](/troubleshooting/plan-limits). - **Paused**: changes of this type are paused on **Permissions**. ## 2. The red banners at the top of the page - **"1 connection needs reconnecting."** (or more): lists each account whose login stopped working, with the reason and a **Reconnect** button. AI apps can't use those accounts until you reconnect. - **"All changes are paused."** or, for example, **"Email changes are paused."**: a pause on the **Permissions** page is on. Your AI can still read and write drafts, but can't send or change anything of that type, whatever the account switches say. Click **Resume**, or **Manage** to open **Permissions**. - **"Refresh Claude to use your changes"** (or ChatGPT, Cursor and so on): your AI app still has an old list of tools. Follow the steps in the notice. See [Your AI can't see an account](/troubleshooting/ai-cant-see-account#your-ai-app-has-an-old-list-of-tools). ## 3. Activity **Activity** lists everything your AI did, with a result for each: | Result | What it means | | --- | --- | | **Succeeded** | The read or change went through. | | **Blocked** | One of your own safety settings stopped it before anything happened: the account's switch was off, the MCP server is read-only, changes were paused, or the daily email limit was reached. The reason is shown underneath. | | **Failed** | The service refused it or didn't answer, for example an expired sign-in or a ticket that no longer exists. Nothing was changed. The service's message is shown underneath. | Find the message under the badge in the articles below. ## 4. What your AI says When a tool is refused, your AI gets a message explaining why, and usually passes it on. Ask your AI to "list my accounts" to see which accounts it can reach and whether each one may send or make changes. ## Find your problem - [Your AI can't see an account](/troubleshooting/ai-cant-see-account): missing accounts, "Unknown account", tools that don't appear. - [Your AI can't send or change anything](/troubleshooting/ai-cant-send-or-change): every reason a send, reply, update or booking is refused. - [Reconnect needed](/troubleshooting/reconnect-needed): expired or revoked logins, for each service. - [Errors while connecting an account](/troubleshooting/connection-errors): sign-in errors, wrong passwords, store keys and more. - [App password problems](/troubleshooting/app-passwords): Gmail, iCloud, Yahoo and other providers that need an app password. - [Plans and limits](/troubleshooting/plan-limits): "upgrade" messages, connection and server limits, the daily email limit. - [Sign-in problems](/troubleshooting/sign-in-problems): signing in to Plugsight itself. - [AI app problems](/troubleshooting/ai-app-problems): adding Plugsight to Claude, ChatGPT and other apps. - [Errors from your AI's tools](/troubleshooting/tool-errors): messages from Gmail, Zendesk, Google Ads and other services, passed on by your AI. ## Still stuck? Email info@plugsight.app with what you tried, the exact message you saw and roughly when it happened. --- # Your AI can't see an account URL: https://docs.plugsight.app/troubleshooting/ai-cant-see-account Fix an AI that can't find an account or its tools - the account isn't in the MCP server, the app needs a refresh, or an item is hidden. Your AI can only use accounts that are in the MCP server it's connected to, and only with the list of tools it loaded when the chat started. Most "can't see it" problems are one of these. ## Quick checks 1. On **Connections**, look at the line under the account's name. If it says **not in any MCP server**, add it to one (below). 2. Open **MCP servers** and the server your AI uses. If **Account access** is **Selected accounts**, make sure the account is ticked. 3. If you just connected a new type of account (your first Zendesk, say), refresh Plugsight in your AI app and start a new chat. 4. In the chat, check the Plugsight connector is switched on. In Claude, click **+** below the message box, then **Connectors**. In ChatGPT, click **+** and select the server. 5. Ask your AI to "list my accounts". It shows exactly what this MCP server reaches. ## The account isn't in the MCP server An MCP server only reaches the accounts you put in it. If it uses **Selected accounts**, accounts you connect later aren't added by themselves. 1. Open **MCP servers** and click the server. 2. Click **Edit configuration**. 3. Under **Account access**, tick the account, or choose **All accounts**. 4. Click **Save changes**. If the account is a new type for this server, also refresh your AI app's tool list (next section). ## Your AI app has an old list of tools AI apps load Plugsight's list of tools once, for example when a chat starts. When you add the first account of a new type, or remove the last one, the tools change. Until the app reloads the list, your AI can't use the new tools. When this happens, **Connections** shows a notice such as **"Refresh Claude to use your changes"**, naming each AI app that still has the old list, with the steps for it. It goes away by itself once the app has the new list. Your AI may also tell you: "Note from Plugsight: the user's connections changed since this chat loaded its tool list, so the list here is out of date." followed by which tools are new or gone. ### Claude 1. Open claude.ai/customize/connectors (in the desktop app: **Settings** → **Customize**) and click your Plugsight server under **Your connectors**. 2. Click **⋯** (top right, next to **Disconnect**) → **Refresh tools list**. 3. Start a **new chat**. Chats already open keep the old list. 4. Not there yet? Claude can take a few minutes to pick up the new list. Wait, refresh again, then open another new chat. ### Claude Code 1. Type `/mcp`, choose your server, then **Reconnect**. 2. Or quit and start Claude Code again. ### ChatGPT 1. Open chatgpt.com/settings/plugins-settings and click your Plugsight server. 2. Scroll down to **Manage app** and click **Refresh tools**. If any new actions show as off, switch them on. 3. Start a **new chat**. On Business or Enterprise, a workspace admin may need to refresh and publish the update first. ### Cursor 1. Open **Cursor Settings** → **Tools & MCP** and switch your server off and on again. 2. Still the old list? Run **Developer: Reload Window** from the command palette, or quit and reopen Cursor. ### Other apps Open the app's connector or MCP settings and refresh Plugsight (or switch it off and on), then start a new chat. > [!TIP] > Can't find the refresh option? Remove the connector in your AI app and add it again. Nothing in Plugsight is lost. ## Messages your AI may show ### Unknown account "…". Call list_accounts to see valid ids. Also: **Unknown Zendesk account "…". Call list_accounts to see valid ids.** and, for calendars and contacts, **Unknown calendar connection "…"** or **Unknown contacts connection "…"**. **What it means:** your AI asked for an account by a short name that this MCP server doesn't include. Either the name is wrong, or the account isn't in this server. **How to fix it:** on **Connections**, check the account's short name (shown in grey under its name). If it's right, add the account to the MCP server: **Edit configuration** → tick it, or choose **All accounts**. ### This MCP has no calendar connection. Also for other types, such as **This MCP has no contacts connection.** **What it means:** your AI tried a tool for a type of account this MCP server doesn't reach. **How to fix it:** connect an account of that type, and make sure it's in the MCP server. Then refresh your AI app's tool list. ### This MCP has 2 calendar connections; pass account (one of: …). Also: **This MCP has 2 Zendesk accounts; pass account (one of: …).** **What it means:** the server has more than one account of that type, and your AI didn't say which one. **How to fix it:** nothing to change in Plugsight. Tell your AI which account to use, by its name or short name. It usually asks you or picks one from the list. ### No connection in this MCP reaches … "…" (or it is hidden). Call list_marketing_accounts. **What it means:** your AI asked for a Search Console site, Google Analytics property or ad account that this MCP server doesn't reach, or that you've hidden from AI apps. **How to fix it:** 1. On **Connections**, click **Show sites & accounts** on the marketing account's row. 2. If the item says **Hidden**, switch it back to **Visible**. 3. If it isn't listed, make sure you signed in with the login that has access to it, then click **Refresh list**. 4. Make sure the connection is in the MCP server. ### Unknown connection "…". Call list_marketing_accounts. **What it means:** your AI named a marketing connection this MCP server doesn't include. **How to fix it:** add the connection to the MCP server, or tell your AI which site or ad account you mean. ### No Google Analytics accounts are connected and visible. The service name changes: Search Console, Google Ads and so on. **What it means:** this MCP server has no visible accounts for that service. Either none is connected, it isn't in the server, or every one of its items is hidden. **How to fix it:** connect the service, add it to the MCP server, and check its items are **Visible** on **Connections**. ### Unknown or hidden calendar. Call calendar_list_calendars. **What it means:** your AI asked for a calendar that doesn't exist or that you've hidden from AI apps. **How to fix it:** on **Connections**, click **Show calendars** on the calendar account's row and make sure the one you want is **Visible**. ### … is a Zendesk account, not a mailbox. Use the zendesk_* tools. Also: **… isn't a mailbox. Use the tools for its type (list_accounts shows each type).** and **… is not a Zendesk account.** **What it means:** your AI used an email tool with a non-email account, or a Zendesk tool with something that isn't Zendesk. **How to fix it:** nothing to change in Plugsight. Ask again, naming the right kind of account. Your AI usually corrects itself. ## Marketing answers stop on the Free plan On the Free plan, your AI can make 25 marketing tool calls a month. Once they're used, marketing tools answer with a note saying so, until the 1st of next month. See [Plans and limits](/troubleshooting/plan-limits). ## Calendar booking tools missing The tools that book, move and cancel events only appear when at least one calendar account in the MCP server was connected with permission to change events. If yours was connected read-only, reconnect it and allow changes when the provider asks. Google Calendar stays read-only until Google approves Plugsight's booking permission; Outlook and iCloud calendars can book. See [Your AI can't send or change anything](/troubleshooting/ai-cant-send-or-change). ## Related articles - [Troubleshooting overview](/troubleshooting) - [AI app problems](/troubleshooting/ai-app-problems) - [Reconnect needed](/troubleshooting/reconnect-needed) --- # Your AI can't send or change anything URL: https://docs.plugsight.app/troubleshooting/ai-cant-send-or-change Every reason Plugsight refuses a send, reply, ticket update or booking, with the exact message your AI shows and how to fix each one. Before your AI can send an email, reply to or update a ticket, or book, move or cancel an event, all of these must be true: 1. Your plan includes changes (Pro or Agency). 2. Nothing is paused on the **Permissions** page. 3. The MCP server has **Allow changes** ticked. 4. The account's switch under **Write access** on **Connections** is on. 5. For email: the account hasn't reached its daily email limit. 6. You said yes in the chat. When one isn't met, Plugsight refuses the change, records it in **Activity** as **Blocked**, and tells your AI why. Find the message below. > [!TIP] > The fastest check: on **Connections**, read the line under the account's switch. **Ready** means everything in Plugsight is set; anything else names the one thing still stopping it. Marketing and analytics, contacts, stores and Mailchimp only read: there's no way to make changes with them, so they show **Read-only** with no switch. ## Plan ### Sending email and changing helpdesk tickets are on the Pro plan. Upgrade under Billing to turn write access on. (https://app.plugsight.app/app/billing) **What it means:** you're on the Free plan. Your AI can read everything and write email drafts, but can't send, change tickets or book events. On **Connections**, the account shows **Drafts only · Upgrade** or **Read-only · Upgrade** instead of a switch. **How to fix it:** upgrade to Pro or Agency under **Billing**. Then turn on the account's switch on **Connections**. See [Plans and limits](/troubleshooting/plan-limits). ## Paused on the Permissions page A pause always wins over the account switches. While it's on, a red banner shows on every page. ### All write actions are paused for this account (Permissions page). Email sends add: "Save it as a draft instead." **What it means:** **Pause everything** is on. No account can send or make changes, whatever its switch says. **How to fix it:** open **Permissions** and click **Resume all**, or click **Resume** in the red banner. ### Email sending is paused (Permissions page). Save it as a draft instead. **What it means:** email is paused on **Permissions**. Your AI can still read and write drafts, but can't send. **How to fix it:** open **Permissions** and click **Resume** on the **Email** row. ### Email changes are paused (Permissions page). **What it means:** your AI tried to mark, label or move emails while email is paused. **How to fix it:** open **Permissions** and click **Resume** on the **Email** row. ### Helpdesk replies and updates are paused (Permissions page). **What it means:** helpdesk changes are paused. Your AI can still read tickets, but can't reply, add notes, update, apply macros or create tickets. **How to fix it:** open **Permissions** and click **Resume** on the **Helpdesk** row. ### Calendar changes are paused (Permissions page). **What it means:** calendar changes are paused. Your AI can still read your calendars and find free time, but can't book, move or cancel events. **How to fix it:** open **Permissions** and click **Resume** on the **Calendar** row. ## The MCP server doesn't allow changes ### The "…" MCP is set to drafts only. Save it as a draft instead. **What it means:** the MCP server your AI uses has **Allow changes** unticked, so email can only be drafted. **How to fix it:** 1. Open **MCP servers** and click the server named in the message. 2. Click **Edit configuration**. 3. Tick **Allow changes** and click **Save changes**. ### The "…" MCP is read-only. Allow changes on the MCP server first (MCP servers page). **What it means:** the same, for helpdesk or calendar changes. **How to fix it:** open the server on **MCP servers**, click **Edit configuration**, tick **Allow changes** and click **Save changes**. ## The account's switch is off ### Sending is off for "…". Turn it on under Connections, or save it as a draft. **What it means:** the email account's switch shows **Drafts only**. **How to fix it:** on **Connections**, click the account's switch under **Write access** so it shows **Can send**. ### Changes are off for "…". Allow them under Connections first. **What it means:** the Zendesk or calendar account's switch is off. **How to fix it:** on **Connections**, click the account's switch so it shows **Can reply & update** (Zendesk) or **Can book & change** (calendar). ## Daily email limit ### Daily limit reached: "…" sent 20 emails in the last 24 hours (limit 20, which you can change on the Permissions page). Save it as a draft instead. The numbers match your account and your limit. **What it means:** each email account can send a limited number of emails in any 24 hours: 20 by default. The window rolls: each email counts for 24 hours after it was sent, so sends free up one at a time. Drafts never count. **How to fix it:** - Wait. **Permissions** → **Daily email limit** shows each account's usage and when the next send frees up. - Or raise the limit there, anywhere from 1 to 500 emails a day per account. - Meanwhile, ask your AI to save the email as a draft and send it yourself. ## Not approved in the chat Every change waits for your yes in the chat. If your AI tries without it, Plugsight refuses and tells it to ask you first. The message depends on the change: - **Not sent: show the user the final email and set confirm: true only after they explicitly approve.** - **Not sent: show the user the draft and set confirm: true only after they explicitly approve.** - **Not posted: show the user the exact text and ticket, and set confirm: true only after they approve.** - **Not updated: show the user the exact changes and set confirm: true only after they approve.** - **Not applied: show the user the preview and set confirm: true only after they approve.** - **Not created: show the user the exact ticket details and set confirm: true only after they approve.** - **Not booked: show the user the exact event details and set confirm: true only after they approve.** - **Not changed: show the user the exact changes and set confirm: true only after they approve.** - **Not cancelled: show the user which event will be cancelled and set confirm: true only after they approve.** **What it means:** nothing is wrong with your settings. Your AI didn't have your approval yet. **How to fix it:** check the details your AI shows you, then reply "yes, go ahead". If you use the developer API, add `"confirm": true` to the request. ## Connected read-only Some accounts were connected with read access only. Turning the switch on isn't enough: you need to reconnect and allow the extra permission. On **Connections**, these show **Read-only** with a lock; click it to see "How to allow changes". ### "…" was connected read-only. Reconnect it on the Connections page in Plugsight and allow "View and edit events". **What it means:** the Google Calendar account was connected without permission to change events. **How to fix it:** on **Connections**, click **Reconnect** on the account and, when Google asks, tick "View and edit events". Your settings stay. Google only offers this permission once it has approved Plugsight's booking permission; until then, Google Calendar connections are read-only. ### This Outlook account was connected read-only. Reconnect it in the app (Connections → Reconnect) to allow drafts and sending. **What it means:** the Outlook mailbox was connected without permission to write drafts or send. **How to fix it:** on **Connections**, click **Reconnect** on the account and allow the extra permission when Microsoft asks. ### You can only view "…", not change it. Pick another calendar. **What it means:** you can see this calendar, but your account can't change it (for example, a calendar someone shared with you as view-only). **How to fix it:** ask your AI to use another calendar, or ask the calendar's owner for edit access. ## Other reasons ### Sending is turned off on this server. Save it as a draft instead. **What it means:** sending email is switched off for everyone on this Plugsight service. On **Permissions**, the type shows **Not available yet**. It's not a setting you can change. **How to fix it:** ask your AI to save a draft, then send it yourself from your mailbox. ### Sending isn't available for this account type (no outgoing mail server configured). **What it means:** the mailbox was connected without an outgoing (SMTP) server, so it can read and draft but not send. **How to fix it:** connect the mailbox again with its outgoing server details filled in. Connecting the same address again updates the existing connection. ### Outlook always emails invitations to guests. Book without guests, or allow the invitations. **What it means:** your AI tried to add guests to an Outlook event without sending invitations. Outlook can't do that. **How to fix it:** tell your AI to send the invitations, or to book the event without guests. ### Google Meet links can only be added to Google calendars. Add a video link in the description instead. **What it means:** your AI asked for a Meet link on an Outlook or iCloud calendar. **How to fix it:** ask your AI to put a video link in the event description instead. ### Zendesk refused this action for that agent (…). Ask a Zendesk admin for that permission, or reconnect as an admin. **What it means:** Plugsight is allowed to make the change, but the Zendesk agent you connected doesn't have permission to do it in Zendesk. **How to fix it:** ask a Zendesk admin to give that agent the permission, or reconnect Zendesk as an agent who has it. ## Still blocked? Open **Activity** and find the attempt. **Blocked** means a Plugsight setting stopped it, and the reason is shown underneath. **Failed** means the service itself refused it; see [Errors from your AI's tools](/troubleshooting/tool-errors). ## Related articles - [Troubleshooting overview](/troubleshooting) - [Plans and limits](/troubleshooting/plan-limits) - [Reconnect needed](/troubleshooting/reconnect-needed) --- # Reconnect needed URL: https://docs.plugsight.app/troubleshooting/reconnect-needed Why an account shows Reconnect needed, the reason Plugsight gives for each service, and how to reconnect it without losing any settings. When a service stops accepting an account's login, Plugsight marks it **Reconnect needed**. Your AI can't use that account until you sign in again. Your other accounts keep working. ## Where you see it - On **Connections**, the account's **Status** shows **Reconnect needed**, with the reason underneath. - A red banner at the top of the app says **"1 connection needs reconnecting."** (or more), listing each account with a **Reconnect** button. - We email you, with the subject **"Reconnect … to keep using it with your AI"**, the first time it happens (at most once a day per account). - Your AI may pass on a message such as "… no longer accepts this connection's sign-in. Reconnect it on the Connections page in Plugsight." Plugsight checks each login regularly, so a broken login usually shows before your AI runs into it. While it's working, **Status** shows **Connected** and "Login checked … ago". Network problems and timeouts never mark an account. Only a clear "no" from the service does. ## How to reconnect 1. Open **Connections**. 2. Click **Reconnect** on the account's row (or in the red banner). 3. Sign in again, or paste a new password or key, as you did when you first connected it. 4. You're back on **Connections**, with a message starting "Reconnected". Nothing is lost: the account keeps its short name, its MCP servers, its write switch and its hidden items. The mark clears as soon as the new login works. > [!TIP] > For accounts connected with a password, app password or key, connecting the same account again (same email address or store address) updates the existing connection rather than adding a second one. ## Reasons, by service The line under **Reconnect needed** says what the service told us. ### Google sign-in was revoked or has expired. Your AI may see: "Google session expired or was revoked; reconnect this account in the app." **What it means:** Google stopped accepting Plugsight's access to this Google account. This usually happens after a password change, or when access was removed at Google. **How to fix it:** click **Reconnect**, choose the same Google account, and tick every permission box Google shows. ### Microsoft sign-in was revoked or has expired. Also: **Microsoft rejected this connection's access.** Your AI may see: "Microsoft session expired or was revoked; reconnect this account in the app." **What it means:** Microsoft stopped accepting the sign-in for this Outlook, Outlook Calendar, Outlook Contacts or Microsoft Advertising account. This usually happens after a password change, or when access was removed at Microsoft. **How to fix it:** click **Reconnect** and sign in with the same Microsoft account. If Microsoft says an administrator must approve, see [Errors while connecting an account](/troubleshooting/connection-errors). ### This Meta Ads sign-in expired on …: Meta sign-ins last about 60 days. Reconnect Meta Ads on the Connections page. Also: **Meta no longer accepts this Meta Ads sign-in: it expired (Meta sign-ins last about 60 days) or access was removed. Reconnect Meta Ads on the Connections page.** **What it means:** Meta's sign-ins can't be renewed in the background, so a Meta Ads connection needs signing in again about every 60 days, or sooner if the Facebook password changed or Plugsight was removed from the account's apps. **How to fix it:** click **Reconnect** and sign in with the same Facebook account. See [Meta Ads](/connectors/meta-ads). ### This LinkedIn Ads sign-in expired on [date]. Reconnect LinkedIn Ads on the Connections page. Also: **LinkedIn no longer accepts this LinkedIn Ads sign-in: it expired or access was removed. Reconnect LinkedIn Ads on the Connections page.** **What it means:** LinkedIn's sign-ins last about 60 days. Plugsight renews them in the background when LinkedIn allows it, for up to a year after you connected; after that, or if access was removed, LinkedIn needs you to sign in again. **How to fix it:** click **Reconnect** and sign in with the same LinkedIn account. See [LinkedIn Ads](/connectors/linkedin-ads). ### TikTok no longer accepts this TikTok Ads sign-in: access was removed or the authorisation was revoked. Reconnect TikTok Ads on the Connections page. Also: **This TikTok Ads sign-in expired on …, and TikTok can't renew it. Reconnect TikTok Ads on the Connections page.** **What it means:** TikTok stopped accepting the sign-in, for example because Plugsight's access was removed from the ad account, or the sign-in reached an end date TikTok set. **How to fix it:** click **Reconnect** and sign in with the same TikTok for Business login, choosing the same ad accounts. See [TikTok Ads](/connectors/tiktok-ads). ### The provider rejected this connection's access; it may have been revoked. Reconnect it on the Connections page. **What it means:** a Google or Microsoft service other than email (for example Search Console, Google Analytics, Google Ads, Google Calendar or Contacts) refused the saved login. **How to fix it:** click **Reconnect** and sign in again, ticking the permission box. ### The mail server rejected the password; it may have been changed or revoked. **What it means:** a mailbox connected with a password or app password (Gmail with an app password, iCloud Mail, Yahoo, AOL, Zoho, any IMAP mailbox) no longer accepts it. Usually the app password was deleted, or the account's password was changed. **How to fix it:** 1. Create a new app password at your provider. See [App password problems](/troubleshooting/app-passwords). 2. On **Connections**, click **Reconnect**. The connect form opens with your address filled in. 3. Paste the new app password and click **Test connection & save**. ### Apple rejected the Apple ID or app-specific password. Make a new app-specific password and reconnect. **What it means:** iCloud Calendar or iCloud Contacts no longer accepts the app-specific password, for example because it was deleted at Apple. **How to fix it:** create a new app-specific password at account.apple.com → **Sign-In and Security** → **App-Specific Passwords**. Then click **Reconnect** and paste it. ### Zendesk sign-in expired or was revoked. Your AI may see: "Zendesk sign-in expired or was revoked. Reconnect this account in the app." **What it means:** the Zendesk agent connected with **Sign in with Zendesk** is no longer signed in, for example because Plugsight's access was removed in Zendesk. **How to fix it:** click **Reconnect** and sign in to Zendesk as an agent or admin. ### Zendesk rejected the API token. Your AI may see: "Zendesk rejected the credentials. Check the agent email and API token. Zendesk no longer issues new tokens, so use Sign in with Zendesk if this one was removed." **What it means:** the Zendesk API token was deleted, switched off or expired. Zendesk tokens unused for 30 days stop working. **How to fix it:** remove the connection and connect Zendesk again with **Sign in with Zendesk**. Zendesk stopped creating new API tokens on 27 October 2026, and switches existing ones off on 30 April 2027. ### The store rejected Plugsight's keys; they may have been revoked. **What it means:** your WooCommerce store no longer accepts the keys Plugsight was given. Someone may have deleted them under **WooCommerce** → **Settings** → **Advanced** → **REST API**. **How to fix it:** click **Reconnect** and approve Plugsight in your store again, or create new read-only REST API keys and paste them. ### The store rejected Plugsight's integration keys; the integration may have been deleted or its keys renewed. **What it means:** your Magento store no longer accepts the four integration keys. The integration may have been deleted, or its keys renewed. **How to fix it:** in Magento admin, go to **System** → **Extensions** → **Integrations**, check the Plugsight integration is active, and copy its four keys again. Then reconnect Magento in Plugsight and paste them. ### Mailchimp rejected the API key; it may have been deleted or disabled. **What it means:** the Mailchimp API key was deleted, disabled or has expired. New Mailchimp keys expire after a year. **How to fix it:** create a new key in Mailchimp (profile picture → **Profile** → **Extras** → **API keys** → **Create A Key**), then reconnect Mailchimp and paste it. ## "Reconnect" without "Reconnect needed" Sometimes an account shows a **Reconnect** button while its status is still **Connected**. That means it works, but was connected with read access only, so your AI can't make changes with it. Reconnect it and allow the extra permission if you want changes. See [Your AI can't send or change anything](/troubleshooting/ai-cant-send-or-change#connected-read-only). ## Related articles - [Troubleshooting overview](/troubleshooting) - [App password problems](/troubleshooting/app-passwords) - [Errors while connecting an account](/troubleshooting/connection-errors) --- # Errors while connecting an account URL: https://docs.plugsight.app/troubleshooting/connection-errors Every error you can see while connecting Google, Microsoft, a mailbox, iCloud, Zendesk, WooCommerce, Magento, Shopify or Mailchimp, and how to fix it. Plugsight checks every new connection before saving it: it signs in, or tests the password or keys with the service. If that fails, nothing is saved and you see an error. Find it below. > [!TIP] > Failed attempts also appear in **Activity**, starting "Connecting … failed:", with the full message. ## Signing in with Google, Microsoft or Zendesk These messages appear after the provider's sign-in page sends you back to Plugsight. "Google", "Microsoft" or "Zendesk" is filled in. ### You didn't allow access in Google. Click Connect again and allow it, ticking every permission box. **What it means:** you clicked **Cancel** or **Deny** on the provider's page, or closed it. **How to fix it:** start again from the connector and, on the provider's page, allow access. On Google's page, tick every permission box: unticked boxes mean the connection can't work. ### Your organisation needs an administrator to approve Plugsight in Microsoft. Ask your IT admin, or if you are the admin, sign in and consent on behalf of the organisation. **What it means:** your company restricts which apps staff can connect, and Plugsight hasn't been approved yet. **How to fix it:** ask your IT admin to approve Plugsight. If you are the admin, connect again and tick **Consent on behalf of your organisation** when Microsoft asks. ### The Google sign-in expired before it finished. Click Connect and sign in again. Also: **The sign-in didn't finish. Click Connect and sign in again.** **What it means:** the sign-in wasn't completed in time. **How to fix it:** start again from the connector, and finish the provider's pages in one go. ### Google sign-in didn't finish. Click Connect to try again. (Google said: …) **What it means:** the provider ended the sign-in with an error of its own, shown in brackets. **How to fix it:** try again. If it repeats, the provider's message in brackets usually says why; send it to info@plugsight.app if it doesn't make sense. ### Your session changed during sign-in. Please try again. **What it means:** while you were on the provider's page, you signed out of Plugsight or signed in as someone else in another tab. **How to fix it:** make sure you're signed in to the right Plugsight account, then connect again. ### We couldn't read this account's email address. Sign in again, choosing an account that has an email address. **What it means:** the Google or Microsoft account you picked didn't give an email address. **How to fix it:** connect again and choose a different account, one with an email address. ## Google ### "Google hasn't verified this app" **What it means:** Google shows this warning while it reviews new apps. It doesn't mean anything is wrong. **How to fix it:** on Google's page, click **Advanced**, then **Go to Plugsight (unsafe)**, and carry on. ### Google returned no refresh token. Remove the app's access in your Google account and try again. **What it means:** Google didn't give Plugsight lasting access to the account. **How to fix it:** remove Plugsight's access in your Google account, then connect again. ### Gmail access wasn't granted. Tick the Gmail permission and try again. Also, for other Google services: **… access wasn't granted. Tick the permission and try again.**, with the service's name (Google Analytics, Search Console, Google Ads, Calendar, Contacts and so on). **What it means:** on Google's permission page, the box for this service was left unticked. **How to fix it:** connect again and tick the permission box Google shows. The Plugsight page before Google's names the exact permission to tick. ### … is a Google account without a Gmail inbox. If your email is in Outlook or Microsoft 365, connect it with Outlook instead; for other providers, use "Connect a mailbox". **What it means:** this Google account has no Gmail. Your email lives somewhere else. **How to fix it:** connect the mailbox with the right connector: **Outlook** for Microsoft 365. For other providers, open the **Connector catalog**, type your email address in the box "Or type an email address to detect its provider" and click **Detect**. ### That Google service isn't recognised. Pick one from the list of connectors. **What it means:** the page was opened from an old or edited link. **How to fix it:** go back to the **Connector catalog** and pick the Google service again. ### Problems: Google Ads: the Google Ads developer token only has test access, so real ad accounts are blocked. … **What it means:** the connection was saved, but Google Ads refused to list real ad accounts. The message after "Problems:" names each service that failed and why. **How to fix it:** the Google Ads developer token belongs to the Plugsight service, not to your account, so contact info@plugsight.app about this one. For other services named after "Problems:", open **Connections**, click **Show sites & accounts** on the account and then **Refresh list**. ### Google Ads isn't set up on this server (no developer token). Search Console and Analytics still work. Also: **Microsoft Advertising isn't set up on this server (no developer token).** **What it means:** this Plugsight service can't reach that ad platform yet. **How to fix it:** nothing you can change. Contact info@plugsight.app. ### … didn't answer: … Try Refresh list below; if it keeps failing, reconnect this account. **What it means:** on **Connections**, when you open a marketing account's sites and accounts, one Google or Microsoft service didn't answer. **How to fix it:** click **Refresh list**. If it keeps failing, click **Reconnect** on the account. ### This login doesn't reach anything yet. **What it means:** the Google or Microsoft login you used has no sites, properties or ad accounts in that service. **How to fix it:** connect again with the login that has access, or give this login access at the provider. Then click **Refresh list**. ## Microsoft (Outlook and Microsoft Advertising) ### Microsoft didn't grant lasting access. Remove Plugsight at myapps.microsoft.com, then connect again. **What it means:** Microsoft didn't give Plugsight access that lasts beyond the sign-in. **How to fix it:** open myapps.microsoft.com, remove Plugsight, then connect again. ### Outlook isn't set up on this server yet. Also: **Choose Outlook Calendar or Outlook Contacts.** (from an old or edited link). **What it means:** this Plugsight service can't connect Outlook right now, or the link was wrong. **How to fix it:** pick the connector again from the **Connector catalog**. If Outlook still isn't available, contact info@plugsight.app. ## Mailboxes with a password (IMAP) For Gmail with an app password, iCloud Mail, Yahoo, AOL, Zoho and other mailboxes. For problems making the app password itself, see [App password problems](/troubleshooting/app-passwords). ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** the mail server refused the login. The part after "Could not connect:" is the mail server's own message. **How to fix it:** 1. Make sure you pasted an **app password**, not your normal password. Most providers require one. 2. Make sure the email address is exactly the mailbox the app password belongs to. 3. If you made the app password a while ago, make a new one: it may have been deleted. 4. Some providers need IMAP access switched on in their settings first, for example Zoho, GMX, WEB.DE, Yandex, Seznam and many others. The connect page for your provider says what to switch on. ### Could not connect: … Without the password hint, the mail server refused for another reason, given in its message. **How to fix it:** read the mail server's message. For "Other IMAP" mailboxes, check the server names and ports with your provider. ### Couldn't find imap.example.com. Check the server name for typos. **What it means:** the server name doesn't exist. **How to fix it:** check the spelling of the IMAP (and SMTP) server name. ### imap.example.com refused the connection. Check the port number, or whether the server allows this kind of access. **What it means:** the server exists but refused on that port. **How to fix it:** check the port. IMAP is usually 993, and SMTP 465 or 587. Also check the provider allows IMAP access. ### Couldn't reach imap.example.com in time. Check the server name and port, then try again. **What it means:** the server didn't answer. **How to fix it:** check the server name and port, then try again. ### The secure connection to imap.example.com failed. Check the port and whether it expects SSL/TLS. **What it means:** the server's secure connection didn't work on that port. **How to fix it:** use the port that matches SSL/TLS (usually 993 for IMAP). ### We couldn't detect this provider's settings. Enter its IMAP (and SMTP) details below. **What it means:** Plugsight couldn't work out your provider from the email address. **How to fix it:** enter the incoming (IMAP) and outgoing (SMTP) server details from your provider's help pages. ### IMAP server is required. **What it means:** the **Other IMAP** form was sent without an IMAP server name. **How to fix it:** fill in the IMAP server. ### Proton Mail only works through Proton Mail Bridge running on your own computer, so it can't be connected to a cloud service like this one. **What it means:** Proton Mail can't be connected to Plugsight. **How to fix it:** there's no workaround. ### Enter the password. Also: **Enter a valid email address.**, **Enter a full email address.** and **Unknown provider.** **What it means:** a field is empty or isn't valid. **How to fix it:** fill it in and try again. ## iCloud Calendar and Contacts ### Apple didn't accept that Apple ID and password. Use an app-specific password (account.apple.com → Sign-In and Security → App-Specific Passwords), not your normal password. **What it means:** Apple refused the login. Apple only allows app-specific passwords here. **How to fix it:** create an app-specific password at account.apple.com → **Sign-In and Security** → **App-Specific Passwords**, paste it, and use your Apple ID email address. ### Enter the app-specific password. **What it means:** the password box is empty. **How to fix it:** paste the app-specific password. ### Pick iCloud Calendar or iCloud Contacts from the catalog. **What it means:** the page was opened from an old or edited link. **How to fix it:** go back to the **Connector catalog** and pick iCloud Calendar or iCloud Contacts. ## Zendesk ### Enter your Zendesk address, like yourcompany.zendesk.com. **What it means:** the address box is empty or isn't a Zendesk address. **How to fix it:** type the part of your Zendesk address before `.zendesk.com`, as in your browser's address bar when you use Zendesk. ### Zendesk sign-in failed: … **What it means:** connecting with **Sign in with Zendesk** didn't finish. The rest of the message says why, using the sign-in messages above. **How to fix it:** click **Continue with Zendesk** again, sign in as an agent or admin, and click **Allow**. ### That Zendesk user isn't an agent. Use an agent or admin account. **What it means:** you signed in with a Zendesk customer (end-user) account. Plugsight needs an agent. **How to fix it:** sign in to Zendesk as an agent or admin, then connect again. ### Could not connect: Zendesk rejected the credentials. Check the agent email and API token. Zendesk no longer issues new tokens, so use Sign in with Zendesk if this one was removed. **What it means:** the API token or the agent email is wrong, or the token was switched off. **How to fix it:** use **Sign in with Zendesk** instead. Zendesk stopped creating new API tokens on 27 October 2026 and switches existing ones off on 30 April 2027. Tokens unused for 30 days already stop working, and Zendesk accounts created since 28 July 2026 can't use tokens. ### Sign in with Zendesk isn't set up on this server yet. If you already have a Zendesk API token, use that. **What it means:** this Plugsight service can't use Zendesk sign-in right now. **How to fix it:** connect with an API token that's still active, or contact info@plugsight.app. ### Enter the API token. **What it means:** the token box is empty. **How to fix it:** paste the token, with the email of the agent the AI should act as. ## WooCommerce ### Enter your store's web address, like shop.example.com. **What it means:** the address box is empty or isn't a web address. **How to fix it:** type the address customers visit, like shop.example.com. Your store must use https. ### That address isn't a public website. Enter your store's web address, like shop.example.com. **What it means:** the address points to a private network, not a public website. **How to fix it:** use your store's public address. ### shop.example.com didn't answer like a WooCommerce store (HTTP …). Check the address, and that WooCommerce is installed and its REST API isn't blocked by a security plugin. **What it means:** the site answered, but not as a WooCommerce store would. **How to fix it:** check the address, check WooCommerce is installed and active, and check no security plugin or firewall blocks the WooCommerce REST API. ### The store wasn't connected: the approval was cancelled. Click Connect and choose Approve. **What it means:** you didn't click **Approve** on your store's "Plugsight would like to connect" page. **How to fix it:** click **Continue to my store** again and click **Approve**. ### shop.example.com approved Plugsight but couldn't send us the keys (some hosts block this). Use "Connect with REST API keys" below instead. **What it means:** your web host blocked the store from sending the keys to Plugsight. **How to fix it:** 1. Open **Connect with REST API keys instead** on the WooCommerce connect page. 2. In WordPress, go to **WooCommerce** → **Settings** → **Advanced** → **REST API** and click **Add key**. 3. Describe it as "Plugsight", pick your user, set **Permissions** to **Read** and click **Generate API key**. 4. Copy both keys (WooCommerce shows the secret once) and paste them into Plugsight. ### The store didn't accept these keys. Copy both again in full from WooCommerce → Settings → Advanced → REST API, with Read access. **What it means:** the consumer key or secret is wrong, incomplete or deleted. **How to fix it:** create a new read-only key and paste both parts in full. ### The store's keys don't allow this. Reconnect and approve read access, or check a security plugin isn't blocking the WooCommerce API. **What it means:** the store accepted the keys but refused to share orders with them. **How to fix it:** make sure the key has **Read** permission, and that no security plugin blocks the WooCommerce REST API. ### The consumer key starts with ck_. Also: **The consumer secret starts with cs_.**, **Enter the consumer key.**, **Enter the consumer secret.** and **Enter your store's web address.** **What it means:** a key was pasted into the wrong box, cut short, or left empty. **How to fix it:** paste the consumer key (starts with `ck_`) and the consumer secret (starts with `cs_`) into their own boxes. ### Couldn't reach the store: … Or one of the network messages: "Couldn't find …", "… refused the connection", "Couldn't reach … in time", "The secure connection to … failed". **What it means:** Plugsight couldn't reach your store's website. **How to fix it:** check the address, and that your site is online and uses https. ## Magento / Adobe Commerce ### shop.example.com didn't answer like a Magento store (HTTP …). Check the address, and that the REST API isn't blocked by a firewall or security module. **What it means:** the site answered, but not as a Magento store would. **How to fix it:** check the address, and check no firewall or security module blocks Magento's REST API. ### The store didn't accept these keys. Copy all four again from the integration's details in Magento admin, and check the integration says Active. **What it means:** one of the four keys is wrong, or the integration isn't active. **How to fix it:** in Magento admin, go to **System** → **Extensions** → **Integrations**. Check the Plugsight integration is active (click **Activate**, then **Allow**, if not). Copy all four keys again with **Edit** → **Integration Details**. ### The integration isn't allowed to read this. In Magento admin, edit the integration's API resources to include …, save, then reauthorize it. **What it means:** the integration can't read orders, products or customers. **How to fix it:** edit the integration, open the **API** tab, set **Resource Access** to **Custom** and tick **Sales** → **Operations** → **Orders**, **Catalog** → **Inventory** → **Products** and **Customers** → **All Customers**. Save, reauthorize it, then copy the new keys into Plugsight. ### The consumer key is 32 letters and numbers. Copy it from the integration's details. The same message appears for the consumer secret, access token and access token secret, along with **Enter the consumer key.** and so on when a box is empty. **What it means:** a key is incomplete or in the wrong box. **How to fix it:** copy each of the four keys into its matching box. ## Shopify ### Enter your store's myshopify.com address, like your-store.myshopify.com. Your Shopify admin shows it under Settings → Domains. **What it means:** Plugsight connects to Shopify stores only by their myshopify.com address, not a custom domain. **How to fix it:** in your Shopify admin, open **Settings** → **Domains** and copy the address ending in .myshopify.com. ### Shopify didn't accept this client ID and secret for …. Check you copied both from the app's settings in the Dev Dashboard, that the app is installed on this store, and that the store belongs to the same organisation as the app. **What it means:** Shopify wouldn't give Plugsight an access token for the store. **How to fix it:** copy the client ID and secret again, check the app is installed on that store, and make the app from the store's own admin, signed in with a staff account of the store's organisation (an agency's collaborator account can't). See [Shopify](/connectors/shopify#what-you-need). ### The app on … can't read orders. Add the read_orders access scope (and …) to the app, release a new version and update the app on the store, then try again. **What it means:** the app is missing the access scopes Plugsight needs. **How to fix it:** add the access scopes the message lists to the app, release the new version, approve the update on your store, then connect again. ## Mailchimp ### That isn't a Mailchimp API key. It ends with a dash and letters and numbers, like -us21. Also: **Enter your Mailchimp API key.** **What it means:** what you pasted isn't a complete Mailchimp API key. **How to fix it:** copy the whole key, including the ending like `-us21`. ### Mailchimp didn't accept that API key. Check you copied all of it, including the ending like -us21, and that it hasn't been deleted. **What it means:** Mailchimp refused the key. **How to fix it:** create a new key in Mailchimp (**API keys** → **Create A Key** → **Generate Key**) and paste it. Mailchimp shows the key once. ### Couldn't reach Mailchimp: … **What it means:** Mailchimp didn't answer. **How to fix it:** try again in a few minutes. ## Any connector ### That didn't work. Refresh the page and try again; if it keeps happening, contact us. Also: **The server didn't answer properly (error …). Wait a moment and try again.** **What it means:** something unexpected went wrong. **How to fix it:** refresh the page and try again. If it keeps happening, email info@plugsight.app. ### Your Free plan includes 2 connections. Upgrade to Pro for 10. Or another plan limit message. See [Plans and limits](/troubleshooting/plan-limits). ### Marketing and analytics connectors (Google Ads, Microsoft Ads, Search Console, GA4 and others) are on the Pro plan. Upgrade under Billing to connect them. See [Plans and limits](/troubleshooting/plan-limits). ## Related articles - [App password problems](/troubleshooting/app-passwords) - [Reconnect needed](/troubleshooting/reconnect-needed) - [Troubleshooting overview](/troubleshooting) --- # App password problems URL: https://docs.plugsight.app/troubleshooting/app-passwords Fix app password problems for Gmail, iCloud, Yahoo, AOL, Zoho and other mailboxes, including Google's "not available for your account". Many email providers don't let other apps use your normal password. Instead, you create an **app password**: a separate password just for Plugsight. Your real password stays private, and you can delete the app password at your provider any time to cut access. ## Problems that apply to every provider ### Could not connect: … Check the password; most providers need an app password, not your normal one. **What it means:** the mail server refused the password. **How to fix it:** 1. Make sure you pasted the **app password**, not your normal password. 2. Make sure the email address is the account the app password was made for. If you're signed in to several accounts at your provider, check you made it in the right one. 3. Copy it again. Providers show it only once: if you closed the page, make a new one. 4. Spaces don't matter for known providers. They often show app passwords in groups, and Plugsight removes the spaces for you. ### It worked, then stopped **What it means:** the app password was deleted, or the account's password was changed. **Connections** shows **Reconnect needed** with "The mail server rejected the password; it may have been changed or revoked." **How to fix it:** make a new app password, then click **Reconnect** on the account and paste it. Connecting the same email address again updates the existing connection. See [Reconnect needed](/troubleshooting/reconnect-needed). ## Gmail Google only offers app passwords when **2-Step Verification** is on. 1. Open myaccount.google.com/signinoptions/twosv. If you see a blue **Turn on 2-Step Verification** button, add your **Phone number** first, then click that button. 2. Open myaccount.google.com/apppasswords, type **Plugsight** as the name and click **Create**. 3. Google shows a 16-letter password. Copy it before closing the tab: Google shows it only once. 4. Paste it into Plugsight and click **Test connection & save**. > [!TIP] > Signed in to several Google accounts? The links on Plugsight's Gmail page open the account you typed. Check the photo at the top right of Google's page shows the right account. ### Google says "The setting you are looking for is not available for your account" **What it means:** Google hides the App passwords page for accounts that can't use app passwords. It's one of four reasons. Check them in order: 1. **2-Step Verification is off.** The most common reason. Turn it on (step 1 above), wait a minute, then open App passwords again. 2. **2-Step Verification uses only passkeys or security keys.** On the 2-Step Verification page, add a phone number or an authenticator app, then try again. 3. **It's a work or school account (Google Workspace).** Your administrator controls this. Ask them to allow 2-Step Verification for you in the Google Admin console. 4. **Advanced Protection is on.** Google never allows app passwords on these accounts, so this account can't be connected this way. **How to fix it:** fix the reason that applies. Still stuck? Sign out of Google, sign back in to this account, and try again: Google can take a few minutes to show the page after you change 2-Step Verification. ## iCloud Mail, iCloud Calendar and iCloud Contacts Apple calls it an **app-specific password**. 1. Open account.apple.com and sign in. 2. Go to **Sign-In and Security** → **App-Specific Passwords**. 3. Create one and copy it. 4. In Plugsight, use your Apple ID email address and paste the app-specific password. ### Apple didn't accept that Apple ID and password. Use an app-specific password (account.apple.com → Sign-In and Security → App-Specific Passwords), not your normal password. **What it means:** Apple refused the login for iCloud Calendar or Contacts. **How to fix it:** make a new app-specific password as above and paste it, with your Apple ID email address. ## Yahoo and AOL - **Yahoo:** Yahoo account → **Account security** → **External connections** → **Create app password** (login.yahoo.com/account/security). - **AOL:** AOL account → **Account security** → **Generate app password** (login.aol.com/account/security). Verizon.net addresses use AOL. ## Other providers What each provider asks for, as shown on its Plugsight connect page: | Provider | What to do | | --- | --- | | Zoho Mail | IMAP needs a paid Zoho Mail plan (not Forever Free). Turn on IMAP in Zoho Mail → Settings → Mail Accounts. With two-factor login, create an app-specific password. Custom-domain accounts: pick your data centre's Zoho entry. | | Fastmail | Settings → Privacy & Security → Connected apps & API tokens → Manage app passwords and access → New app password (keep Mail access). Not on Basic plans. | | Yandex Mail | Settings → Email clients: turn on IMAP and "App passwords and OAuth tokens", then create an app password in your Yandex ID. | | GMX, WEB.DE | Turn on POP3/IMAP access in settings. With two-factor login on, create an app-specific password. | | Mail.com | IMAP needs a Mail.com Premium plan. Then enable POP3/IMAP access in settings. | | Mail.ru | Third-party mail apps need a paid Mail.ru plan. Then Security → Passwords for external applications → create one with IMAP/SMTP access. | | AT&T | Create a secure mail key in your AT&T profile → Sign-in info → Secure mail key. | | T-Online | Create an E-Mail-Passwort in the T-Online Kundencenter (it differs from your login password). | | BT Email | Use your BT Email password, not your My BT ID password. | | Virgin Media | Create a Virgin Media Mail app password in My Virgin Media → Account details. | | mailbox.org | Use your mailbox.org password, or create one under Settings → mailbox.org → Email App Passwords. | | QQ, 163, 126, Yeah.net, Sina | Enable IMAP in the mail settings and create an authorization code. Use the code as the password. | | Naver, Kakao | Enable IMAP; with 2-step verification on, create an app password. | | Comcast / Xfinity | If your Comcast.net mail has moved to Yahoo, choose Yahoo Mail instead. Otherwise, allow third-party access in Xfinity Connect settings → Security, then use your Xfinity password. | | Cox | Cox.net mail has moved to Yahoo: if it doesn't connect, choose Yahoo Mail and use a Yahoo app password. | | GoDaddy | Use your GoDaddy email password. If your mailbox has moved to Microsoft 365, connect it with Outlook instead. | | Rediffmail | Rediffmail Pro (business) accounts only; free Rediffmail doesn't offer IMAP. | | Proton Mail | Can't be connected: it only works through Proton Mail Bridge on your own computer. | If your provider isn't listed, open the **Connector catalog**, type your email address in the box "Or type an email address to detect its provider" and click **Detect**: Plugsight finds the settings. If it can't, you see "We couldn't detect this provider's settings" and can enter the IMAP and SMTP details yourself. ## Related articles - [Errors while connecting an account](/troubleshooting/connection-errors) - [Reconnect needed](/troubleshooting/reconnect-needed) - [Troubleshooting overview](/troubleshooting) --- # Plans and limits URL: https://docs.plugsight.app/troubleshooting/plan-limits What each upgrade and limit message means, for connections, MCP servers, marketing data, sending email, the developer API and the daily email limit. Some features and limits depend on your plan. When you reach one, Plugsight says so and links to **Billing**. ## What each plan includes | | Free | Pro | Agency | | --- | --- | --- | --- | | Connections | 2 | 10 | 50 | | MCP servers | 1 | 5 | Unlimited | | Marketing and analytics connectors | To try: 1 connection, 25 tool calls a month | Yes | Yes | | Sending email, helpdesk changes, calendar bookings | No | Yes | Yes | | Developer API | No | Yes | Yes | | Price | $0 | $29 a month or $290 a year | $99 a month or $990 a year | On every plan, your AI can read everything you connect and write email drafts. ## Connection and MCP server limits ### Your Free plan includes 2 connections. Upgrade to Pro for 10. The same message names your plan and its limit: - **Your Free plan includes 1 MCP server. Upgrade to Pro for 5.** - **Your Pro plan includes 10 connections. Upgrade to Agency for 50.** - **Your Pro plan includes 5 MCP servers. Upgrade to Agency for unlimited.** - **Your Agency plan includes 50 connections. Contact us for a higher limit.** **What it means:** you already have as many connections or MCP servers as your plan allows, so you can't add another. **How to fix it:** click **See plans** next to the message, or open **Billing**, and upgrade. Or remove a connection or MCP server you no longer use. On Agency, email info@plugsight.app for more connections. > [!NOTE] > **Billing** shows how many connections and MCP servers you're using, out of your plan's limit. ## Marketing and analytics ### Your Free plan includes 1 marketing connection. Upgrade to Pro to connect more. **What it means:** you tried to connect another marketing or analytics account on the Free plan, which includes 1 to try. **How to fix it:** remove the one you don't need on **Connections**, or upgrade to Pro or Agency under **Billing**, then connect it. ### You've used the 25 marketing tool calls your Free plan includes this month. **What it means:** on Free, your AI can make 25 marketing tool calls each calendar month (UTC), counting only calls that worked. This one answered with this note instead of your data. **Billing** shows **Marketing calls this month**. **How to fix it:** they start again on the 1st of next month, or upgrade to Pro or Agency under **Billing** for no limit. If your plan changed to Free after you connected several marketing accounts, they all stay in your list and your AI can still use them, within Free's monthly marketing tool calls. Upgrading removes the limit. ## Sending and changes ### Sending email and changing helpdesk tickets are on the Pro plan. Upgrade under Billing to turn write access on. **What it means:** you tried to turn on an account's switch under **Write access** on the Free plan, or your AI tried to send, reply, update a ticket or book an event. On Free, the account shows **Drafts only · Upgrade** or **Read-only · Upgrade**, and **Permissions** shows **On the Pro plan**. **How to fix it:** upgrade to Pro or Agency under **Billing**, then turn on the account's switch on **Connections**. Your AI can still read everything and write email drafts on Free. ## Developer API ### The developer API is on the Pro and Agency plans. Upgrade at https://app.plugsight.app/app/billing. **What it means:** your code called the developer API with a valid key, but your account is on Free. The API answers `403 plan_required`. **How to fix it:** upgrade under **Billing**. See [Developer API errors](/developers/errors). ## Daily email limit Each email account can send up to 20 emails in any 24 hours by default. Change it on **Permissions** → **Daily email limit**, from 1 to 500. The 24 hours roll: each email counts for 24 hours after it's sent. Drafts never count. When an account reaches its limit, your AI sees "Daily limit reached". See [Your AI can't send or change anything](/troubleshooting/ai-cant-send-or-change#daily-email-limit). Messages when you change the limit: ### The limit can be at most 500 emails a day per account. **How to fix it:** enter 500 or less. ### The limit must be at least 1. **How to fix it:** enter 1 or more. To stop all sending, use **Pause** on **Permissions**, or turn off the account's switch. ### Enter a whole number. Also: **Enter a number of emails.** **How to fix it:** enter a number without decimals. ## Billing messages ### Payment failed **What it means:** this badge on **Billing** means your card couldn't be charged. Stripe tries again over the next few days, and your plan keeps working meanwhile. If every retry fails, you move to the Free plan: marketing connectors and sending email stop working in your AI. **How to fix it:** click **Update card** (or **Invoices, card & cancel**) and update your card. ### Cancelling **What it means:** you cancelled. You keep your plan until the date shown, then move to Free. Marketing and analytics connectors stop working in your AI, and it can't send email or make helpdesk changes (it can still read and draft). Accounts and MCP servers you already have stay, but you can't add more beyond the Free limits. **How to fix it:** changed your mind? Use **Invoices, card & cancel** to keep your plan. ### There's no billing account yet. Choose a plan first. **What it means:** you clicked to manage invoices or your card before ever choosing a paid plan. **How to fix it:** choose a plan under **Plans** on the **Billing** page first. ### That plan isn't available yet. **What it means:** the plan you picked can't be bought right now. **How to fix it:** choose another plan, or email info@plugsight.app. ### Billing isn't set up on this server. **What it means:** this Plugsight service doesn't take payments, so every feature is available without a plan. You won't see this on app.plugsight.app. **How to fix it:** nothing to do. ## Related articles - [Your AI can't send or change anything](/troubleshooting/ai-cant-send-or-change) - [Errors while connecting an account](/troubleshooting/connection-errors) - [Troubleshooting overview](/troubleshooting) --- # Sign-in problems URL: https://docs.plugsight.app/troubleshooting/sign-in-problems Every message you can see while signing in to Plugsight, creating an account, confirming your email or resetting your password, and how to fix it. These are problems signing in to Plugsight itself, at app.plugsight.app. For problems connecting an account such as Gmail or Zendesk, see [Errors while connecting an account](/troubleshooting/connection-errors). You can sign in three ways: with your email and password, with **Email me a sign-in link**, or with **Continue with Google** or **Continue with Microsoft**. ## Signing in ### Wrong email or password. **What it means:** the email address and password don't match an account. If you created your account with Google, Microsoft or a sign-in link, it may have no password at all. **How to fix it:** - Check the email address for typos. - Click **Email me a sign-in link** to sign in without a password. - Or click **Forgot password?** to choose a new one. ### Too many attempts. Try again in 15 minutes. **What it means:** there were too many wrong passwords for this email address (from your network, or from all networks together), too many sign-in attempts from your network, or too many sign-in link requests, in 15 minutes. Plugsight pauses them to protect your account. **How to fix it:** wait 15 minutes and try again. Meanwhile, nothing about your account changes. ### Enter your email first, then tap Email me a sign-in link. **What it means:** you clicked **Email me a sign-in link** with the email box empty. **How to fix it:** type your email address, then click it again. ### No sign-in link arrived After you ask for a link, Plugsight says a link is on its way "if [your address] can sign in". It always says this, so nobody can find out which addresses have accounts. **How to fix it:** - Check your spam folder. - Check you typed the address you signed up with. - The link works once and expires in 20 minutes. Ask for a new one if it's older. ### This sign-in link no longer works The page may also say **That login link is invalid or has expired.** **What it means:** the link was already used, or it's more than 20 minutes old. **How to fix it:** go back to sign in and click **Email me a sign-in link** again. ### Your Google account didn't share a verified email address. Also for Microsoft: **Your Microsoft account didn't share a verified email address.** **What it means:** Google or Microsoft didn't tell Plugsight a confirmed email address for the account you chose. **How to fix it:** choose another account, or sign in with your email address and a password or sign-in link instead. ### You didn't allow access in Google. Click Connect again and allow it, ticking every permission box. Or the other sign-in messages from Google or Microsoft, such as "The Google sign-in expired before it finished." **What it means:** the Google or Microsoft sign-in didn't finish. **How to fix it:** click **Continue with Google** (or Microsoft) again and finish the steps. See [Errors while connecting an account](/troubleshooting/connection-errors) for each sign-in message. ### Please sign in. **What it means:** you're signed out, for example because your session ended or you changed your password. **How to fix it:** sign in again. ## Creating an account ### That email already has an account. Sign in or reset your password. **What it means:** someone (probably you) already signed up with this address. **How to fix it:** sign in instead, or click **Forgot password?** on the sign-in page. ### Sign-ups are closed right now. **What it means:** Plugsight isn't taking new accounts at the moment. Existing accounts can still sign in. **How to fix it:** email info@plugsight.app to be told when sign-ups open. ### Too many sign-ups from your network. Try again later. **What it means:** there were too many sign-ups from your network in the last hour, or a great many sign-up forms that were refused (a short password or a mistyped address). A few mistakes on the form don't count towards the limit. **How to fix it:** try again in an hour. ### Use at least 10 characters. Also: **That password is too long.** and **Enter a valid email address.** **How to fix it:** choose a password of 10 characters or more, and check the email address. ## Confirming your email After signing up with a password, Plugsight sends a confirmation link. Until you open it, you see **Confirm your email**. ### Confirm your email address first. **What it means:** you tried to use the app before confirming your email. **How to fix it:** open the link in the email from Plugsight. Not there after a minute? Check your spam folder, or click **Resend email**. You'll see "Sent. Check your inbox and spam folder." ### Couldn't confirm your email The page may also say **That link is invalid or has expired. We can send you a new one.** **What it means:** the confirmation link was already used or is too old. **How to fix it:** sign in, then click **Resend email** on the **Confirm your email** page. ### That link is for a different account. Sign out and open it again. **What it means:** you opened a confirmation link for one email address while signed in as another. **How to fix it:** on the **Confirm your email** page, click **Use a different account**, sign in with the address the link was sent to, and open the link again. ### Sign in to confirm your email. **What it means:** you opened the confirmation link while signed out. **How to fix it:** sign in, then open the link again. ### Wrong address? On the **Confirm your email** page, click **Use a different account** to sign out and start again. ## Resetting your password 1. On the sign-in page, click **Forgot password?**. 2. Enter your email and click **Send reset link**. 3. Open the link in the email and choose a new password. The link expires in 1 hour. If the address has an account, a reset link is sent. Plugsight shows the same answer either way, so check you used the right address and your spam folder if nothing arrives. ### That link is invalid or has expired. Ask for a new one. **What it means:** the reset link was already used or is more than an hour old. **How to fix it:** click **Need a new link?** on the page, or **Forgot password?** on the sign-in page. ## Changing your password or deleting your account ### Current password is wrong. **What it means:** when changing your password under **Settings**, the current password didn't match. **How to fix it:** type your current password again. If you don't know it, sign out and use **Forgot password?**. After a password change, you're signed out everywhere and see "Password saved. Sign in again." ### Type your email exactly to confirm. **What it means:** to delete your account, you must type your account's email address, and what you typed didn't match. **How to fix it:** type your email address exactly as it appears in **Settings**. ## Related articles - [Troubleshooting overview](/troubleshooting) - [Plans and limits](/troubleshooting/plan-limits) - [Errors while connecting an account](/troubleshooting/connection-errors) --- # AI app problems URL: https://docs.plugsight.app/troubleshooting/ai-app-problems Fix problems adding Plugsight to Claude, ChatGPT and other AI apps - the sign-in window, approval screen errors, unknown accounts and missing tools. To use Plugsight, an AI app connects to one of your MCP servers. You paste the server's link into the app, a Plugsight window opens, and you click **Allow access**. These are the problems that can happen along the way, and after. ## The sign-in window doesn't open, or closes with an error **What it means:** the AI app couldn't open the Plugsight window, or the window couldn't finish. **How to fix it:** 1. Allow pop-ups for the AI app's website in your browser. 2. Make sure you're signed in to Plugsight in the same browser. 3. Remove the Plugsight connector in the AI app and add it again. > [!NOTE] > In Claude and ChatGPT, add the connector on the website (claude.ai or chatgpt.com) in a web browser. Their desktop and phone apps can't add one. Once added on the website, it works in Claude's apps too. ## Messages on Plugsight's approval screen ### This connector points at an MCP server that isn't in your account. Switch to the account that created it, or use the URL of one of your own servers. **What it means:** the link you pasted into the AI app belongs to an MCP server created by a different Plugsight account than the one you're signed in with. **How to fix it:** on the approval screen, click **Switch account** (next to "Signed in as …") and sign in with the account that created the server. Or, in the AI app, use the link of one of your own MCP servers, from **MCP servers** in Plugsight. ### You don't have an MCP server yet. Create one and pick the accounts it should reach, then go back to your AI app and connect again. **What it means:** your Plugsight account has no MCP server to connect to. **How to fix it:** click **Create one**, choose its accounts and click **Create server**. Then go back to the AI app and connect again. ### This AI app isn't registered. Start the connection again from your AI app. **What it means:** the AI app's request to Plugsight is incomplete or too old. **How to fix it:** close the window and start connecting again from the AI app. ### This AI app's connection is out of date. Remove the Plugsight connector in your AI app and add it again. **What it means:** the AI app is using connection details that Plugsight no longer recognises. **How to fix it:** in the AI app, remove the Plugsight connector, then add it again with your MCP server's link. ### This connector was set up for a different MCP server. Pick that server, or add a new connector in your AI app for this one. **What it means:** the link you pasted is for one MCP server, but a different one was chosen on the approval screen. **How to fix it:** approve the server the connector was made for. To use a different server, add a separate connector in the AI app with that server's link. ### Choose one of your MCPs. **What it means:** no server, or a server that isn't yours, was chosen on the approval screen. **How to fix it:** pick one of your servers under **Choose an MCP server**, then click **Allow access**. ### Signed in as the wrong person? The approval screen shows "Signed in as …" at the bottom. If it's the wrong account, click **Switch account**. ## Connected, but your AI can't find an account ### Unknown account "…". Call list_accounts to see valid ids. **What it means:** your AI asked for an account that isn't included in this MCP server. **How to fix it:** open the server on **MCP servers**, click **Edit configuration**, and choose **All accounts** or tick the account. See [Your AI can't see an account](/troubleshooting/ai-cant-see-account) for all the related messages. ## Connected, but tools are missing ### Plugsight's tools don't show in the chat **How to fix it:** - **Claude:** in the chat, click **+** (bottom left of the message box) → **Connectors**, and make sure your Plugsight server is switched on. - **ChatGPT:** start a new chat, click **+** next to the message box and select your Plugsight server. - Still missing? Refresh the app's tool list (below). ### Tools for an account you just added are missing **What it means:** AI apps load Plugsight's list of tools once, for example when a chat starts. When your connections change, the app keeps the old list until it reloads. **Connections** shows a notice such as **"Refresh Claude to use your changes"** with the steps for each app that needs it, and your AI may say "Note from Plugsight: the user's connections changed since this chat loaded its tool list…". **How to fix it:** - **Claude:** claude.ai/customize/connectors → your server → **⋯** → **Refresh tools list**, then start a new chat. - **ChatGPT:** chatgpt.com/settings/plugins-settings → your server → **Manage app** → **Refresh tools**, then start a new chat. - **Claude Code:** type `/mcp`, choose the server, then **Reconnect**. - **Cursor:** **Cursor Settings** → **Tools & MCP**, switch the server off and on. Full steps are in [Your AI can't see an account](/troubleshooting/ai-cant-see-account#your-ai-app-has-an-old-list-of-tools). ### ChatGPT can read but not send or change anything **What it means:** on the ChatGPT Pro plan (ChatGPT's own plan, not Plugsight Pro), ChatGPT connects to custom MCP servers read-only. **How to fix it:** use ChatGPT Business, Enterprise or Edu, or another AI app, to make changes. ### ChatGPT has no option to add a custom MCP server **What it means:** on Business, Enterprise and Edu, a workspace admin must allow it first. **How to fix it:** ask your workspace admin to allow **Create custom MCP servers** in the workspace settings (this used to be called Developer mode). ## Apps that use an API key Claude Code and other tools that can't open a sign-in window use the MCP server's API key instead. ### Sign in to use this MCP. **What it means:** the app sent no key, or a key that's been replaced or revoked. Apps that sign in with a window see it too after **Disconnect all AI apps**, but that button doesn't affect a key. **How to fix it:** on the MCP server's page, under **API key**, click **Create API key** (or **Regenerate key**), copy it, and update it in the app. For Claude Code, the server page shows the full `claude mcp add` command with the new key right after you create it. ## The AI app stopped working ### The MCP server was deleted **What it means:** when an MCP server is deleted, its link stops working in every AI app, for good. In Plugsight you may see "That MCP server no longer exists. Refresh the page." **How to fix it:** create a new MCP server, and add its link to the AI app as a new connector. ### Someone clicked Disconnect all AI apps **What it means:** **Disconnect all AI apps** in an MCP server's **Danger zone** cuts off every AI app using it at once. **How to fix it:** in each AI app, connect again and click **Allow access** on Plugsight's window. ### An account needs reconnecting **What it means:** your AI can't use an account whose login stopped working. A red banner on Plugsight says which. **How to fix it:** see [Reconnect needed](/troubleshooting/reconnect-needed). ## Related articles - [Your AI can't see an account](/troubleshooting/ai-cant-see-account) - [Your AI can't send or change anything](/troubleshooting/ai-cant-send-or-change) - [Troubleshooting overview](/troubleshooting) --- # Errors from your AI's tools URL: https://docs.plugsight.app/troubleshooting/tool-errors Messages from Gmail, Outlook, Zendesk, Google Ads, Analytics, stores and calendars that your AI passes on, what they mean and what to do. When your AI uses a tool and the service refuses or something's wrong with the request, Plugsight explains it in plain words and your AI usually passes it on. In **Activity**, these show as **Failed**, with the message underneath. Most are about the request itself, so your AI can often correct it and try again without you changing anything. ## Messages any service can give "…" is the service's name, such as Zendesk, WooCommerce, Magento, Mailchimp, Google or Microsoft. The service's own words often follow in brackets, starting "(… said: …)". ### … didn't accept that request. Check the values it names below and try again with corrected ones. **What it means:** the service rejected a value in the request, such as a date, field or id. **How to fix it:** nothing to change in Plugsight. Your AI reads the service's words in brackets and retries with corrected values. If it keeps failing, rephrase your request. ### … no longer accepts this connection's sign-in. Reconnect it on the Connections page in Plugsight. **What it means:** the login stopped working. **How to fix it:** click **Reconnect** on the account on **Connections**. See [Reconnect needed](/troubleshooting/reconnect-needed). ### … says this login isn't allowed to do that. Use an account with access, or ask its admin to grant it. **What it means:** the account you connected doesn't have permission for this at the service. **How to fix it:** ask the service's admin to give the login access, or connect a login that has it. ### … couldn't find that item. It may have been deleted, or the id is wrong: search or list again for a current id. **What it means:** the email, ticket, order or other item doesn't exist any more, or your AI used an old id. **How to fix it:** ask your AI to search again. ### … reported a conflict, usually because the item changed meanwhile. Fetch it again, then retry. **What it means:** someone changed the item while your AI was working on it. **How to fix it:** ask your AI to read it again and retry. ### … is limiting requests right now. Wait a minute, then try again. **What it means:** the service's own rate limit was reached. **How to fix it:** wait a minute, then ask again. Large questions over long date ranges use more requests. ### … is having problems right now. Try again in a few minutes. **What it means:** the service is down or overloaded. **How to fix it:** try again in a few minutes. ### … returned an unexpected error (HTTP …). Try again; if it keeps happening, reconnect the account. **What it means:** the service gave an error Plugsight doesn't recognise. **How to fix it:** try again. If it keeps happening, reconnect the account on **Connections**. ## Email ### This account has no "…" folder. Call list_folders to see what exists. **What it means:** your AI asked for a folder name that isn't in this mailbox. **How to fix it:** nothing to change. Your AI lists the folders and uses the right name. ### This mailbox has no Archive folder. Move it to a folder from list_folders instead (move_to: "\"). **What it means:** the mailbox has no folder called Archive. **How to fix it:** tell your AI which folder to move the emails to. ### Labels are a Gmail feature. For this mailbox, move the email to a folder instead (move_to). **What it means:** your AI tried to add a label in a mailbox that uses folders. **How to fix it:** ask your AI to move the email to a folder instead. ### Pick one folder to move to, e.g. "archive", "inbox" or a folder from list_folders. **What it means:** your AI asked to move emails to "all", which isn't a single folder. **How to fix it:** tell your AI the folder to use. ### Nothing to change: pass read, flagged, add_labels, remove_labels or move_to. **What it means:** your AI asked to organise emails without saying what to do. **How to fix it:** tell your AI what you want: mark read, flag, label or move. ### Message not found (it may have been moved or deleted) Also: **Invalid message id "…": use an id returned by search_emails or get_thread for this account.** **What it means:** the email was moved or deleted since your AI found it, or the id is from another account. **How to fix it:** ask your AI to search again. ### Draft not found (it may have been sent or deleted). Also: **That email isn't a draft.** and **The draft has no recipients.** **What it means:** your AI tried to send a draft that no longer exists, an email that isn't a draft, or a draft with no one to send to. **How to fix it:** check the draft in your mailbox, or ask your AI to write a new one. ### Add at least one recipient. **What it means:** your AI tried to send or draft an email with nobody in To, Cc or Bcc. **How to fix it:** tell your AI who it's for. ### Attachments total … MB; the limit is 20 MB. **What it means:** the attachments are too big to send in one email. **How to fix it:** send fewer or smaller files, or share a link instead. ### … is larger than 3 MB, which isn't supported for Outlook yet. **What it means:** Outlook accounts can't attach files over 3 MB through Plugsight yet. **How to fix it:** share a link to the file instead. ### Use either reply_to_email_id or forward_email_id, not both. **What it means:** your AI tried to reply and forward in one email. **How to fix it:** ask for a reply or a forward. ### No attachment at index …; this email has …. Also: **… is a link to a cloud file (OneDrive/SharePoint), not a stored file.**, **… is not an email or winmail.dat, so it has no attachments inside.** and **No file at index …; it contains ….** **What it means:** the attachment your AI asked for doesn't exist, or it's a link rather than a file. **How to fix it:** for cloud links, open the file from OneDrive or SharePoint yourself. Otherwise ask your AI to read the email again. ### Could not extract text from …: … **What it means:** the attachment couldn't be read as text, for example a damaged or protected file. **How to fix it:** open the file yourself. ## Zendesk ### Zendesk has no ticket or user with that id. Use zendesk_search_tickets or zendesk_find_users to find the right one. **What it means:** the ticket or user id doesn't exist, or was deleted. **How to fix it:** ask your AI to search for the ticket by subject or requester. ### Nothing to change: pass at least one of status, custom_status, priority, type, assignee_id, add_tags, remove_tags or from_address. **What it means:** your AI asked to update a ticket without any change. **How to fix it:** tell your AI what to change. ## Marketing and analytics ### Unknown field "…" for …. Call list_marketing_fields. **What it means:** your AI asked for a metric or dimension the service doesn't have. The message may suggest similar names. **How to fix it:** nothing to change. Your AI looks up the right field and retries. ### Unrecognised date "…". Use YYYY-MM-DD, today, yesterday or NdaysAgo. **What it means:** your AI used a date format the tool doesn't accept. **How to fix it:** nothing to change. Your AI retries with a correct date. You can also give exact dates in your question. ### These fields come from different Google Ads reports and can't be combined in one query: …. Split the request. Also for Microsoft Advertising, and: **"…" isn't available together with the other requested fields.** **What it means:** Google Ads or Microsoft Advertising can't report those fields together. **How to fix it:** ask for them in separate questions, or let your AI split the request. ### Microsoft Advertising has no field "…". **What it means:** your AI asked for a field Microsoft Advertising doesn't offer. **How to fix it:** nothing to change. Your AI picks another field. ### Report … still pending after 2 minutes; try a shorter date range. Also: **Microsoft Advertising failed to build the report.** and **Microsoft Advertising did not return a report id.** **What it means:** Microsoft Advertising took too long to build the report, or failed. **How to fix it:** ask for a shorter date range, or try again later. ### This report needs connector google_ads or bing_ads. Also: **period_comparison needs a connector.** and **period_comparison needs fields, e.g. [campaign, cost, conversions, cpa].** **What it means:** your AI started a ready-made analysis without the details it needs. **How to fix it:** nothing to change. Your AI adds the details and retries. ### Step "…": give either event or page_contains. **What it means:** a Google Analytics funnel step was set up wrongly. **How to fix it:** describe each funnel step by an event name or a page address. ## Calendar ### To move an event, give both start and end. Also: **Nothing to change: pass a new time, title, description, location or add_guests.** **What it means:** your AI asked to change an event without the full details. **How to fix it:** tell your AI the new start and end time, or what to change. ### No event with id "…" in "…". Use an id from calendar_list_events. **What it means:** the event was deleted or moved, or the id is wrong. **How to fix it:** ask your AI to look the event up again. ### The event changed in iCloud meanwhile. Fetch it again, then retry. Also: **iCloud didn't accept the event (HTTP …). Try again in a minute.** **What it means:** the iCloud event changed while your AI was working on it, or iCloud refused the change. **How to fix it:** ask your AI to try again. ## Contacts and stores ### No contact with id "…". Use an id from contacts_search. **What it means:** the contact doesn't exist, or the id is wrong. **How to fix it:** ask your AI to search for the contact by name or email. ### No order "…". Use magento_list_orders to find it. Also: **The store couldn't find that.** **What it means:** the Magento order number doesn't exist in the store. **How to fix it:** check the order number, or ask your AI to list recent orders. ### Mailchimp couldn't find that. Check the id (list tools return valid ids). **What it means:** the audience, campaign or subscriber doesn't exist. **How to fix it:** ask your AI to list audiences or campaigns first. ### Mailchimp doesn't allow this key to read that. **What it means:** the Mailchimp API key doesn't have access to that data. **How to fix it:** create a new key with a Mailchimp account that has access, then reconnect Mailchimp. ### The integration isn't allowed to read this. In Magento admin, edit the integration's API resources to include …, save, then reauthorize it. **What it means:** the Magento integration can't read orders, products or customers. **How to fix it:** see [Errors while connecting an account](/troubleshooting/connection-errors) for the exact resources to tick. ## Related articles - [Troubleshooting overview](/troubleshooting) - [Reconnect needed](/troubleshooting/reconnect-needed) - [Your AI can't send or change anything](/troubleshooting/ai-cant-send-or-change) --- # Developer API URL: https://docs.plugsight.app/developers Use the same live data your AI sees in your own website, dashboard or system, over plain HTTPS and JSON. Pro and Agency plans. The developer API lets your own code use the accounts you've connected to Plugsight: Google Analytics, Google Ads, Search Console, Zendesk, your mailbox, your store, your calendar and the rest. You connect each account once in the app. You never build OAuth apps, store tokens or learn each provider's API. It runs the **same tools** your AI app uses, with the same rules. Your code sends an HTTPS request with a key, Plugsight reads the data live from the provider, and you get JSON back. > [!NOTE] > The developer API is on the **Pro** and **Agency** plans. On Free, every request is refused with `403 plan_required`. ## How it works 1. **Connect your accounts** under **Connections** in the app. 2. **Choose what the key can reach.** An MCP server is your API project: it groups the accounts one key may use. 3. **Create the API key** on the MCP server's page. 4. **Call a tool** by name, such as `get_marketing_data`, and get its data back. There's nothing to install and no SDK. Any language that can send an HTTPS request works. ## Words used in these articles | Word | What it means | | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Connection | An account you've linked, such as a Google Ads account or a Zendesk helpdesk. You add them under **Connections**. | | MCP server | A named group of connections with its own key. AI apps like Claude and ChatGPT use the same thing, which is why the app calls it an MCP server. For the API, think of it as a project. Make one per website or system, so each key reaches only what it needs. | | API key | The secret that identifies your MCP server. It starts with `mcpk_`. Each MCP server has at most one key. | | Tool | One thing the API can do, like "search Zendesk tickets" or "get Google Ads spend by campaign". Each has a name, arguments and an answer. | | Read and Change | Read tools only fetch data. Change tools do something, such as send an email or update a ticket, and need extra permission. | ## Quick start About five minutes. 1. Open **Connections** and connect an account, for example Google Analytics. 2. Open **MCP servers** and click **Create MCP server**. Name it after where you'll use it, for example "Company website". 3. Under **Account access**, choose **Selected accounts** and tick only the accounts this key should reach. 4. Untick **Allow changes** if the key only needs to read. 5. On the MCP server's page, find **API key** and click **Create API key**. 6. Copy the key straight away. It's shown only once. 7. Save it as an environment variable on your server: ```bash export PLUGSIGHT_API_KEY="mcpk_…" ``` 8. List the tools the key can use: ```bash curl https://app.plugsight.app/v1/tools \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" ``` 9. Find your account ids: ```bash curl -X POST https://app.plugsight.app/v1/tools/list_accounts \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" -d '{}' ``` 10. Get real data, for example the last 30 days of website sessions by day: ```bash curl -X POST https://app.plugsight.app/v1/tools/get_marketing_data \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"connector": "analytics", "fields": ["date", "sessions", "users"], "date_preset": "last_30d"}' ``` ## Same rules as your AI app The API uses the MCP server's tools exactly as an AI app does, so everything you've set in the app applies: - **Which accounts:** only the MCP server's accounts, minus any sites, properties or ad accounts you've hidden. - **Which tools:** the tools follow the connections. Add Zendesk to the MCP server and the Zendesk tools appear; remove it and they go. - **Your plan:** your plan's limits and features apply. Marketing and analytics data needs Pro or Agency. - **Changes:** change tools need `"confirm": true`, **Allow changes** on the MCP server, the account's switch on, nothing paused on **Permissions**, and the daily email limit not reached. The exception is `organize_emails` (archive, label, mark read), which needs only a Pro or Agency plan and nothing paused. - **Activity:** every call appears in **Activity** in the app, as "Developer API". ## Limits - Up to **120 requests a minute** per MCP server. Over that, you get `429 rate_limited`. Need more? Use a second MCP server, or cache results on your side. - Providers' own limits still apply (Google Ads, Zendesk and so on). When a provider says "slow down", the tool returns an error saying so. - Data is read live on every call. Plugsight keeps only short-lived lists, such as which accounts a login reaches (15 minutes) and contacts (5 minutes), so cache results yourself if you show them often. ## In this section - [Authentication](/developers/authentication): the API key, the header, and keeping it secret. - [Calling tools](/developers/calling-tools): listing tools, calling one, the answer format and making changes. - [Errors](/developers/errors): every status code and error body. - Tool reference: [Accounts](/developers/accounts-tools), [Email](/developers/email-tools), [Zendesk](/developers/zendesk-tools), [Marketing and analytics](/developers/marketing-tools), [Calendar](/developers/calendar-tools), [Contacts](/developers/contacts-tools), [WooCommerce](/developers/woocommerce-tools), [Magento](/developers/magento-tools), [Shopify](/developers/shopify-tools), [Mailchimp](/developers/mailchimp-tools), [Bing Webmaster Tools](/developers/bing-webmaster-tools), [Custom API](/developers/custom-api-tools), [Custom MCP server](/developers/custom-mcp-tools) and [PageSpeed](/developers/pagespeed-tools). - Tools for connectors still waiting for Google's approval: [Google Drive](/developers/drive-tools) (coming soon), [Google Tag Manager](/developers/tag-manager-tools), [YouTube](/developers/youtube-tools), [Google Merchant Center](/developers/merchant-center-tools), [Google Sheets](/developers/sheets-tools), [Google Docs](/developers/docs-tools), [Google Forms](/developers/forms-tools), [Google Meet](/developers/meet-tools). --- # Authentication URL: https://docs.plugsight.app/developers/authentication Create an API key for an MCP server, send it in the Authorization header, and keep it secret, regenerate it or revoke it. Every request to the developer API carries an **API key**. The key belongs to one MCP server, and it reaches exactly the accounts that MCP server reaches, with the same permissions. ## Create a key 1. Open **MCP servers** and click the MCP server the key is for. 2. Find the **API key** section. 3. Click **Create API key**. 4. Copy the key from the **API key created** message. It's shown once and never again. The key starts with `mcpk_`. Each MCP server has at most one key at a time. > [!TIP] > Make one MCP server per website or system, and tick only the accounts it needs under **Selected accounts**. Then each key reaches the least it can. ## Send the key Put the key in the `Authorization` header of every request, after the word `Bearer`: ```http Authorization: Bearer mcpk_… ``` For example: ```bash curl https://app.plugsight.app/v1/tools \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" ``` A request with no key, a key in the wrong format, or a key that's been replaced or revoked gets `401 unauthorized`. See [Errors](/developers/errors). ## Keep it secret Anyone with the key can read what its MCP server reaches, and, if changes are allowed, send or change things too. - **Keep it on your server.** Store it in an environment variable or your platform's secret settings. - **Never put it in web page code, a mobile app or a public repository.** The API sends no CORS headers, so browsers can't call it directly anyway. - **To show data on your website**, have your web page ask your own server, and your server ask Plugsight. Send the page only the numbers it needs. - **If you only need to read**, untick **Allow changes** on the MCP server. Then the key can't send or change anything, even with `"confirm": true`. ## Replace a key 1. Open the MCP server's page. 2. In **API key**, click **Regenerate key**. 3. Click **Replace key** to confirm. 4. Copy the new key and update it wherever you use it. The old key stops working at once. Anything still using it is refused until you paste in the new one. ## Turn a key off 1. Open the MCP server's page. 2. In **API key**, click **Revoke key**. 3. Click **Revoke key** to confirm. The key stops working at once, and the MCP server has no key until you create a new one. > [!NOTE] > Regenerating or revoking the key doesn't affect Claude, ChatGPT or other AI apps that signed in through the browser. They don't use the key. ## Plans The developer API is on the **Pro** and **Agency** plans. With a valid key on the Free plan, every request gets `403 plan_required`. Upgrade under **Billing** in the app. ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Developer API overview](/developers) --- # Calling tools URL: https://docs.plugsight.app/developers/calling-tools List the tools an API key can use, call one with JSON arguments, read the answer, pick an account and make changes with confirm. The developer API has two endpoints. Both need your key in the `Authorization` header (see [Authentication](/developers/authentication)). | Endpoint | What it does | | ----------------------- | ------------------------------------------------------- | | `GET /v1/tools` | Lists the tools this key can use, with their arguments. | | `POST /v1/tools/{name}` | Runs one tool. The JSON body is its arguments. | ## Basics | | | | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Base URL | `https://app.plugsight.app/v1` (HTTPS only) | | Headers | `Authorization: Bearer ` and, for `POST`, `Content-Type: application/json` | | Success | Status `200` with `{ "data": … }` | | Failure | Status `4xx` or `5xx` with `{ "error", "message", "docs" }`. See [Errors](/developers/errors). | | Dates | `YYYY-MM-DD`. Date-times in ISO 8601 with an offset, such as `2026-11-20T15:00:00+00:00`. | | Paging | Tools with many results take `limit` and `page`, `offset` or `page_token`. Each tool's arguments say which. | | Freshness | Live: each call reads from the provider at that moment. Plugsight stores none of it; only short lists, such as which accounts a login reaches, are kept for a few minutes. | ## List the tools ```bash curl https://app.plugsight.app/v1/tools \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" ``` The answer lists each tool with: | Field | What it is | | -------------- | ------------------------------------------------------------------------- | | `name` | The name to call it by. | | `title` | A short human name. | | `description` | What it does. | | `read_only` | `true` for tools that only read; `false` for tools that change something. | | `input_schema` | A JSON Schema of its arguments. | ```json { "tools": [ { "name": "list_accounts", "title": "List connected accounts", "description": "Lists the accounts this MCP can use…", "read_only": true, "input_schema": { "type": "object", "properties": {} } } ] } ``` The list depends on the MCP server's connections. Add Zendesk to it and the Zendesk tools appear; remove Zendesk and they go. `list_accounts` and `pagespeed_check` are always there. The tool reference lists every tool by group, starting with [Accounts](/developers/accounts-tools). ## Call a tool Send a `POST` to `/v1/tools/` followed by the tool's name. The body is a JSON object of its arguments. Send `{}` when it takes none. ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_ticket_stats \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"from": "2026-11-01", "to": "2026-11-15"}' ``` A successful answer is status `200` with the tool's result under `data`. What's inside `data` depends on the tool: usually an object or a list. For example, `get_marketing_data`: ```json { "data": { "connector": "Google Analytics 4", "date_range": { "from": "2026-10-17", "to": "2026-11-15" }, "accounts": ["acme.com (properties/123456789)"], "columns": ["date", "sessions", "users"], "rows": [ ["2026-10-17", 412, 388], ["2026-10-18", 455, 419] ], "row_count": 30, "totals": { "sessions": 13240, "users": 11872 } } } ``` Most tools answer with JSON. If a tool's answer isn't JSON, `data` is a string of text. If the tool can't run (a wrong argument, a change that isn't allowed, or the provider said no), you get `400 tool_error` and a `message` saying what to fix. See [Errors](/developers/errors). ## Choose an account Many tools take an `account` argument. 1. Call `list_accounts` to get each account's `id`. 2. Pass that `id` as `account`. If the MCP server has only one account of that kind, you can leave `account` out. With more than one, the tool returns an error listing the ids to choose from. Marketing tools work differently: call `list_marketing_accounts` for the sites, properties and ad accounts the key reaches, and pass their ids as `accounts`. Leave `accounts` out to use all of them. ## Making changes Change tools, such as `send_email`, `zendesk_add_comment` or `calendar_create_event`, only run when all of these are true: - **The request includes `"confirm": true`.** This stops a change happening by accident. Set it only once your own code or your user has decided to go ahead. - **The MCP server allows changes:** **Allow changes** is ticked on its page. - **The account allows changes:** its switch under **Write access** on **Connections** is on. - **Nothing is paused** on the **Permissions** page. - **The daily email limit isn't reached** (for sending email). It's 20 emails per account in a rolling 24 hours unless you've changed it on **Permissions**. ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_add_comment \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"ticket_id": 1042, "body": "Thanks, your refund is on its way.", "public": true, "confirm": true}' ``` If one condition isn't met, you get `400 tool_error` with a message naming it. Every change, and every blocked attempt, appears in **Activity** in the app. A few change tools work differently: - `create_draft` saves a draft and never sends. It needs no `confirm`. - `organize_emails` marks, labels or moves emails. It needs no `confirm`, and stops only while email changes are paused. - `zendesk_apply_macro` previews first. Call it with `preview` left at `true`, then again with `"preview": false` and `"confirm": true` to apply it. ## Code examples ### Node.js ```js async function plugsight(tool, args = {}) { const res = await fetch(`https://app.plugsight.app/v1/tools/${tool}`, { method: "POST", headers: { Authorization: `Bearer ${process.env.PLUGSIGHT_API_KEY}`, "Content-Type": "application/json" }, body: JSON.stringify(args), }); const body = await res.json(); if (!res.ok) throw new Error(`${body.error}: ${body.message}`); return body.data; } const stats = await plugsight("zendesk_ticket_stats", { from: "2026-11-01", to: "2026-11-30" }); ``` ### Python ```python import os, requests def plugsight(tool, **args): r = requests.post(f"https://app.plugsight.app/v1/tools/{tool}", headers={"Authorization": f"Bearer {os.environ['PLUGSIGHT_API_KEY']}"}, json=args, timeout=60) body = r.json() if not r.ok: raise RuntimeError(f"{body['error']}: {body['message']}") return body["data"] print(plugsight("woocommerce_sales_report", **{"from": "2026-11-08", "to": "2026-11-15"})) ``` ### Show data on your website The key must stay secret, so don't call the API from a web page. Instead: 1. Your web page calls a route on your own server, such as `/api/stats`. 2. Your server adds the key, calls Plugsight, and keeps only the numbers the page needs. 3. Cache the result for a few minutes, so you stay well under 120 requests a minute. Serverless platforms work the same way: keep the key in the platform's environment variables. ## Related articles - [Authentication](/developers/authentication) - [Errors](/developers/errors) - [Accounts tools](/developers/accounts-tools) --- # Errors URL: https://docs.plugsight.app/developers/errors Every status code and error body the developer API returns, with the exact messages, what each means and how to fix it. When a request fails, the API answers with a `4xx` or `5xx` status and a JSON body with three fields: ```json { "error": "tool_error", "message": "Unknown Zendesk account \"desk-2\". Call list_accounts to see valid ids.", "docs": "https://plugsight.app/developers" } ``` | Field | What it is | | --------- | -------------------------------------------------------- | | `error` | A short code you can check in your code. | | `message` | What went wrong, in plain words, and usually what to do. | | `docs` | A link to the developer documentation. | ## All errors at a glance | Status | `error` | What happened | What to do | | ------ | --------------- | --------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | | 400 | `tool_error` | The tool couldn't run: a wrong or missing argument, a change that isn't allowed, or the provider said no. | Read `message`: it says what to fix. | | 400 | `bad_json` | The request body isn't valid JSON, so nothing ran. | Send a JSON object as the body (`{}` for no arguments). | | 401 | `unauthorized` | The key is missing, mistyped, replaced or revoked, or the person who made it has left the team or is now a Member. | Check the header, or create a new key. | | 403 | `plan_required` | The account isn't on Pro or Agency. | Upgrade under **Billing** in the app. | | 404 | `unknown_tool` | The MCP server has no tool by that name, often because the connection it needs isn't in the MCP server. | `GET /v1/tools` lists what it has. | | 404 | `not_found` | The address isn't an API endpoint. | Use `GET /v1/tools` or `POST /v1/tools/`. | | 429 | `rate_limited` | Over 120 requests in a minute for this MCP server. | Wait the `Retry-After` seconds, then retry. | | 500 | `server_error` | Something broke on Plugsight's side. | Retry. If it keeps happening, contact support. | ## 400 tool_error **What it means:** the request reached the tool, but the tool couldn't do what you asked. The `message` is the tool's own explanation. The most common ones: | Message starts with | What to do | | ----------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | | `Unknown account "…"` or `Unknown Zendesk account "…"` | Use an `id` from `list_accounts`. | | `This MCP has 2 … connections; pass account (one of: …)` | Add the `account` argument with one of the ids listed. | | `Not sent:`, `Not posted:`, `Not updated:`, `Not applied:`, `Not created:`, `Not booked:`, `Not changed:` or `Not cancelled:` | Add `"confirm": true` to the arguments, once you've decided to go ahead. | | `The "…" MCP is set to drafts only` or `The "…" MCP is read-only` | Tick **Allow changes** on the MCP server's page. | | `Sending is off for "…"` or `Changes are off for "…"` | Turn on the account's switch under **Write access** on **Connections**. | | `All write actions are paused` or `… are paused (Permissions page)` | Click **Resume** on the **Permissions** page. | | `Daily limit reached` | Wait for the 24-hour window to free up, or raise the limit under **Daily email limit** on **Permissions**. | | `… no longer accepts this connection's sign-in` or `… rejected …` | Reconnect the account on **Connections**. | | `… is limiting requests right now` | The provider asked to slow down. Wait a minute, then try again. | The [Troubleshooting](/troubleshooting) section explains each of these messages in full, including [why changes are refused](/troubleshooting/ai-cant-send-or-change) and [reconnecting accounts](/troubleshooting/reconnect-needed). Arguments that don't match the tool's `input_schema` (a missing required argument, or the wrong type) also return `400 tool_error`, with a message naming the argument. ## 401 unauthorized ### Send your MCP server's API key as: Authorization: Bearer \. **What it means:** the request had no `Authorization` header, or it didn't start with `Bearer` followed by a key. **How to fix it:** send the header exactly as `Authorization: Bearer mcpk_…`, with one space after `Bearer`. ### That API key isn't valid. Create a new one on the MCP server's page in Plugsight. **What it means:** the key is mistyped, was replaced with **Regenerate key**, was turned off with **Revoke key**, its MCP server was deleted, or the person who made it has left the team, been removed, had their account deleted, or become a Member (only Owners and Admins can have working keys). **How to fix it:** check you copied the whole key. If it's been replaced or revoked, open the MCP server's page and click **Create API key** (or **Regenerate key**), then update the key wherever you use it. See [Authentication](/developers/authentication). ## 403 plan_required ### The developer API is on the Pro and Agency plans. Upgrade at https://app.plugsight.app/app/billing. **What it means:** the key is valid, but the Plugsight account it belongs to is on the Free plan. **How to fix it:** upgrade to Pro or Agency under **Billing**. If your paid plan ended or a payment failed and the account moved to Free, the API stops working until you upgrade again. ## 404 unknown_tool ### This MCP server has no tool "…". GET /v1/tools lists the ones it has. **What it means:** the name is mistyped, or the tool belongs to a kind of connection the MCP server doesn't include. For example, `zendesk_search_tickets` only exists when the MCP server has a Zendesk connection, and marketing tools only exist on Pro and Agency. **How to fix it:** 1. Call `GET /v1/tools` and check the exact name. 2. If the tool is missing, open the MCP server's page in the app, click **Edit configuration**, and add the account it needs (or choose **All accounts**). ## 404 not_found ### Unknown endpoint. Use GET /v1/tools or POST /v1/tools/\. **What it means:** the path isn't one of the API's two endpoints, or it used the wrong method (for example `GET` to run a tool). **How to fix it:** list tools with `GET /v1/tools`, and run one with `POST /v1/tools/`. ## 429 rate_limited ### Too many requests: up to 120 a minute per MCP server. Try again shortly. **What it means:** this MCP server's key made more than 120 requests in a minute. The answer has a `Retry-After: 60` header. **How to fix it:** 1. Wait the number of seconds in `Retry-After`, then retry. 2. Cache results on your side, especially data you show on a website. 3. If you need more, split the work across a second MCP server with its own key. ## 500 server_error ### Something went wrong on our side. Try again; if it keeps happening, contact support. **What it means:** an unexpected failure inside Plugsight. **How to fix it:** retry the request. If it keeps happening, email info@plugsight.app with the tool name, the `error` and `message` you got, and the time of the request. ## Related articles - [Calling tools](/developers/calling-tools) - [Authentication](/developers/authentication) - [Troubleshooting](/troubleshooting) --- # Accounts tools URL: https://docs.plugsight.app/developers/accounts-tools The list_accounts tool: every account an API key can reach, its type and whether it may make changes. **Needs:** Always available. 1 tool. Every MCP server has this tool, whatever it is connected to, so every API key can call it. Send its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. Call it first: the `id` of each account is what other tools take as their `account` argument. If the MCP server has only one account of a kind, you can leave `account` out of those tools. An example answer (shortened): ```json { "data": [ { "id": "google-analytics", "label": "Acme Ltd", "type": "marketing", "provider": "google_analytics", "changes": "read-only" }, { "id": "zendesk", "label": "Acme Support", "type": "helpdesk", "provider": "zendesk", "site": "acme.zendesk.com", "changes": "off (read-only)" } ] } ``` Each account says whether it may make changes. Mailboxes have `sending` (`on`, `paused` or `off (drafts only)`). Zendesk and calendars have `changes` (`on`, `paused` or `off (read-only)`), Custom APIs have `changes` (`on`, `paused` or `off (read-only: GET and HEAD only)`) with their `base_url` and imported `operations`, and custom MCP servers have `changes` (`on`, `paused` or `off (read-only: only tools the server marks read-only)`) with their `server` host, tool counts and how long ago their tools were listed. Marketing, files (Drive, Sheets, Docs, Forms, Meet), contacts, stores and Mailchimp always say `read-only`. | Tool | What it does | Kind | | --- | --- | --- | | [`list_accounts`](#list_accounts) | List connected accounts | Read | ## list_accounts **List connected accounts** · Read Lists the accounts this MCP can use (mailboxes such as Gmail, Outlook, iCloud; helpdesks such as Zendesk; marketing logins for Google Search Console/Analytics/Ads, Microsoft Advertising, Meta Ads, LinkedIn Ads, TikTok Ads, Tag Manager, YouTube and Merchant Center; Google Drive and Sheets; Google, iCloud or Outlook Calendar and Contacts; WooCommerce, Magento and Shopify stores; Mailchimp; Bing Webmaster Tools; Custom APIs; custom MCP servers), their type, and whether each may send or make changes. Use the returned id in other tools. No arguments: send `{}`. Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/list_accounts \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # Email tools URL: https://docs.plugsight.app/developers/email-tools Every email tool in the developer API, with arguments and examples: search, read, draft, send and organise email. **Needs:** Gmail, Outlook, iCloud Mail, Yahoo or any IMAP mailbox. 9 tools. These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. | Tool | What it does | Kind | | ------------------------------------- | ----------------------------- | ------ | | [`list_folders`](#list_folders) | List folders | Read | | [`search_emails`](#search_emails) | Search / list emails | Read | | [`get_email`](#get_email) | Read an email | Read | | [`get_thread`](#get_thread) | Read a conversation | Read | | [`get_attachment`](#get_attachment) | Read an attachment | Read | | [`create_draft`](#create_draft) | Create a draft | Change | | [`send_email`](#send_email) | Send an email | Change | | [`organize_emails`](#organize_emails) | Archive, label or mark emails | Change | | [`send_draft`](#send_draft) | Send a draft | Change | Change tools in this group: `create_draft`, `send_email`, `organize_emails`, `send_draft`. Check each tool's notes below for what it needs before it runs. The example requests fill in only the required arguments, with placeholder values. Replace `ACCOUNT_ID` with an `id` from [`list_accounts`](/developers/accounts-tools). ## list_folders **List folders** · Read Lists folders/labels of one account with message and unread counts. | Argument | Type | Required | What it is | | --------- | ------ | -------- | ----------------------------- | | `account` | string | Yes | Account id from list_accounts | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/list_folders \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account": "ACCOUNT_ID"}' ``` ## search_emails **Search / list emails** · Read Lists or searches emails across one or all accounts. All filters combine with AND; a list (e.g. from: ["a@x.com", "b@y.com"]) matches any entry. With no filters it lists the latest inbox emails. Results include a short preview and the attachment list. `query` is a text match; on Gmail accounts it also accepts Gmail search syntax (e.g. "from:amazon newer_than:7d"), on Outlook accounts Outlook search syntax (e.g. "from:amazon AND received>=2026-01-01"). Searches run live against each mail server and cover the whole mailbox history. For "find all" questions, keep paging with offset until no more results come back. When more_per_account lists an account, its results are incomplete or can continue: follow its note, e.g. call again for that account with cursor: next_cursor. | Argument | Type | Required | What it is | | ----------------- | ------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | `account` | string | No | Account id, or "all" (default) | | `folder` | string | No | Folder path from list_folders, or: inbox (default), sent, drafts, trash, junk, archive, all (every folder except trash/junk) | | `query` | string | No | Free text anywhere in the email | | `from` | string or array of string | No | Sender name/address contains (string or list, any match) | | `to` | string or array of string | No | Recipient (To) contains | | `cc` | string or array of string | No | Cc contains | | `bcc` | string or array of string | No | Bcc contains (only visible on emails you sent) | | `subject` | string | No | Subject contains | | `body` | string | No | Body contains | | `exclude_from` | string or array of string | No | Leave out emails from these senders | | `exclude_subject` | string | No | Leave out emails whose subject contains this | | `exclude_text` | string | No | Leave out emails containing this text | | `since` | string | No | On or after this date, YYYY-MM-DD | | `before` | string | No | Before this date, YYYY-MM-DD | | `unread` | boolean | No | true = only unread, false = only read | | `flagged` | boolean | No | true = only flagged/starred, false = only unflagged | | `answered` | boolean | No | true = only emails you replied to, false = not replied | | `has_attachment` | boolean | No | true = has real attachments (images embedded in the body don't count), false = none | | `attachment_name` | string | No | An attachment's filename contains this | | `attachment_type` | string | No | Has an attachment of this type: pdf, image, document, spreadsheet, presentation, calendar, archive, email, audio, video, or a file extension | | `larger_than_kb` | number | No | Email size above this many KB | | `smaller_than_kb` | number | No | Email size below this many KB | | `sort` | string | No | Sort order. One of: `newest`, `oldest`. Default `"newest"`. | | `include_preview` | boolean | No | Include a ~200 character body preview. Default `true`. | | `limit` | integer | No | Most results to return. Default `20`. | | `offset` | integer | No | Skip this many results (pagination) Default `0`. | | `cursor` | string | No | next_cursor from an earlier result (Outlook): continues that search where it stopped. Needs the same account and filters; offset must be 0 | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/search_emails \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## get_email **Read an email** · Read Returns the full email: headers, body text and the attachment list. Images embedded in the body are listed with inline: true and marked in the text as [inline image #N]; read them with get_attachment. Links in HTML emails are kept as "text (url)". Does not mark the email as read. | Argument | Type | Required | What it is | | ----------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------ | | `account` | string | Yes | Account id from list_accounts | | `email_id` | string | Yes | Email id from search_emails | | `include_html` | boolean | No | Also return the raw HTML body. Default `false`. | | `include_headers` | boolean | No | Also return all raw headers (e.g. List-Unsubscribe, Received, authentication results) Default `false`. | | `max_chars` | integer | No | Truncate body to this many characters. Default `20000`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/get_email \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account": "ACCOUNT_ID", "email_id": "…"}' ``` ## get_thread **Read a conversation** · Read Returns every email in the same conversation as the given email, oldest first. | Argument | Type | Required | What it is | | --------------------- | ------- | -------- | ----------------------------------------------------------------- | | `account` | string | Yes | Account id from list_accounts | | `email_id` | string | Yes | Email id from search_emails | | `max_chars_per_email` | integer | No | Longest email text returned; longer ones are cut. Default `5000`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/get_thread \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account": "ACCOUNT_ID", "email_id": "…"}' ``` ## get_attachment **Read an attachment** · Read Reads one attachment, including images embedded in the body. `attachment` is the index from get_email; for files inside a forwarded email (.eml) or Outlook winmail.dat use a path like "2.0". Returned as text for PDF, Word (.docx), Excel (.xlsx), PowerPoint (.pptx), HTML, CSV and other text files; as an image for images. Use mode "base64" to get the raw file instead. | Argument | Type | Required | What it is | | ------------ | ----------------- | -------- | --------------------------------------------------------------------------------------------------------------- | | `account` | string | Yes | Account id from list_accounts | | `email_id` | string | Yes | Email id from search_emails | | `attachment` | integer or string | Yes | Index from get_email (e.g. 0), or a nested path (e.g. "2.0") | | `mode` | string | No | auto: text when the file can be read as text; base64: the raw file. One of: `auto`, `base64`. Default `"auto"`. | | `max_chars` | integer | No | Truncate extracted text. Default `50000`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/get_attachment \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account": "ACCOUNT_ID", "email_id": "…", "attachment": 1}' ``` ## create_draft **Create a draft** · Change Saves an email as a draft in the account's Drafts folder; nothing is sent. Supports new emails, replies (reply_to_email_id, reply_all) and forwards (forward_email_id), with attachments uploaded as base64 or copied from another email. > [!NOTE] > This saves a draft in the mailbox and never sends anything. It needs no `confirm`, and it works even when sending is off for the account or the MCP server. | Argument | Type | Required | What it is | | ------------------- | ------------------------- | -------- | ------------------------------------------------------------------------------------ | | `account` | string | Yes | Account id to send from (list_accounts) | | `to` | string or array of string | No | Recipients: address or "Name \
" (string or list) | | `cc` | string or array of string | No | Cc recipients: address or list | | `bcc` | string or array of string | No | Bcc recipients: address or list | | `subject` | string | No | Subject. Defaults to "Re: …" / "Fwd: …" for replies and forwards | | `body` | string | Yes | Plain-text body. For replies/forwards the original is quoted below it automatically | | `reply_to_email_id` | string | No | Reply to this email (sender is added as recipient, threading kept) | | `reply_all` | boolean | No | With reply_to_email_id: also include the original To and Cc. Default `false`. | | `forward_email_id` | string | No | Forward this email, including its attachments | | `attachments` | array of object | No | Files to attach: email_id + attachment index from an email, or name + base64 content | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/create_draft \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account": "ACCOUNT_ID", "body": "…"}' ``` ## send_email **Send an email** · Change Sends an email immediately (new, reply or forward). Sending must be allowed for the account and this MCP in the app, and is limited per day; if blocked, offer create_draft instead. > [!IMPORTANT] > This tool makes a change, so the request must include `"confirm": true`, and changes must be allowed. See [Making changes](/developers/calling-tools#making-changes). | Argument | Type | Required | What it is | | ------------------- | ------------------------- | -------- | ------------------------------------------------------------------------------------ | | `account` | string | Yes | Account id to send from (list_accounts) | | `to` | string or array of string | No | Recipients: address or "Name \
" (string or list) | | `cc` | string or array of string | No | Cc recipients: address or list | | `bcc` | string or array of string | No | Bcc recipients: address or list | | `subject` | string | No | Subject. Defaults to "Re: …" / "Fwd: …" for replies and forwards | | `body` | string | Yes | Plain-text body. For replies/forwards the original is quoted below it automatically | | `reply_to_email_id` | string | No | Reply to this email (sender is added as recipient, threading kept) | | `reply_all` | boolean | No | With reply_to_email_id: also include the original To and Cc. Default `false`. | | `forward_email_id` | string | No | Forward this email, including its attachments | | `attachments` | array of object | No | Files to attach: email_id + attachment index from an email, or name + base64 content | | `confirm` | boolean | Yes | Must be true: the user has seen this exact email and explicitly approved sending it | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/send_email \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account": "ACCOUNT_ID", "body": "…", "confirm": true}' ``` ## organize_emails **Archive, label or mark emails** · Change Changes up to 100 emails at once: mark read or unread, flag or unflag, add or remove labels (Gmail labels, Outlook categories), and move them (move_to: "archive", "trash", "inbox", "junk" or a folder from list_folders). Use ids from search_emails. Before moving to trash, or changing more than 10 emails, say what will happen and get a yes first. > [!NOTE] > This changes the emails (marks, labels, moves) but sends nothing. It needs no `confirm`. It stops only while email changes, or all changes, are paused on the **Permissions** page. | Argument | Type | Required | What it is | | --------------- | --------------- | -------- | ----------------------------------------------------------------------- | | `account` | string | Yes | Account id from list_accounts | | `email_ids` | array of string | Yes | Email ids from search_emails or get_thread | | `read` | boolean | No | true = mark read, false = mark unread | | `flagged` | boolean | No | true = flag/star, false = remove the flag | | `add_labels` | array of string | No | Gmail labels or Outlook categories to add (created if new) | | `remove_labels` | array of string | No | Labels or folders to remove | | `move_to` | string | No | "archive", "trash", "inbox", "junk", or a folder path from list_folders | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/organize_emails \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account": "ACCOUNT_ID", "email_ids": []}' ``` ## send_draft **Send a draft** · Change Sends an existing draft (from create_draft, or found in the drafts folder) and removes it from Drafts. Read it with get_email first. > [!IMPORTANT] > This tool makes a change, so the request must include `"confirm": true`, and changes must be allowed. See [Making changes](/developers/calling-tools#making-changes). | Argument | Type | Required | What it is | | ---------- | ------- | -------- | ----------------------------------------------------------------------------------- | | `account` | string | Yes | Account id from list_accounts | | `draft_id` | string | Yes | Email id of the draft | | `confirm` | boolean | Yes | Must be true: the user has seen this exact draft and explicitly approved sending it | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/send_draft \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account": "ACCOUNT_ID", "draft_id": "…", "confirm": true}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # Zendesk tools URL: https://docs.plugsight.app/developers/zendesk-tools Every Zendesk tool in the developer API, with arguments and examples: search, read, reply to, update and create tickets. **Needs:** A Zendesk connection. 13 tools. These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. | Tool | What it does | Kind | | ------------------------------------------------------------------- | ---------------------------------- | ------ | | [`zendesk_search_tickets`](#zendesk_search_tickets) | Search Zendesk tickets | Read | | [`zendesk_get_ticket`](#zendesk_get_ticket) | Read a Zendesk ticket | Read | | [`zendesk_get_attachment`](#zendesk_get_attachment) | Read a Zendesk attachment | Read | | [`zendesk_find_users`](#zendesk_find_users) | Find Zendesk users | Read | | [`zendesk_list_support_addresses`](#zendesk_list_support_addresses) | List Zendesk support addresses | Read | | [`zendesk_list_ticket_statuses`](#zendesk_list_ticket_statuses) | List Zendesk ticket statuses | Read | | [`zendesk_get_side_conversations`](#zendesk_get_side_conversations) | Read a ticket's side conversations | Read | | [`zendesk_add_comment`](#zendesk_add_comment) | Reply or add a note | Change | | [`zendesk_update_ticket`](#zendesk_update_ticket) | Update a Zendesk ticket | Change | | [`zendesk_ticket_stats`](#zendesk_ticket_stats) | Zendesk ticket counts | Read | | [`zendesk_list_macros`](#zendesk_list_macros) | List Zendesk macros | Read | | [`zendesk_apply_macro`](#zendesk_apply_macro) | Apply a Zendesk macro | Change | | [`zendesk_create_ticket`](#zendesk_create_ticket) | Create a Zendesk ticket | Change | Change tools in this group: `zendesk_add_comment`, `zendesk_update_ticket`, `zendesk_apply_macro`, `zendesk_create_ticket`. Check each tool's notes below for what it needs before it runs. The example requests fill in only the required arguments, with placeholder values. ## zendesk_search_tickets **Search Zendesk tickets** · Read Searches tickets with Zendesk search syntax, e.g. "status:open", "requester:jane@acme.com", "assignee:me status\2026-01-01", "updated>24hours", or plain words. Newest updated first. status takes new, open, pending, hold, solved or closed; a custom status (e.g. "Waiting on customer") is custom_status_id:\ from zendesk_list_ticket_statuses (a custom status name after status: is translated for you). Dates are yyyy-mm-dd, an ISO time with offset, or relative such as updated>24hours (7d, today and yesterday are translated). Zendesk search returns at most the first 1,000 matches (pages past that fail); for larger sets narrow the query, e.g. by created or updated date, and use zendesk_ticket_stats for counts. | Argument | Type | Required | What it is | | ------------ | ------- | -------- | --------------------------------------------------------------------------------------------------- | | `account` | string | No | Zendesk account id from list_accounts (optional when there's only one) | | `query` | string | No | Zendesk search query (type:ticket is added automatically) | | `sort_by` | string | No | Field to sort by. One of: `updated_at`, `created_at`, `priority`, `status`. Default `"updated_at"`. | | `sort_order` | string | No | asc or desc. One of: `desc`, `asc`. Default `"desc"`. | | `limit` | integer | No | Most results to return. Default `25`. | | `page` | integer | No | Page of results, from 1. Default `1`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_search_tickets \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## zendesk_get_ticket **Read a Zendesk ticket** · Read Returns a ticket with requester, assignee, CCs and followers, organisation, group, brand, form, satisfaction rating, custom fields (by name, with drop-down option names), its custom status when the account has them (custom_status, e.g. "Waiting on customer"; status is its category) and the full conversation (public replies and internal notes, oldest first). For email, `source` shows which address wrote and which support address received it; `replies_from` is the support address public replies go out from. Side conversations (separate email/Slack threads started from the ticket) aren't included; read them with zendesk_get_side_conversations. Each comment lists its files, numbered from 0, including images pasted into the reply (inline: true, marked in the text as [inline image #N]). Open any of them, e.g. a customer's screenshot or a PDF, with zendesk_get_attachment. | Argument | Type | Required | What it is | | ----------------------- | ------- | -------- | ---------------------------------------------------------------------- | | `account` | string | No | Zendesk account id from list_accounts (optional when there's only one) | | `ticket_id` | integer | Yes | Ticket number | | `include_comments` | boolean | No | Include the ticket's comments. Default `true`. | | `max_chars_per_comment` | integer | No | Longest comment text returned; longer ones are cut. Default `4000`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_get_ticket \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"ticket_id": 1}' ``` ## zendesk_get_attachment **Read a Zendesk attachment** · Read Opens a file from a ticket comment, including images pasted into the reply (screenshots). `comment_id` and `attachment` (the file's index) come from zendesk_get_ticket. Images are returned as images, so you can look at them; PDF, Word (.docx), Excel (.xlsx), PowerPoint (.pptx), HTML, CSV and other text files as text. For a file inside an attached email (.eml) use a path like "1.0". Use mode "base64" for the raw file. | Argument | Type | Required | What it is | | ------------ | ----------------- | -------- | --------------------------------------------------------------------------------------------------------------- | | `account` | string | No | Zendesk account id from list_accounts (optional when there's only one) | | `ticket_id` | integer | Yes | Ticket number | | `comment_id` | integer | Yes | Comment id from zendesk_get_ticket | | `attachment` | integer or string | Yes | File index from zendesk_get_ticket (e.g. 0), or a path inside an attached email (e.g. "1.0") | | `mode` | string | No | auto: text when the file can be read as text; base64: the raw file. One of: `auto`, `base64`. Default `"auto"`. | | `max_chars` | integer | No | Truncate extracted text. Default `50000`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_get_attachment \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"ticket_id": 1, "comment_id": 1, "attachment": 1}' ``` ## zendesk_find_users **Find Zendesk users** · Read Finds people (customers or agents) by name, email or phone, with their phone and organisation. Shows up to 50; has_more says when more match, so narrow the search. Use the id for assignee changes. | Argument | Type | Required | What it is | | --------- | ------ | -------- | ---------------------------------------------------------------------- | | `account` | string | No | Zendesk account id from list_accounts (optional when there's only one) | | `query` | string | Yes | Search text | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_find_users \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "…"}' ``` ## zendesk_list_support_addresses **List Zendesk support addresses** · Read The email addresses customers write to in this Zendesk account, each with its brand and whether it's the default. A ticket's replies go out from one of these; choose a different one with from_address on zendesk_create_ticket or zendesk_update_ticket. | Argument | Type | Required | What it is | | --------- | ------ | -------- | ---------------------------------------------------------------------- | | `account` | string | No | Zendesk account id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_list_support_addresses \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## zendesk_list_ticket_statuses **List Zendesk ticket statuses** · Read The ticket statuses agents can choose in this Zendesk account, including custom ones such as "Waiting on customer" or "In progress", each with its id, its category (new, open, pending, hold or solved) and whether it's that category's default. Set one with custom_status on zendesk_update_ticket or zendesk_add_comment. Accounts without custom ticket statuses only have the built-in statuses (available: false); use status for those. | Argument | Type | Required | What it is | | --------- | ------ | -------- | ---------------------------------------------------------------------- | | `account` | string | No | Zendesk account id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_list_ticket_statuses \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## zendesk_get_side_conversations **Read a ticket's side conversations** · Read Side conversations on a ticket: separate email, Slack or child-ticket threads an agent started (e.g. asking a supplier or another team), with every message in each, oldest first. They aren't part of zendesk_get_ticket. Needs Zendesk's Collaboration add-on or Suite Professional or above. | Argument | Type | Required | What it is | | ----------------------- | ------- | -------- | ---------------------------------------------------------------------- | | `account` | string | No | Zendesk account id from list_accounts (optional when there's only one) | | `ticket_id` | integer | Yes | Ticket number | | `max_chars_per_message` | integer | No | Longest message text returned; longer ones are cut. Default `4000`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_get_side_conversations \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"ticket_id": 1}' ``` ## zendesk_add_comment **Reply or add a note** · Change Adds a public reply (emailed to the requester) or an internal note to a ticket, optionally changing its status (status, or custom_status for one of the account's own statuses such as "Waiting on customer"). Internal notes are only seen by agents. Needs changes allowed for this Zendesk account and MCP server. > [!IMPORTANT] > This tool makes a change, so the request must include `"confirm": true`, and changes must be allowed. See [Making changes](/developers/calling-tools#making-changes). | Argument | Type | Required | What it is | | --------------- | ----------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `account` | string | No | Zendesk account id from list_accounts (optional when there's only one) | | `ticket_id` | integer | Yes | Ticket number | | `body` | string | Yes | Text of the reply or note | | `public` | boolean | Yes | true = public reply to the customer, false = internal note | | `status` | string | No | Also set the ticket status. One of: `open`, `pending`, `hold`, `solved`. | | `custom_status` | string or integer | No | One of the account's ticket statuses (zendesk_list_ticket_statuses), by its name (any case, e.g. "Waiting on customer") or id. It also sets the ticket's status to that status's category, so don't pass status as well. | | `confirm` | boolean | Yes | Must be true: the user approved this exact text | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_add_comment \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"ticket_id": 1, "body": "…", "public": true, "confirm": true}' ``` ## zendesk_update_ticket **Update a Zendesk ticket** · Change Changes a ticket's status, priority, type, assignee, tags or the support address its replies go out from (from_address, which also moves it to that address's brand). For one of the account's own statuses, such as "Waiting on customer", use custom_status instead of status (zendesk_list_ticket_statuses). Needs changes allowed for this Zendesk account and MCP server. > [!IMPORTANT] > This tool makes a change, so the request must include `"confirm": true`, and changes must be allowed. See [Making changes](/developers/calling-tools#making-changes). | Argument | Type | Required | What it is | | --------------- | ----------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `account` | string | No | Zendesk account id from list_accounts (optional when there's only one) | | `ticket_id` | integer | Yes | Ticket number | | `status` | string | No | Status. One of: `new`, `open`, `pending`, `hold`, `solved`, `closed`. | | `custom_status` | string or integer | No | One of the account's ticket statuses (zendesk_list_ticket_statuses), by its name (any case, e.g. "Waiting on customer") or id. It also sets the ticket's status to that status's category, so don't pass status as well. | | `priority` | string | No | Priority. One of: `low`, `normal`, `high`, `urgent`. | | `type` | string | No | Type. One of: `question`, `incident`, `problem`, `task`. | | `assignee_id` | integer | No | Agent user id (zendesk_find_users) | | `add_tags` | array of string | No | Tags to add | | `remove_tags` | array of string | No | Tags to remove | | `from_address` | string | No | Support address the ticket's emails go out from, e.g. help@brand-b.com (zendesk_list_support_addresses). When the account has several and the user didn't say which, ask them. | | `confirm` | boolean | Yes | Must be true: the user approved these exact changes | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_update_ticket \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"ticket_id": 1, "confirm": true}' ``` ## zendesk_ticket_stats **Zendesk ticket counts** · Read Counts tickets for a quick overview: open, pending, on hold, new and unsolved right now, plus created and solved in a period. Narrow it with a Zendesk query, e.g. "tags:refund", "group:Billing" or "assignee:me". For trends, call it for each period. | Argument | Type | Required | What it is | | --------- | ------ | -------- | ---------------------------------------------------------------------- | | `account` | string | No | Zendesk account id from list_accounts (optional when there's only one) | | `from` | string | Yes | Period start, YYYY-MM-DD | | `to` | string | Yes | Period end, YYYY-MM-DD (inclusive) | | `query` | string | No | Extra Zendesk search filter applied to every count | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_ticket_stats \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"from": "2026-11-01", "to": "2026-11-15"}' ``` ## zendesk_list_macros **List Zendesk macros** · Read The saved replies and actions (macros) this agent can use, optionally filtered by words in the title. Use zendesk_apply_macro to use one. | Argument | Type | Required | What it is | | --------- | ------ | -------- | ---------------------------------------------------------------------- | | `account` | string | No | Zendesk account id from list_accounts (optional when there's only one) | | `search` | string | No | Words in the macro title | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_list_macros \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## zendesk_apply_macro **Apply a Zendesk macro** · Change Applies a macro to a ticket (its reply text, status, tags and other changes). Needs changes allowed for this Zendesk account and MCP server. > [!IMPORTANT] > Call it first with `preview` left at `true` to see what the macro would do. To apply it, call again with `"preview": false` and `"confirm": true`. Changes must be allowed. See [Making changes](/developers/calling-tools#making-changes). | Argument | Type | Required | What it is | | ----------- | ------- | -------- | -------------------------------------------------------------------------------- | | `account` | string | No | Zendesk account id from list_accounts (optional when there's only one) | | `ticket_id` | integer | Yes | Ticket number | | `macro_id` | integer | Yes | Macro id from zendesk_list_macros | | `preview` | boolean | No | true = only show what would change. Default `true`. | | `confirm` | boolean | No | Must be true to apply: the user approved the previewed changes. Default `false`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_apply_macro \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"ticket_id": 1, "macro_id": 1, "preview": false, "confirm": true}' ``` ## zendesk_create_ticket **Create a Zendesk ticket** · Change Opens a new ticket for a customer (by email; Zendesk creates the person if new), with a first message, priority, type and tags. By default the first message is an internal note, so the customer isn't emailed; set notify_requester: true to email them. It goes out from the account's default support address unless from_address names another (that address's brand is used too). Needs changes allowed for this Zendesk account and MCP server. > [!IMPORTANT] > This tool makes a change, so the request must include `"confirm": true`, and changes must be allowed. See [Making changes](/developers/calling-tools#making-changes). | Argument | Type | Required | What it is | | ------------------ | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `account` | string | No | Zendesk account id from list_accounts (optional when there's only one) | | `subject` | string | Yes | Subject | | `body` | string | Yes | The first message | | `requester_email` | string | Yes | Requester's email address | | `requester_name` | string | No | Requester's name | | `notify_requester` | boolean | No | true = the first message is a public reply emailed to the requester. Default `false`. | | `priority` | string | No | Priority. One of: `low`, `normal`, `high`, `urgent`. | | `type` | string | No | Type. One of: `question`, `incident`, `problem`, `task`. | | `tags` | array of string | No | Tags | | `assignee_id` | integer | No | Agent user id (zendesk_find_users) | | `from_address` | string | No | Support address the ticket's emails go out from, e.g. help@brand-b.com (zendesk_list_support_addresses). When the account has several and the user didn't say which, ask them. | | `confirm` | boolean | Yes | Must be true: the user approved these exact details | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/zendesk_create_ticket \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"subject": "…", "body": "…", "requester_email": "someone@example.com", "confirm": true}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # Marketing and analytics tools URL: https://docs.plugsight.app/developers/marketing-tools Search Console, Google Analytics, Google Ads and Microsoft Advertising tools in the developer API, with every argument. **Needs:** Google Search Console, Google Analytics, Google Ads, Microsoft Advertising, Meta Ads, LinkedIn Ads or TikTok Ads (coming soon) (Pro and Agency; Free can try 1 connection and 25 calls a month). 15 tools. These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. Marketing tools don't take an `account` from `list_accounts`. Call `list_marketing_accounts` for the sites, properties and ad accounts this key reaches, and pass their ids as `accounts` (leave it out for all). Sites or accounts you've hidden in Plugsight aren't listed and can't be read. | Tool | What it does | Kind | | --- | --- | --- | | [`list_marketing_accounts`](#list_marketing_accounts) | List marketing accounts | Read | | [`list_marketing_fields`](#list_marketing_fields) | List marketing data fields | Read | | [`get_marketing_data`](#get_marketing_data) | Get marketing data | Read | | [`marketing_deep_dive`](#marketing_deep_dive) | Marketing deep dive | Read | | [`search_console_inspect_url`](#search_console_inspect_url) | Inspect URL in Search Console | Read | | [`search_console_sitemaps`](#search_console_sitemaps) | List sitemaps | Read | | [`analytics_realtime`](#analytics_realtime) | Google Analytics 4 realtime | Read | | [`analytics_key_events`](#analytics_key_events) | GA4 key events | Read | | [`analytics_funnel`](#analytics_funnel) | GA4 funnel | Read | | [`analytics_metadata`](#analytics_metadata) | GA4 dimensions and metrics | Read | | [`google_ads_query`](#google_ads_query) | Google Ads query (GAQL) | Read | | [`microsoft_ads_campaigns`](#microsoft_ads_campaigns) | Microsoft Advertising campaigns | Read | | [`meta_ads_campaigns`](#meta_ads_campaigns) | Meta Ads campaigns | Read | | [`linkedin_ads_campaigns`](#linkedin_ads_campaigns) | LinkedIn Ads campaigns | Read | | [`tiktok_ads_campaigns`](#tiktok_ads_campaigns) | TikTok Ads campaigns | Read | The example requests fill in only the required arguments, with placeholder values. ## list_marketing_accounts **List marketing accounts** · Read Lists the marketing connections this MCP can use and everything they reach: Search Console sites, Google Analytics 4 properties, Google Ads customers (including accounts under a manager/MCC), Microsoft Advertising (Bing Ads) accounts, Meta (Facebook and Instagram) ad accounts, LinkedIn ad accounts and TikTok advertisers (ad accounts). Use the returned ids in the other marketing tools. Call this first. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `service` | string | No | Only this service. One of: `google_ads`, `microsoft_ads`, `meta_ads`, `linkedin_ads`, `tiktok_ads`, `search_console`, `analytics`. | | `search` | string | No | Only resources whose name or id contains this text | | `refresh` | boolean | No | Re-discover now instead of using the 15-minute cache. Default `false`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/list_marketing_accounts \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## list_marketing_fields **List marketing data fields** · Read Every field get_marketing_data accepts for a connector, as dimensions and metrics with descriptions. Derived metrics (ctr, cpc, cpa, roas, conversion_rate…) are recalculated after combining rows, so they stay correct across accounts. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `connector` | string | Yes | google_ads, microsoft_ads (Microsoft Advertising / Bing Ads), meta_ads (Facebook and Instagram ads), linkedin_ads, tiktok_ads, search_console, analytics (GA4) One of: `google_ads`, `microsoft_ads`, `meta_ads`, `linkedin_ads`, `tiktok_ads`, `search_console`, `analytics`. | | `search` | string | No | Only fields whose name or description contains this | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/list_marketing_fields \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"connector": "google_ads"}' ``` ## get_marketing_data **Get marketing data** · Read The main analysis tool. Pulls any combination of dimensions and metrics from Google Ads, Microsoft Advertising, Meta Ads, LinkedIn Ads, TikTok Ads, Search Console or GA4, for one, several or all connected accounts at once, and returns a compact table with totals. Pick fields from list_marketing_fields. The right report is chosen automatically (e.g. search_term → search-term report, keyword → keyword report). Examples: converting keywords: fields [keyword, match_type, campaign, cost, conversions, cpa, conversion_value, roas] with filter conversions gt 0; wasted spend: [search_term, keyword, cost, clicks, conversions] with conversions eq 0 and cost gt 20; SEO: [query, page, clicks, impressions, ctr, position]. Rows from different accounts are combined unless account_name is a field. Totals use the platform's own figures where it gives them (Search Console, GA4), so they can exceed the sum of rows. Meta Ads: campaign → campaign level, ad_set / ad → finer levels; conversions are purchases unless options.conversion_action names another action. LinkedIn Ads: campaign_group, campaign and ad (creative) levels; conversions are website conversions and leads are Lead Gen Form leads. TikTok Ads: campaign / ad_group / ad set the level; conversions are TikTok's Conversions column and conversion_value is website purchase value; any TikTok report metric is tiktok:\ (rates such as tiktok:ctr are null where rows are combined; prefer the shared ratios). data_notes explain any data Google, Microsoft, Meta or TikTok withhold; partial is true when an account stopped at a row limit (partial_reason says what is incomplete); account_errors lists accounts that couldn't be read. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `connector` | string | Yes | google_ads, microsoft_ads (Microsoft Advertising / Bing Ads), meta_ads (Facebook and Instagram ads), linkedin_ads, tiktok_ads, search_console, analytics (GA4) One of: `google_ads`, `microsoft_ads`, `meta_ads`, `linkedin_ads`, `tiktok_ads`, `search_console`, `analytics`. | | `fields` | array of string | Yes | Dimensions and metrics, in output column order | | `accounts` | array of string | No | Account / customer / property ids or site URLs from list_marketing_accounts. Omit for all | | `date_preset` | string | No | Used when date_from/date_to aren't given. Default last_30d. One of: `today`, `yesterday`, `last_7d`, `last_14d`, `last_28d`, `last_30d`, `last_90d`, `last_180d`, `last_365d`, `this_month`, `last_month`, `this_year`, `last_year`. | | `date_from` | string | No | YYYY-MM-DD, or "today", "yesterday", "NdaysAgo" (e.g. "28daysAgo") | | `date_to` | string | No | YYYY-MM-DD, or "today", "yesterday", "NdaysAgo" (e.g. "28daysAgo") | | `filters` | array of object | No | All combine with AND. Text matching ignores case. Metric filters apply after combining rows. Default `[]`. | | `order_by` | array of object | No | Default: first metric, descending | | `limit` | integer | No | Rows returned (after sorting) Default `500`. | | `max_rows_per_account` | integer | No | Rows fetched per account before combining. Default `100000`. | | `totals` | boolean | No | Add a totals row. Default `true`. | | `options` | object | No | Advanced report options. Default `{}`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/get_marketing_data \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"connector": "google_ads", "fields": []}' ``` ## marketing_deep_dive **Marketing deep dive** · Read Ready-made analyses that combine several queries and return findings plus tables: - account_overview: every connected platform/account (Google Ads, Microsoft Advertising, Meta Ads, LinkedIn Ads, TikTok Ads, Search Console, GA4), this period vs previous (spend, conversions, CPA, ROAS, organic clicks, sessions, revenue) - wasted_spend (google_ads/microsoft_ads): non-converting search terms and keywords, % of budget wasted, negative-keyword candidates - scale_opportunities (ads): campaigns/keywords at or below average CPA that lose impression share to budget or rank - search_term_winners (ads): converting search terms not yet added as keywords - quality_score_audit (ads): spend by quality score and which component drags low scores down - paid_vs_organic (ads + Search Console): paying where you rank top 3, paid winners with weak SEO, organic queries worth a paid test - seo_opportunities (Search Console): striking-distance queries, low-CTR snippets, pages losing clicks - period_comparison (any connector, needs fields): this period vs previous period or last year, biggest gains and drops Use get_marketing_data to drill into anything a deep dive surfaces. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `report` | string | Yes | Which ready-made analysis to run. One of: `account_overview`, `wasted_spend`, `scale_opportunities`, `search_term_winners`, `quality_score_audit`, `paid_vs_organic`, `seo_opportunities`, `period_comparison`. | | `connector` | string | No | Ads reports: google_ads (default) or microsoft_ads. period_comparison: any. One of: `google_ads`, `microsoft_ads`, `meta_ads`, `linkedin_ads`, `tiktok_ads`, `search_console`, `analytics`. | | `accounts` | array of string | No | Account ids for the connector. Omit for all | | `site_urls` | array of string | No | Search Console sites for paid_vs_organic / seo_opportunities. Omit for all | | `date_preset` | string | No | Default last_30d. One of: `last_7d`, `last_14d`, `last_28d`, `last_30d`, `last_90d`, `last_180d`, `last_365d`, `this_month`, `last_month`, `this_year`, `last_year`. | | `date_from` | string | No | YYYY-MM-DD, or "today", "yesterday", "NdaysAgo" (e.g. "28daysAgo") | | `date_to` | string | No | YYYY-MM-DD, or "today", "yesterday", "NdaysAgo" (e.g. "28daysAgo") | | `compare` | string | No | Period to compare with. One of: `previous_period`, `previous_year`. Default `"previous_period"`. | | `fields` | array of string | No | period_comparison: dimensions + metrics, e.g. [campaign, cost, conversions, cpa] | | `filters` | array of object | No | period_comparison only | | `min_cost` | number | No | Spend threshold for wasted_spend lists. Default `10`. | | `min_conversions` | number | No | Conversion threshold for winners / scale reports. Default `1`. | | `min_impressions` | number | No | Impression threshold for SEO reports. Default `100`. | | `top` | integer | No | Rows per table. Default `25`. | | `conversion_action` | string | No | Meta Ads only: the action type counted as conversions, e.g. lead or complete_registration. Default: purchases | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/marketing_deep_dive \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"report": "account_overview"}' ``` ## search_console_inspect_url **Inspect URL in Search Console** · Read Index status of one URL as Google sees it: coverage, last crawl, canonical, mobile usability, rich results. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `site_url` | string | Yes | Site from list_marketing_accounts that contains the URL | | `url` | string | Yes | Full URL to inspect | | `language_code` | string | No | For translated issue messages, e.g. en-GB | | `connection` | string | No | Connection id from list_marketing_accounts. Optional: a connection that reaches the resource is picked automatically. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/search_console_inspect_url \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"site_url": "…", "url": "…"}' ``` ## search_console_sitemaps **List sitemaps** · Read Sitemaps submitted for a Search Console site, with submitted/indexed counts, errors and warnings. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `site_url` | string | Yes | Search Console site from list_marketing_accounts (optional with one site) | | `connection` | string | No | Connection id from list_marketing_accounts. Optional: a connection that reaches the resource is picked automatically. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/search_console_sitemaps \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"site_url": "…"}' ``` ## analytics_realtime **Google Analytics 4 realtime** · Read Activity in the last 30 minutes, e.g. activeUsers by country, unifiedScreenName or eventName (GA4 API names). | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `property_id` | string | Yes | GA4 property id from list_marketing_accounts (optional with one property) | | `metrics` | array of string | No | GA4 realtime metrics. Default `["activeUsers"]`. | | `dimensions` | array of string | No | GA4 realtime dimensions. Default `[]`. | | `limit` | integer | No | Most results to return. Default `50`. | | `connection` | string | No | Connection id from list_marketing_accounts. Optional: a connection that reaches the resource is picked automatically. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/analytics_realtime \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"property_id": "…"}' ``` ## analytics_key_events **GA4 key events** · Read The events a GA4 property counts as key events (conversions), with how many happened and the key event rate in a period. Use it to answer 'what counts as a conversion here' and 'which conversions are happening'. For breakdowns by channel or page, use get_marketing_data with conversions. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `property_id` | string | Yes | GA4 property id from list_marketing_accounts (optional with one property) | | `start_date` | string | No | YYYY-MM-DD, "today", "yesterday" or "NdaysAgo". Default `"28daysAgo"`. | | `end_date` | string | No | YYYY-MM-DD, "today", "yesterday" or "NdaysAgo". Default `"yesterday"`. | | `connection` | string | No | Connection id from list_marketing_accounts. Optional: a connection that reaches the resource is picked automatically. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/analytics_key_events \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"property_id": "…"}' ``` ## analytics_funnel **GA4 funnel** · Read Builds a funnel from 2–10 steps and shows how many users reach each step, the completion rate and where they drop off. Each step is an event (e.g. view_item, add_to_cart, begin_checkout, purchase) or a page (page view whose URL contains text). Closed funnels (default) count users who start at step 1; open funnels let users enter at any step. Optionally break down by a dimension such as deviceCategory or sessionDefaultChannelGroup. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `property_id` | string | Yes | GA4 property id from list_marketing_accounts (optional with one property) | | `steps` | array of object | Yes | Funnel steps, in order: each a name and an event | | `open_funnel` | boolean | No | true: people can enter at any step. Default `false`. | | `breakdown` | string | No | GA4 dimension, e.g. deviceCategory | | `start_date` | string | No | YYYY-MM-DD, "today", "yesterday" or "NdaysAgo". Default `"28daysAgo"`. | | `end_date` | string | No | YYYY-MM-DD, "today", "yesterday" or "NdaysAgo". Default `"yesterday"`. | | `connection` | string | No | Connection id from list_marketing_accounts. Optional: a connection that reaches the resource is picked automatically. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/analytics_funnel \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"property_id": "…", "steps": []}' ``` ## analytics_metadata **GA4 dimensions and metrics** · Read All dimensions and metrics available for a GA4 property, including its custom definitions. Any of these work in get_marketing_data. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `property_id` | string | Yes | GA4 property id from list_marketing_accounts (optional with one property) | | `search` | string | No | Only fields whose name or description contains this | | `connection` | string | No | Connection id from list_marketing_accounts. Optional: a connection that reaches the resource is picked automatically. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/analytics_metadata \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"property_id": "…"}' ``` ## google_ads_query **Google Ads query (GAQL)** · Read Runs any read-only Google Ads Query Language SELECT against one customer, for anything get_marketing_data doesn't cover. Rows come back flattened ("campaign.name", "metrics.clicks"). cost_micros ÷ 1,000,000 = account currency. Manager accounts can't report metrics; query their clients. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `customer_id` | string | Yes | Customer id from list_marketing_accounts (dashes optional) | | `query` | string | Yes | GAQL SELECT statement | | `limit` | integer | No | Most results to return. Default `500`. | | `connection` | string | No | Connection id from list_marketing_accounts. Optional: a connection that reaches the resource is picked automatically. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/google_ads_query \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"customer_id": "…", "query": "…"}' ``` ## microsoft_ads_campaigns **Microsoft Advertising campaigns** · Read Campaign settings in a Microsoft Advertising account: status, type, budget and bidding strategy. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `account_id` | string | Yes | Account id from list_marketing_accounts (optional with one account) | | `connection` | string | No | Connection id from list_marketing_accounts. Optional: a connection that reaches the resource is picked automatically. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/microsoft_ads_campaigns \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account_id": "…"}' ``` ## meta_ads_campaigns **Meta Ads campaigns** · Read Campaign settings in a Meta (Facebook and Instagram) ad account: status, objective, daily or lifetime budget (in the account's currency) and bid strategy. For results, use get_marketing_data with connector meta_ads. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `account_id` | string | Yes | Ad account id from `list_marketing_accounts` (with or without `act_`) | | `connection` | string | No | Connection id from list_marketing_accounts. Optional: a connection that reaches the resource is picked automatically. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/meta_ads_campaigns \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account_id": "…"}' ``` ## linkedin_ads_campaigns **LinkedIn Ads campaigns** · Read Campaign settings in a LinkedIn ad account: status, type, objective, campaign group, daily and total budget (in the account's currency), bid and schedule. For results, use get_marketing_data with connector linkedin_ads. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `account_id` | string | Yes | Ad account id from `list_marketing_accounts` | | `connection` | string | No | Connection id from list_marketing_accounts. Optional: a connection that reaches the resource is picked automatically. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/linkedin_ads_campaigns \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account_id": "…"}' ``` ## tiktok_ads_campaigns **TikTok Ads campaigns** · Read Campaign settings in a TikTok ad account (advertiser): status, delivery status, objective and budget (daily or total, in the account's currency). For results, use get_marketing_data with connector tiktok_ads. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `account_id` | string | Yes | Advertiser id from `list_marketing_accounts` | | `connection` | string | No | Connection id from list_marketing_accounts. Optional: a connection that reaches the resource is picked automatically. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/tiktok_ads_campaigns \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account_id": "…"}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # Calendar tools URL: https://docs.plugsight.app/developers/calendar-tools Every calendar tool in the developer API, with arguments and examples: list events, find free time, book and change events. **Needs:** Google, Outlook or iCloud Calendar. 7 tools. These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. | Tool | What it does | Kind | | ----------------------------------------------------- | ----------------------- | ------ | | [`calendar_list_calendars`](#calendar_list_calendars) | List calendars | Read | | [`calendar_list_events`](#calendar_list_events) | List calendar events | Read | | [`calendar_get_event`](#calendar_get_event) | Read a calendar event | Read | | [`calendar_find_free_time`](#calendar_find_free_time) | Find free time | Read | | [`calendar_create_event`](#calendar_create_event) | Book a calendar event | Change | | [`calendar_update_event`](#calendar_update_event) | Change a calendar event | Change | | [`calendar_cancel_event`](#calendar_cancel_event) | Cancel a calendar event | Change | Change tools in this group: `calendar_create_event`, `calendar_update_event`, `calendar_cancel_event`. Check each tool's notes below for what it needs before it runs. The example requests fill in only the required arguments, with placeholder values. ## calendar_list_calendars **List calendars** · Read Calendars this connection can read (Google, Outlook or iCloud), with their ids, time zones and whether events can be added. | Argument | Type | Required | What it is | | --------- | ------ | -------- | ------------------------------------------------------------------------------ | | `account` | string | No | Connection id from list_accounts (optional when there's only one of this type) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/calendar_list_calendars \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## calendar_list_events **List calendar events** · Read Events between two times, across all visible calendars or one, optionally matching text. Times are ISO 8601 (e.g. "2026-11-20T09:00:00+04:00") or dates (YYYY-MM-DD), which cover whole days in the calendar's time zone. Recurring events are expanded. Long descriptions are shortened (description_truncated: true); calendar_get_event returns an event in full. When more events match than `limit`, the result says truncated: true and gives next_from to continue from. | Argument | Type | Required | What it is | | ------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------- | | `from` | string | Yes | Start: ISO date-time or YYYY-MM-DD | | `to` | string | Yes | End: ISO date-time or YYYY-MM-DD (inclusive for dates) | | `query` | string | No | Text to match in title, description, location or attendees | | `calendar_id` | string | No | One calendar id from calendar_list_calendars; default all visible | | `time_zone` | string | No | IANA time zone for dates and times given without an offset, e.g. "Europe/London". Default: the calendar's own | | `limit` | integer | No | Most events to return. Default `100`. | | `account` | string | No | Connection id from list_accounts (optional when there's only one of this type) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/calendar_list_events \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"from": "2026-11-01", "to": "2026-11-15"}' ``` ## calendar_get_event **Read a calendar event** · Read One event in full: the whole description, every guest and their reply, video-call and dial-in links, location and attached files (names and links). Use an event id (and calendar_id) from calendar_list_events. | Argument | Type | Required | What it is | | ------------- | ------ | -------- | ----------------------------------------------------------------------------------------- | | `event_id` | string | Yes | Event id from calendar_list_events | | `calendar_id` | string | No | The event's calendar_id from calendar_list_events; default: look in each visible calendar | | `account` | string | No | Connection id from list_accounts (optional when there's only one of this type) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/calendar_get_event \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"event_id": "…"}' ``` ## calendar_find_free_time **Find free time** · Read Busy times across visible calendars between two times, and free gaps of at least min_minutes. Dates (YYYY-MM-DD) cover whole days in the calendar's time zone. Events marked free don't block time; all-day events marked busy or out of office do. Use it to suggest meeting slots; check notes for calendars that couldn't be read. | Argument | Type | Required | What it is | | ------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------- | | `from` | string | Yes | Start: ISO date-time or YYYY-MM-DD | | `to` | string | Yes | End: ISO date-time or YYYY-MM-DD (inclusive for dates) | | `time_zone` | string | No | IANA time zone for dates and times given without an offset, e.g. "Europe/London". Default: the calendar's own | | `min_minutes` | integer | No | Shortest free gap worth listing, in minutes. Default `30`. | | `account` | string | No | Connection id from list_accounts (optional when there's only one of this type) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/calendar_find_free_time \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"from": "2026-11-01", "to": "2026-11-15"}' ``` ## calendar_create_event **Book a calendar event** · Change Creates an event, optionally inviting guests (and, on Google calendars, adding a Google Meet link). Check calendar_find_free_time first. Times are ISO 8601 with offset (e.g. "2026-11-20T15:00:00+04:00"), or YYYY-MM-DD for all-day events (end is the day after). > [!IMPORTANT] > This tool makes a change, so the request must include `"confirm": true`, and changes must be allowed. See [Making changes](/developers/calling-tools#making-changes). | Argument | Type | Required | What it is | | --------------- | --------------- | -------- | ------------------------------------------------------------------------------ | | `title` | string | Yes | Event title | | `start` | string | Yes | ISO date-time with offset, or YYYY-MM-DD for all day | | `end` | string | Yes | ISO date-time with offset, or YYYY-MM-DD (exclusive) for all day | | `time_zone` | string | No | IANA zone, e.g. "Europe/London"; default the calendar's | | `description` | string | No | Description | | `location` | string | No | Location | | `guests` | array of string | No | Email addresses to invite | | `google_meet` | boolean | No | Add a Google Meet video link (Google calendars only) Default `false`. | | `notify_guests` | boolean | No | Email the guests (invitations, updates or cancellation) Default `true`. | | `calendar_id` | string | No | Default: the primary calendar | | `account` | string | No | Connection id from list_accounts (optional when there's only one of this type) | | `confirm` | boolean | Yes | Must be true: the user approved these exact details | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/calendar_create_event \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"title": "…", "start": "2026-11-20T15:00:00+00:00", "end": "2026-11-20T15:30:00+00:00", "confirm": true}' ``` ## calendar_update_event **Change a calendar event** · Change Moves or edits an event: new time, title, description, location, or more guests. Only the fields given change. Use the event id from calendar_list_events. > [!IMPORTANT] > This tool makes a change, so the request must include `"confirm": true`, and changes must be allowed. See [Making changes](/developers/calling-tools#making-changes). | Argument | Type | Required | What it is | | --------------- | --------------- | -------- | ------------------------------------------------------------------------------ | | `event_id` | string | Yes | Event id from calendar_list_events | | `calendar_id` | string | No | The event's calendar; default the primary calendar | | `title` | string | No | New title | | `start` | string | No | New start, ISO 8601 date-time | | `end` | string | No | New end, ISO 8601 date-time | | `time_zone` | string | No | IANA time zone, e.g. Europe/London | | `description` | string | No | Description | | `location` | string | No | Location | | `add_guests` | array of string | No | Guest email addresses to invite | | `notify_guests` | boolean | No | Email the guests (invitations, updates or cancellation) Default `true`. | | `account` | string | No | Connection id from list_accounts (optional when there's only one of this type) | | `confirm` | boolean | Yes | Must be true: the user approved these exact details | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/calendar_update_event \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"event_id": "…", "confirm": true}' ``` ## calendar_cancel_event **Cancel a calendar event** · Change Deletes an event and, by default, emails guests a cancellation. For a repeating event, Google cancels only the given occurrence; iCloud cancels the whole series. > [!IMPORTANT] > This tool makes a change, so the request must include `"confirm": true`, and changes must be allowed. See [Making changes](/developers/calling-tools#making-changes). | Argument | Type | Required | What it is | | --------------- | ------- | -------- | ------------------------------------------------------------------------------ | | `event_id` | string | Yes | Event id from calendar_list_events | | `calendar_id` | string | No | Calendar id from calendar_list_calendars (default: the main calendar) | | `notify_guests` | boolean | No | Email the guests (invitations, updates or cancellation) Default `true`. | | `account` | string | No | Connection id from list_accounts (optional when there's only one of this type) | | `confirm` | boolean | Yes | Must be true: the user approved these exact details | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/calendar_cancel_event \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"event_id": "…", "confirm": true}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # Contacts tools URL: https://docs.plugsight.app/developers/contacts-tools Every contacts tool in the developer API, with arguments and examples: search, list and read contacts. **Needs:** Google, Outlook or iCloud Contacts. 3 tools. These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. | Tool | What it does | Kind | | ------------------------------------- | --------------- | ---- | | [`contacts_search`](#contacts_search) | Search contacts | Read | | [`contacts_list`](#contacts_list) | List contacts | Read | | [`contacts_get`](#contacts_get) | Get a contact | Read | The example requests fill in only the required arguments, with placeholder values. ## contacts_search **Search contacts** · Read Finds people by name, email, phone or company. Google also searches 'other contacts' (people you've emailed); iCloud and Outlook search the whole address book. Returns { contacts, note }: a note means some contacts couldn't be searched, and says why. | Argument | Type | Required | What it is | | --------- | ------- | -------- | ------------------------------------------------------------------------------ | | `query` | string | Yes | Name, email, phone number or company | | `limit` | integer | No | Most results to return. Default `20`. | | `account` | string | No | Connection id from list_accounts (optional when there's only one of this type) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/contacts_search \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "…"}' ``` ## contacts_list **List contacts** · Read Saved contacts with paging (Google: most recently changed first; iCloud and Outlook: by name). A note means the list isn't complete, and says why. | Argument | Type | Required | What it is | | ------------ | ------- | -------- | ------------------------------------------------------------------------------ | | `limit` | integer | No | Most results to return. Default `100`. | | `page_token` | string | No | next_page_token from the previous page | | `account` | string | No | Connection id from list_accounts (optional when there's only one of this type) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/contacts_list \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## contacts_get **Get a contact** · Read Everything saved for one contact: emails, phones, organisation, addresses, notes, birthday and links. | Argument | Type | Required | What it is | | --------- | ------ | -------- | ------------------------------------------------------------------------------ | | `id` | string | Yes | Contact id from contacts_search or contacts_list | | `account` | string | No | Connection id from list_accounts (optional when there's only one of this type) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/contacts_get \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"id": "…"}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # WooCommerce tools URL: https://docs.plugsight.app/developers/woocommerce-tools Every WooCommerce tool in the developer API, with arguments and examples: sales reports, orders, products and customers. **Needs:** A WooCommerce store. 5 tools. These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. | Tool | What it does | Kind | | --------------------------------------------------------------- | ---------------------------- | ---- | | [`woocommerce_sales_report`](#woocommerce_sales_report) | WooCommerce sales | Read | | [`woocommerce_list_orders`](#woocommerce_list_orders) | List WooCommerce orders | Read | | [`woocommerce_get_order`](#woocommerce_get_order) | Read a WooCommerce order | Read | | [`woocommerce_search_products`](#woocommerce_search_products) | Search WooCommerce products | Read | | [`woocommerce_search_customers`](#woocommerce_search_customers) | Search WooCommerce customers | Read | The example requests fill in only the required arguments, with placeholder values. ## woocommerce_sales_report **WooCommerce sales** · Read Sales for a period from a WooCommerce store: gross and net sales, orders, items sold, average order, tax, shipping, refunds and discounts, with a per-day (or per-month) breakdown and the best-selling products with quantity and net revenue. Use it for 'how did the shop do' questions. | Argument | Type | Required | What it is | | -------------- | ------- | -------- | ----------------------------------------------------------------------- | | `from` | string | Yes | YYYY-MM-DD | | `to` | string | Yes | YYYY-MM-DD | | `top_products` | integer | No | How many best-selling products to list. Default `10`. | | `account` | string | No | Store connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/woocommerce_sales_report \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"from": "2026-11-01", "to": "2026-11-15"}' ``` ## woocommerce_list_orders **List WooCommerce orders** · Read Orders, newest first, optionally by status, date range or a search (customer name, email, order number or product). Use woocommerce_get_order for the items, addresses and notes of one order. | Argument | Type | Required | What it is | | --------- | ------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | `status` | string | No | Status. One of: `any`, `pending`, `processing`, `on-hold`, `completed`, `cancelled`, `refunded`, `failed`, `checkout-draft`. Default `"any"`. | | `from` | string | No | YYYY-MM-DD | | `to` | string | No | YYYY-MM-DD | | `search` | string | No | Search text | | `limit` | integer | No | Most results to return. Default `25`. | | `page` | integer | No | Page of results, from 1. Default `1`. | | `account` | string | No | Store connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/woocommerce_list_orders \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## woocommerce_get_order **Read a WooCommerce order** · Read One order in full: items with the options chosen (size, colour, add-ons) and variation id, totals, fees, discounts, shipping, refunds, payment method and transaction id, when it was paid and completed, shipment tracking, customer, addresses and order notes. | Argument | Type | Required | What it is | | ---------- | ------- | -------- | ----------------------------------------------------------------------- | | `order_id` | integer | Yes | Order number | | `account` | string | No | Store connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/woocommerce_get_order \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"order_id": 1}' ``` ## woocommerce_search_products **Search WooCommerce products** · Read Products by name or SKU, optionally only those out of stock or on backorder, with price, stock level and total sales. Sort by popularity to see best sellers of all time. Set include_variations to list each variable product's variations (size, colour…) with their own SKU, price and stock, which the product itself doesn't show. | Argument | Type | Required | What it is | | -------------------- | ------- | -------- | --------------------------------------------------------------------------------------------------- | | `search` | string | No | Search text | | `sku` | string | No | Product SKU | | `stock_status` | string | No | Only products with this stock status. One of: `instock`, `outofstock`, `onbackorder`. | | `orderby` | string | No | Sort products by. One of: `popularity`, `date`, `title`, `price`, `rating`. Default `"popularity"`. | | `include_variations` | boolean | No | Also list each variable product's variations with SKU, price and stock. Default `false`. | | `limit` | integer | No | Most results to return. Default `25`. | | `page` | integer | No | Page of results, from 1. Default `1`. | | `account` | string | No | Store connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/woocommerce_search_products \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## woocommerce_search_customers **Search WooCommerce customers** · Read Registered customers by name or email, with how many orders they placed and how much they spent. Newest first unless searching. Guest checkouts aren't customers here; find them with woocommerce_list_orders. | Argument | Type | Required | What it is | | --------- | ------- | -------- | ----------------------------------------------------------------------- | | `search` | string | No | Name or email | | `limit` | integer | No | Most results to return. Default `25`. | | `page` | integer | No | Page of results, from 1. Default `1`. | | `account` | string | No | Store connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/woocommerce_search_customers \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # Magento tools URL: https://docs.plugsight.app/developers/magento-tools Every Magento / Adobe Commerce tool in the developer API, with arguments and examples: sales, orders, products and customers. **Needs:** A Magento store. 5 tools. These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. | Tool | What it does | Kind | | ------------------------------------------------------- | ------------------------ | ---- | | [`magento_sales_report`](#magento_sales_report) | Magento sales | Read | | [`magento_list_orders`](#magento_list_orders) | List Magento orders | Read | | [`magento_get_order`](#magento_get_order) | Read a Magento order | Read | | [`magento_search_products`](#magento_search_products) | Search Magento products | Read | | [`magento_search_customers`](#magento_search_customers) | Search Magento customers | Read | The example requests fill in only the required arguments, with placeholder values. ## magento_sales_report **Magento sales** · Read Sales for a period from a Magento / Adobe Commerce store, added up from every order in it: revenue, orders, items, average order, discounts, shipping, tax and refunds, a per-day breakdown and the best-selling products. Only paid orders count (processing, complete, closed); unpaid, on-hold, in-review and cancelled orders are listed separately under `excluded`. Totals are per currency when the store has several. On very busy stores the report can stop early: then complete is false and covered_through says how far it got. Dates are UTC. | Argument | Type | Required | What it is | | -------------- | ------- | -------- | ----------------------------------------------------------------------- | | `from` | string | Yes | YYYY-MM-DD (UTC) | | `to` | string | Yes | YYYY-MM-DD (UTC) | | `top_products` | integer | No | How many best-selling products to list. Default `10`. | | `account` | string | No | Store connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/magento_sales_report \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"from": "2026-11-01", "to": "2026-11-15"}' ``` ## magento_list_orders **List Magento orders** · Read Orders, newest first, optionally by status, date range (UTC) or customer email. Use magento_get_order for the items, addresses, payment and comments of one order. | Argument | Type | Required | What it is | | --------- | ------- | -------- | ----------------------------------------------------------------------- | | `status` | string | No | e.g. pending, processing, complete, canceled, closed, holded | | `from` | string | No | YYYY-MM-DD (UTC) | | `to` | string | No | YYYY-MM-DD (UTC) | | `email` | string | No | Customer email, or part of it | | `limit` | integer | No | Most results to return. Default `25`. | | `page` | integer | No | Page of results, from 1. Default `1`. | | `account` | string | No | Store connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/magento_list_orders \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## magento_get_order **Read a Magento order** · Read One order in full by its order number (e.g. 000000123) or id: items with the variant and options chosen, quantities shipped and refunded, totals, discounts, shipping, refunds, payment method, addresses, comments, and its shipments (with tracking numbers), invoices and credit memos. | Argument | Type | Required | What it is | | --------- | ------ | -------- | ----------------------------------------------------------------------- | | `order` | string | Yes | Order number as customers see it, or the id from magento_list_orders | | `account` | string | No | Store connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/magento_get_order \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"order": "…"}' ``` ## magento_search_products **Search Magento products** · Read Products by name or SKU with price, special (sale) price, stock quantity, type and status. Set low_stock_below to list products whose stock is at or under that quantity instead, with their SKU and name. | Argument | Type | Required | What it is | | ----------------- | ------- | -------- | ----------------------------------------------------------------------- | | `search` | string | No | Part of the product name | | `sku` | string | No | SKU, or part of it | | `low_stock_below` | integer | No | Only products with less stock than this | | `limit` | integer | No | Most results to return. Default `25`. | | `page` | integer | No | Page of results, from 1. Default `1`. | | `account` | string | No | Store connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/magento_search_products \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## magento_search_customers **Search Magento customers** · Read Registered customers by email or name, with when they joined and their default address. Use magento_list_orders with email for their orders. | Argument | Type | Required | What it is | | --------- | ------- | -------- | ----------------------------------------------------------------------- | | `email` | string | No | Email, or part of it | | `name` | string | No | First or last name, or part of it | | `limit` | integer | No | Most results to return. Default `25`. | | `page` | integer | No | Page of results, from 1. Default `1`. | | `account` | string | No | Store connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/magento_search_customers \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # Shopify tools URL: https://docs.plugsight.app/developers/shopify-tools Every Shopify tool in the developer API, with arguments and examples: sales, orders, products, stock and customers. **Needs:** A Shopify store. 6 tools. These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. | Tool | What it does | Kind | | ------------------------------------------------------- | ------------------------- | ---- | | [`shopify_sales_report`](#shopify_sales_report) | Shopify sales | Read | | [`shopify_list_orders`](#shopify_list_orders) | List Shopify orders | Read | | [`shopify_get_order`](#shopify_get_order) | Read a Shopify order | Read | | [`shopify_search_products`](#shopify_search_products) | Search Shopify products | Read | | [`shopify_inventory`](#shopify_inventory) | Shopify stock by location | Read | | [`shopify_search_customers`](#shopify_search_customers) | Search Shopify customers | Read | The example requests fill in only the required arguments, with placeholder values. ## shopify_sales_report **Shopify sales** · Read Sales for a period from a Shopify store, added up from every order in it: revenue (order totals), orders, items, average order, discounts, shipping, tax and refunds, a per-day breakdown and the best-selling products. Only paid orders count (paid, partially paid, partially refunded, refunded); pending, authorised-only, voided and expired payments, cancelled orders and test orders are listed separately under `excluded`. Amounts are in the store's currency. On very busy stores or long periods the report can stop early: then complete is false and covered_through says how far it got. complete is also false when the period starts more than 60 days ago and the store's app lacks read_all_orders; note says why. Dates are UTC. Pass account to choose the store when several are connected. | Argument | Type | Required | What it is | | -------------- | ------- | -------- | ----------------------------------------------------------------------------- | | `from` | string | Yes | YYYY-MM-DD (UTC) | | `to` | string | Yes | YYYY-MM-DD (UTC) | | `top_products` | integer | No | How many best-selling products to list. Default `10`. | | `account` | string | No | Store connection id from list_accounts (optional when there's only one store) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/shopify_sales_report \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"from": "2026-11-01", "to": "2026-11-15"}' ``` ## shopify_list_orders **List Shopify orders** · Read Orders, newest first, optionally by status, payment status, fulfilment status, date range (UTC), customer email or free text. Use shopify_get_order for the items, addresses, shipping, tracking and refunds of one order. | Argument | Type | Required | What it is | | ------------ | ------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `status` | string | No | Order status: open, closed (archived), cancelled, or any. One of: `open`, `closed`, `cancelled`, `any`. Default `"any"`. | | `payment` | string | No | Payment (financial) status. One of: `paid`, `pending`, `authorized`, `partially_paid`, `partially_refunded`, `refunded`, `voided`, `expired`. | | `fulfilment` | string | No | Fulfilment status: shipped, partial, unshipped (none shipped), unfulfilled (not fully shipped), on_hold or scheduled. One of: `shipped`, `partial`, `unshipped`, `unfulfilled`, `on_hold`, `scheduled`. | | `from` | string | No | YYYY-MM-DD (UTC) | | `to` | string | No | YYYY-MM-DD (UTC) | | `email` | string | No | Customer email | | `search` | string | No | Free text: an order number, customer name, product title or SKU | | `limit` | integer | No | Most results to return. Default `25`. | | `cursor` | string | No | next_cursor from the previous page, for the page after it | | `account` | string | No | Store connection id from list_accounts (optional when there's only one store) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/shopify_list_orders \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## shopify_get_order **Read a Shopify order** · Read One order in full by its order number (e.g. #1001) or id: items with variant, SKU, quantities still to ship and refunded, totals, discount codes, shipping method, tax, payment gateways, addresses, note and tags, its fulfilments with tracking numbers, and its refunds. | Argument | Type | Required | What it is | | --------- | ------ | -------- | --------------------------------------------------------------------------------- | | `order` | string | Yes | Order number as customers see it (e.g. #1001), or the id from shopify_list_orders | | `account` | string | No | Store connection id from list_accounts (optional when there's only one store) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/shopify_get_order \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"order": "…"}' ``` ## shopify_search_products **Search Shopify products** · Read Products by title, SKU, vendor or type, with status, price range, total stock and their variants (price, compare-at price, SKU, stock). Set low_stock_below to list variants whose stock is at or under that quantity instead, lowest first. | Argument | Type | Required | What it is | | ----------------- | ------- | -------- | ----------------------------------------------------------------------------- | | `search` | string | No | Words in the product title, or other free text | | `sku` | string | No | A variant's SKU | | `vendor` | string | No | The product vendor (brand or supplier), as set on the product | | `product_type` | string | No | The product type, as set on the product | | `status` | string | No | Status. One of: `active`, `draft`, `archived`. | | `low_stock_below` | integer | No | List variants with this many or fewer in stock (tracked inventory only) | | `limit` | integer | No | Most results to return. Default `25`. | | `cursor` | string | No | next_cursor from the previous page, for the page after it | | `account` | string | No | Store connection id from list_accounts (optional when there's only one store) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/shopify_search_products \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## shopify_inventory **Shopify stock by location** · Read Stock of one product's variants at each location: available, on hand, committed (ordered, not yet shipped) and incoming. Find the product by SKU or by its id from shopify_search_products. | Argument | Type | Required | What it is | | ------------ | ------ | -------- | ----------------------------------------------------------------------------- | | `sku` | string | No | A variant's SKU | | `product_id` | string | No | Product id from shopify_search_products | | `account` | string | No | Store connection id from list_accounts (optional when there's only one store) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/shopify_inventory \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## shopify_search_customers **Search Shopify customers** · Read Customers by name, email or other text, with their order count, amount spent, when they joined, tags and location. Use shopify_list_orders with email for their orders. | Argument | Type | Required | What it is | | --------- | ------- | -------- | ----------------------------------------------------------------------------- | | `search` | string | No | Name, email, phone or other text | | `email` | string | No | Exact email address | | `limit` | integer | No | Most results to return. Default `25`. | | `cursor` | string | No | next_cursor from the previous page, for the page after it | | `account` | string | No | Store connection id from list_accounts (optional when there's only one store) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/shopify_search_customers \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # Mailchimp tools URL: https://docs.plugsight.app/developers/mailchimp-tools Every Mailchimp tool in the developer API, with arguments and examples: audiences, campaigns, reports and subscribers. **Needs:** A Mailchimp account. 7 tools. These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. | Tool | What it does | Kind | | ----------------------------------------------------------- | -------------------------------- | ---- | | [`mailchimp_list_audiences`](#mailchimp_list_audiences) | List Mailchimp audiences | Read | | [`mailchimp_list_campaigns`](#mailchimp_list_campaigns) | List Mailchimp campaigns | Read | | [`mailchimp_campaign_report`](#mailchimp_campaign_report) | Mailchimp campaign report | Read | | [`mailchimp_audience_growth`](#mailchimp_audience_growth) | Mailchimp audience growth | Read | | [`mailchimp_find_subscriber`](#mailchimp_find_subscriber) | Find a Mailchimp subscriber | Read | | [`mailchimp_list_automations`](#mailchimp_list_automations) | List Mailchimp automations | Read | | [`mailchimp_list_segments`](#mailchimp_list_segments) | List Mailchimp tags and segments | Read | The example requests fill in only the required arguments, with placeholder values. ## mailchimp_list_audiences **List Mailchimp audiences** · Read Audiences (lists) with subscribers, unsubscribes, cleaned addresses, average open and click rates and how many campaigns each has had. Use the ids in the other Mailchimp tools. | Argument | Type | Required | What it is | | --------- | ------ | -------- | --------------------------------------------------------------------------- | | `account` | string | No | Mailchimp connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/mailchimp_list_audiences \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## mailchimp_list_campaigns **List Mailchimp campaigns** · Read Campaigns, newest first, with subject, audience, emails sent, open and click rates, and orders and revenue when the store is connected to Mailchimp. Filter by status, send date or audience. Use mailchimp_campaign_report for one campaign in full. | Argument | Type | Required | What it is | | ------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------ | | `status` | string | No | sent (default), save (drafts), schedule, sending, paused. One of: `sent`, `save`, `schedule`, `sending`, `paused`. Default `"sent"`. | | `sent_from` | string | No | YYYY-MM-DD | | `sent_to` | string | No | YYYY-MM-DD | | `audience_id` | string | No | Audience id from mailchimp_list_audiences | | `limit` | integer | No | Most results to return. Default `25`. | | `offset` | integer | No | Results to skip, for paging. Default `0`. | | `account` | string | No | Mailchimp connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/mailchimp_list_campaigns \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## mailchimp_campaign_report **Mailchimp campaign report** · Read One sent campaign's full results: opens, clicks, bounces, unsubscribes, spam complaints, orders and revenue, how it compares with the audience's average and the industry, and its most-clicked links. For an A/B test, what was tested, each variation's results and the winner. | Argument | Type | Required | What it is | | ------------- | ------- | -------- | --------------------------------------------------------------------------- | | `campaign_id` | string | Yes | Campaign id from mailchimp_list_campaigns | | `top_links` | integer | No | How many most-clicked links to list. Default `10`. | | `account` | string | No | Mailchimp connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/mailchimp_campaign_report \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"campaign_id": "…"}' ``` ## mailchimp_audience_growth **Mailchimp audience growth** · Read Month-by-month growth of one audience: new subscribers (opt-ins and imports), unsubscribes, cleaned addresses and the total at month end. | Argument | Type | Required | What it is | | ------------- | ------- | -------- | --------------------------------------------------------------------------- | | `audience_id` | string | Yes | Audience id from mailchimp_list_audiences | | `months` | integer | No | How many months back. Default `12`. | | `account` | string | No | Mailchimp connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/mailchimp_audience_growth \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"audience_id": "…"}' ``` ## mailchimp_find_subscriber **Find a Mailchimp subscriber** · Read Looks someone up by email address or name across audiences: their status (subscribed, unsubscribed, cleaned), when they joined, tags, rating, average open and click rates, their audience fields (merge fields such as name, birthday, address) and the groups (interests) they're in. | Argument | Type | Required | What it is | | ------------- | ------ | -------- | --------------------------------------------------------------------------- | | `query` | string | Yes | Email address, or part of a name or email | | `audience_id` | string | No | Only this audience | | `account` | string | No | Mailchimp connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/mailchimp_find_subscriber \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "…"}' ``` ## mailchimp_list_automations **List Mailchimp automations** · Read Classic automations (welcome series, abandoned cart, date-based…) with their status, audience, trigger, emails sent and open and click rates; with include_emails, each email in the series with its delay and results. Mailchimp's API doesn't list Customer Journeys (the newer journey builder), so those aren't included. | Argument | Type | Required | What it is | | ---------------- | ------- | -------- | --------------------------------------------------------------------------------- | | `include_emails` | boolean | No | Also list each automation's emails with their delay and results. Default `false`. | | `account` | string | No | Mailchimp connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/mailchimp_list_automations \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## mailchimp_list_segments **List Mailchimp tags and segments** · Read An audience's tags and saved segments with how many contacts each has. Use the audience id from mailchimp_list_audiences. | Argument | Type | Required | What it is | | ------------- | ------ | -------- | --------------------------------------------------------------------------- | | `audience_id` | string | Yes | Audience id from mailchimp_list_audiences | | `account` | string | No | Mailchimp connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/mailchimp_list_segments \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"audience_id": "…"}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # PageSpeed tool URL: https://docs.plugsight.app/developers/pagespeed-tools The pagespeed_check tool: Core Web Vitals and PageSpeed scores for any public web page, with its arguments and an example. **Needs:** Nothing to connect: every MCP server has it. 1 tool. Every MCP server has this tool, whatever it is connected to, so every API key can call it. Send its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. | Tool | What it does | Kind | | ------------------------------------- | ------------------------------------ | ---- | | [`pagespeed_check`](#pagespeed_check) | Check page speed and Core Web Vitals | Read | The example requests fill in only the required arguments, with placeholder values. ## pagespeed_check **Check page speed and Core Web Vitals** · Read Google PageSpeed Insights for any public page: performance, SEO, accessibility and best-practice scores; real-user Core Web Vitals (LCP, INP, CLS) for the page and the whole site from Chrome users, as Google Search uses them; lab timings; and the fixes that would save the most time. Takes 10–40 seconds. | Argument | Type | Required | What it is | | ------------ | --------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `url` | string | Yes | The page to check, e.g. https://example.com/pricing | | `strategy` | string | No | Mobile is what Google ranks on. One of: `mobile`, `desktop`. Default `"mobile"`. | | `categories` | array of string | No | Which scores to include. One of: `performance`, `seo`, `accessibility`, `best-practices`. Default `["performance", "seo", "accessibility", "best-practices"]`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/pagespeed_check \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"url": "…"}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # Bing Webmaster Tools tools URL: https://docs.plugsight.app/developers/bing-webmaster-tools Every Bing Webmaster Tools tool in the developer API, with its arguments and an example call. **Needs:** A Bing Webmaster Tools connection (Pro and Agency; Free can try 1 connection and 25 calls a month). 5 tools. These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. | Tool | What it does | Kind | | ------------------------------------------------------------------------- | ----------------------------- | ---- | | [`bing_webmaster_sites`](#bing_webmaster_sites) | List Bing Webmaster sites | Read | | [`bing_webmaster_search_performance`](#bing_webmaster_search_performance) | Bing search performance | Read | | [`bing_webmaster_crawl`](#bing_webmaster_crawl) | Bing crawl stats | Read | | [`bing_webmaster_sitemaps`](#bing_webmaster_sitemaps) | Bing sitemaps | Read | | [`bing_webmaster_url_info`](#bing_webmaster_url_info) | Bing index details for a page | Read | The example requests fill in only the required arguments, with placeholder values. ## bing_webmaster_sites **List Bing Webmaster sites** · Read The sites in this Bing Webmaster Tools account that AI apps may use, and whether each is verified. Use a site's URL in the other Bing Webmaster tools. | Argument | Type | Required | What it is | | --------- | ------ | -------- | -------------------------------------------------------------------------------- | | `account` | string | No | Bing Webmaster connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/bing_webmaster_sites \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## bing_webmaster_search_performance **Bing search performance** · Read How a site does in Bing search: clicks and impressions by day, and its top search queries and pages with clicks, impressions, CTR and average position. Bing keeps about six months and reports queries and pages by week, so from/to pick whole weeks. Default: everything Bing has. | Argument | Type | Required | What it is | | ---------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------ | | `account` | string | No | Bing Webmaster connection id from list_accounts (optional when there's only one) | | `site_url` | string | No | Site exactly as bing_webmaster_sites lists it, e.g. https://example.com/ (optional when the account has one) | | `from` | string | No | YYYY-MM-DD | | `to` | string | No | YYYY-MM-DD | | `top` | integer | No | How many top queries and pages (by clicks) Default `25`. | | `sort_by` | string | No | Field to sort by. One of: `clicks`, `impressions`. Default `"clicks"`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/bing_webmaster_search_performance \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## bing_webmaster_crawl **Bing crawl stats** · Read How Bing crawls a site, day by day: pages crawled, pages in the index, crawl errors, blocked by robots.txt, and responses by status (2xx, 301, 4xx, 5xx). About six months. | Argument | Type | Required | What it is | | ---------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------ | | `account` | string | No | Bing Webmaster connection id from list_accounts (optional when there's only one) | | `site_url` | string | No | Site exactly as bing_webmaster_sites lists it, e.g. https://example.com/ (optional when the account has one) | | `from` | string | No | YYYY-MM-DD | | `to` | string | No | YYYY-MM-DD | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/bing_webmaster_crawl \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## bing_webmaster_sitemaps **Bing sitemaps** · Read The sitemaps and feeds submitted for a site in Bing Webmaster Tools, with what Bing reports for each. | Argument | Type | Required | What it is | | ---------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------ | | `account` | string | No | Bing Webmaster connection id from list_accounts (optional when there's only one) | | `site_url` | string | No | Site exactly as bing_webmaster_sites lists it, e.g. https://example.com/ (optional when the account has one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/bing_webmaster_sitemaps \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## bing_webmaster_url_info **Bing index details for a page** · Read What Bing knows about one page of a site: whether and when it was discovered and crawled, and its index details. | Argument | Type | Required | What it is | | ---------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------ | | `account` | string | No | Bing Webmaster connection id from list_accounts (optional when there's only one) | | `site_url` | string | No | Site exactly as bing_webmaster_sites lists it, e.g. https://example.com/ (optional when the account has one) | | `url` | string | Yes | The page's full URL | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/bing_webmaster_url_info \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"url": "…"}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # Google Tag Manager tools URL: https://docs.plugsight.app/developers/tag-manager-tools The Google Tag Manager tools in the developer API, with every argument: list containers, read tags, audit and version history. **Needs:** A Google Tag Manager connection (Pro and Agency, once Google approves it). 5 tools, all read-only. > [!IMPORTANT] > Google is still reviewing the permission this connector needs. Until it approves it, Plugsight offers Google Tag Manager to Plugsight admins only, so for most people it isn't in the **Connector catalog** yet and these tools don't appear. See [Google Tag Manager](/connectors/google-tag-manager). These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. These tools need a plan that includes marketing connectors (Pro or Agency). On the Free plan they don't appear, even if the connection exists. These tools don't take an `account` argument. Call `tag_manager_list_containers` for the containers this key reaches and pass a GTM id (like `GTM-ABC123`) as `container`; leave it out when there's only one. Containers you've hidden in Plugsight aren't listed and can't be read. | Tool | What it does | Kind | | ------------------------------------------------------------- | ------------------------------ | ---- | | [`tag_manager_list_containers`](#tag_manager_list_containers) | List Tag Manager containers | Read | | [`tag_manager_container`](#tag_manager_container) | Tag Manager container contents | Read | | [`tag_manager_get_tag`](#tag_manager_get_tag) | Get a Tag Manager tag | Read | | [`tag_manager_audit`](#tag_manager_audit) | Audit a Tag Manager container | Read | | [`tag_manager_versions`](#tag_manager_versions) | Tag Manager version history | Read | Every tool here only reads: none of them changes anything in Google Tag Manager, so none needs `confirm`. The example requests fill in only the required arguments, with placeholder values. ## tag_manager_list_containers **List Tag Manager containers** · Read Lists the Google Tag Manager containers this MCP reaches, with their GTM ids and accounts. No arguments: send `{}`. Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/tag_manager_list_containers \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## tag_manager_container **Tag Manager container contents** · Read Everything in a container's published (live) version: each tag with its type, the triggers it fires on and whether it's paused; every trigger and variable. | Argument | Type | Required | What it is | | ----------- | ------ | -------- | ------------------------------------------------------------- | | `container` | string | No | Container id like GTM-ABC123 (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/tag_manager_container \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## tag_manager_get_tag **Get a Tag Manager tag** · Read One tag in full from the published version: its settings (measurement or conversion ids, event names, parameters), triggers and blocking triggers. | Argument | Type | Required | What it is | | ----------- | ------ | -------- | ------------------------------------------------------------- | | `tag` | string | Yes | Tag name or id from tag_manager_container | | `container` | string | No | Container id like GTM-ABC123 (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/tag_manager_get_tag \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"tag": "…"}' ``` ## tag_manager_audit **Audit a Tag Manager container** · Read Checks the published version for common tracking problems: tags that never fire, retired Universal Analytics tags, paused tags, possible duplicate tags (double counting), unused triggers and variables, Custom HTML tags; and lists changes waiting unpublished in workspaces. | Argument | Type | Required | What it is | | ----------- | ------ | -------- | ------------------------------------------------------------- | | `container` | string | No | Container id like GTM-ABC123 (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/tag_manager_audit \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## tag_manager_versions **Tag Manager version history** · Read Published versions of a container, newest first, with how many tags, triggers and variables each had. | Argument | Type | Required | What it is | | ----------- | ------- | -------- | ------------------------------------------------------------- | | `container` | string | No | Container id like GTM-ABC123 (optional when there's only one) | | `limit` | integer | No | Most results to return. From 1 to 100. Default `20`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/tag_manager_versions \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## Related articles - [Google Tag Manager](/connectors/google-tag-manager) - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Accounts tools](/developers/accounts-tools) --- # Custom API tools URL: https://docs.plugsight.app/developers/custom-api-tools Every Custom API tool in the developer API, with its arguments and an example call. **Needs:** A Custom API connection (Pro and Agency). Each imported OpenAPI operation also becomes its own tool, named after the connection. 2 tools. These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. Each operation imported from the connection's OpenAPI spec is also its own tool, named after the connection and the operation (for example `acme_crm_list_invoices`), for connections with up to 50 operations. Those tools differ for every connection, so they aren't listed here: `GET /v1/tools` shows the ones your API key reaches, and `custom_api_operations` lists every imported operation, with its parameters. | Tool | What it does | Kind | | --- | --- | --- | | [`custom_api_operations`](#custom_api_operations) | List a Custom API's operations | Read | | [`custom_api_request`](#custom_api_request) | Call a Custom API | Change | Change tools in this group: `custom_api_request`. Check each tool's notes below for what it needs before it runs. The example requests fill in only the required arguments, with placeholder values. ## custom_api_operations **List a Custom API's operations** · Read Lists the operations imported from a Custom API connection's OpenAPI spec: each one's operation_id, method, path, summary, parameters and body schema, and its own tool name when it has one. Call one with its tool, or with custom_api_request and operation_id. Use search to narrow a long list. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `account` | string | No | Custom API connection id from list_accounts (optional when there's only one) | | `search` | string | No | Only operations whose id, path or summary contain these words | | `limit` | integer | No | Most operations to return (default 100) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/custom_api_operations \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## custom_api_request **Call a Custom API** · Change Sends one HTTP request to a Custom API connection, signed with its saved credentials. Give a method and a path under the connection's base URL (never a full address), or an imported operation's operation_id with its params. GET and HEAD only read. Changes also need changes allowed for the connection and the MCP server. Any HTTP status comes back as data, with the body (JSON parsed; long bodies are cut at about 100,000 characters and marked truncated). > [!IMPORTANT] > `GET` and `HEAD` requests only read. `POST`, `PUT`, `PATCH` and `DELETE` make a change, so they must include `"confirm": true`, and changes must be allowed. See [Making changes](/developers/calling-tools#making-changes). | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `account` | string | No | Custom API connection id from list_accounts (optional when there's only one) | | `method` | string | No | HTTP method (default GET) One of: `GET`, `HEAD`, `POST`, `PUT`, `PATCH`, `DELETE`. | | `path` | string | No | Path under the base URL, like /users/42 | | `query` | object | No | Query string parameters, by name | | `body` | any | No | Request body: JSON (sent as application/json) or a string (sent as text) | | `headers` | object | No | Extra request headers. Not Authorization, cookies or the connection's own headers | | `operation_id` | string | No | An imported operation's id from custom_api_operations, instead of method and path | | `params` | object | No | With operation_id: its path, query and header parameters, by name (or by location and name, like "query:id", when two share a name) | | `confirm` | boolean | No | Must be true for POST, PUT, PATCH and DELETE: the user approved this exact request | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/custom_api_request \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"method": "GET", "path": "/users", "query": {"limit": 10}}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # YouTube tools URL: https://docs.plugsight.app/developers/youtube-tools The YouTube tools in the developer API, with every argument: list channels and videos, and run YouTube Analytics reports. **Needs:** A YouTube connection (Pro and Agency, once Google approves it). 3 tools, all read-only. > [!IMPORTANT] > Google is still reviewing the permission this connector needs. Until it approves it, Plugsight offers YouTube to Plugsight admins only, so for most people it isn't in the **Connector catalog** yet and these tools don't appear. See [YouTube](/connectors/youtube). These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. These tools need a plan that includes marketing connectors (Pro or Agency). On the Free plan they don't appear, even if the connection exists. These tools don't take an `account` argument. Call `youtube_list_channels` for the channels this key reaches and pass a channel id (`UC…`) as `channel`; leave it out when there's only one. Channels you've hidden in Plugsight aren't listed and can't be read. | Tool | What it does | Kind | | ------------------------------------------------- | ---------------------- | ---- | | [`youtube_list_channels`](#youtube_list_channels) | List YouTube channels | Read | | [`youtube_report`](#youtube_report) | YouTube channel report | Read | | [`youtube_list_videos`](#youtube_list_videos) | List YouTube videos | Read | Every tool here only reads: none of them changes anything in YouTube, so none needs `confirm`. The example requests fill in only the required arguments, with placeholder values. ## youtube_list_channels **List YouTube channels** · Read The YouTube channels this MCP reaches, with subscribers, total views and video count. No arguments: send `{}`. Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/youtube_list_channels \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## youtube_report **YouTube channel report** · Read YouTube Analytics for a channel over a period: views, watch time, average view duration, subscribers gained and lost, likes, comments, shares. group_by splits it: day or month (trends), video (top videos, with titles), country, device, traffic_source (search, suggested, external…), playback_location, subscribed_status, or age_gender (share of viewers). Returns a compact table with totals. | Argument | Type | Required | What it is | | ------------- | --------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `channel` | string | No | Channel id (UC…) from youtube_list_channels (optional when there's only one) | | `group_by` | string | No | How to split the report. One of: `none`, `day`, `month`, `video`, `country`, `device`, `traffic_source`, `playback_location`, `subscribed_status`, `age_gender`. Default `"none"`. | | `metrics` | array of string | No | YouTube Analytics metrics. Default: views, estimatedMinutesWatched, averageViewDuration, subscribersGained, subscribersLost, likes, comments, shares. Traffic, device and location splits allow views and estimatedMinutesWatched | | `sort_by` | string | No | Metric to rank by, for video, country and source splits. Default: the first metric | | `limit` | integer | No | Most rows to return. From 1 to 200. Default `25`. | | `date_preset` | string | No | Used when date_from/date_to aren't given. Default last_28d. One of: `last_7d`, `last_28d`, `last_30d`, `last_90d`, `last_365d`, `this_month`, `last_month`, `this_year`, `last_year`. | | `date_from` | string | No | YYYY-MM-DD, or "today", "yesterday", "NdaysAgo" (e.g. "28daysAgo") | | `date_to` | string | No | YYYY-MM-DD, or "today", "yesterday", "NdaysAgo" (e.g. "28daysAgo") | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/youtube_report \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## youtube_list_videos **List YouTube videos** · Read A channel's uploads, newest first, with publish date, length, views, likes, comments and link. Use youtube_report with group_by video for watch time over a period. | Argument | Type | Required | What it is | | --------- | ------- | -------- | ---------------------------------------------------------------------------- | | `channel` | string | No | Channel id (UC…) from youtube_list_channels (optional when there's only one) | | `search` | string | No | Only videos whose title contains this | | `limit` | integer | No | Most videos to return. From 1 to 200. Default `25`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/youtube_list_videos \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## Related articles - [YouTube](/connectors/youtube) - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Accounts tools](/developers/accounts-tools) --- # Custom MCP server tools URL: https://docs.plugsight.app/developers/custom-mcp-tools Every Custom MCP server tool in the developer API, with its arguments and an example call. **Needs:** A custom MCP server connection (Pro and Agency). Each of the server's own tools also becomes a tool, named after the connection. 1 tool. These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. Each tool of a custom MCP server is also a tool here, named after the connection and the server's own tool (for example `notes__search_notes`), with the server's own input schema. A tool counts as a change unless the server marks it read-only, and then takes `"confirm": true` (or `"plugsight_confirm": true` when the server's tool has its own `confirm` argument). Those tools differ for every server, so they aren't listed here: `GET /v1/tools` shows the ones your API key reaches. | Tool | What it does | Kind | | --- | --- | --- | | [`custom_mcp_refresh_tools`](#custom_mcp_refresh_tools) | Refresh a custom MCP server's tools | Read | The example requests fill in only the required arguments, with placeholder values. ## custom_mcp_refresh_tools **Refresh a custom MCP server's tools** · Read Lists a custom MCP server's tools again now, instead of using the list Plugsight keeps for a few minutes, and says how many only read and how many make changes. If its tools changed, the AI app needs to reload Plugsight's tool list to see them. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `account` | string | No | Custom MCP server connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/custom_mcp_refresh_tools \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## Related articles - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Authentication](/developers/authentication) --- # Google Merchant Center tools URL: https://docs.plugsight.app/developers/merchant-center-tools The Google Merchant Center tools in the developer API, with every argument: feed health, products and Shopping performance. **Needs:** A Google Merchant Center connection (Pro and Agency, once Google approves it). 4 tools, all read-only. > [!IMPORTANT] > Google is still reviewing the permission this connector needs. Until it approves it, Plugsight offers Google Merchant Center to Plugsight admins only, so for most people it isn't in the **Connector catalog** yet and these tools don't appear. See [Google Merchant Center](/connectors/google-merchant-center). These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. These tools need a plan that includes marketing connectors (Pro or Agency). On the Free plan they don't appear, even if the connection exists. These tools don't take an `account` argument. Call `merchant_center_list_accounts` for the Merchant Center accounts this key reaches and pass an id as `merchant`; leave it out when there's only one. Accounts you've hidden in Plugsight aren't listed and can't be read. | Tool | What it does | Kind | | ------------------------------------------------------------------- | ----------------------------- | ---- | | [`merchant_center_list_accounts`](#merchant_center_list_accounts) | List Merchant Center accounts | Read | | [`merchant_center_product_health`](#merchant_center_product_health) | Merchant Center feed health | Read | | [`merchant_center_list_products`](#merchant_center_list_products) | List Merchant Center products | Read | | [`merchant_center_performance`](#merchant_center_performance) | Merchant Center performance | Read | Every tool here only reads: none of them changes anything in Google Merchant Center, so none needs `confirm`. The example requests fill in only the required arguments, with placeholder values. ## merchant_center_list_accounts **List Merchant Center accounts** · Read The Google Merchant Center accounts this MCP reaches. No arguments: send `{}`. Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/merchant_center_list_accounts \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## merchant_center_product_health **Merchant Center feed health** · Read How many products are approved, limited (disapproved in some countries), pending or disapproved, and the most common product issues with how many products each affects, examples and Google's help link. | Argument | Type | Required | What it is | | ------------ | ------- | -------- | ---------------------------------------------------------------------------------------------- | | `merchant` | string | No | Merchant Center account id from merchant_center_list_accounts (optional when there's only one) | | `top_issues` | integer | No | How many issues to list. From 1 to 100. Default `15`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/merchant_center_product_health \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## merchant_center_list_products **List Merchant Center products** · Read Products with their status, price, availability, link and issues. Filter by status (e.g. disapproved) or by text in the title or offer id. | Argument | Type | Required | What it is | | ---------- | ------- | -------- | ---------------------------------------------------------------------------------------------- | | `merchant` | string | No | Merchant Center account id from merchant_center_list_accounts (optional when there's only one) | | `status` | string | No | Only products with this status. One of: `approved`, `limited`, `pending`, `disapproved`. | | `search` | string | No | Only products whose title or offer id contains this | | `limit` | integer | No | Most products to return. From 1 to 500. Default `50`. | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/merchant_center_list_products \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## merchant_center_performance **Merchant Center performance** · Read Shopping performance (free listings and Shopping ads) from Merchant Center: impressions, clicks, click-through rate, conversions and conversion value, by product, by day or in total. | Argument | Type | Required | What it is | | ------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `merchant` | string | No | Merchant Center account id from merchant_center_list_accounts (optional when there's only one) | | `group_by` | string | No | product: top products by clicks; day: a trend; none: totals only. One of: `product`, `day`, `none`. Default `"product"`. | | `limit` | integer | No | Most rows to return. From 1 to 1,000. Default `50`. | | `date_preset` | string | No | Used when date_from/date_to aren't given. Default last_28d. One of: `last_7d`, `last_28d`, `last_30d`, `last_90d`, `last_365d`, `this_month`, `last_month`, `this_year`, `last_year`. | | `date_from` | string | No | YYYY-MM-DD, or "today", "yesterday", "NdaysAgo" (e.g. "28daysAgo") | | `date_to` | string | No | YYYY-MM-DD, or "today", "yesterday", "NdaysAgo" (e.g. "28daysAgo") | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/merchant_center_performance \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## Related articles - [Google Merchant Center](/connectors/google-merchant-center) - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Accounts tools](/developers/accounts-tools) --- # Google Sheets tools URL: https://docs.plugsight.app/developers/sheets-tools The Google Sheets tools in the developer API, with every argument: read a spreadsheet's tabs, named ranges and values. **Needs:** A Google Sheets connection. 2 tools, all read-only. > [!IMPORTANT] > Google is still reviewing the permission this connector needs. Until it approves it, Plugsight offers Google Sheets to Plugsight admins only, so for most people it isn't in the **Connector catalog** yet and these tools don't appear. See [Google Sheets](/connectors/google-sheets). These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. Open a spreadsheet by its link or id. The optional `account` argument takes a Google Sheets connection `id` from [`list_accounts`](/developers/accounts-tools); leave it out when the MCP server has only one. | Tool | What it does | Kind | | ------------------------------------- | ------------------- | ---- | | [`sheets_get_info`](#sheets_get_info) | Spreadsheet details | Read | | [`sheets_read`](#sheets_read) | Read a spreadsheet | Read | Every tool here only reads: none of them changes anything in Google Sheets, so none needs `confirm`. The example requests fill in only the required arguments, with placeholder values. ## sheets_get_info **Spreadsheet details** · Read A Google Sheets spreadsheet's title, tabs (with their size) and named ranges. Call it before sheets_read to pick a tab. | Argument | Type | Required | What it is | | ------------- | ------ | -------- | ------------------------------------------------------------------------------- | | `spreadsheet` | string | Yes | The spreadsheet's link (from the browser's address bar) or its id | | `account` | string | No | Google Sheets connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/sheets_get_info \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"spreadsheet": "…"}' ``` ## sheets_read **Read a spreadsheet** · Read Reads values as shown in Google Sheets from a tab or range, e.g. "Sales", "Sales!A1:F200" or a named range. With header true, the first row becomes the column names. | Argument | Type | Required | What it is | | ------------- | ------- | -------- | ------------------------------------------------------------------------------------------ | | `spreadsheet` | string | Yes | The spreadsheet's link (from the browser's address bar) or its id | | `range` | string | No | Tab name or A1 range, e.g. "Sales" or "Sales!A1:F200". Default: the first tab | | `header` | boolean | No | Treat the first row as column names. Default `true`. | | `max_rows` | integer | No | Most rows to return. From 1 to 5,000. Default `500`. | | `formulas` | boolean | No | Return each cell's formula (e.g. =SUM(B2:B9)) instead of its shown value. Default `false`. | | `account` | string | No | Google Sheets connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/sheets_read \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"spreadsheet": "…"}' ``` ## Related articles - [Google Sheets](/connectors/google-sheets) - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Accounts tools](/developers/accounts-tools) --- # Google Docs tool URL: https://docs.plugsight.app/developers/docs-tools The docs_read tool in the developer API, with every argument: read a Google Doc as text, with headings, lists and tables. **Needs:** A Google Docs connection. 1 tool, all read-only. > [!IMPORTANT] > Google is still reviewing the permission this connector needs. Until it approves it, Plugsight offers Google Docs to Plugsight admins only, so for most people it isn't in the **Connector catalog** yet and these tools don't appear. See [Google Docs](/connectors/google-docs). These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. Open a document by its link or id. The optional `account` argument takes a Google Docs connection `id` from [`list_accounts`](/developers/accounts-tools); leave it out when the MCP server has only one. | Tool | What it does | Kind | | ------------------------- | ----------------- | ---- | | [`docs_read`](#docs_read) | Read a Google Doc | Read | Every tool here only reads: none of them changes anything in Google Docs, so none needs `confirm`. The example requests fill in only the required arguments, with placeholder values. ## docs_read **Read a Google Doc** · Read Reads a Google Docs document as text, keeping headings, bullet lists and tables (every tab of a tabbed document). Open it by its link. | Argument | Type | Required | What it is | | ----------- | ------- | -------- | ---------------------------------------------------------------------------------------- | | `document` | string | Yes | The document's link (from the browser's address bar) or its id | | `max_chars` | integer | No | Longest text returned; longer documents are cut. From 1,000 to 500,000. Default `60000`. | | `account` | string | No | Google Docs connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/docs_read \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"document": "…"}' ``` ## Related articles - [Google Docs](/connectors/google-docs) - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Accounts tools](/developers/accounts-tools) --- # Google Forms tools URL: https://docs.plugsight.app/developers/forms-tools The Google Forms tools in the developer API, with every argument: read a form's questions, its responses and totals. **Needs:** A Google Forms connection. 3 tools, all read-only. > [!IMPORTANT] > Google is still reviewing the permission this connector needs. Until it approves it, Plugsight offers Google Forms to Plugsight admins only, so for most people it isn't in the **Connector catalog** yet and these tools don't appear. See [Google Forms](/connectors/google-forms). These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. Open a form by its edit link (from Google Forms, not the link people fill in) or its id. The optional `account` argument takes a Google Forms connection `id` from [`list_accounts`](/developers/accounts-tools); leave it out when the MCP server has only one. | Tool | What it does | Kind | | ------------------------------------- | ------------------------------- | ---- | | [`forms_get`](#forms_get) | Google Form details | Read | | [`forms_responses`](#forms_responses) | Google Form responses | Read | | [`forms_summary`](#forms_summary) | Summarise Google Form responses | Read | Every tool here only reads: none of them changes anything in Google Forms, so none needs `confirm`. The example requests fill in only the required arguments, with placeholder values. ## forms_get **Google Form details** · Read A Google Form's title, description, fill-in link and every question with its type and options. | Argument | Type | Required | What it is | | --------- | ------ | -------- | ------------------------------------------------------------------------------ | | `form` | string | Yes | The form's edit link (from Google Forms, not the fill-in link) or its id | | `account` | string | No | Google Forms connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/forms_get \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"form": "…"}' ``` ## forms_responses **Google Form responses** · Read A form's responses as a table, newest first: when it was submitted, the respondent's email when the form collects it, and one column per question. | Argument | Type | Required | What it is | | --------- | ------- | -------- | ------------------------------------------------------------------------------ | | `form` | string | Yes | The form's edit link (from Google Forms, not the fill-in link) or its id | | `since` | string | No | Only responses submitted on or after this date, YYYY-MM-DD | | `limit` | integer | No | Most responses to return. From 1 to 5,000. Default `200`. | | `account` | string | No | Google Forms connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/forms_responses \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"form": "…"}' ``` ## forms_summary **Summarise Google Form responses** · Read Totals per question: how many chose each option of choice, scale and rating questions, and how many answered the others. Use forms_responses to read the written answers. | Argument | Type | Required | What it is | | --------- | ------ | -------- | ------------------------------------------------------------------------------ | | `form` | string | Yes | The form's edit link (from Google Forms, not the fill-in link) or its id | | `since` | string | No | Only responses submitted on or after this date, YYYY-MM-DD | | `account` | string | No | Google Forms connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/forms_summary \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"form": "…"}' ``` ## Related articles - [Google Forms](/connectors/google-forms) - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Accounts tools](/developers/accounts-tools) --- # Google Meet tools URL: https://docs.plugsight.app/developers/meet-tools The Google Meet tools in the developer API, with every argument: list the meetings you organised and read transcripts. **Needs:** A Google Meet connection. 2 tools, all read-only. > [!IMPORTANT] > Google is still reviewing the permission this connector needs. Until it approves it, Plugsight offers Google Meet to Plugsight admins only, so for most people it isn't in the **Connector catalog** yet and these tools don't appear. See [Google Meet](/connectors/google-meet). These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. The optional `account` argument takes a Google Meet connection `id` from [`list_accounts`](/developers/accounts-tools); leave it out when the MCP server has only one. Only meetings where transcription was turned on have a transcript. | Tool | What it does | Kind | | --------------------------------------------- | ---------------------------- | ---- | | [`meet_list_meetings`](#meet_list_meetings) | List Google Meet meetings | Read | | [`meet_get_transcript`](#meet_get_transcript) | Get a Google Meet transcript | Read | Every tool here only reads: none of them changes anything in Google Meet, so none needs `confirm`. The example requests fill in only the required arguments, with placeholder values. ## meet_list_meetings **List Google Meet meetings** · Read Google Meet meetings you organised in a period, newest first: start, length, who joined, and whether a transcript exists. | Argument | Type | Required | What it is | | ------------- | ------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | `date_preset` | string | No | Used when date_from/date_to aren't given. Default last_7d. One of: `last_7d`, `last_28d`, `last_30d`, `last_90d`, `this_month`, `last_month`. | | `date_from` | string | No | YYYY-MM-DD, or "today", "yesterday", "NdaysAgo" (e.g. "28daysAgo") | | `date_to` | string | No | YYYY-MM-DD, or "today", "yesterday", "NdaysAgo" (e.g. "28daysAgo") | | `limit` | integer | No | Most meetings to return. From 1 to 100. Default `25`. | | `account` | string | No | Google Meet connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/meet_list_meetings \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## meet_get_transcript **Get a Google Meet transcript** · Read The transcript of one meeting as "Name: words" lines, with who joined. Only meetings where transcription was turned on have one. Use it to summarise decisions and action items. | Argument | Type | Required | What it is | | ----------- | ------- | -------- | ----------------------------------------------------------------------------------------- | | `meeting` | string | Yes | Meeting id from meet_list_meetings | | `max_chars` | integer | No | Longest transcript returned; longer ones are cut. From 1,000 to 500,000. Default `80000`. | | `account` | string | No | Google Meet connection id from list_accounts (optional when there's only one) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/meet_get_transcript \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"meeting": "…"}' ``` ## Related articles - [Google Meet](/connectors/google-meet) - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Accounts tools](/developers/accounts-tools) --- # Google Drive tools URL: https://docs.plugsight.app/developers/drive-tools The Google Drive tools in the developer API, with every argument: search Drive, read files and list shared drives. Coming soon. **Needs:** A Google Drive connection (not offered yet). 3 tools, all read-only. > [!IMPORTANT] > Google Drive is **coming soon**. Google treats full Drive access as a restricted permission that needs a security audit before an app can offer it to everyone, so Google Drive isn't in the **Connector catalog** yet and these tools don't appear for any API key. They're listed here so you know what to expect. See [Google Drive](/connectors/google-drive). These tools appear in `GET /v1/tools` only when the API key's MCP server includes a connection of this kind. Call each one with `POST /v1/tools/\`, sending its arguments as a JSON object. See [Calling tools](/developers/calling-tools) for the request and response format. The optional `account` argument takes a Google Drive connection `id` from [`list_accounts`](/developers/accounts-tools); leave it out when the MCP server has only one. Drives you've hidden in Plugsight aren't listed and can't be searched or read. | Tool | What it does | Kind | | ------------------------------------------- | ------------------------ | ---- | | [`drive_search_files`](#drive_search_files) | Search Google Drive | Read | | [`drive_read_file`](#drive_read_file) | Read a Google Drive file | Read | | [`drive_list_drives`](#drive_list_drives) | List Google Drive drives | Read | Every tool here only reads: none of them changes anything in Google Drive, so none needs `confirm`. The example requests fill in only the required arguments, with placeholder values. ## drive_search_files **Search Google Drive** · Read Finds files in Google Drive (My Drive and shared drives) by words inside them, name, type, date, owner or folder. Use drive_read_file to read one. Newest first unless searching by text. | Argument | Type | Required | What it is | | ----------------- | ------- | -------- | ------------------------------------------------------------------------------------------ | | `text` | string | No | Words that appear in the file's content or name | | `name` | string | No | Part of the file name | | `type` | string | No | Type of file. One of: `document`, `spreadsheet`, `presentation`, `pdf`, `folder`, `image`. | | `modified_after` | string | No | YYYY-MM-DD | | `modified_before` | string | No | YYYY-MM-DD | | `owner` | string | No | Owner's email address | | `folder_id` | string | No | Only files directly inside this folder | | `drive_id` | string | No | A shared drive id from drive_list_drives, or "my-drive" | | `limit` | integer | No | Most results to return. From 1 to 100. Default `25`. | | `page_token` | string | No | next_page_token from a previous call | | `account` | string | No | Connection id from list_accounts (optional when there's only one of this type) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/drive_search_files \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## drive_read_file **Read a Google Drive file** · Read Reads a file as text: Google Docs, Sheets (every sheet) and Slides, PDFs, Word, Excel, PowerPoint, CSV and text files. | Argument | Type | Required | What it is | | ----------- | ------- | -------- | ------------------------------------------------------------------------------------ | | `file_id` | string | Yes | File id from drive_search_files | | `max_chars` | integer | No | Longest text returned; longer files are cut. From 1,000 to 200,000. Default `40000`. | | `account` | string | No | Connection id from list_accounts (optional when there's only one of this type) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/drive_read_file \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{"file_id": "…"}' ``` ## drive_list_drives **List Google Drive drives** · Read My Drive and the shared drives this connection can use. Use a drive's id to search inside it. | Argument | Type | Required | What it is | | --------- | ------ | -------- | ------------------------------------------------------------------------------ | | `account` | string | No | Connection id from list_accounts (optional when there's only one of this type) | Example request: ```bash curl -X POST https://app.plugsight.app/v1/tools/drive_list_drives \ -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' ``` ## Related articles - [Google Drive](/connectors/google-drive) - [Calling tools](/developers/calling-tools) - [Errors](/developers/errors) - [Accounts tools](/developers/accounts-tools) --- # Security & privacy URL: https://docs.plugsight.app/security How Plugsight protects your logins, what it stores and never keeps, what it asks Google and Microsoft for, and how to report an issue. Your connected accounts hold your business. This section explains exactly how Plugsight treats them. ## In short - **Your logins are encrypted.** Connection credentials (sign-in tokens, app passwords, API tokens) are encrypted with AES-256-GCM before they're saved. They never reach your AI. - **Your data is read live, not stored.** Emails, tickets and reports are fetched when you or your AI ask, passed to your AI app, and not kept. - **Your AI reads until you allow more.** Changes are off for every account until you switch them on, and each one needs your approval in the chat. - **You see everything.** **Activity** records every sign-in, settings change and AI request, without email bodies or report contents, for one year. - **Each account is isolated.** One customer's AI apps can never reach another customer's accounts. - **You can cut access at any time**, in Plugsight or at the provider. ## In this section - [How credentials are stored](/security/credentials): encryption, password hashing, keys and sessions. - [What Plugsight stores and logs](/security/data-handling): what's kept, what isn't, and for how long. - [Permissions Plugsight asks Google and Microsoft for](/security/provider-permissions): each permission, and why. - [Remove Plugsight's access](/security/remove-access): in Plugsight, in your AI apps and at Google, Microsoft and other providers. - [Security issues and the privacy policy](/security/contact-security): how to tell us, and where to find the privacy policy. --- # How credentials are stored URL: https://docs.plugsight.app/security/credentials How Plugsight encrypts your connection logins with AES-256-GCM, hashes passwords and keys, and protects your sessions. ## Connection credentials When you connect an account, Plugsight keeps what it needs to reach that account for you: - **Sign-in tokens** from Google, Microsoft, Zendesk and other services you connect by signing in. Plugsight never sees your password for those services. - **App passwords** you create at your email provider (for Gmail with an app password, iCloud, Yahoo, AOL, Zoho and other email). - **API keys or tokens** for services that use them, such as Mailchimp, WooCommerce and Magento. These are encrypted with **AES-256-GCM** before they're saved to the database. Each one is encrypted with a fresh random value, and the encryption also detects any tampering. The encryption key is kept apart from the database. Credentials are only decrypted on Plugsight's servers, at the moment a request needs them. They never leave Plugsight's servers and are never sent to your AI app. When you remove a connection, its stored credentials are deleted straight away. Deleting your account deletes all of them. ## Your Plugsight password Your Plugsight password is never stored. Plugsight keeps only a one-way scrambled form of it (a hash, made with scrypt), which can check a password but can't be turned back into it. Passwords must be at least 10 characters. If you sign in with Google, Microsoft or an email link, Plugsight has no password for you at all. ## MCP server API keys An API key is shown once, when you create it. Plugsight stores only a hash of it, so nobody can show it again, including Plugsight. If you lose a key, regenerate it. See [API keys](/mcp-servers/api-keys). ## AI app access When you click **Allow access** for an AI app, Plugsight gives that app its own access to one MCP server: - The access works only for the server you approved. - It's short-lived and renewed automatically while the app keeps using it. Unused for 90 days, it expires and the app must sign in again. - Plugsight stores only hashes of these tokens. - **Disconnect all AI apps** on a server ends every app's access to it straight away. ## Sign-in sessions and links - Your browser session is kept in a secure cookie. Plugsight stores only a hash of it. A session lasts up to 30 days. - Changing or resetting your password ends every browser session. - Emailed sign-in links work once and expire in 20 minutes; reset links expire in 1 hour; confirmation links in 2 days. - Too many wrong passwords block sign-in for 15 minutes, and the attempts appear in **Activity**. ## In transit All traffic to and from Plugsight is encrypted with TLS. ## Related articles - [What Plugsight stores and logs](/security/data-handling) - [Remove Plugsight's access](/security/remove-access) - [Change or reset your password](/account/password) --- # What Plugsight stores and logs URL: https://docs.plugsight.app/security/data-handling Your emails, tickets and reports are read live and not stored. Here is exactly what Plugsight keeps, what it logs, and for how long. ## Read live, not stored When you or your AI ask a question, Plugsight reads what's needed from the connected account at that moment, passes it to your AI app, and doesn't keep it. That covers emails and attachments, helpdesk tickets, marketing and analytics reports, files, calendar events, contacts and store orders. The exceptions are kept briefly in memory, never in the database, so Plugsight doesn't have to ask the provider every time: lists of what a login reaches (which sites, properties, ad accounts, drives and calendars), for up to 15 minutes, and Outlook and iCloud contact lists, for up to 5 minutes so looking people up is quick. ## What Plugsight stores | What | Why | How long | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ------------------------------------------------------ | | **Your account**: name, email address, a hashed password if you set one, and which Google or Microsoft identity you sign in with | To sign you in | Until you delete your account | | **Connections**: each account's email or login name, its label, and its encrypted credentials | To reach the account for you | Until you remove the connection or delete your account | | **Settings**: your MCP servers and which accounts each reaches, account switches, pauses, the daily email limit, and sites or accounts you hid | So Plugsight does what you set | Until you change them or delete your account | | **Activity records**: see below | So you can see what happened, and for security | One year | | **Emails sent to you**: which account and billing emails Plugsight has sent you, and when (not their content) | So each one goes out only once | Kept as a record | | **Billing**: your plan, billing period and renewal date. Card details are held by Stripe; Plugsight never sees or stores them | To give you your plan | Until you delete your account | | **Where you first came from**: the referring site, campaign tags and first page of your first visit, if you allowed analytics cookies (and the ad click identifier, only if you chose **Accept all**) | To know which channels bring people to Plugsight | Until you delete your account; saved once, at sign-up | ## What's logged in Activity Each entry records: - When it happened, and the IP address and browser it came from. - What happened, as a one-line summary. - Who did it: you, or which AI app, through which MCP server. - The result: **Succeeded**, **Blocked** or **Failed**, with the reason. - For AI tool calls: which tool was used and its settings (for example the account, a search query, a ticket number, email recipients and subject). What's never logged: **email bodies, attachments and report contents**. Activity shows what was done, never the content. For emails your AI sends, drafts or tries to send, Plugsight also keeps the recipients and subject, which is how the daily email limit is counted. Activity entries are deleted automatically after one year. If you delete your account, its entries are kept until they reach one year old, with only the email address the account had, for security. See [Activity log](/permissions/activity). ## Usage analytics Plugsight uses PostHog, hosted in the EU, to see how the website, these docs and the app are used, and to catch errors. - **What it gets:** pages viewed, sign-ups, which kind of account you connect (for example Gmail, never its contents), MCP servers created, AI apps connected, plan changes and payments (amount and currency, never card details), each request to Plugsight's servers (which page or endpoint, whether it worked and how long it took, never what was sent), and each AI tool call's name, how long it took, whether it worked, which AI model made it, the options it chose (such as page size, sort order or which fields a search filtered on, never the words, names or values searched for) and how much came back (size and number of items, never the content). Ask AI sends the model used, its token counts and timing, and your 👍 or 👎. - **What your AI app may add:** with each tool call, your AI app may send a short description of what you asked it to do, such as "finding a customer's last order". Plugsight removes email addresses from it before it's stored. - **What it never gets:** your emails, tickets, orders, files or messages, what your AI app sent to a tool or got back from it, the words you search for in these docs, or what you type into Ask AI. - **Who you are to it:** an internal account number, never your name or email address. Events Plugsight records on its own servers always carry it, whatever your cookie choice: signing up and in, adding or removing a connection, each AI tool call, Ask AI questions while you're signed in, and plan changes. Your visits in the browser (the website, these docs and the app's pages) carry it only if you allow analytics cookies; if you decline, they're counted without cookies and aren't linked to you. Error reports have email addresses, tokens and keys removed before they're sent. - **Session replay:** the website can be recorded for visitors who allow analytics cookies, with everything typed into forms hidden. In the app, only the sign-up and sign-in screens, and during your first week the setup screens (adding a connection, creating an MCP server, connecting an AI app), with every form field hidden and images blocked. These docs and the rest of the app are never recorded. - **Your choice:** the cookie choice is shared by the website, these docs and the app. Choose **Decline**, **Analytics only** or **Accept all** from **Cookie settings** at the bottom of any website page or at the bottom of the left-hand menu here. If you decline, visits are counted without cookies and can't be linked to you. - **Ads:** only with **Accept all**, Plugsight tells Google, Meta or LinkedIn when an ad led to a sign-up or a paid plan, with your email address only in hashed form. Changing your choice to **Analytics only** or **Decline** stops this. ## What your AI app receives Your AI app (Claude, ChatGPT and others) receives only the data needed to answer your request. Once it's there, that AI provider's own terms and privacy policy apply. Plugsight recommends using an AI app or plan whose settings don't use your conversations for model training. Plugsight itself doesn't use your data to train AI models and doesn't sell it. Your connected accounts' data is never used for advertising. ## Each account is separate Each Plugsight user's connections, MCP servers and settings are separate. An AI app only reaches the accounts in the one MCP server it was approved for. One customer's AI apps can never reach another customer's accounts. ## Who works with Plugsight Plugsight uses these providers to run the service: Railway (hosting and database), Resend (service emails), Stripe (payments), Anthropic (writing [Ask AI](/get-started/ask-ai) answers from these docs; it never receives data from your connected accounts) and PostHog (usage analytics and error tracking, as above). The services you connect, such as Google, Microsoft and Zendesk, provide the data you ask for. The full list is in the [privacy policy](https://plugsight.app/privacy). ## Related articles - [How credentials are stored](/security/credentials) - [Activity log](/permissions/activity) - [Security issues and the privacy policy](/security/contact-security) --- # Permissions Plugsight asks Google and Microsoft for URL: https://docs.plugsight.app/security/provider-permissions Each permission Plugsight requests when you sign in or connect a Google or Microsoft service, and why it needs it. Each Google or Microsoft service is a separate connection that you choose to add, and each one asks only for the access that service needs. Connecting one never adds permissions for another. ## Signing in to Plugsight | Provider | Asks for | Why | | --- | --- | --- | | **Continue with Google** | Your name, email address and basic profile | To know who you are. Nothing else is shared. | | **Continue with Microsoft** | Your name, email address and basic profile | The same. | Signing in doesn't connect Gmail, Outlook or anything else. ## Google connections | Connection | Permission | Why | | --- | --- | --- | | **Gmail** (Google sign-in) | Full access to Gmail | Plugsight reads, drafts and sends mail using the standard mail protocols (IMAP and SMTP), and this is the only Google permission that allows them. Sending still needs the account's switch on and your approval in the chat. | | **Google Search Console** | View your Search Console data (read-only) | Your sites' search performance, URL inspection and sitemaps. | | **Google Analytics 4** | View your Analytics data (read-only) | Your GA4 properties and their reports. | | **Google Ads** | Manage your Google Ads accounts | Your ad accounts and performance reports. Google only offers this permission with edit rights; Plugsight uses it for reports only and never creates, changes or deletes anything in your Ads accounts. | | **Google Calendar** | View your calendars (read-only). Once Google approves it, also optionally view and edit events | Your events and free time. The edit permission is only for booking, moving and cancelling events after you approve each one. Until Google approves it, Plugsight doesn't ask for it and Google Calendar connections are read-only; after that, you can untick it when Google asks and the connection stays read-only. | | **Google Contacts** | View your contacts and "other contacts" (read-only) | To look people up. | | **Google Drive** | View your Drive files (read-only) | To find and read your documents. | | **Google Sheets** | View your spreadsheets (read-only) | Only a spreadsheet you or your AI give the link to. | | **Google Docs** | View your documents (read-only) | Only a document you or your AI give the link to. | | **Google Forms** | View your forms and their responses (read-only) | Only a form you or your AI give the link to. | | **Google Meet** | View your meetings (read-only) | Meetings you organise and their transcripts. | | **Google Tag Manager** | View your Tag Manager containers (read-only) | To audit your tracking set-up. | | **YouTube** | View your YouTube account (read-only) | Your channels, videos and analytics. | | **Google Merchant Center** | Manage your product listings | Your products, their status and Shopping performance. Google only offers this permission with edit rights; Plugsight uses it for reading only. | Some Google connections show as **Coming soon** in the catalog while Google reviews Plugsight's access to them. Plugsight's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. Plugsight doesn't use Google data for advertising, doesn't sell it, and doesn't use it to train AI models. ## Microsoft connections | Connection | Permissions | Why | | --- | --- | --- | | **Outlook / Microsoft 365 mail** | Read your mail, read and write your mail, send mail as you, read your profile, and keep access | Reading and searching email; writing drafts and organising email; sending, only when the account's switch is on and you approve each email. | | **Outlook Calendar** | Read and write your calendars, read your profile, and keep access | Your events and free time; booking, moving and cancelling events after you approve each one. | | **Outlook Contacts** | Read your contacts, read your profile, and keep access | To look people up. | | **Microsoft Advertising** | Manage your Microsoft Advertising accounts, and keep access | Your ad accounts and performance reports. Plugsight only reads reports. | "Keep access" (offline access) lets Plugsight reach the account when you ask, without you signing in each time. If your organisation restricts apps, Microsoft may say an administrator must approve Plugsight. Ask your IT admin, or if you are the admin, sign in and consent on behalf of the organisation. ## Related articles - [Read-only connectors](/permissions/read-only-connectors) - [Remove Plugsight's access](/security/remove-access) - [How credentials are stored](/security/credentials) --- # Remove Plugsight's access URL: https://docs.plugsight.app/security/remove-access Cut off access in Plugsight, in your AI apps, or at Google, Microsoft and other providers - each works on its own. You can cut access at several levels. Each one works on its own, so use whichever fits. ## Stop changes, keep reading On **Permissions**, click **Pause everything**. Your AI can still read, but can't send or change anything until you click **Resume**. See [Pause changes](/permissions/pause). ## Cut off AI apps | To cut off | Do this | | --- | --- | | Every AI app using one MCP server | On the server's page, **Danger zone** → **Disconnect all AI apps**. See [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete). | | A tool using an API key | On the server's page, **API key** → **Revoke key** or **Regenerate key**. See [API keys](/mcp-servers/api-keys). | | One AI app | Remove the Plugsight connector in that AI app. | | Everything through one server, for good | **Delete server**. | ## Remove an account from Plugsight 1. Open **Connections**. 2. Click **Remove** next to the account. 3. Click **Remove** to confirm. The stored login for that account is deleted straight away. Nothing in the account itself is touched. To use it again, connect it again from **Add connection**; you'll need to sign in again. ## Remove access at the provider You can also revoke Plugsight at the service itself. Plugsight then can't reach the account, even though it's still listed on **Connections**. Plugsight notices, marks the connection as needing reconnecting, and emails you "Reconnect [account] to keep using it with your AI". Remove it from **Connections** too, so it doesn't stay listed. - **Google:** in your Google Account, open the third-party access page (myaccount.google.com/permissions) and remove Plugsight. - **Microsoft:** remove Plugsight from the apps with access in your Microsoft account. On a work account, your IT admin can also remove it. - **App passwords** (Gmail with an app password, iCloud, Yahoo, AOL, Zoho and other email): delete the app password you made for Plugsight at your email provider. Your normal password isn't affected. - **API keys and tokens** (Mailchimp, Magento and similar): delete or disable the key at the service. Changing your password at an email provider can also end Plugsight's access, depending on the provider. ## Delete everything Deleting your Plugsight account removes all your connections, stored logins, MCP servers and settings, and cancels any paid plan. See [Delete your account](/account/delete-account). It doesn't change your accounts at Google, Microsoft and elsewhere, so you may also want to remove Plugsight's access there, as above. ## Related articles - [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete) - [Delete your account](/account/delete-account) - [Permissions Plugsight asks Google and Microsoft for](/security/provider-permissions) --- # Security issues and the privacy policy URL: https://docs.plugsight.app/security/contact-security How to tell Plugsight about a security problem or suspicious activity, what to do first, and where to read the privacy policy. ## Tell us about a security problem If you think you've found a security problem in Plugsight, email [info@plugsight.app](mailto:info@plugsight.app). Please include: - What you found, and where (a page, an address, or a step in the app). - How to reproduce it, step by step. - What someone could do with it. Please don't access other people's data, and give us time to fix the problem before telling anyone else. ## If you think someone got into your account Act straight away, in this order: 1. **Stop changes:** on **Permissions**, click **Pause everything**. 2. **Change your Plugsight password** under **Settings**. This signs out every browser session. See [Change or reset your password](/account/password). 3. **Cut off AI apps:** on each MCP server, use **Disconnect all AI apps**, and revoke or regenerate any API key. See [Disconnect AI apps or delete a server](/mcp-servers/disconnect-and-delete). 4. **Check Activity** for sign-ins, settings changes and AI requests you don't recognise. See [Activity log](/permissions/activity). 5. **Email info@plugsight.app** so we can help secure your account. If you got a "Your Plugsight password was changed" email you didn't expect, click **It wasn't me: reset my password** in that email, then follow the steps above. ## Privacy policy The full privacy policy, including what Plugsight collects, how Google user data is handled, the providers we use and your rights, is at [plugsight.app/privacy](https://plugsight.app/privacy). To ask to access, correct, delete or receive a copy of your personal data, do it in the app where you can, or email info@plugsight.app. ## Related articles - [What Plugsight stores and logs](/security/data-handling) - [How credentials are stored](/security/credentials) - [Remove Plugsight's access](/security/remove-access) --- # Frequently asked questions URL: https://docs.plugsight.app/faq Short answers to the questions people ask most about Plugsight, grouped by topic, each with a link to the full article. Short answers to the questions people ask most, from the website and the app. Each answer links to the full article. ## Topics - [General](/faq/general): what Plugsight is, which AI apps work, what you can connect and ask, and how long setup takes. - [Connecting accounts](/faq/connecting-accounts): app passwords, Google and Microsoft sign-in messages, several accounts of one kind, hiding sites and reconnecting. - [AI apps](/faq/ai-apps): turning Plugsight on in a chat, refreshing the tools list, and what to do when your AI can't see an account. - [Safety and permissions](/faq/safety-and-permissions): what your AI can change, approvals, Pause, the daily email limit, Activity and your data. - [Plans and billing](/faq/plans-and-billing): the Free plan, what counts as a connection, changing or cancelling, and discounts. - [Developer API](/faq/developer-api): who can use it, what it reaches, keys and caching. ## The five questions asked most ### What is Plugsight? A secure link between your own accounts (email, ads, analytics, helpdesk, calendars, stores and more) and AI apps like Claude and ChatGPT. You connect each account once, then add one Plugsight link to your AI app. See [What is Plugsight?](/get-started). ### Do you store my emails or ad data? No. Data is read live when your AI asks, and isn't kept. Plugsight stores your connection credentials, encrypted, and your settings. See [What Plugsight stores and logs](/security/data-handling). ### Can my AI change things in my accounts? Only if you allow it, and only after you approve each change in the chat. Many connectors only ever read. See [How changes are allowed](/permissions/how-changes-are-allowed). ### I connected an account, but my AI can't see it Check the account is in your MCP server, then refresh the tools list in your AI app if it's a new type of account. See [Your AI can't see an account](/troubleshooting/ai-cant-see-account). ### Is there a free plan? Yes: two connections and one MCP server, with no credit card. See [Plans](/get-started/plans). ## Didn't find your answer? Search these docs, or email [info@plugsight.app](mailto:info@plugsight.app). --- # General questions URL: https://docs.plugsight.app/faq/general What Plugsight is, which AI apps and accounts it works with, what you can ask, and how long setup takes. ## What is Plugsight? A secure link between your own accounts and your AI app. You connect tools like Google Ads, Search Console, GA4, Gmail, Outlook, Zendesk, calendars and your online store once, then add one Plugsight link to Claude, ChatGPT or another MCP app. Your AI then answers with your real data instead of general advice. More: [What is Plugsight?](/get-started) and [How Plugsight works](/get-started/how-it-works). ## What is an MCP server? Your AI link: a private web address that lets an AI app use the accounts you choose, and nothing else. You can make several, for example one per client, each reaching different accounts. For the developer API, an MCP server is the project that a key belongs to. More: [MCP servers](/mcp-servers) and [Use several MCP servers](/mcp-servers/multiple-servers). ## Which AI apps work with Plugsight? - **Claude** on the web, desktop and phone, on any Claude plan. - **ChatGPT** on Business, Enterprise and Edu. ChatGPT Pro can connect, but read-only. The ChatGPT free plan isn't eligible. - **Claude Code**, **Cursor**, **VS Code** and other apps that support remote MCP servers. Your AI app's subscription is separate from your Plugsight plan. More: [Connect AI apps](/ai-apps). ## What can I connect? Email (Gmail, Outlook, iCloud, Yahoo and almost any other mailbox), Zendesk, marketing and analytics (Google Ads, Microsoft Ads, Meta Ads, LinkedIn Ads, Search Console, GA4 and Bing Webmaster Tools), calendars, contacts, online stores (WooCommerce and Magento) and Mailchimp. Every MCP server also has a built-in PageSpeed check with nothing to connect. More: [Connectors](/connectors). ## What can I ask? Anything your connected accounts can answer, in plain language. For example: "Which search terms wasted money last month?", "What are customers complaining about this week?" or "When am I free on Thursday?". Each connector article has example questions. More: [Questions to try first](/get-started/first-questions). ## Can my AI combine data from different tools? Yes. Every account in your MCP server is available in the same chat, so your AI can compare Google Ads spend with Search Console rankings, or store revenue with campaign results. More: [How your AI analyses marketing data](/connectors/marketing-data). ## What are the ready-made analyses? Deep dives for common questions, such as wasted ad spend, search terms worth scaling, paid and organic overlap, and period comparisons. They let a short question get a full answer. They're on the Pro and Agency plans. More: [How your AI analyses marketing data](/connectors/marketing-data). ## Do I need to write code or know what MCP is? No. You sign in to each account, or paste a password or key that the connect page walks you through, then add one link to your AI app. "MCP server" is only the name the app uses for your AI link. More: [Quick start](/get-started/quick-start). ## How long does setup take? About five minutes: connect an account, create an MCP server, and add it to your AI app. More: [Quick start](/get-started/quick-start). ## Does it replace my dashboards? It sits alongside them. Dashboards show what you planned to track. Your AI can answer the questions you didn't plan for, from the same data. ## Do I need an analyst to use it? No. Ask in plain language, like "Which campaigns wasted money last month?", and your AI pulls the numbers and explains them. ## Why use Plugsight if a tool has its own AI connector? Many tools have none, and some official ones only do part of the job: Mailchimp's own connector builds campaigns but doesn't read their results. Built-in connectors also often allow one account per app, while Plugsight connects as many as your plan allows. And Plugsight puts all your tools in one place, so your AI can compare them in one chat. More: [Several accounts per service](/ai-apps/multiple-accounts). ## Can an agency keep each client separate? Yes. Create one MCP server per client, each reaching only that client's accounts, and add the right one to each chat or team. You can also hide single sites, ad accounts and calendars. More: [Use several MCP servers](/mcp-servers/multiple-servers). ## Can a support team use it safely? Yes. Reading tickets is always on. Replies and ticket changes are off until you allow them, and each one needs approval in the chat. Every AI request is listed in **Activity**. More: [Zendesk](/connectors/zendesk) and [Activity log](/permissions/activity). ## Can I ask for a new connector? Yes. Email [info@plugsight.app](mailto:info@plugsight.app) with the tool and what you'd like your AI to answer from it. Requests decide what gets built next. ## Where do I get help? Search these docs, or email [info@plugsight.app](mailto:info@plugsight.app). Include the exact message you saw and roughly when it happened. **Activity** in the app shows the exact error for every AI request, which often says what to fix. ## Related articles - [Connecting accounts FAQ](/faq/connecting-accounts) - [AI apps FAQ](/faq/ai-apps) - [Glossary](/get-started/glossary) --- # Connecting accounts URL: https://docs.plugsight.app/faq/connecting-accounts Answers about connecting accounts to Plugsight - app passwords, Google and Microsoft messages, several accounts, hiding sites and reconnecting. ## Which method will my account use? - **Outlook / Microsoft 365, Microsoft Advertising and Zendesk:** you sign in and click allow. - **Google services** (Search Console, GA4, Google Ads, Calendar, Contacts): you sign in with Google and tick the permission. - **Gmail, iCloud, Yahoo, AOL, Zoho, Fastmail and most other mailboxes:** you create an *app password* at your provider (the connect page links straight to where you make one) and paste it. - **Stores and Mailchimp:** WooCommerce asks you to approve Plugsight in WordPress or paste keys, Magento needs four keys from an integration you create, and Mailchimp needs an API key. - **Anything else:** type your email address and Plugsight finds the settings. More: [Connectors](/connectors) and [Connect any email address](/connectors/connect-any-email). ## What is an app password? A separate password your email provider creates for Plugsight. Your real password stays private, and you can delete the app password at your provider any time to cut access. More: [App password problems](/troubleshooting/app-passwords). ## My company email uses Google Workspace or Microsoft 365. Which do I pick? Type your address in the box **Or type an email address to detect its provider** in the **Connector catalog**, and click **Detect**. Plugsight checks your domain and sends you to the right page. If your mail is with Microsoft 365, use Outlook, even if you also have a Google account on that address. More: [Connect any email address](/connectors/connect-any-email). ## Google says "Google hasn't verified this app" Click **Advanced**, then **Go to Plugsight (unsafe)**. Google shows this while it reviews new apps; it doesn't mean anything is wrong. You'll then see the permission to tick. More: [Google Analytics 4](/connectors/google-analytics-4) shows the full sign-in steps. ## Microsoft says an administrator must approve Your company restricts which apps can connect. Ask your IT administrator to approve Plugsight. If you are the admin, sign in and tick **Consent on behalf of your organisation** on Microsoft's permission screen. More: [Outlook / Microsoft 365](/connectors/outlook) and [Connection errors](/troubleshooting/connection-errors). ## Do I need admin rights? Only for some tools. Some companies require IT approval before anyone can sign in to an app with Microsoft. The connect page tells you when. ## Do I need my own Google Ads or Microsoft developer token? No. You sign in with your own Google or Microsoft account, and Plugsight handles the API access. More: [Google Ads](/connectors/google-ads). ## Can I connect more than one account of the same type? Yes, as many as your plan allows. Connect two Gmail inboxes, five Google Ads logins or three Zendesk accounts, and your AI can search across all of them in one question. One Google Ads, Analytics, Search Console or Microsoft Advertising login brings every account it can see, including client accounts under a Google Ads manager (MCC). More: [Several accounts per service](/ai-apps/multiple-accounts). ## Does each account need its own sign-in? Each separate login does: a second Gmail inbox is its own connection. A marketing login brings every site, property or ad account it can see in one go. More: [Several accounts per service](/ai-apps/multiple-accounts). ## Can my AI tell which account something came from? Yes. Every result says which connection it came from, and you can ask about one account by name, like "only my work inbox". Give accounts clear names on **Connections** to make this easier. More: [Several accounts per service](/ai-apps/multiple-accounts). ## Can I stop the AI seeing a particular site or ad account? Yes. On **Connections**, click **Show sites & accounts** (or **Show drives**, **Show calendars**) on the connection, and switch the item to **Hidden**. Hidden items are never used, even if your AI asks for them by name. More: [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). ## A connection says "Reconnect needed" The provider stopped accepting the login, usually because the password was changed or access was removed. Click **Reconnect** next to it and sign in again, or paste a new app password. Your AI can't use that account until you do. Connecting the same address again updates the existing connection rather than adding a second one. More: [Reconnect needed](/troubleshooting/reconnect-needed). ## Why can't I connect Google Drive, Tag Manager, YouTube or Merchant Center? Google Drive isn't offered yet: Google treats full Drive access as a restricted permission that needs a security audit first. It appears in the **Connector catalog** once that's done. Google is also still reviewing the permissions Google Tag Manager, YouTube and Google Merchant Center need, so until it approves them they're offered to Plugsight admins only. Google Sheets, Google Docs, Google Forms and Google Meet are waiting for Google's review too, and are offered to Plugsight admins only until then. More: [Google Drive](/connectors/google-drive) and [Google Tag Manager](/connectors/google-tag-manager). ## Can my AI book in Google Calendar? Not yet. Google Calendar is read-only for now: your AI can see events and find free time. To let your AI book, move and cancel meetings today, connect [Outlook Calendar](/connectors/outlook-calendar) or [iCloud Calendar](/connectors/icloud-calendar). More: [Google Calendar](/connectors/google-calendar). ## Can I still use a Zendesk API token? Only if you already have one that still works. Zendesk stopped creating new API tokens on 27 October 2026 and switches existing ones off on 30 April 2027. Use **Sign in with Zendesk** instead. More: [Zendesk](/connectors/zendesk) and [Connect Zendesk with an API token](/connectors/zendesk-api-token). ## Related articles - [Connection errors](/troubleshooting/connection-errors) - [AI apps FAQ](/faq/ai-apps) - [Plans and billing FAQ](/faq/plans-and-billing) --- # AI apps URL: https://docs.plugsight.app/faq/ai-apps Answers about using Plugsight in Claude, ChatGPT and other AI apps - turning it on, refreshing tools, and when your AI can't see an account. ## Is Plugsight switched on in my chat? - **Claude:** start a new chat, click **+** (bottom left of the message box), then **Connectors**, and make sure your server is switched on. - **ChatGPT:** start a new chat, click **+** next to the message box and select your server. Then ask directly, for example "Using Plugsight, show last week's Google Ads spend". More: [Claude on the web](/ai-apps/claude) and [ChatGPT](/ai-apps/chatgpt). ## My AI answers without using my data Plugsight probably isn't on in that chat: see the question above. If it is, name Plugsight in your question so your AI knows to use it. More: [AI app problems](/troubleshooting/ai-app-problems). ## When does my AI app need refreshing? Only when the kinds of actions change. AI apps load Plugsight's list of actions once and keep it, so refresh after you connect the **first** account of a new type (your first Zendesk or Google Analytics, say), or remove the last one. You don't need to refresh after adding a second account of a type you already have, renaming an account, turning changes on or off, changing the daily email limit or hiding sites. Plugsight shows a notice on **Overview**, **Connections** and the MCP server's page naming each AI app that needs a refresh, with its steps. It clears once that app has the new list. More: [Refresh the tools list](/ai-apps/refresh-tools). ## How do I refresh in Claude? Open [claude.ai/customize/connectors](https://claude.ai/customize/connectors) (desktop app: **Settings** → **Customize**), click your Plugsight server under **Your connectors**, click **⋯** (top right, next to **Disconnect**) and choose **Refresh tools list**. Then start a new chat. Claude can take a few minutes to pick up the change. On the Claude phone app, refresh on the web or desktop; the change reaches your phone too. More: [Refresh the tools list](/ai-apps/refresh-tools). ## How do I refresh in ChatGPT? Open [chatgpt.com/settings/plugins-settings](https://chatgpt.com/settings/plugins-settings) (**Settings** → **Plugins**) and click your Plugsight server. Scroll to **Manage app** and click **Refresh tools**. Switch on any new actions that show as off, then start a new chat. On Business and Enterprise, a workspace admin may need to refresh the connector and publish the update first. More: [Refresh the tools list](/ai-apps/refresh-tools). ## How do I refresh in Claude Code, Cursor or another app? - **Claude Code:** type `/mcp`, choose your Plugsight server, then **Reconnect**. Or restart Claude Code. - **Cursor:** in **Cursor Settings** → **Tools & MCP**, switch the server off and on. If the list is still old, run **Developer: Reload Window**, or quit and reopen Cursor. - **Other apps:** reconnect or restart the server in the app's MCP settings, then start a new chat. - **Developer API:** nothing to do. `GET /v1/tools` is always current. More: [Refresh the tools list](/ai-apps/refresh-tools). ## I can't find the refresh option Menus in AI apps move from time to time. Remove the Plugsight connector in your AI app and add it again with the same server URL, then sign in and click **Allow access**. Your accounts stay connected in Plugsight; nothing is lost. More: [Refresh the tools list](/ai-apps/refresh-tools). ## I refreshed, but the new actions still don't show Start a new chat (open chats keep the old list). In ChatGPT, check new actions are switched on. In Claude, wait a few minutes and refresh again. Then check you refreshed the right connector, and that the account is in the MCP server that connector uses. More: [Refresh the tools list](/ai-apps/refresh-tools). ## I connected a new account, but my AI can't see it Check two things, in this order: 1. **Is it in your MCP server?** Open **MCP servers** and look at **Account access**. With **Selected accounts**, accounts you connect later aren't added by themselves: tick the new one in **Edit configuration** and save, or choose **All accounts**. 2. **Does your AI app need a refresh?** Only if it's a new type of account. Then start a new chat. Ask your AI "list my Plugsight accounts" to see exactly what it can reach. More: [Your AI can't see an account](/troubleshooting/ai-cant-see-account). ## The AI says an account is unknown That account isn't in the MCP server your AI app uses, or it was removed. Add it in **Edit configuration** on the server's page (choose **All accounts**, or tick it). If you removed the last account of a type, refresh your AI app. More: [Several accounts per service](/ai-apps/multiple-accounts). ## I removed an account, but my AI still mentions it Your AI app is using the list it loaded earlier. If it was the last account of its type, refresh your AI app. Until then, asking about it returns "unknown account", and nothing is read from it. More: [Refresh the tools list](/ai-apps/refresh-tools). ## My AI uses the wrong account, or asks which one When you have several accounts of one type, name the one you mean: "in my work Gmail", "for Bright Dental's Google Ads". Give accounts clear names on **Connections**. To keep a client's data out of a chat entirely, give them their own MCP server with only their accounts. More: [Several accounts per service](/ai-apps/multiple-accounts). ## The sign-in window doesn't open, or closes with an error Allow pop-ups for the AI app, make sure you're signed in to Plugsight in the same browser, then remove the connector in the AI app and add it again. More: [Connect AI apps](/ai-apps). ## "This connector points at an MCP server that isn't in your account" You're signed in to Plugsight with a different account from the one that created that MCP server, often a work and a personal login in the same browser. Click **Switch account** on the approval screen and sign in with the right one. More: [AI app problems](/troubleshooting/ai-app-problems). ## My AI asks me to sign in to Plugsight again Its access ended, usually because the MCP server was deleted, its AI apps were disconnected, or its access was revoked. Click the sign-in prompt, sign in to the same Plugsight account you set things up with, check the server name and click **Allow access**. More: [Disconnect an AI app](/ai-apps/disconnect). ## It works on my computer but not in the Claude phone app Connectors are added on the Claude website and then appear in the desktop and phone apps. Open a new chat on the phone and check the connector is switched on (**+** → **Connectors**). If you only just refreshed, give it a minute. More: [Claude phone app](/ai-apps/claude-mobile). ## Can I use several MCP servers in one AI app? Yes. Add each server's link as its own connector, for example "Work" and "Clients". Each one reaches only its own accounts. More: [Use several MCP servers](/mcp-servers/multiple-servers). ## How do I cut off an AI app right now? On the MCP server's page, use **Disconnect all AI apps**. Every AI app loses access straight away and must click **Allow access** again to come back. To stop changes but keep reading, use **Pause everything** on **Permissions** instead. More: [Disconnect an AI app](/ai-apps/disconnect). ## Something failed and I don't know why Open **Activity** in the app. It lists every request your AI made, which app and account it used, and the exact error, which usually says what to fix. More: [Activity log](/permissions/activity) and [Errors from your AI's tools](/troubleshooting/tool-errors). ## Related articles - [Connect AI apps](/ai-apps) - [Safety and permissions FAQ](/faq/safety-and-permissions) - [General FAQ](/faq/general) --- # Safety and permissions URL: https://docs.plugsight.app/faq/safety-and-permissions Answers about what your AI can change, approvals, the account switch, Pause, the daily email limit, Activity and how your data is handled. ## Can my AI change things in my accounts? Only if you allow it. - **Read-only, always:** marketing and analytics, contacts, docs and files, stores and email marketing. Plugsight never changes anything there. - **Off until you switch it on:** sending email, replying to and updating helpdesk tickets, and booking, moving or cancelling events in Outlook or iCloud calendars. Turn them on per account on **Connections**, and each action then needs your approval in the chat. - **Archiving, labelling and marking emails read** don't need the account's switch, because they're easy to undo, but they do need a plan that includes changes (Pro or Agency) and stop while email changes are paused. Your AI can always write email drafts. Drafts never send without you. More: [How changes are allowed](/permissions/how-changes-are-allowed) and [Read-only connectors](/permissions/read-only-connectors). ## What does a change need? All of these: a plan that includes changes (Pro or Agency), the account's switch on, **Allow changes** ticked on the MCP server (the default for new servers), nothing paused on **Permissions**, and your approval in the chat. For email, the account must also have sends left under its daily limit. More: [How changes are allowed](/permissions/how-changes-are-allowed). ## What does the switch under Write access do? It decides whether your AI may change things with that one account. **Off** (**Drafts only** for email, **Read-only** for others): the AI can read, and draft emails, but can't send or change anything. **On** (**Can send**, **Can reply & update**, **Can book & change**): it may, once you approve each action in the chat. Accounts that only read show **Read-only** with a lock and have no switch. More: [Switch states under each account](/permissions/switch-states). ## The switch is on. Can my AI make changes now? Look at the line under the switch. **Ready** means yes: your AI asks you before each change. Otherwise it names the one thing still stopping it, such as the type being paused, the account not being in an MCP server yet, or its MCP servers not allowing changes. More: [Switch states under each account](/permissions/switch-states). ## I switched on write access, but the AI still can't send or change anything Check the line under the account's switch on **Connections**: it says **Ready**, or names what's missing. Usually it's one of these: changes are paused (every page then shows a red notice with **Resume**), **Allow changes** is unticked on the MCP server, or your plan doesn't include changes. Fixing it works straight away, with no refresh. Every change also waits for your yes in the chat. More: [Your AI can't send or change anything](/troubleshooting/ai-cant-send-or-change). ## Can I keep one account read-only and let another send? Yes. The switch is per account, and every change still needs your approval in the chat. More: [How changes are allowed](/permissions/how-changes-are-allowed). ## How do I make a whole MCP server read-only? Untick **Allow changes** in the server's **Edit configuration**. Your AI can then read that server's accounts and write email drafts, but can't send email, update tickets or book events through it, whatever the account switches say. It can still archive, label and mark emails. More: [Edit an MCP server](/mcp-servers/edit). ## What does Pause do? It's an emergency brake. **Pause** stops every change of one type straight away, for all your accounts of that type: no emails sent, no tickets updated, no events booked. **Pause everything** stops all types at once. Your AI can still read, and still write email drafts. Click **Resume** to let changes through again. More: [Pause changes](/permissions/pause). ## What's the difference between the account switch and Pause? The switch on **Connections** is the everyday setting for one account. **Pause** on **Permissions** is an emergency brake for a whole type, or everything. A pause always wins: while a type is paused, its accounts show **Paused** even with the switch on. Turning the switch off and on doesn't undo a pause; click **Resume** on **Permissions**, or on the account itself. More: [Pause changes](/permissions/pause). ## When should I use Pause instead of the account switch? Use the account switch for everyday choices, like letting one inbox send but not another. Use **Pause** when you want everything of a type to stop at once, for example while you check something that looks wrong, or before someone else uses your AI chat. Your account switches stay as they were. More: [Pause changes](/permissions/pause). ## Why do some types have no Pause button? They only read. Marketing and analytics, contacts, docs and files, stores and email marketing can't change anything in your accounts, so there's nothing to pause. More: [Read-only connectors](/permissions/read-only-connectors). ## Does pausing cancel anything already sent? No. It stops new changes from that moment on. Anything already sent or updated stays as it is. **Activity** lists every change your AI made. More: [Activity log](/permissions/activity). ## How many emails can my AI send a day? Up to 20 per email account in a rolling 24 hours by default, so a mistake can never send hundreds. You can set it from 1 to 500 under **Permissions** → **Daily email limit**. Drafts never count, every send still needs your approval, and your email provider has its own daily limits too. More: [Daily email limit](/permissions/daily-email-limit). ## When does the daily email limit reset? There's no fixed reset time: the 24 hours roll. Each email counts for 24 hours after it's sent, then frees up a send. **Permissions** → **Daily email limit** shows each account's usage, like "7 of 20 sent", and when the next send frees up. More: [Daily email limit](/permissions/daily-email-limit). ## My AI says the daily email limit is reached That account has sent its limit in the last 24 hours. Your AI can still save the email as a draft. Wait for a send to free up, or raise the limit on **Permissions**. More: [Daily email limit](/permissions/daily-email-limit). ## Can I see what my AI accessed? Yes. **Activity** lists every AI request (when, which app, which account and the result), plus sign-ins and settings changes. Email bodies and attachments are never stored there, only what was done. Entries are kept for one year. More: [Activity log](/permissions/activity). ## What do Blocked and Failed mean in Activity? **Blocked:** a safety setting stopped it, such as the account or MCP server not allowing changes, a pause, or the daily limit. **Failed:** the provider refused it, for example a wrong recipient address or an expired sign-in. The reason shows under the badge. More: [Activity log](/permissions/activity). ## Do you store my emails, tickets or ad data? No. They're read live for each request and aren't kept. Plugsight stores your connection credentials, encrypted with AES-256-GCM, and your settings. More: [What Plugsight stores and logs](/security/data-handling). ## How are my logins protected? Credentials are encrypted with AES-256-GCM before they're saved, and they're never sent to your AI app. More: [How credentials are stored](/security/credentials). ## Is my data used to train AI? Not by Plugsight. Data goes only to the AI app you connected, to answer your request, and that AI provider's own terms apply there. More: [What Plugsight stores and logs](/security/data-handling). ## Can clients see each other's data? Not if you give each client their own MCP server reaching only their accounts. You can also hide single sites, ad accounts and calendars. More: [Use several MCP servers](/mcp-servers/multiple-servers). ## How do I cut access? Any of these works on its own: remove the connection in Plugsight, disconnect AI apps from your MCP server, or remove Plugsight's access at the provider (for example in your Google account's permissions). More: [Remove Plugsight's access](/security/remove-access). ## Related articles - [Permissions & safety](/permissions) - [Security & privacy](/security) - [AI apps FAQ](/faq/ai-apps) --- # Plans and billing URL: https://docs.plugsight.app/faq/plans-and-billing Answers about the Free, Pro and Agency plans, what counts as a connection, upgrading, cancelling, discounts and your AI app's subscription. ## Is there a free plan? Yes. **Free** includes 2 connections and 1 MCP server, with no credit card. Your AI can search and read your accounts and write email drafts. Upgrade when you need more connections, the marketing and analytics connectors, or sending and changes. More: [Plans](/get-started/plans). ## What do Pro and Agency add? | | Free | Pro | Agency | |---|---|---|---| | Price | $0 | $29 a month, or $290 a year | $99 a month, or $990 a year | | Connections | 2 | 10 | 50 | | MCP servers | 1 | 5 | Unlimited | | Marketing and analytics connectors | To try: 1 connection, 25 tool calls a month | Yes | Yes | | Sending email and other changes, each approved by you | No | Yes | Yes | | Developer API | No | Yes | Yes | Prices are in US dollars. Larger teams can ask about Enterprise at [info@plugsight.app](mailto:info@plugsight.app). More: [Plans](/get-started/plans). ## What counts as a connection? One sign-in to one service: a mailbox, a Zendesk account, a Microsoft Advertising login, or one Google service such as Search Console or Google Ads. A marketing login brings every site, property or ad account it can see, and all of them count as one connection. A second Gmail inbox is its own connection. More: [Plans](/get-started/plans) and [Several accounts per service](/ai-apps/multiple-accounts). ## Which connectors need Pro? Only the marketing and analytics ones: Google Ads, Microsoft Ads, Meta Ads, LinkedIn Ads, Search Console, GA4 and Bing Webmaster Tools, plus Tag Manager, YouTube and Merchant Center once Google approves them. Email, Zendesk, calendars, contacts, stores, Mailchimp and the rest work on every plan, within your connection limit. More: [Plans and billing](/account/plans-and-billing). ## Is my AI app's subscription included? No. Claude, ChatGPT and other AI apps are paid separately, and some of their plans can't use custom connectors. See which plans work in [Connect AI apps](/ai-apps). ## Do I need my own Google Ads or Microsoft developer token? No. You sign in with your own Google or Microsoft account, and Plugsight handles the API access. More: [Google Ads](/connectors/google-ads). ## What happens when I reach my plan's limit? You can't add another connection or MCP server until you remove one or upgrade. The app says which limit you reached and which plan raises it. The **Billing** page shows your usage against your plan. More: [Plans and limits](/troubleshooting/plan-limits). ## How do I upgrade? On the **Billing** page, choose monthly or yearly, then click **Upgrade to Pro** or **Upgrade to Agency**. Upgrades apply straight away. More: [Upgrade your plan](/account/upgrade). ## Is there a free trial? Yes, two ways. The Free plan needs no card and includes 1 marketing connection with 25 marketing tool calls a month. And if you've never had a paid plan or a trial, your first Pro subscription starts with a 7-day free trial: Stripe takes your card at checkout and charges it when the trial ends, unless you cancel before then. More: [Upgrade your plan](/account/upgrade#the-free-pro-trial). ## Can I change or cancel my plan? Yes, at any time. Upgrades apply straight away. Moving to a cheaper plan or cancelling takes effect at the end of the period you've paid for, and you keep everything until then. Cancelling doesn't delete anything: your account moves to Free. More: [Cancel your plan](/account/cancel) and [Invoices, card and plan changes](/account/manage-billing). ## Can I get a refund? Yes, for your first payment: it has a 14-day money-back guarantee. Email info@plugsight.app within 14 days of the first payment for your first paid plan (after a free trial, the first charge when it ends) and we refund it in full and cancel the plan, so your account moves to Free. Later payments aren't refunded, including unused time when you cancel or move to a cheaper plan. When you cancel, you keep your plan until the end of the period you've paid for, and you're never charged again. We do refund duplicate charges, billing errors, and a charge made after you cancelled if it was our mistake. For any question about a charge, email info@plugsight.app before contacting your bank; we reply within 2 business days. More: [Cancel your plan](/account/cancel) and the [terms](https://plugsight.app/terms). ## What happens when a paid plan ends? Your account moves to Free and nothing is deleted. Your connections and MCP servers stay, but marketing and analytics connectors drop to Free's 25 tool calls a month, sending and other changes and the developer API stop working, and you can't add more beyond Free's limits. More: [Cancel your plan](/account/cancel). ## Where are my invoices? In the billing portal, opened from the **Billing** page. You can also change your card and plan there. More: [Invoices, card and plan changes](/account/manage-billing). ## A payment failed. What now? Your plan keeps working while Stripe tries again over the next few days. Open **Billing**, click the **Payment failed** badge, then **Update card**. If every retry fails, your account moves to Free. More: [When a payment fails](/account/failed-payment). ## Do you offer discounts? Paying yearly gets you two months free. For non-profits, education or larger agencies, email [info@plugsight.app](mailto:info@plugsight.app). More: [Plans](/get-started/plans). ## Related articles - [Account & billing](/account) - [General FAQ](/faq/general) - [Developer API FAQ](/faq/developer-api) --- # Developer API URL: https://docs.plugsight.app/faq/developer-api Answers about Plugsight's developer API - which plans include it, what it reaches, keys, calling it from a web page, caching and missing tools. ## Do I need to know what MCP is? No. "MCP server" is what the app calls a project with a key, because AI apps use the same projects. For the API, it's a key that reaches the accounts you picked. More: [Developer API](/developers). ## Which plans include the API? Pro and Agency. On Free, every request is refused with `403 plan_required`. More: [Developer API](/developers) and [Errors](/developers/errors). ## What can I pull? Whatever the MCP server's connections reach, through the same tools your AI app uses: email, Zendesk, marketing and analytics, calendars, contacts, stores, Mailchimp and the PageSpeed check. `GET /v1/tools` lists the tools a key can use right now. More: [Calling tools](/developers/calling-tools) and the tool reference in [Developer API](/developers). ## Is it the same as the AI app connection? Yes: the same MCP servers, the same tools, the same permissions and the same **Activity** log. AI apps connect through MCP; your code uses the server's API key through a JSON API. API calls show in **Activity** as "Developer API". More: [Developer API](/developers). ## Can I call it from a web page or mobile app? Not directly: the key would be visible to anyone who opens the page. Call it from your server or a serverless function, and send your page only the numbers it needs. More: [Authentication](/developers/authentication). ## Is the data cached or stored? No. Each call reads live from the provider. Cache results on your side if you show them often: it's faster and keeps you under the limits. More: [Developer API](/developers). ## How many requests can I make? Up to 120 a minute per MCP server. Over that, you get `429 rate_limited`. Providers' own limits apply too. More: [Errors](/developers/errors). ## Why did a tool disappear? Tools follow the MCP server's connections. If you remove the last account of a type from the server, that type's tools go away until one is back. A connection that needs reconnecting keeps its tools, but its calls fail until you reconnect it. `list_accounts` shows each account's state. More: [Accounts tools](/developers/accounts-tools). ## Can my code send email or change tickets? Yes, with the same rules as an AI app: the request must include `"confirm": true`, **Allow changes** must be ticked on the MCP server, the account's switch must be on, nothing may be paused, and email needs sends left under the daily limit. The exception is `organize_emails` (archive, label, mark read), which needs only a Pro or Agency plan and nothing paused. More: [Calling tools](/developers/calling-tools). ## Where do I get help? Email [info@plugsight.app](mailto:info@plugsight.app) with the error code and message you got, and the time of the request. ## Related articles - [Developer API](/developers) - [Authentication](/developers/authentication) - [Plans and billing FAQ](/faq/plans-and-billing) - [Build a dashboard with Claude Code and the developer API](/guides/developer-dashboard) --- # What's new URL: https://docs.plugsight.app/whats-new New connectors, features and notable fixes in Plugsight, newest first, grouped by month. New connectors, features and fixes in Plugsight, newest first. ## November 2026 ### 20 November - **LinkedIn Ads for everyone.** LinkedIn has approved Plugsight's access to its Advertising API, so LinkedIn Ads is now in the **Connector catalog** for everyone. Read-only. [LinkedIn Ads](/connectors/linkedin-ads) - **Try marketing on Free.** Free now includes 1 marketing connection and 25 marketing tool calls a month, so you can try Google Ads, GA4, Search Console and the other marketing connectors before upgrading. **Billing** shows how many calls you've used and when they start again. [Plans](/get-started/plans) - **A free Pro trial.** If you've never had a paid plan or a trial, your first Pro subscription starts with a 7-day free trial. Stripe takes your card but doesn't charge it until the trial ends, and you can cancel before then at no cost. [The free Pro trial](/account/upgrade#the-free-pro-trial) - **14-day money-back guarantee.** Your first payment for a paid plan can be refunded in full within 14 days: email info@plugsight.app. [Refunds](/account/cancel#refunds) - **Team members.** On Agency, invite up to 5 people, you included, to work in your workspace. Members use its MCP servers from their own AI apps, each signing in as themselves; Admins also manage connections, MCP servers, API keys and settings. Every action shows in **Activity** with who did it. [Team members](/account/team) - **Shopify.** Connect one Shopify store or many with a read-only app from Shopify's Dev Dashboard, so your AI can report on sales, orders, best sellers, stock by location and customers. Built for agencies: each store is its own connection. [Shopify](/connectors/shopify) - **Custom API.** On Pro and Agency, connect any REST API on a public https address, such as your own app or a tool without a connector, with an API key, bearer token, username and password, or OAuth 2.0 client. Import its OpenAPI (Swagger) spec and each endpoint becomes a tool your AI can use. Changes wait for your approval in the chat. [Custom API](/connectors/custom-api) - **Custom MCP server.** On Pro and Agency, add any remote MCP server on a public https address, signed in with OAuth, a token or headers. Its tools appear in your Plugsight MCP servers next to your other accounts, so your AI app needs only Plugsight. Tools the server marks read-only work straight away; every other tool waits for your approval in the chat. [Custom MCP server](/connectors/custom-mcp) - **TikTok Ads, coming soon.** Sign in with TikTok for Business so your AI can report on TikTok ad spend, video views, clicks, conversions and ROAS, next to Google Ads, Microsoft Advertising, Meta Ads and LinkedIn Ads. Read-only. It's waiting for TikTok to approve Plugsight's access to its API for Business. [TikTok Ads](/connectors/tiktok-ads) ### 19 November - **LinkedIn Ads.** Sign in with LinkedIn so your AI can report on Campaign Manager spend, clicks, leads, conversions and ROAS, next to Google Ads, Microsoft Advertising and Meta Ads. Read-only. [LinkedIn Ads](/connectors/linkedin-ads) - **Meta Ads.** Sign in with Facebook so your AI can report on Facebook and Instagram ad spend, reach, results and ROAS, next to Google Ads and Microsoft Advertising. Read-only. [Meta Ads](/connectors/meta-ads) ### 18 November - **Bing Webmaster Tools.** Connect with an API key so your AI can read Bing search clicks, impressions, top queries and pages, crawl stats and sitemaps. Read-only. [Bing Webmaster Tools](/connectors/bing-webmaster) ### 17 November - **Zendesk attachments and screenshots.** Your AI can now look at screenshots customers paste or attach in Zendesk, and read attached PDF, Word, Excel and text files. Pasted images are also marked in the conversation where they appear. See [Zendesk](/connectors/zendesk). - **Ask AI.** Ask a question in your own words, in the app's **Help** panel or in these docs, and get an answer written from the help centre with links to the articles it used. See [Ask AI about Plugsight](/get-started/ask-ai). - **Help inside the app.** **Help** in the top bar opens the articles for the page you're on, and every info pop-up links to its full article. - **This help centre.** Plugsight's docs now live at docs.plugsight.app, with step-by-step articles for every connector, AI app, setting and error message. - **Clearer Gmail setup.** The Gmail connect page walks you through making an app password step by step, and shows a clear card when Google says app passwords aren't available for your account. See [Gmail and Google Workspace](/connectors/gmail). - **The account switch is the one control for changes.** New MCP servers have **Allow changes** ticked by default, so each account's switch on **Connections** decides what your AI may change. You still approve every change in the chat. See [How changes are allowed](/permissions/how-changes-are-allowed). - **Pauses can't go unnoticed.** While anything is paused, every page shows a red notice with **Resume**. A paused account's switch shows **Paused**, with an info pop-up saying why and offering **Resume**. Plugsight also asks you to confirm before pausing. See [Pause changes](/permissions/pause). - **Help where you need it.** Confirmations, short explanations and clearer wording across the app, so each screen says what a setting does. - **One contact address.** Every email from Plugsight and every "contact us" in the app now points to info@plugsight.app, and replies to Plugsight's emails go there too. - **Fixed:** Google Contacts now connects when you leave the optional "Other contacts" permission unticked, as the connect page says. See [Google Contacts](/connectors/google-contacts). - **Fixed:** the email you get when a paid plan ends now says exactly what happens on Free: your connections are kept and keep working, while marketing connectors and sending stop. - **Fixed:** deleting your account now says correctly that a record of its activity is kept for up to a year, with only your email address. See [Delete your account](/account/delete-account). ### 16 November - **Developer API.** On Pro and Agency, your own website or system can use the same tools as your AI app, over HTTPS with an API key. Each MCP server's page has a **Developer API** panel with examples. See [Developer API](/developers). - **Set your own daily email limit.** Choose from 1 to 500 emails per account in a rolling 24 hours, on **Permissions**. Each email account shows its usage, like "7 of 20 sent", and when the next send frees up. See [Daily email limit](/permissions/daily-email-limit). - **New Google connectors, waiting for Google's approval:** [Google Tag Manager](/connectors/google-tag-manager), [YouTube](/connectors/youtube), [Google Merchant Center](/connectors/google-merchant-center), [Google Sheets](/connectors/google-sheets), [Google Docs](/connectors/google-docs), [Google Forms](/connectors/google-forms) and [Google Meet](/connectors/google-meet). Until Google approves the permissions they need, only Plugsight admins can connect them. - **PageSpeed check on every MCP server.** Ask your AI how fast any public page is: scores, real-user Core Web Vitals and the biggest fixes, with nothing to connect. See [PageSpeed Insights](/connectors/pagespeed-insights). - **Free or Pro on every connector.** On the Free plan, the **Connector catalog** marks each connector Free or Pro, and Pro connectors say **On Pro: upgrade to connect**. - **Emails for every account and billing event:** confirming your email, sign-in links, password changes, plan changes, receipts, failed payments and renewal reminders, all in one design. See [Emails Plugsight sends you](/account/emails). - **Deleting your account cancels a paid plan straight away**, so you're not charged again. - **Exact refresh steps for each AI app**, matching Claude's and ChatGPT's current screens. ChatGPT setup no longer needs Developer mode. See [Refresh the tools list](/ai-apps/refresh-tools) and [ChatGPT](/ai-apps/chatgpt). - **A clearer next step** after you connect an account, so creating an MCP server is hard to miss. ### 15 November - **A refreshed app**, with a tab bar on phones. - **The catalog shows only what you can connect today.** Planned connectors and the "Coming soon" filter are gone. Google Drive is held back until Google approves it. See [Google Drive](/connectors/google-drive). - **Add another** next to each service on **Connections**, to add a second account of the same kind. - **Better example questions.** "Try asking your AI" suggests questions only for accounts your AI apps can use. - **Setup steps open in place.** On **MCP servers**, **Show setup steps** opens the guide for your AI app in a pop-up. - **Easier WooCommerce keys.** Type your store address first, and Plugsight opens the exact WordPress screen where you make the keys. See [WooCommerce](/connectors/woocommerce). - **Sign in with Zendesk is the way to connect Zendesk.** Zendesk stopped creating new API tokens on 27 October 2026 and switches existing ones off on 30 April 2027. See [Connect Zendesk with an API token](/connectors/zendesk-api-token). - **Phone fixes:** tabs stay in one swipeable row, and buttons, checkboxes and links are easier to tap. - **Fixed:** copy buttons no longer fail silently when the browser blocks the clipboard; they say **Couldn't copy** instead. ### 14 November - **New connectors:** [Mailchimp](/connectors/mailchimp) (campaign results, audiences and subscribers), [Magento / Adobe Commerce](/connectors/magento) and [WooCommerce](/connectors/woocommerce) (sales, orders, products and customers). All read-only. - **Outlook Calendar and Contacts.** Your AI can read Outlook calendars and contacts, and book, move and cancel Outlook events once you allow it. See [Outlook Calendar](/connectors/outlook-calendar) and [Outlook Contacts](/connectors/outlook-contacts). - **iCloud Calendar and Contacts**, connected with an app-specific password, including booking with your approval. See [iCloud Calendar](/connectors/icloud-calendar) and [iCloud Contacts](/connectors/icloud-contacts). - **Google Calendar is read-only for now.** Booking in Google Calendar comes once Google approves the permission it needs. Outlook and iCloud calendars can book today. See [Google Calendar](/connectors/google-calendar). ### 13 November - **More your AI can do:** - Book, move and cancel calendar events, with your approval. See [What your AI can do with calendars](/connectors/calendar-tools). - Archive, move, label, flag and mark emails read, without counting toward the daily email limit. See [Sending, drafts and the daily email limit](/connectors/email-safety). - Create Zendesk tickets, use macros, and count tickets. See [Zendesk](/connectors/zendesk). - More Microsoft Advertising reports, and GA4 funnels and key events. - **Plans:** Free, Pro and Agency, with yearly billing. See [Plans](/get-started/plans). - **The Permissions page**, with one place to pause changes by type, or everything at once. - **Your AI app is told when its list of actions is out of date.** Plugsight shows which AI apps need a refresh on **Overview**, **Connections** and the MCP server's page, with the steps. See [Refresh the tools list](/ai-apps/refresh-tools). - **Errors explain what to do next**, in plain words, for your AI and in the app. See [Errors from your AI's tools](/troubleshooting/tool-errors). - **A tidier app:** logos, connections grouped by service, search across the app, and a redesigned panel for choosing which sites and accounts your AI sees. See [Choose which sites and accounts your AI can see](/connectors/hide-sites-and-accounts). - **A clear connection status.** Opening **Overview** or **Connections** checks each login, so a connection that stopped working shows **Reconnect needed** before your AI hits it. ### 12 November - **Plugsight** is the new name, with a new logo. - **Marketing and analytics connectors:** [Google Search Console](/connectors/google-search-console), [Google Analytics 4](/connectors/google-analytics-4), [Google Ads](/connectors/google-ads) and [Microsoft Advertising](/connectors/microsoft-advertising). Each Google service is its own connection, with only its own permission. - **Google Calendar and Google Contacts** connectors. See [Google Calendar](/connectors/google-calendar) and [Google Contacts](/connectors/google-contacts). - **Gmail connects with an app password** by default. See [Gmail and Google Workspace](/connectors/gmail). - **Reconnect needed, everywhere it matters.** When a provider rejects a login, the connection shows **Reconnect needed** with the reason, on **Overview**, **Connections** and in your AI's list of accounts. Mailboxes and Zendesk API tokens can be reconnected with the form filled in, without making a duplicate. See [Reconnect needed](/troubleshooting/reconnect-needed). - **Lists that work on phones**, and connection problems shown as warnings. ### 3 November - **Activity log.** See every sign-in, settings change and AI request in one place. See [Activity log](/permissions/activity). ## October 2026 ### 30 October - **Sign up for your own account.** Anyone can create a Plugsight account, with their own connections and MCP servers. - **Connect any email provider.** More than 60 providers are built in, and Plugsight detects the right settings from your address. See [Connect any email address](/connectors/connect-any-email). - **Zendesk connector**, with **Sign in with Zendesk**. See [Zendesk](/connectors/zendesk). - **One-click Outlook** with Microsoft sign-in. See [Outlook / Microsoft 365](/connectors/outlook). - **Write controls per type of account**, and step-by-step guides throughout the app. - **A connector catalog** you can group and filter. ### 7 October - **Drafts and guarded sending.** Your AI can write email drafts, and send only with safety checks in place. See [Sending, drafts and the daily email limit](/connectors/email-safety). ### 6 October - **First release:** search and read email from iCloud, Gmail and any IMAP mailbox, plus Outlook / Microsoft 365, from AI apps that sign in through a browser window. ## Related articles - [Connectors](/connectors) - [FAQ](/faq)