All integrations

Run agents with Google Calendar

Connect Google Calendar once, and every run that names it works in Google Calendar on the account you connected.

Connect Google CalendarOpens Settings → Connections in the console.

What an agent can do in Google Calendar

Read calendars and create events.

Jobs on Rush that use Google Calendar

How Google Calendar connects

Google Calendar is a built-in app: you sign in with your Google account on its own page, through Rush's own app, so you register no OAuth app. The sign-in asks only for the scopes listed below, and the run's token reaches www.googleapis.com, the Google Calendar REST API.

Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.

After that, a run that names google-calendar in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.

Scopes the sign-in asks for:

  • https://www.googleapis.com/auth/userinfo.email
  • https://www.googleapis.com/auth/calendar.readonly
  • https://www.googleapis.com/auth/calendar.events
POST https://api.phoenix.so/me/connections

{
  "type": "app",
  "name": "google-calendar"
}

Whose Google Calendar account the agent uses

Your Google Calendar connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Google Calendar, and a run started with an API key uses the Google Calendar of the member who created the key.

To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Google Calendar, and that agent's runs use their account and nothing else: never yours, never another user's.

More Productivity integrations

Frequently asked questions

How do I connect Google Calendar to Rush?

Open Settings → Connections in the console and connect Google Calendar, or send POST /me/connections with {"type":"app","name":"google-calendar"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.

Does every run get my Google Calendar account?

No. A run gets your Google Calendar connection only when it names it in connections ("connections": ["google-calendar"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.

What can an agent do in Google Calendar?

Read calendars and create events. 5 published jobs use it; this page lists them.

Can my app's users connect their own Google Calendar?

Yes. Make each user an agent from your template, and they sign in to their own Google Calendar through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.

Keep reading