Onboarding guide

Create or sign in to Cal.com and connect with OAuth

This is the lowest-friction setup path for new tenants. It shows the exact consent screens, highlights the account-selection step that trips teams up most often, and brings you back to Amfion without handling an API key manually.

Screenshot walkthroughUsually 2 to 3 minutes

This is the fastest Cal.com setup path for Amfion. Start from the integrations page, stay signed into the right Google or Cal.com account, approve both calendar permissions, and return without handling a manual API key.

Start from Amfion

Click Continue with Cal.com from the Integrations tab and follow the prompts in order.

Use the correct account

The biggest setup mistake is approving the wrong Google account. Verify the email every time.

Approve both permissions

Cal.com needs both calendar permissions for reliable availability and booking actions.

Before you click Continue with Cal.com

The flow is quick once the correct account is in place. Most OAuth setup issues happen because the wrong Google login is active before the redirect starts.

  • Be signed into the Google or Cal.com account you want connected before clicking Continue with Cal.com.
  • If you manage multiple Google accounts, use a private window or switch accounts first to avoid linking the wrong calendar.
  • If you do not already have a Cal.com account, this sign-in flow is still the fastest setup path.
Prefer the API key path?Full Cal.com guide
Cal.com sign-in screen prompting the user to continue with the selected Google account
Step 1

Continue with the Google account you want connected

Start the OAuth flow from Amfion, then confirm the Google account on the Cal.com sign-in screen before continuing.

  • Use the same Google account that owns or manages the calendar you want Amfion to read.
  • Double-check the email shown on screen before clicking Continue.
  • If the wrong Google account appears, back out and switch accounts first.
Google permissions screen requesting calendar access for Cal.com
Step 2

Approve Cal.com calendar access

Google will ask you to grant Cal.com access so it can check availability and create bookings on your calendar.

  • Select both calendar permissions before continuing.
  • If Google shows a Select all shortcut, use it to avoid missing one of the required permissions.
  • These permissions are what allow Amfion to offer real-time booking through Cal.com.
Google permissions screen showing both required calendar permissions selected for Cal.com
Step 3

Make sure both permissions stay selected

This is what the permissions screen should look like before you move forward with the OAuth flow.

  • Both calendar access boxes should remain checked.
  • If only one permission is selected, availability checks or booking creation can fail later.
  • Once both permissions are selected, click Continue.
Amfion authorization screen asking the user to allow access to the selected Cal.com account
Step 4

Allow Amfion to access your Cal.com account

On the final screen, confirm the Cal.com account one last time, then allow Amfion to complete the connection.

  • The email shown here should still be the account you want connected to Amfion.
  • Click Allow to return to Amfion automatically.
  • There is no API key to copy in this flow. The connection is completed through OAuth.

Final step

Return to Amfion and finish the connection

Once you approve the final access screen, Amfion should bring you back to the integrations page and mark the account as connected.

  1. 1Start in Amfion Settings > Integrations and click Continue with Cal.com.
  2. 2Complete the consent screens shown above without switching accounts mid-flow.
  3. 3Wait for Amfion to return to the integrations page and show Connected.
  4. 4Use Sync Services or Import Existing Cal Event Types once the connection is live.

If OAuth does not complete

  • If the wrong Google account keeps appearing, sign out of the extra account, switch accounts in Google first, or retry in a private window.
  • If the flow returns to Amfion without connecting, restart the OAuth flow from Integrations and complete all permission prompts again.
  • If your team prefers manually managed credentials, use the API key fallback guide instead.

Need the manual path instead?

If your team wants full manual control of credentials, or if OAuth is unavailable on your deployment, the API key guide covers the fallback path step by step.

Open API key guideOpen Cal.com