Integrations
Connect GitHub, Supabase, Figma, Vercel, Netlify, and Stripe so the agent works with the tools you already use
Integrations give the agent direct access to the external services in your stack. Once you connect a provider, generated code uses your real credentials, your real schemas, and your real product catalogs — not placeholder values that you have to swap out before shipping. Authorize once at the workspace level and every project inherits the connection.
Most providers connect through OAuth. The flow opens a popup, you approve in the provider's UI, and the popup posts back to Swarmz with an authorization code. Swarmz exchanges that code for tokens, encrypts them with TOKEN_ENCRYPTION_KEY, and stores them as a row in workspace_connections (or for GitHub, in github_connections and github_installations). The agent reads those rows when it needs to call out to the provider, refreshes tokens automatically when they near expiry, and surfaces errors inline if a connection breaks.
Available integrations
Integrations are grouped by what they do. You can connect every category, none of them, or just the ones you need — the agent adapts based on what's available.
Source control
| Provider | Purpose |
|---|---|
| GitHub | Two-way repo sync, branch management, PRs, auto-pull every 60s |
GitHub is the only source provider with full sync today. GitLab and Bitbucket are on the roadmap.
Backend
| Provider | Purpose |
|---|---|
| Supabase | Connect an existing Supabase project so the agent reads your real schema |
This is separate from Swarmz Cloud, the managed backend that ships with every project. Use the Supabase integration only when you already own a Supabase project you want the agent to work against.
Design
| Provider | Purpose |
|---|---|
| Figma | Import frames as React components via the Swarmz Figma plugin |
The plugin lives in your Figma workspace; you select frames inside Figma and click Send to Swarmz to spin up a new project from the design.
Hosting
| Provider | Purpose |
|---|---|
| Vercel | One-click deploys, preview URLs per branch, edge runtime |
| Netlify | Production deploys, preview URLs, custom domains |
Both providers deploy directly from a GitHub repo, so you'll usually want the GitHub integration connected first.
Payments
| Provider | Purpose |
|---|---|
| Stripe | Add Stripe Checkout, subscriptions, and webhooks to apps you build |
Stripe here is for apps you build with Swarmz, not for billing your Swarmz subscription. That's handled separately under Billing.
Connecting an integration
Open your workspace and go to Settings → Integrations.
Find the provider in the list and click Connect.
A popup opens with the provider's authorization screen. Approve the requested scopes.
The popup closes automatically and the integration card flips to Connected.
Stripe is the one exception to the OAuth flow — it uses a secret key. Paste your sk_test_ key for development, then swap to sk_live_ when you're ready to take real payments.
Workspace vs. personal scope
Most integrations are workspace-scoped: every project in the workspace inherits the connection, and any teammate with access can use it. A small set — like Custom MCP servers — are personal: they're only visible to you and don't leak across the team.
Workspace connections are owned by whoever clicked Connect. If they leave the workspace, you'll need to reconnect or transfer ownership through the workspace admin settings.
Disconnecting
From Settings → Integrations, click the connected provider and choose Disconnect. Swarmz revokes its stored tokens and removes the connection record. For GitHub specifically, disconnecting also removes the linked repo on every project that used it (the repo on GitHub itself is untouched).
What the agent does with a connection
Once connected, the agent has tools wired up to the provider. Some examples:
- GitHub — push commits, open PRs, clone a repo into a fresh project, read file contents from a branch
- Supabase — run SQL, list tables, read the schema, deploy edge functions
- Figma — fetch a frame's node tree, pull asset URLs, mirror auto-layout into flex/grid
- Vercel / Netlify — trigger a deploy, list deployments, read environment variables
- Stripe — list products and prices, create Checkout Sessions, subscribe to webhook events
The agent only reaches for an integration when the prompt calls for it. You don't need to mention "use GitHub" or "use Stripe" — it inspects what's connected, looks at the request, and picks the right tool.