docs(integrations): add Scheduling section — Cal.com, Calendly, Google Calendar - #392
Open
harshitajain165 wants to merge 7 commits into
Open
docs(integrations): add Scheduling section — Cal.com, Calendly, Google Calendar#392harshitajain165 wants to merge 7 commits into
harshitajain165 wants to merge 7 commits into
Conversation
…ogle Calendar New Scheduling section in the top-level Integrations tab, alongside Agent Framework / Agent Platform / Telephony / etc. - Cal.com: full page, grounded in the real atoms-platform catalog and tool registry (BYOK API key + event type, check_availability / book_meeting / reschedule_meeting / cancel_meeting tools). - Calendly: coming-soon stub, but documents the same four planned tools since it's built on the same architecture as Cal.com. - Google Calendar: bare coming-soon stub, no tool details yet. Neither Calendly nor Google Calendar exist in atoms-platform's integrations catalog yet — only Cal.com does — so those two are explicitly marked upcoming rather than documented as live.
|
crim doesn't review pull requests automatically here. Comment |
Same 3 planned tools as Cal.com/Calendly (check_availability, book_meeting, cancel_meeting), but noting Google Calendar will connect via OAuth (like Salesforce/HubSpot) rather than Cal.com's BYOK API key. Still marked coming soon — no catalog/tool-registry entry exists in atoms-platform yet.
Grounded in atoms-platform's calendly integration (commits 240826cea, 177297541, 98e9e2c40): personal access token + event type (BYOK-style token, not OAuth), tools check_availability / book_meeting / cancel_meeting. No reschedule tool — Calendly has no reschedule endpoint, only a hosted link a person visits directly, so that's called out under Good to know. Regenerated fern/llms.txt for the updated page description.
Grounded in atoms-platform's google-calendar integration (eabb837dd):
OAuth connect via the generic engine, not BYOK. Full tool surface per
the registry: check_availability, book_meeting, reschedule_meeting,
cancel_meeting, list_events ("List upcoming events") — the only
scheduling integration with a calendar-lookup tool. Unlike Calendly,
reschedule is a real single API call (Google's PATCH), called out
under Good to know. Operates on the primary calendar per the catalog.
Regenerated fern/llms.txt for the updated page description.
harshitajain165
marked this pull request as ready for review
August 25, 2026 13:16
|
crim doesn't review pull requests automatically here. Comment |
Cross-links now point exclusively at sibling scheduling pages (Cal.com <-> Calendly <-> Google Calendar) instead of mixing in CRM/Custom APIs links.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a Scheduling section to the top-level Integrations tab (alongside Agent Framework, Agent Platform, Telephony, SDKs & Libraries, Automation, Transcription Tools, AI Gateway), with three pages:
atoms-platformintegrations catalog and tool registry (BYOK API key + event type;check_availability/book_meeting/reschedule_meeting/cancel_meetingtools).Why this structure
Scheduling tools are an Atoms (voice-agent) product feature — "connect my agent to a calendar I already use" — not a developer-framework integration like LiveKit/Pipecat, so it lives in a new section rather than under an existing one. It's Atoms-only; not mirrored into the Waves (Models) product's Integrations tab, since raw Pulse/Lightning/Electron models have no agent-builder UI to "Connect" a calendar into.
Verification
atoms-platform'sintegrations-catalog.tsandintegration-tools.tsdirectly — only Cal.com exists today (BYOK, 4 tools). Calendly and Google Calendar have no catalog entry, tool registry entry, or client code, so they're documented as upcoming rather than live.fern check— 0 errors, no new warnings.Follow-ups (not in this PR)
crm/folder structure already on disk that could move into this same Integrations tab for consistency. Flagging for a separate PR.