Connections

A connection gives a project a way to reach an external system. Work on Repeat supports two kinds:

• Tool connections — managed providers such as Customer.io, Clay, Firecrawl, Exa, Close, Semrush, Supabase, Linear, Stripe, Resend, Sentry, Slack, HubSpot, Notion, Atlassian, Cal.com, Intercom, Apollo, Plain, Pylon, Attio, Granola, Twenty CRM, Retool, Google Drive, Gmail, Google Calendar, Salesforce, Xero, Pipedrive, Apify, Loops, GitHub, PostHog, and Zernio, plus self-managed MCP servers.
• Result destinations — outbound-only delivery connections such as Discord.
• Self-managed MCP servers — any Streamable HTTP MCP server you host or subscribe to, configured with a URL and optional encrypted headers.

Both kinds end up in the same place: a connection whose tools are discovered per routine and disabled by default.

Customer.io, Clay, Supabase, Slack, HubSpot, Notion, Atlassian, Cal.com, Intercom, Apollo, Plain, Pylon, Attio, Granola, Twenty CRM, Retool, Google Drive, Gmail, Google Calendar, Salesforce, Xero, Pipedrive, and Loops are OAuth-only. Exa supports a credential-free connection with an optional API key. Firecrawl, Close, Semrush, Linear, Stripe, Resend, Sentry, and Apify use an OAuth-first flow with an advanced API-key fallback — an Apify API token, in Apify's case. Their provider-owned tools pass Work on Repeat's versioned safety policy at discovery and immediately before each call. See Managed integrations for setup, minimum credential guidance, and provider-specific boundaries.

OAuth refresh tokens and Discord webhook URLs are encrypted at rest, as are OAuth access tokens, API-key credentials, and connection headers. They are masked in the product and never returned after setup.

GitHub and PostHog (OAuth)

Open Connections and select Connect GitHub or Connect PostHog. You are redirected to the provider, approve the scopes, and return to the dashboard.

PostHog uses PKCE with S256. GitHub OAuth apps do not support PKCE, so that flow relies on the client secret and a single-use state.

Every authorization request stores a state bound to your user and the active project, valid for ten minutes and consumed on first use. The callback is refused when the state is unknown, expired, already used, or finished by a different session.

Access tokens are encrypted at rest with ENCRYPTION_KEY and are never returned by the API. Re-authorizing replaces the stored credentials in place rather than creating a second connection.

If a provider's connect button is disabled, that deployment has not configured its OAuth client. See Deployment.

Zernio (API key)

Zernio holds the social accounts you have already connected — X, LinkedIn, Instagram, TikTok, and others. Rather than re-authorizing each network here, paste a Zernio API key from your Zernio dashboard.

The key is verified immediately against GET /v1/accounts. A key Zernio rejects is never stored. On success the dashboard lists each connected social account with its platform, handle, and whether it is active, read live from Zernio so it always reflects the current state.

Self-managed MCP servers

Any Streamable HTTP MCP server can be registered with a name, a URL, and optional headers. See Connect your own MCP server for the walkthrough, including the header limits and network rules.

Connection status

Discover tools

Open a routine, choose a connection, and select Discover tools. The API asks the MCP server for its current tool definitions and creates a per-routine policy for each.

Every discovered tool is disabled by default. Rediscovery refreshes the remote schema and resets prior approvals, so changed server behaviour cannot inherit an old automatic-execution grant.

Explicit execution approval

MCP annotations such as readOnlyHint are shown as context, but the remote server controls those annotations and they are not treated as authorization. Allowing any external tool to run automatically requires a separate confirmation that names the tool and explains that it may read or change connected data.

Automatic execution is a distinct choice and requires the tool to be enabled first. Tool calls and results appear in the run trace. See Tool permissions.

Disconnect

Selecting Disconnect deletes the stored credentials and the connection. Revoke the grant at the provider as well — GitHub under Applications, PostHog under Authorized applications, Zernio by deleting the API key.

If a managed connection shows reauthorization_required, open Connections and start OAuth again, or atomically replace its API key. The saved connection stays visible and manageable while setup is temporarily disabled, so an operator can inspect its non-secret status, recover it after rollout resumes, or disconnect it. Work on Repeat will not run with a known-stale OAuth token.

Network controls

Production connections reject unsafe destinations such as loopback, link-local, and private network addresses. The validated public DNS answers are pinned to the outbound connection to prevent DNS rebinding between validation and use. Local development can connect to an explicit fixture server for testing.