Integration categories
Productivity
Gmail, Google Calendar, Google Docs, Google Search, Google News, Fetch Website, Google Shopping
Financial
Plaid, Finnhub, CoinMarketCap, Exchange Rate
Travel & transportation
FlightAware, Amadeus, Amtrak, Caltrain
Entertainment & local services
Yelp, TripAdvisor, Ticketmaster, MovieGlu, AccuWeather, WeatherAPI, Amazon, EasyPost
Total integrations
| Category | Services |
|---|---|
| Productivity | Gmail, Google Calendar, Google Docs, Google Search, Google News, Fetch Website, Google Shopping |
| Financial | Plaid, Finnhub, CoinMarketCap, Exchange Rate |
| Travel & transportation | FlightAware, Amadeus, Amtrak, Caltrain |
| Entertainment & local | Yelp, TripAdvisor, Ticketmaster, MovieGlu, AccuWeather, WeatherAPI, Amazon, EasyPost |
How integrations are configured
Each integration is declared inintegrations.yaml at the project root. The configuration drives the frontend display, onboarding prompts, and agent capability documentation.
id— unique identifier used internallyname— display name shown in the UIdescription— capability summarylogo— URL to the integration logo assetprompts— example prompts shown to guide users
Example prompts
Theprompts field in integrations.yaml teaches users what each agent can do. Here is a sample across categories:
Authentication requirements
Integrations use two authentication models: OAuth 2.0 (user authorization required) These services require the user to connect their account through an OAuth flow before use:| Integration | OAuth scope |
|---|---|
| Gmail | https://mail.google.com/ |
| Google Calendar | https://www.googleapis.com/auth/calendar |
| Google Docs / Drive / Sheets | https://www.googleapis.com/auth/drive, docs, spreadsheets |
| Plaid | Plaid Link OAuth — bank-level access |
See Environment variables for the full list of required API keys and how to configure them.
Multi-agent combinations
The orchestrator can chain multiple integrations in a single request. TheCombinations! entry in integrations.yaml illustrates this: