Connect a Google account's calendar so a workflow's Integration step can run Create Event, List Events, Get Event, Update Event or Delete Event.
Google Calendar uses Google as its parent provider. If your project already has Google sign-in set up, Google Calendar can reuse that OAuth client — you add one redirect URI and connect. Otherwise, give Google Calendar its own OAuth client. How integrations work explains parent providers.
In the Google Cloud console:
Anythink requests the https://www.googleapis.com/auth/calendar and https://www.googleapis.com/auth/calendar.events scopes, with offline access so it can refresh the token.
https://<your dashboard domain>/org/<project id>/settings/integrations/callback, to that OAuth client's Authorized redirect URIs, then select Connect.Add http://localhost:8745/callback to the OAuth client's Authorized redirect URIs. If your project doesn't use Google sign-in yet, save the client for Google Calendar:
anythink integrations oauth configure google-calendar --client-id <CLIENT_ID> --client-secret <CLIENT_SECRET>
Then connect:
anythink integrations oauth connect google-calendar --name "Team calendar"
anythink integrations oauth status google-calendar shows whether a client is configured, including one inherited from Google sign-in.
Warning: Don't run
oauth configure googleon a project that already uses Google sign-in. It replaces the saved Google client IDs, including the ones your mobile apps sign in with.
Connect Google Calendar to this project with the anythink CLI and tell me the connection ID.
The assistant calls the cli tool with integrations oauth connect google-calendar. Google's consent screen opens in your browser, so this needs the MCP server running locally in stdio mode.
Add an Integration step, choose Google Calendar and the operation Create Event, then fill in the inputs. As JSON:
{
"summary": "Kickoff call with {{ $anythink.trigger.data.customer_email }}",
"startDateTime": "{{ $anythink.trigger.data.starts_at }}",
"endDateTime": "{{ $anythink.trigger.data.ends_at }}",
"timeZone": "Europe/London",
"addGoogleMeet": true,
"sendUpdates": "all"
}
startDateTime and endDateTime must be ISO 8601 date-times. The event is created on the connected account's primary calendar. The step returns the event's id, htmlLink and, with Add Google Meet, a meetLink.
Run Test Workflow with a sample record, then check the event appears on the connected Google Calendar. The step's output in View Job History includes the event id.
id on the record, then pass it as eventId to Update Event or Delete Event. Integration recipes for Slack and Google Calendar has a complete booking workflow.