Update event with the Google Calendar API

Changes 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.

Identifier
google_calendar_update_event

The request

POST https://connect.reportei.com/api/tools/google_calendar_update_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>",
    "eventId": "<eventId>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
calendarIdstringYesCalendar id from List calendars, or primary.
eventIdstringYesEvent id, from List events. The id of a recurring event changes the whole series; the id of one instance, listed with singleEvents true, changes only that one.
sendUpdatesstringNoWho receives an email about the change.Values: all, externalOnly, none
conferenceDataVersionintegerNoSend 1 together with conferenceData. With the default, 0, the conference in the body is ignored.
summarystringNoTitle of the event.
descriptionstringNoDescription of the event.
locationstringNoFree-form location.
startobjectNoWhen the event starts: dateTime for a timed event, or date for an all-day event.
endobjectNoWhen the event ends: dateTime for a timed event, or date for an all-day event.
attendeesarrayNoThe full list of people invited to the event.
recurrencearrayNoRRULE, EXRULE, RDATE or EXDATE lines of RFC 5545 for a recurring event, for example RRULE:FREQ=WEEKLY;BYDAY=MO;COUNT=10. A recurring event needs timeZone in start and end. DTSTART and DTEND lines are not accepted.
conferenceDataobjectNoVideo conference of the event. For a new Google Meet link send createRequest, with conferenceDataVersion 1. The link comes back in hangoutLink and in conferenceData.entryPoints.

Supported connections

Your customer connects their Google Calendar account once, with one of the modes below. The same connection serves every tool of the toolkit.

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.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/google_calendar_update_event. It becomes your agent's tool definition with no conversion.

Other Google Calendar tools

See all 8 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.