# Connect your tools

> Every kind of connection LopeBase reads, grouped by what it does, how each one connects, and what its health states mean once it is running.

Source: https://lopebase.com/docs/connections
Updated: 2026-10-08
Open in the app: https://app.lopebase.com/connections

Connections are how LopeBase learns about a property: its traffic, its search performance, its money, its errors, and more. Every connection reads, and nothing it reads can change anything in the tool itself unless this page says otherwise for that one.

Open Connections

## Pick what to connect

Connections groups every tool by what it is for. Open a tile to connect it: most either open a one-click sign-in, or show the steps to create a read-only key in that service, with a link that pre-fills the right name and permissions where the service supports it.

| Group | Tools | What it reads |
| --- | --- | --- |
| LopeBase Adapter | Your own app | Users, signups, plans, and anything else you declare. See [Install the LopeBase Adapter](https://lopebase.com/docs/lopebase-adapter). |
| Content | EmDash CMS | Your blog, so LopeBase can draft, review, and publish posts. |
| Analytics | PostHog, Google Analytics, Plausible, Cloudflare Web Analytics | Pageviews, visitors, traffic sources, and (PostHog and Google Analytics) funnels and retention. |
| Search | Google Search Console, Bing Webmaster Tools | Organic impressions, clicks, and the queries bringing people to your site. |
| Money | Stripe, Polar, Mercury, Brex, Rho, Wise | MRR, subscriptions, and revenue (Stripe, Polar), or balances and transactions (the banks). |
| Monitoring | Sentry, Rollbar, Honeybadger, Bugsnag, Better Stack, plus uptime checks | Open errors, daily error counts, and whether a site or monitor is up. |
| Email | Resend, Sequenzy | Bounce and complaint rates (Resend), audience size and running sequences (Sequenzy). |
| Infrastructure | GitHub, Cloudflare, Supabase | Pull requests and Actions runs, Workers and deploys, project and database health. |
| AI | Your AI provider | Not read from; it is the key LopeBase uses to draft content and run reviews. |

A few also show up under Monitoring for what they report there too: GitHub's failing Actions runs, Cloudflare's Worker error rates, PostHog's own error tracking, and Supabase's service health.

## Read-only, with the few exceptions said plainly

Almost everything here only reads. Where a key or sign-in could also change something, the connect dialog says so: Sequenzy can turn a sequence on or pause it when you press that button yourself, and EmDash only creates or publishes the posts you approve. Nothing connects with write access by accident; where a service's own keys cannot be limited to reading, like Resend or Supabase, LopeBase still never uses the extra access.

## Linking a connection to your properties

Most tools are connected once per property, since each property usually has its own PostHog project, Stripe account, or GitHub repo. When a tool's key can see more than one project or site, like PostHog, Sentry, GitHub, and Supabase, LopeBase lists what it can see and lets you match each one to a property, or connect **All my properties** at once from a single key. Reusing an existing key for a second property, rather than pasting it again, is offered automatically.

## Connection health states

Once connected, a tool shows one of a few states, wherever its status appears:

| State | What it means |
| --- | --- |
| Working / Updated recently | Its last read succeeded and the numbers are current. |
| Last refreshed a while ago | Nothing has failed, but the numbers are older than usual, often because nothing new has happened yet. |
| Failing | A real error, not just a slow or busy service. LopeBase waits before showing this, so a brief blip never shows as failing. |
| Needs reconnecting | The service itself confirmed the key or sign-in no longer works. A Reconnect link appears next to its numbers. |

A service that is simply busy or rate-limiting LopeBase is never reported as failing; LopeBase waits and reads it again on the next pass.

## Don't see a tool you use

Every group on Connections ends with a card to ask for a tool LopeBase does not connect yet. Name it, its website, and what you would want from it, and it comes straight to the team building LopeBase.

## Where to go next

- [Connect Search Console and Google Analytics](https://lopebase.com/docs/connect-google) for the most common first connections.
- [Connect Stripe and Polar](https://lopebase.com/docs/connect-stripe) for revenue.
- [Reconnect a connection](https://lopebase.com/docs/reconnect-a-connection) if one needs it.

## If something goes wrong

### A connection shows as failing but the service is up

LopeBase only reports a connection as failing after a real error, and waits out brief blips before alerting you. If it is still failing after a while, the key or sign-in itself may no longer have the access it needs; open the connection and check its permissions.

### It says a connection needs reconnecting

The service itself told LopeBase the key or sign-in no longer works, often because it was revoked or expired on the service's side. Press Reconnect next to it and go through the same steps again.

### I connected a tool for the wrong property

Open that connection from the property it is wrongly attached to and connect it again for the right one. For a tool whose key covers several projects or sites, you can also just add the missing property under the same key instead of starting over.

### A key my provider calls "read-only" still shows a write warning

A small number of services, like Resend and Supabase, have no way to limit a key to reading. LopeBase still only ever reads with those keys; the note is just saying the key itself is capable of more than LopeBase uses.

### I don't see the tool I want to connect

Use the "Missing a tool" card at the end of any group on Connections to ask for it directly.

### There is a small icon on the LopeBase Adapter card

It means at least one property is running an older `@lopebase/adapter` than the latest release. Open the card for a list of which properties, what the newer version adds, and buttons to copy the update command and a prompt for your coding agent. See [Install the LopeBase Adapter](https://lopebase.com/docs/lopebase-adapter).