Skip to main content
This page is generated, not hand-written. Every module, integration option, and status below comes straight from Gravity’s deployment registry — the single source of truth for what’s available in your Gravity agent suite — via scripts/generate-integrations-doc.py. It’s regenerated whenever that registry changes, so it can’t quietly go stale the way a hand-maintained page could. Please don’t hand-edit this file directly — update the source registry and regenerate instead.
This page lists every module and every integration option available in Gravity Agents Lite — the fleet of Anthropic-Claude-based agents (Pipeline Strategy, Meeting Prep, Fundraising Digest, and more) deployed for you, plus the self-serve configuration MCP server you connect to Claude.ai or ChatGPT to manage your own settings. For what each module actually does — its trigger and schedule, exactly what it reads and writes, and which of its settings are configurable today — see Agent reference.

​
What “Available” / “On demand” / “Custom” / “Not supported” actually mean

  • Available — built and ready today. Connect it and the integration works out of the box, no custom build or waiting required.
  • On demand — not pre-built yet. Gravity builds this specific connector when a customer actually needs it — a real, scoped piece of work fit into your onboarding timeline, not a speculative “someday” roadmap item.
  • Custom — there’s no pre-built connector for this slot. Gravity scopes a fully custom integration with you directly instead: a timeline and cost agreed up front, before any work starts.
  • Not supported — this isn’t part of Gravity’s current product surface, and isn’t in the standard on-demand build queue either. If it’s a hard requirement for your team, talk to Gravity directly about scoping it as its own dedicated project.

​
Modules

Each module is a self-contained agent capability. Included in the base package modules ship as part of every Gravity Agents Lite deployment; Add-on modules are enabled on request. “Requires” lists which integration categories (below) that module needs a connection for. Additional detail on a few modules:
  • Company Clarity — Cross-domain strategic monitor; reads all agent output + a founder north-star doc. Two managed agents (Opus synthesis + Sonnet scan).
A few modules also have their own configurable settings — set during onboarding, and self-serve editable afterward through the config MCP server, no support request needed:
  • Email Follow-up — window_days — How many business days of inactivity before a follow-up nudge
  • Meeting Prep — summary_buffer_minutes — How long after a meeting ends before its summary fires
  • Market Intelligence — identity — Identity; watchlist — Watchlist; extra_signals — Extra signals; owner_lanes — Owner lanes
See Agent reference for the full detail on each of these, and Self-Serve Settings for the complete list of what you can adjust yourself.

​
Integrations, by category

Every category below is something you can (optionally) connect. Skipping an optional category is normal — it just means the modules that need it won’t be part of your deployment yet.

​
Messaging

Choose exactly one. Where your agents post digests, ask for approvals, and take commands.

​
Email

Choose exactly one. Where agents read context for drafting, and where founder email drafts land. No “something else” option is listed for this category — if none of the above fits, ask Gravity; it usually rides along with a related integration or gets scoped directly.

​
Programmatic Email Sending

Choose one, or skip this category entirely.
OPTIONAL capability — programmatic outbound sending (approval-gated sequences). Selecting nothing is a valid, common choice: the default is GMAIL DRAFT-ONLY, where every agent-written email lands as a Gmail draft the founder sends by hand (no setup, no sending provider). This is separate from the founder email draft flow, which always stays on the email integration above. Pick ‘resend’ only if the customer wants Gravity to send programmatically (a dedicated sending subdomain; replies route to founders’ real inboxes via Reply-To; resend.enabled stays false until the sequence layer is turned on). If the customer already has their own sending tool, pick ‘other’ — that’s a custom integration scoped with Gravity, not a pre-built option.

​
Calendar

Choose exactly one.
Usually follows email choice; covered by the same OAuth grant.
No “something else” option is listed for this category — if none of the above fits, ask Gravity; it usually rides along with a related integration or gets scoped directly.

​
Data Store

Choose one, or skip this category entirely.
New, purpose-built pipeline/fundraising store created and owned by Gravity in the customer’s tool.

​
CRM Sync

Choose one, or skip this category entirely.
Bidirectional sync with an EXISTING CRM. Scoped per customer — more complex than a new data store.

​
File Storage

Choose one, or skip this category entirely.
For meeting-note / doc signal detection.

​
Meeting Notes

Choose one, or skip this category entirely. Where your agents pull meeting transcripts/summaries from for prep briefs and follow-ups.

​
LinkedIn

Choose any number of these, or none.
Only required by LinkedIn modules.
No “something else” option is listed for this category — if none of the above fits, ask Gravity; it usually rides along with a related integration or gets scoped directly.

​
Don’t see your tool?

An unlisted tool isn’t a dead end. Every category above either has its own “Something else” option, or (for the couple that don’t) rides along with a related integration you’ve already connected. Either way, tell Gravity what you use — most “on demand” and “custom” slots exist because a customer asked for exactly that.

​
Next steps