- A skill or workflow that knows how to talk to the service
- The secret or secrets that authorize access
Common setup flow
- Open Environment and store the required secret.
- Make it global or grant it to a specific instance.
- Use a prebuilt instance or install the matching skill.
- Ask the agent to perform a real task.
Available integrations
| Integration | What it enables |
|---|---|
| GitHub | Read repos, create files, open PRs, manage issues, trigger Actions |
| Privy | Create agentic wallets and manage wallet policies |
| Resend | Send transactional or operational email |
| PostgreSQL | Query, inspect, and update database data |
| Vercel | Deploy GitHub repos and inspect deployment state |
| X | Post and delete tweets, interact with X workflows |
| Twilio | Send SMS messages and work with messaging flows |
| Cloudflare | Manage DNS and inspect nameservers |
| Google Workspace | Work with Gmail, Drive, Docs, Calendar, and Sheets |
| Polymarket | Browse and analyze prediction market data |
| Replicate | Run hosted AI models |
| fal.ai | Run generative media models |
| Custom | Add your own service by combining secrets with a skill |
Skill installed does not mean ready to use
An agent with the right skill but no secret still cannot use the integration. The same rule applies to every service.Choosing between prebuilt and bare
- Choose prebuilt when you want Operator managed skills ready to go.
- Choose bare when you want to install and manage your own skills manually.
Where to go next
- Environment for secret setup
- Instances for prebuilt versus bare
- API if you want to drive integration workflows from code