Calendar & scheduling tools for agents
Agents must read/write Google/Microsoft calendars, propose slots, and book meetings via OAuth toolkits without building calendar OAuth from scratch.
At a glance — Oct 2026
Updated 2026-10-27 · forward this page: /jtbds/calendar-scheduling-tools#briefScores as of 2026-10-19 (8 days old).
- Depot Pick
- Composio · 7.81/10 for this job (curated estimate, high confidence)
No first-party Calendar SaaS in Depot — pick is tool-router based. Confidence: medium; verify Composio calendar actions + scopes before pilot.
- Runner-up
- Nango · 8.21/10
Scores higher than the pick on: Capability fit, Price / performance, Latency / reliability, Privacy / data retention, Lock-in risk (higher = worse), Maturity / track record.
- When not to use the pick
- You only need generic SaaS sync (Nango), or enterprise directory/SSO is the hard part (WorkOS) rather than calendar verbs.
- Lock-in / migration
- Runner-up Nango has lower stored lock-in risk (3.5 vs 5.8, 0–10, higher = more lock-in).
- Sourced price (no comparable unit)
Pick: no sourced price in this job's unit (no_matching_sourced_price).
No cheapest SKU (no_comparable_unit_for_job). No price was invented.
- Free option
- No free resource lists this job. A cheap paid SKU is not a free option.
- Failure modes to watch
- Identity confusion: Bind every tool call to a user or tenant id. Refuse the call if that id changed mid-task. For a public bot, the operator owns the words the bot shows.
- Confirmation skip: Gate those tool names on an approval id recorded before the call. A missing approval is a failure even if the downstream tool returns success.
- Context overflow: If the input exceeds the window, say so and retrieve a narrower slice. Do not answer from a truncated head as if it were the whole source.
- Instruction drift: Restate the stop condition in the trace. End the run when it is met. Review long traces for steps that do not serve the original task.
- Prompt injection: Compare each tool call to the original user task. If the call only makes sense given text that arrived from a fetched page, file, or message, stop and ask. Record which source the instruction came from. This catalog does not store payloads or attack steps.
- Stale retrieval: Store the source URL and the time it was fetched. If a newer canonical page exists, or two stored sources disagree, do not answer from the older one.
Cite: Agent Provider Depot, Depot Pick for calendar-scheduling-tools: composio, scores as of 2026-10-19. Agents: GET /api/decide?jtbd=calendar-scheduling-tools
Composio
No first-party Calendar SaaS in Depot — pick is tool-router based. Confidence: medium; verify Composio calendar actions + scopes before pilot.
Pricing (directional): As of 2026-10-24 (composio.dev/pricing, fetched 2026-10-24; 'New pricing applies to signups on or after August 15, 2026'): Hobby $0 — '100,000 tool calls, 50,000 triggers, and 3 team members included free each month'; 'The Hobby plan is har…
Lock-in risk: higher = more lock-in (worse). Overall already inverts this dimension.
Depot pick for tool/MCP router with managed OAuth across 1500+ apps. Official rate card is now public — Hobby is real free for light agents; Pro is the agent-scale default. Not a compute fabric; pair with E2B/Browserbase when you need sandboxes/browsers.
Quote for Calendar & scheduling tools for agents
Depot Pick stays Composio. Prices below are sourced SKU rows only (as of 2026-10-27). Input and output are not blended. GET /api/quote?jtbd=calendar-scheduling-tools
Nothing was compared. no comparable sourced unit for this job; chat input $/1M and other units were not borrowed pickIsPriceWinner is null.
- BAA usd_per_tool_call $0.0003 source as of 2026-10-03
- Direct execution outside a Session usd_per_tool_call $0.0001 source as of 2026-10-03
- IP allowlist usd_per_tool_call $0.0001 source as of 2026-10-03
- Proxy execute usd_per_tool_call $0.0002 source as of 2026-10-03
- Sandbox execution usd_per_tool_call $0.0001 source as of 2026-10-03
- Shared connection tool calls usd_per_tool_call $0.0003 source as of 2026-10-03
- Zero data retention usd_per_tool_call $0.0001 source as of 2026-10-03
- Hobby usd_per_month $0 source as of 2026-10-03
- Composio-managed connected accounts usd_per_connection $0.1 source as of 2026-10-24
- Composio-managed tool calls usd_per_tool_call $0.0005 source as of 2026-10-03
- Composio-managed trigger events usd_per_trigger_event $0.005 source as of 2026-10-03
- Pro usd_per_month $29 source as of 2026-10-03
- Sandbox LLM tokens usd_per_million_tokens $3.75 source as of 2026-10-03
- Tool calls own app usd_per_tool_call $0.0003 source as of 2026-10-03
- Trigger events own app usd_per_trigger_event $0.003 source as of 2026-10-03
- Advanced white-labeling usd_per_connection $0.3 source as of 2026-10-03
3 of 4 candidates have no sourced price row. 4 are excluded from the Matching price comparison (none). no comparable sourced unit for this job; chat input $/1M and other units were not borrowed
Runners-up
Nango
Depot pick for saas-oauth-integrations (embed customer SaaS OAuth/sync). Composio remains agent-tool-router…
WorkOS
When your first big customer asks for Okta SSO tomorrow, WorkOS is how you say yes without a rewrite.
Trigger.dev
Pick for TS app background agent jobs. Inngest for event meshes; Temporal for polyglot durability.
When NOT to use the top pick
You only need generic SaaS sync (Nango), or enterprise directory/SSO is the hard part (WorkOS) rather than calendar verbs.
Full ranking (score table)
Ranked with this JTBD's weights. Scores are curated estimates unless marked otherwise. Agents: prefer /api/decide then this table for tie-breaks.
| # | Provider | Overall | Fit | $/perf | Latency | DX | As of |
|---|---|---|---|---|---|---|---|
| 1 | WorkOS | 8.7 | 9.2 | 7.5 | 9.0 | 9.4 | 2026-09-14 |
| 2 | Nango | 8.2 | 8.4 | 8.0 | 8.2 | 8.6 | 2026-09-14 |
| 3 | Trigger.dev | 8.1 | 7.8 | 8.2 | 8.0 | 9.2 | 2026-09-14 |
| 4 | ComposioDepot Pick | 7.8 | 8.2 | 7.5 | 7.8 | 8.8 | 2026-10-19 |
Score methodology for this job
No first-party Calendar SaaS in Depot — pick is tool-router based. Confidence: medium; verify Composio calendar actions + scopes before pilot.
capabilityFit: 22%pricePerformance: 14%latencyReliability: 14%developerDx: 28%privacyPosture: 8%lockInRisk: 6%maturity: 8%