Skip to main content
Integrations in Operator have two pieces: a secret in Environment that authorizes access, and a skill the agent uses to talk to the service. Both are required, and both live on the instance the agent runs on. You do not need a prebuilt integration for every service. If a service has an API and you have credentials, Operator can write a skill on the fly that uses your secret. The per-service pages here document the common ones.

​
How connecting a service works

Store the secret

Open Environment, add the credential (API key, token, or URL), and either make it global or grant it to a specific agent.

Ask Operator to use it

In chat, describe what you want the agent to do with that service. If a prebuilt skill already covers it, Operator installs the skill. If not, Operator writes a new skill on the fly and deploys it.

Test with a real task

Give the agent a small version of the real job and watch it in Activity to confirm the credential is flowing through.

​
Prebuilt skills

These services have managed skills Operator installs on request. The setup guide for each covers where to create the credential and which secret names to use.

GitHub

Repos, files, PRs, issues, Actions

Privy

Agentic wallets and wallet policies

Resend

Transactional and operational email

PostgreSQL

Query, inspect, and update data

Vercel

Deploy repos and inspect deployments

X (Twitter)

Post, delete, interact with X workflows

Twilio

SMS messages and messaging flows

Cloudflare

DNS management and nameservers

Google Workspace

Gmail, Drive, Docs, Calendar, Sheets

Polymarket

Prediction market data and analysis

Replicate

Hosted AI model inference

fal.ai

Generative media models

Zernio

Social media scheduling across 14+ platforms

Remotion

Programmatic video and image rendering

Custom

Connect any service with a secret and a skill
Need a service not listed? Follow the Custom integration flow. Any service with an HTTP API is a candidate.

​
Where integrations fit in a project

Integrations supply inputs, outputs, and ground truth. A few examples:
Agent purposeIntegrationWhat it provides
Inbox triageGmail / Google WorkspaceRead mail, draft replies, apply labels
Release monitorGitHubCommit history, tag creation, PR status
Support responderResend / TwilioReply to customers over email or SMS
Deploy assistantVercel + GitHubTrigger builds, inspect deployments
Content schedulerZernioPost to social platforms on a cadence
Data analystPostgresQuery your tables and write summaries
Pair any integration with Automations to turn it into recurring work.

​
Prebuilt vs. blank instances

Prebuilt instances arrive with the common integration skills preinstalled so Operator can install and connect them with a single message. Blank instances start empty; you’ll add the skill as well as the secret when the time comes.
In both cases, the secret has to exist in Environment before the integration works. Skills and secrets are separate concerns.

Environment

Secret storage and access control

Agents

Who ends up using the integration

Instances

Prebuilt vs. blank