Feature · Calendar integration
Calendar integration through one signed webhook.
PyAI has no calendar of its own. Your agent reads and writes your calendar through one registered custom tool, whether users talk in an app, on a website or on a phone line.
What PyAI gives you for calendar integration
- Calendar integration on PyAI runs through one custom webhook tool you host, which the voice agent calls mid-conversation to read free slots and write an event after the user agrees.
- No native Google Calendar, Outlook or Calendly connector ships with PyAI today, so every calendar is reached through an HTTPS endpoint you build and register once per organization.
- Your endpoint gets 5 seconds to reply, write tools must report explicit success before the agent confirms, and an idempotency key on every request lets your code return the first result instead of booking twice.
- The tool call log records time, tool, agent, success and latency per request, which is the first place a slow or broken calendar integration shows up.
What does a calendar tool call look like from your endpoint?
Three invented requests show the documented server tool path, as your endpoint would see it. The lines are an example script, not a recording.
Pick a moment, then press play
How does an AI calendar integration call your API?
On PyAI voice infrastructure, each calendar request goes through one tool that calls your API. Your API gets signed, checked requests. The user keeps talking while the tool runs.
Model picks the tool
The reasoning model calls your registered tool by name with arguments, such as a date and a staff member.
Runner validates
The isolated runner resolves your endpoint, decrypts its auth secret, checks arguments against the input schema and refuses private network addresses.
Signed POST
PyAI sends an HMAC-signed request carrying an idempotency key and waits up to 5 seconds for your answer.
Result and log
Your response returns to the agent, and PyAI records the call in the tool call log with success and latency.
Endpoint answers
The agent continues its reply with the times or the confirmation your calendar returned.
Endpoint fails or stalls
A structured error reaches the agent, which explains the problem to the user instead of inventing a time.
What can a voice agent do with a calendar integration?
Most integrations need only two or three tools. The examples below span apps, websites, kiosks and a phone line.
Read and write tools
A clinic's endpoint wraps Google Calendar: a free-times tool reads busy events for a dentist, and a booking tool writes the visit after the patient agrees by phone. The endpoint rejects any slot that overlaps an existing event.
Arrival windows
A plumbing firm's website agent calls a tool that returns two-hour windows rather than exact times, computed from technician routes the firm already plans in its dispatch calendar.
Client tool
A fitness app runs the agent inside its own screen and registers a class-times lookup as a client tool, answered by the app over the session socket within 5 seconds.
Room reservations
A library lobby kiosk lets a visitor ask for a study room by voice. A read tool lists free rooms for the next two hours, and a write tool holds one in the room calendar.
After-session delivery
A sales team does not book during demos of the voice bot. Post-call extraction pulls the requested meeting time, and a Zapier destination passes it to the rep's calendar workflow.
Calendar integration questions people ask
How do you choose a calendar integration app?
The right calendar integration app depends on which calendars you use and what must stay in sync. Results reviewed in October 2026 were led by scheduling vendors whose help pages explain calendar connections. For AI voice agents, the deciding factors are live availability checks, conflict checks at write time and clear error logs.
How do I integrate all my calendars?
Most people connect every calendar account inside one calendar app, or use a scheduling tool that checks several calendars for conflicts. Choose one-way sync to copy events into a main calendar, or two-way sync to mirror changes. A PyAI agent then needs only one endpoint that reads that combined busy time.
How do I add a Google Calendar integration to a voice agent?
PyAI has no built-in Google Calendar connector, so you host a small endpoint that uses Google's Calendar API to read busy times and create events. Register that endpoint as a PyAI custom tool with an input schema and auth header, store the signing secret, and switch the tool on for the agent.
Can a PyAI voice agent book into Google Calendar?
Yes, through an endpoint you host. You register a custom webhook tool that fronts the Google Calendar API, and the PyAI voice agent calls that tool during the conversation to read free times or create an event. PyAI signs, validates and logs every request. No native Google Calendar connector is documented.
PyAI is voice infrastructure. It hands you the audio and transcript, and does not replace your own models or review tools.