Skip to content

Integrations

An integration connects one of your services to a site: its analytics, its CRM, its file storage, its server. Once connected, Buddy can use it: pull last month’s traffic, update a contact, read a spreadsheet, check a server.

Your credentials stay in Site Buddy. Buddy never sees the password, key or token. Its requests pass through Site Buddy, which adds the credential on the way out.

Adding Google Analytics to a site: Catalog, Add, the Google sign-in, back to Connected, then asking Buddy for last month's top pages.
  1. Open the Integrations pane in the site’s workspace and go to Catalog.
  2. Find the service and press Add.
  3. Fill in its form. Most ask for an API key or token; services that sign in with Google take you to Google’s sign-in page and bring you back when you have approved access.
  4. Save. Site Buddy checks the connection straight away.

Every integration has an optional Agent usage notes field: anything Buddy should know about using it (“this is the client’s live store, read only”, “the main property is the one called Website 2024”).

The Add GitHub form: repository URL, agent usage notes and GitHub token

  • Added: the integrations this site has, each with its status (Connected, Needs sign-in, Error, Verifying… or Draft) and the last error, if any. Click one to edit it; its menu can also reconnect, verify or delete it. Reconnecting one that shows Needs sign-in or Error restarts the site’s container once it checks out, so Buddy gets the connection back straight away.
  • Catalog: every kind of integration. A service a site can only have once shows Added once it is there.
  • Analytics and search: Google Analytics, Google Search Console, Google Tag Manager, Bing Webmaster Tools
  • Advertising: Google Ads, Microsoft Advertising (Bing Ads), Local Services Ads
  • Local listings: Google Business Profile
  • SEO tools: Ahrefs, Semrush, DataForSEO, Surfer
  • Documents and storage: Google Drive, Google Docs, Google Sheets, Dropbox
  • Commerce and CRM: Shopify API, Magento API, HighLevel CRM
  • Code and servers: GitHub, SSH server, Remote WordPress
  • Other: Pangram (AI-text detection), a headless browser, any REST API, and any MCP server

Something missing? A REST API or MCP server integration connects most services that offer an API.

Give the Repository URL and a GitHub token (a fine-grained token limited to that one repository is best). Buddy can then clone the code, commit its work, and push it or open pull requests, depending on what the token allows. To review every change before it lands, protect your main branch on GitHub and ask Buddy to work through pull requests.

Lets Buddy see your Google Maps listings: how often each one is seen and clicked (calls, website visits, direction requests), the searches people found it by, its reviews and its posts. Add it, then use Connect and sign in with the Google account that manages the listings. If that account manages several businesses, say in Agent usage notes which one is this site’s.

It starts read only: Buddy can look but cannot change anything. Two settings open it up:

  • Allow review replies and posts lets Buddy reply to reviews and publish posts. It shows you the exact text first and waits for your yes.
  • Listing fields Buddy may edit lets Buddy change the details you tick: hours, holiday hours, phone, website, description, categories, services, service area (the towns and cities you serve) and labels (private tags for sorting your listings, which customers never see). Before any change, Buddy shows you what each location has now and what it will become, and waits for your yes. Site Buddy refuses any change to a field you haven’t ticked.

A listing’s name and address can never be changed through Site Buddy, whatever you tick, so a slip can never send your listing back to Google for re-verification. Change those in the Google Business Profile manager.

When you connect, Google’s screen says you’re giving Site Buddy permission to manage or edit your listings. That’s expected: Google offers only one permission for Business Profile, and it covers everything. The two settings above are what decide what Buddy can actually do; reconnecting doesn’t change them.

Lets Buddy read one Microsoft Advertising (Bing Ads) account: campaigns, ad groups, keywords, and performance reports such as spend, clicks and conversions. To add it you need:

  • the Customer ID and Account ID: open the account in Microsoft Advertising and go to Campaigns; the address bar shows them as cid= (customer) and aid= (account);
  • a developer token, from Microsoft Advertising under Settings, Developer settings (a Super Admin of the account requests it).

Under Signs in to Microsoft Advertising with, pick how you sign in at ads.microsoft.com: a Microsoft account, or a Google account if you use “Sign in with Google” there. Save the integration, then use Connect and sign in the same way, with the account that can see the ad account.

It starts read only: Buddy can look but cannot change anything. Switch on Allow account changes to let Buddy change campaigns, budgets, bids and ads; even then it shows you exactly what it will change and waits for your yes.

Gives Buddy a real browser: it can open the site’s pages, click through them, and take screenshots, so it checks its work the way a visitor would see it, not just by reading code. Ask it for a screenshot when you want to see what it sees.

Let Buddy reach a server or a live WordPress site outside Site Buddy: to check logs, compare settings, or deliver changes the way your team already does.

Connect almost anything else. For a REST API you give its Base URL, how it expects the key (Auth header), the API token, and optionally a link to its documentation; for an MCP server, its address. Buddy learns the rest from the service itself, its documentation, or your usage notes.

An MCP server signs in one of two ways. If it gave you a token, paste it as the Bearer token and Site Buddy checks it as soon as you save. If you leave the token empty, saving takes you to the server’s own sign-in page, and you come back connected. A server that has no sign-in page sends you back with a note asking for its token instead.