Docs: Coding Agent Setup Prompt

Registering an OAuth app means clicking through a console you may not know well. Paste one of these prompts into a coding agent and it will walk you through that console one step at a time, with Recal's requirements — the redirect URL, the permissions, what to copy — already filled in.

The Recal dashboard's setup checklist offers a shorter version of the same prompt with your dashboard's own redirect URL substituted. This is the fuller one.

Before you paste

Each prompt uses the dashboard's hosted callback, https://dash.recal.dev/oauth/<provider>. That address works for connecting calendars from the dashboard; if you run your own callback, replace it — in the prompt and in Recal — before you start. Whatever you pick, the redirect URL registered with the provider must match the one entered in Recal exactly.

I am setting up Recal (a unified calendar API, https://recal.dev) and need to connect Google Calendar. Walk me through creating an OAuth app in the Google Cloud Console step by step, one step at a time, and wait for me to confirm before moving on. Ask me what I already have before you start.

Context about Recal you should assume:
- Recal is the OAuth client. My users grant it access to their Google Calendars through my own OAuth app; Recal stores the tokens and makes the calendar calls.
- Recal asks for one of three scopes and expands it into Google permissions itself. I do not configure scopes in Recal; the consent screen just has to permit them:
  - free-busy: userinfo.email + calendar.freebusy (busy intervals only, no event details)
  - read: userinfo.email + calendar.readonly
  - write: userinfo.email + calendar.events + calendar.readonly
- The redirect URL I register in Google must be byte-identical to the one I enter in Recal. I will use the Recal dashboard's hosted page: https://dash.recal.dev/oauth/google

What I need at the end:
1. A Google Cloud project with the Google Calendar API enabled.
2. An OAuth consent screen. Tell me when to pick External (my customers are outside my Google Workspace) versus Internal, and which fields are required. Remind me that Testing mode expires refresh tokens after about 7 days and that I must publish to Production before launch.
3. An OAuth client ID of type Web application whose Authorized redirect URIs contains exactly the redirect URL above, character for character: same scheme, host and path, no trailing slash.
4. The Client ID and Client Secret of that client.

Then tell me to paste the client ID, the client secret and the same redirect URL into the Recal dashboard under OAuth Credentials, on the Google card, and save.

Done looks like: the redirect URL in the Google Cloud Console and in Recal are identical, and connecting a calendar from the Recal dashboard ends on a "Connected" page. If Google shows redirect_uri_mismatch, the two URLs differ. If a connection stops working after about a week, the consent screen is still in Testing mode.

The manual walkthroughs cover the same ground without an agent: Google setup and Microsoft setup. If a connection fails after everything is saved, see reconnecting a calendar.