Skip to content
NewSee how

Connect Google or Outlook Calendar

Connect a calendar via OAuth so meeting-booking campaigns can put times on your real calendar. With auto-provisioned Teams links on Outlook.

Tutorials
Integrations
min read
5 min
steps
7 · Beginner

  1. Connectors → Add Connector → Calendar

    Open Connectors, click Add Connector, and pick the Calendar category.

  2. Choose Google or Outlook Calendar

    Select Google Calendar or Outlook Calendar. Both connect by OAuth: no password stored.

    Choose Google or Outlook Calendar

  3. Click Connect and grant access

    Click Connect Google Calendar (or Outlook). A popup opens for consent; grant calendar access: the card shows “Waiting for … consent…” until you finish.

  4. Confirmation

    When consent completes, the popup closes and a toast confirms “Google Calendar connected!” (or Outlook). The connector now appears in Connectors.

  5. Test the connection

    Open the calendar connector and click Test Connection: it reports how many calendars are accessible, confirming FirstSales can read and write your calendar.

  6. Attach it to a meeting campaign

    With a calendar connected, meeting-goal campaigns can offer and book real times. Outlook additionally auto-provisions a Teams link on each booked meeting.

  7. Reconnect if it lapses

    If OAuth authorization expires, reconnect the calendar the same way you would a mailbox: see the reconnect tutorial.

Pro tips

  • Connect the calendar before launching a meeting campaign

    The booking step depends on it: connect first so autopilot doesn't stall at the scheduling step.

  • Outlook gets Teams links for free

    The Outlook connector auto-provisions a Teams online meeting on each booking: pick it if you run Teams calls.

  • Allow popups for OAuth

    The consent window opens as a popup; if it's blocked, the flow falls back to a full-page redirect: either way, complete consent to finish.

  • Test after connecting

    The accessible-calendars check confirms permissions actually stuck before you rely on it in a live campaign.

Frequently asked questions

Which calendars can I connect?

Google Calendar and Outlook Calendar, both via OAuth.

Why connect a calendar at all?

So meeting-booking (autopilot) campaigns can offer and place real times on your calendar.

What's different about Outlook?

Outlook bookings auto-provision a Microsoft Teams online meeting link.

Is my password stored?

No: calendar connect uses OAuth, which stores a revocable token, not a password.

The consent popup was blocked: what happens?

FirstSales falls back to a full-page redirect to complete OAuth; just finish granting access.

How do I know it worked?

A “… Calendar connected!” toast appears, and Test Connection reports the number of accessible calendars.

Does connecting a mailbox also connect its calendar?

No: the calendar is a separate connector. Add it explicitly under the Calendar category.

What if the calendar disconnects later?

Reconnect it via OAuth, the same way you would a mailbox.

Integrations

Outreach that keeps going after you log off.Leads, emails, follow-ups and replies, handled.

Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo.

Start your $1 trial See pricing

$1 for 3 days · Cancel anytime · No contract

Install with AI

Your coding agent sets up the FirstSales CLI and skills for you.

Prompt for Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.
Developer docs ↗npm: @firstsales.io/cli ↗GitHub: firstsales-skills ↗