Integrations live under Build → Integrations and are connected once per organization. Everything you give Weaveflow is encrypted with a key scoped to your organization, and secret values are write-only — the dashboard shows that a key is set, never the key itself.
What each one unlocks
- GitHub — the repository Weaveflow creates for each project, and the pull requests the agent opens. Required for everything.
- Anthropic — the agent itself. This is your own Claude subscription; Weaveflow never meters or marks up tokens. The credential is injected into the agent container at run time and never written to the box’s disk.
- Supabase — the database SaaS Base projects are wired to, and what the project’s Database tab introspects.
- Cloudflare — static-site deploys (they publish to Cloudflare Pages) and instant DNS records when you attach a custom domain.
- Resend — outbound email from your generated app, such as password resets.
- Hetzner — lets the create flow create a server for you on your Hetzner account and enroll it in the same step. Without it you bring your own box, as described in Connect a server — both paths end in the same place.
Slack is listed in the grid as coming soon.
When you are asked for them
The create flow has a keys step that shows only what the chosen starting point needs and skips anything your organization has already connected — sections with an existing answer collapse to confirmed rows on their own. Landing-page projects skip the step entirely.
Project tabs also appear based on what is actually connected and reachable: a static site never shows a Database tab, and a project can only offer what its integrations support.