powered by

Connect Google Calendar to create events from workflows

Updated Sep 30, 2026
Set up a Google OAuth client and connect Google Calendar so workflow steps can create, list, update and delete calendar events, with Google Meet links.

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.

1. Set up the Google OAuth client

In the Google Cloud console:

  1. Create or select a project, then enable the Google Calendar API under APIs & Services › Library.
  2. Configure the OAuth consent screen if you haven't already. While the app's publishing status is Testing, add each Google account you'll connect as a test user.
  3. Under Credentials, create an OAuth client ID of type Web application, or open the client your project already uses for Google sign-in.
  4. Copy the Client ID and Client Secret. You'll add a redirect URI in the next step.

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.

2. Connect Google Calendar

In the Anythink dashboard

  1. Go to Settings › Integrations and open the Integrations tab.
  2. On the Google Calendar card:
    • If it shows Not Configured, select Configure & Connect. Add the callback URL from the dialog to your OAuth client's Authorized redirect URIs, paste the Client ID and Client Secret, and select Save.
    • If it shows OAuth Configured, your project's Google sign-in credentials are being reused. Add the integrations callback URL, https://<your dashboard domain>/org/<project id>/settings/integrations/callback, to that OAuth client's Authorized redirect URIs, then select Connect.
  3. Approve access on Google's consent screen. The card now shows Connected.

With the CLI

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:

bash
anythink integrations oauth configure google-calendar --client-id <CLIENT_ID> --client-secret <CLIENT_SECRET>

Then connect:

bash
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 google on a project that already uses Google sign-in. It replaces the saved Google client IDs, including the ones your mobile apps sign in with.

With an AI assistant (MCP)

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

3. Create an event from a workflow

Add an Integration step, choose Google Calendar and the operation Create Event, then fill in the inputs. As JSON:

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.

Verify

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.

Variations

Next steps

Connect Google Calendar to create events from workflows | Anythink Docs