Work on Repeat
Menu

Integrations for routines

Put your tools to work. On repeat.

Give each routine the live business context it needs—then approve the exact tools it can use before the first scheduled run.

Integration catalog

Start with the system where the work lives.

Use built-in connections for a guided setup, or bring any compatible remote MCP server. The connection supplies capability; each routine gets its own explicit permission list.

7 integrations

Connect with MCP

Revenue

Stripe

Read balances, subscriptions, invoices, and revenue movement without granting transaction access.

  • Balances
  • Subscriptions
  • Invoices

Put it to work on

Quarterly revenue report
Connect with MCP

Engineering

Linear

Turn recurring findings into triaged issues, project updates, and accountable follow-up work.

  • Issues
  • Projects
  • Updates

Put it to work on

Weekly security audit
Connect with MCP

Engineering

Sentry

Review incidents and error trends on a schedule, then surface the changes that need attention.

  • Issues
  • Events
  • Projects

Put it to work on

Weekly security audit
Connect with MCP

Publishing

Resend

Send approved drafts, digests, and recurring customer updates through a bounded email surface.

  • Email
  • Audiences
  • Delivery
Built-in connection

Engineering

GitHub

Read repositories and issues, then open reviewable pull requests through GitHub's remote MCP server.

  • Repositories
  • Issues
  • Pull requests
Built-in connection

Analytics

PostHog

Query product insights, events, and funnels for a recurring brief built around decisions, not dashboards.

  • Insights
  • Events
  • Funnels
Built-in connection

Publishing

Zernio

Create channel-ready posts and publish through the social accounts your team already manages.

  • Accounts
  • Posts
  • Publishing

From access to outcome

One connection. Exact permissions for every routine.

01

Connect

Use a built-in provider or add a remote MCP server with its credentials kept server-side.

02

Discover

Work on Repeat asks the connection which tools it exposes and records the available surface.

03

Approve

Choose the exact tools one routine may call. Everything else stays off by default.

04

Run

The routine runs on schedule with tool calls, model steps, and results preserved in its trace.

Review connection and tool security

Start with Free

Prove one routine. Put the operation on repeat when it is ready.

Put your first routine to work