Connecting Your Integrations
6 min read
Pre connects to the tools you already use. When it can read your real data, it stops relying on what you say you did and starts checking what actually happened.
Why Integrations Matter
Your North Star is probably a number. MRR, active users, deals closed. Without integrations, you report that number to Pre by hand. With integrations, the agent can check it directly.
That changes the conversation. Instead of "I think we're at $12k MRR," the agent can pull it live and tell you exactly where you stand against your weekly goal. The data is the report. You don't have to summarize anything.
You don't need integrations for Pre to work. But with them, the agent becomes significantly more useful as an advisor because it can see the same numbers you see.
How to Connect
Go to Settings → Integrations. Most integrations connect with a single click through OAuth. A few require an API key from the provider's dashboard, which you paste in during setup. Either way, each integration page tells you exactly what to do.
Powered by Composio
Pre's integrations run on Composio, a third-party service that handles the OAuth flows, token storage, and token refresh for all connected accounts. When you click Connect, Composio manages the authorization handshake with the provider and stores the credentials securely.
You may see Composio mentioned during the connection flow. That's expected. It's the infrastructure layer Pre uses to talk to your tools reliably.
What's Available
Product and Engineering
GitHub (read-only)
The agent can list your repos and open pull requests. Useful for tracking what actually got merged versus what was planned. Ask it "what got shipped this week?" and it pulls from GitHub directly.
Linear (read-only)
Lists issues by assignee, project, and state. If your team runs on Linear, the agent can connect your sprint goals to real issue progress. No more guessing what's actually in progress.
Supabase (read-only)
The agent can query your production database. If your North Star is active users, it can check the real count. It supports any read-only query on any table you have access to. Pre never writes to your database.
PostHog (read-only)
Runs analytics queries against your product data. Pageviews, funnel conversions, retention rates. If you track it in PostHog, the agent can pull it.
Finance
Stripe (read-only)
Pre calculates your MRR, active subscriber count, ARPU, week-over-week revenue, and churn from your Stripe data. If your North Star is revenue-based, this is the most directly useful integration.
Ask the agent "how's my MRR doing?" and you get a real answer with trend data, not a number you typed in yourself.
Comms and Ops
Slack (read and write)
The agent can check message history across channels and send messages. This is the only integration where Pre writes. It only does so when you explicitly ask it to.
Gmail (read and write)
The agent can search your inbox, read full emails, create drafts, and send them. Useful for drafting accountability updates, following up with customers, or any email you want help writing. It always shows you the draft before sending.
Google Calendar (read and write)
Lists your upcoming events with attendees and video call links. Can create events or batches of events when you ask. The agent uses your calendar to understand what you actually have time for.
Read-Only vs. Read/Write
Most integrations are read-only. Pre reads your data but cannot change anything. Slack, Gmail, and Google Calendar can write, but the agent only acts on your explicit request. Pre will never send a message or create an event without you asking.
Pre has no way to modify your code, database records, Stripe subscriptions, or Linear issues. Those integrations are strictly read-only at the data level.
Coming Soon
Mercury and Plaid are in progress. When they land, the agent will be able to check your bank balance and runway automatically.