Skip to main content

Overview

Friday can read, create, and modify resources across Google Workspace, including Calendar, Gmail, Drive, Docs, and Sheets. Each service requires a one-time OAuth authorization the first time you use it. This least-privilege approach ensures Friday only requests the specific permissions needed for each service.

Available services

  • Search calendar events by date, keyword, or attendee
  • Check availability across calendars
  • Create events with attendees and Google Meet links
  • Modify or cancel existing events
  • Retrieve meeting details and attendee lists
  • Identify scheduling conflicts
Example: “Every Monday at 8am, check my calendar for the week ahead and email me a briefing on each meeting with attendee background research.”

Prerequisites

  1. A Google Workspace (or personal Google) account that has permission to install third-party apps.
  2. Access to the Google “Apps” directory for the account (the OAuth screens will be shown there).

Step-by-step guide

Friday will detect when a request needs a Google service and will prompt you to complete the OAuth flow.
1

Start with a real Google request

Phrase a prompt that tells Friday what you want to do in a Google product. This gives Friday the context it needs to request access.Example prompts:
  • “Create a calendar event on Friday at 10 am titled Team Sync and invite the #marketing channel.”
  • “Send a weekly email to myself with the subject Weekly Report and attach the most recent file in Weekly Reports folder from Drive.”
  • “Edit the Project Brief Google Doc for any grammar errors or misspellings.”
  • “Add a row to the Leads Google Sheet with name Bob and email bob@example.com.”
2

Start the OAuth flow

  • Click Connect Google … button that Friday presents.
  • You will be redirected to Google’s OAuth screen.
3

Authorize Friday

  • Select the Google account you’d like to connect.
  • Review the scopes listed for the requested service.
  • Click Allow.
  • Google redirects you back to Friday with a confirmation.
4

Continue your task

After authentication, the task you’ve set up in step 1 will continue automatically, and Friday will now be able to interact with your Google-based requests.
5

Use Google services in future tasks

After authorizing a service, that service works automatically in future tasks. If you later use a different Google service (e.g., you authorized Calendar but now need Drive), Friday will prompt you to authorize that service once.
Why separate authorizations? Each Google service (Calendar, Gmail, Drive, Docs, Sheets) has its own OAuth scope. By authorizing services individually, Friday only ever has access to what you’ve explicitly approved — not your entire Google account. Each service receives the minimum scope needed for its full feature set. For example, Gmail requires modify access to support sending, drafting, and label management. Drive requires the drive scope (full access) because the Google Drive API does not offer a more granular write scope — this is a Google API limitation, not a Friday design choice.

Security and permissions

  • Token storage: Friday stores the Google OAuth token securely; the raw token is never exposed to you.
  • Least-privilege scopes: Each service receives the minimum scope needed for its full feature set (e.g., Calendar gets calendar access, Gmail gets modify access for sending and label management).
  • Revoking access: Removing the Friday app from your Google account instantly disables all Google Workspace actions for Friday.

Revoking access

To remove the Google app token from Friday:
  1. In Friday, go to Settings → Integrations.
  2. Find the Google app you’d like to revoke access and click Remove.
To remove Friday from your Google Account:
  1. Go to Google Account → Security → Third-party apps with account access.
  2. Find the entry named Friday (or the name displayed on the OAuth consent screen).
  3. Click Remove Access.
After revocation, any future Friday request that involves a Google service will trigger the OAuth flow again, requiring you to reconnect.

Next steps