Getting started
- Sign in with Discord.Proxima is an app that lives inside your team’s Discord server. Sign-in establishes who you are; Discord is also where every approval shows up.
- Create a workspace. A workspace is a Proxima instance for one team. You can be a member of several. Every integration, every droid context, and every audit log entry is scoped to one workspace.
- Connect your tools. Gmail, Google Calendar, Notion, and an X account if you do lead research. Proxima only requests the OAuth scopes it actually uses — see Privacy for the per-scope breakdown.
- Tell us how you sound. Voice and context live in Preferences. The more you tell us, the more drafts read like you wrote them.
- Approve in Discord.When the droids draft something, it appears as a card in your approvals channel. Approve, edit, or skip — that’s the whole loop.
Concepts
Workspace
A workspace ties one team to one Discord server, one Gmail account, one calendar, and one set of droid contexts. Workspaces are isolated: no droid in workspace A ever sees data from workspace B.
Droid
A specialized worker for one slice of your team’s work — the email droid drafts replies, the lead droid finds prospects, the calendar droid watches your schedule, and so on. Droids run in the background and surface drafts when they have something to ship.
Approval
Every outbound action — every email, every reschedule, every DM — passes through an approval card in Discord. Approval is the contract: nothing leaves Proxima without your explicit yes.
Audit log
Every decision a droid makes — and every approval, edit, or skip you give — is recorded in your workspace audit log. Open it whenever you want to know what happened, when, and why.
The droids
Each droid is a focused worker that knows about one slice of your team’s work. They share context but stay in their lane.
| Droid | What it does | Reads from |
|---|---|---|
| Drafts replies in your voice. | Gmail (read + draft) | |
| Calendar | Spots conflicts, proposes new times, declines noise. | Google Calendar |
| Lead research | Surfaces prospects worth a second look. | X / Twitter, custom feeds, the web |
| Outreach drafts | Writes the first send for a qualified lead. | Lead context + your voice profile |
| Knowledge | Answers questions about your team. | Notion, prior threads |
| Reminders | Remembers what you asked it to. | Whatever you tell it once |
Approvals
Approval is the single most important thing about how Proxima works. Every droid that wants to take an outbound action — send, reply, schedule, post — drafts the action and asks first. The asking happens in Discord, in a channel of your choice (we recommend a private #approvals channel that only your team sees).
An approval card has three buttons:
- Approve — the action ships as drafted.
- Edit — you tweak the draft inline, then it ships. The edit teaches the droid how you wanted it phrased.
- Skip — the action is dropped. If you give a reason, the droid learns from that too.
Read more in Security about how approvals are stored and audited.
Integrations
Proxima reads from your work tools and reports into your team chat. The complete list of what we can connect to today:
Read from
- Gmail — read mailbox, draft replies, send on approval.
- Google Calendar — read events, create or modify on approval.
- Notion — read pages and databases for team knowledge.
- Granola — search and chat with meeting notes and transcripts.
- X / Twitter — monitor keywords, accounts, and lists for lead signals.
- Custom HTTP / RSS — bring your own feed.
Report into
- Discord — primary chat surface. Approvals and DMs live here.
- Telegram, Slack — optional secondary surfaces for specific channels (early access).
Voice & context
Voice settings live in workspace Preferences. They shape every draft your droids write. The fields are intentionally small:
- Sample writing— paste a few real things you’ve sent. The more concrete, the better.
- Lexicon — words you use, words you avoid, names of tools and projects.
- Tone defaults — formal, neutral, warm, dry. Any individual draft can override.
Per-droid context lives on each droid’s page. Tell the lead droid your ICP. Tell the calendar droid your working hours. Tell the email droid who you delegate to.
API & webhooks
A first-party JSON API and webhook framework are on the roadmap. For now, the primary integration surface is OAuth into your existing tools — there is no inbound API to call.
If you need to wire an internal system into Proxima today, talk to us via Help— we’ll help you set up a custom HTTP feed for the lead droid.