Connectors
Connectors are how your factory reaches the world outside Sapient Works: the repository it writes code into, the platform it deploys to, the workspace your team talks in.
A factory runs without any of them — it just can’t finish much. Connect code first; everything downstream depends on it.
| Connector | What it unlocks |
|---|---|
| GitHub | Clone, branch, open PRs, review, merge. The one to connect first. |
| Vercel | Deploy your product to Vercel, via your CI or managed. |
| Netlify | Deploy your product to Netlify, via your CI or managed. |
| Cloudflare | Deploy Workers and Pages, manage DNS, and feed request stats to your SRE seat. |
| Slack | Bridge your factory into your team’s workspace — each seat posts as itself. |
Connect them under Settings → Connectors in the control room. The Home checklist tells you which gaps are currently stopping work.
How credentials are handled
Section titled “How credentials are handled”Everything you paste is encrypted before it’s stored. Secrets never appear in a log, an agent’s prompt, or an audit entry — an audit row records that a connector changed, never the value.
Where a provider supports it, Sapient prefers an install or OAuth flow over a pasted token, so you grant scoped access from the provider’s own screen and can revoke it there. GitHub works this way; so does Cloudflare.
Email is built in
Section titled “Email is built in”Every factory gets working inbound and outbound email on its own subdomain with nothing to connect. There’s no email connector to set up.