Scheduling
Google Calendar in your product and your AI agents, through one API
The Google Calendar toolkit lists calendars, lists, reads, creates, updates and deletes events, checks free/busy intervals and creates secondary calendars. Through Connect, a product or AI agent schedules on the customer's calendar without building the Google OAuth flow or renewing tokens.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/google_calendar_create_event/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"calendarId": "<calendarId>",
"start": {},
"end": {}
}
}How it works
From a connected customer to the first Google Calendar call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their Google Calendar account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with Google Calendar.
Scheduling from your product
Create an event with attendees and a Google Meet link when a lead books a call, a client approves a post or a task gets a deadline.
Finding a free slot
Let an AI agent read the busy intervals of one or more calendars between two dates and propose times that work.
A calendar per client
For an agency tool, create a secondary calendar for each client, such as a content calendar, and add events to it as work is planned.
Tools
8 Google Calendar tools
- List calendarsGETLists the calendars on the user's calendar list. Use the id of an item as calendarId in the event tools. The id primary is the user's main calendar.
- List eventsGETLists the events of a calendar. Set singleEvents to true to expand recurring events, which is required to order by startTime.
- Create eventPOSTCreates an event. Use start.dateTime and end.dateTime for a timed event, or start.date and end.date for an all-day event. sendUpdates decides who is emailed about it. A Google Meet link needs conferenceData with conferenceDataVersion 1.
- Get eventGETReturns one event with its attendees and their responses, the Meet link in hangoutLink, and recurringEventId when it is an instance of a recurring event.
- Update eventPATCHChanges the fields sent and keeps the others. A list, such as attendees or recurrence, replaces the whole list, so send every attendee that should stay. sendUpdates decides who is emailed about the change.
- Delete eventDELETEDeletes an event. The id of a recurring event deletes the whole series; the id of one instance deletes only that one. sendUpdates decides who is emailed about the cancellation. The response is empty, status 204.
- Get free/busyPOSTReturns the busy intervals of one or more calendars between timeMin and timeMax, under calendars, keyed by calendar id. A calendar the user cannot see comes back with errors instead of busy.
- Create calendarPOSTCreates a secondary calendar owned by the user, such as a content calendar for one client. The id in the response goes in calendarId of the event tools.
OAuth with your product's app
You register your product's OAuth app once, with POST /api/merchants/credentials/google_calendar, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.
Questions about the Google Calendar toolkit
Do I need to build against the Google Calendar API?
No. Connect ships 8 Google Calendar tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their Google Calendar account?
With the mode the toolkit accepts: OAuth with your product's app. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
