SourceLace Docs
FAQOpen the app

Mail and calendar

How to connect Gmail and Google Calendar, or Outlook mail and calendar (Microsoft 365). SourceLace reads mail and calendars and can make email drafts. On Google Calendar it can also make, change and cancel events. It never sends email.

Status: Gmail and Google Calendar are Verified: tested on a real Google account. Outlook mail and calendar (Microsoft 365) is Available: built on Google's and Microsoft's published APIs, and validated in your account during onboarding.

At a glance

Connects through Sign-in Network Status First test question
Gmail and Google Calendar Gmail API and Google Calendar API Personal sign-in Nothing to open Verified "Show my 5 newest unread emails", then "What is on my calendar tomorrow?"
Outlook (Microsoft 365) Microsoft Graph Personal sign-in Nothing to open Available The same two questions.

Add each source with the usual steps. The network answers are explained in What your network needs. If the first test question fails, the error message tells you what to fix: look it up under When something goes wrong below.

What SourceLace can and cannot do

  • Read mail: search messages by sender, subject, words, dates, folder, unread or attachment, and read one message's plain-text body and attachment names. Message lists show sender, recipients, subject, date and a snippet, not the body.
  • Read calendars: events in a date range (up to a year at a time), with attendees, and the list of calendars.
  • Make drafts: with changes turned on for drafts, SourceLace can create an email draft after the person confirms the preview. The draft waits in the person's Drafts folder until they review and send it themselves. SourceLace marks its drafts, and only ever updates or deletes drafts it made, never a draft the person wrote and never real mail.
  • Make, change and cancel calendar events (Google Calendar): with changes turned on for events, SourceLace can put an appointment on the person's calendar and invite people, move or edit an event, or cancel it, each after the person confirms a preview that shows the event and who Google will email. Only events the person organizes can be changed or cancelled, and only one occurrence of a repeating event at a time. Outlook calendars are read-only. See Making, changing and cancelling events.
  • Attach files an agent made: an agent whose email draft action may carry files puts the Word, PowerPoint, PDF, Excel or CSV files it made on a new draft, at most 25 MB together so you can still send it (see Sending files the agent made). It is still only a draft. No other permission is needed: the draft permission covers its attachments.
  • Start agents: an agent can start when an email arrives in its owner's Gmail inbox or one of their labels, reading the owner's own mailbox with their own sign-in (see Start when an email arrives in Gmail). Gmail tells SourceLace about new email, so SourceLace does not keep asking.
  • Never: send email, delete messages, or change an event that someone else organizes.

Each person signs in with their own Google or Microsoft account, and sees only their own mailbox and the calendars their account can see. One sign-in belongs to one connection, so a second mailbox is a second connection. There are two ways to get one: for a mailbox the team shares (a support inbox), an admin adds a second Google Workspace or Microsoft 365 connection with a description that says what it is for, and each person signs in to it with the account they want there (Several connections of one system); for a mailbox of your own (a second work account, your personal mail), you add it yourself under My accounts on My connections, where your admin allows it (Your own accounts). Either way the AI sees both mailboxes by their labels and says which one it used, or asks.

Gmail and Google Calendar

Kind: Google Workspace (Gmail and Calendar) (google_workspace). No options.

How sign-in works. SourceLace has its own Google app for mail, calendar and files (separate from "Sign in with Google" to SourceLace). Each person signs in with their own Google account and approves these permissions:

Scope Why
https://www.googleapis.com/auth/gmail.readonly Read mail.
https://www.googleapis.com/auth/gmail.compose Make drafts. Asked for only where an admin turns on drafts for the source. Google has no drafts-only permission; this one would also allow sending, but SourceLace never sends, and refuses every call that is not on its short list of reads and draft calls.
https://www.googleapis.com/auth/calendar.readonly Read calendars.
https://www.googleapis.com/auth/calendar.events Make, change and cancel events. Asked for only where an admin turns on events for the source. Google has no permission for only the events SourceLace makes, so this one covers every event on the person's calendars; SourceLace changes only events the person organizes, after they confirm a preview, and refuses every call that is not on its short list.

People must tick every box on Google's consent screen. Where an admin turns on drafts or events after people have connected, each person connects the source again once to approve it; reading keeps working meanwhile.

What your admin does in Google Workspace

Nothing is registered: SourceLace provides the Google app. Your Google Workspace admin only makes sure people may use it. About 5 minutes.

Who: a Google Workspace super admin (or an admin with the Security settings and Services privileges).

  1. Check whether apps are restricted. In the Google Admin console: Security → Access and data control → API controls. If unconfigured third-party apps are blocked, or Gmail or Calendar is a restricted service, continue with step 2; otherwise skip it.
  2. Trust SourceLace. On the same page, Manage Third-Party App Access: find SourceLace (listed once anyone tried to connect; otherwise Add app and search for it), set its access to Trusted (or Specific Google data, allowing Gmail and Calendar), and Save.
  3. Make sure people have Gmail. Apps → Google Workspace → Gmail: Gmail must be ON for the people's organizational unit. People whose account has no Gmail (for example a Cloud Identity licence) cannot connect this source.

Check that it worked: one person connects, ticks every box on Google's page, and asks for their unread mail from today.

If Google shows an "unverified app" warning or refuses the sign-in, contact support@sourcelace.com. Google's own guide: Google Workspace Admin Help (search for "Control which third-party apps access Google Workspace data").

Outlook (Microsoft 365)

Kind: Microsoft 365 (Outlook mail and calendar) (microsoft365). No options.

How sign-in works. SourceLace uses its Microsoft app (the same one as "Sign in with Microsoft"). Each person signs in with their own work or school account and approves these delegated Microsoft Graph permissions, so SourceLace acts as that person with only their access:

Permission Why
offline_access Stay connected without signing in every hour.
User.Read Know who signed in.
Mail.Read Read mail.
Mail.ReadWrite Make drafts.
Calendars.Read Read calendars.

SourceLace does not ask for Mail.Send, so Microsoft itself would refuse to send mail for SourceLace.

What your admin does in Microsoft 365

Nothing is registered: SourceLace provides the Microsoft app. About 5 minutes.

Who: a Microsoft Entra admin who may grant tenant-wide consent (Global Administrator, Cloud Application Administrator or Application Administrator), and a Microsoft 365 admin for licences.

  1. Approve SourceLace once. If your organization does not let people approve apps themselves, the first person to connect sees Need admin approval. Connect once yourself and tick Consent on behalf of your organization, or open the Entra admin center → Enterprise applications → SourceLace → Permissions → Grant admin consent (or approve the request under Enterprise applications → Admin consent requests).
  2. Mailboxes in Exchange Online. Microsoft Graph reads only mailboxes in Exchange Online. People need a licence that includes Exchange Online (Microsoft 365 admin center → Users → Active users → the person → Licenses and apps); a mailbox still on an on-premises Exchange server cannot be read.

Check that it worked: one person connects and asks for their unread mail from today.

Microsoft's own guide: Microsoft Entra documentation (search for "Grant tenant-wide admin consent").

Add the source (SourceLace admin)

Add a Google Workspace or Microsoft 365 source on Connections. To allow drafts, turn on Allow changes: drafts is filled in under Objects that can be changed for you. On a Google Workspace source you can add events there too (drafts, events) to let people make, change and cancel calendar events; Microsoft 365 accepts only drafts. After you add events, people connect the source again once so Google can ask them for the extra permission.

What people can do

query takes one small JSON object (language json), checked strictly before anything is sent. describe_object on messages, events or calendars lists every key.

  • Mail: {"object": "messages", "from": "ann@corvanta.com", "subject": "renewal", "text": "pricing", "after": "2026-09-01", "before": "2026-10-01", "folder": "inbox", "unread": true, "has_attachment": false}. Every key but object is optional; folder is inbox, sent, drafts or any. Newest first, at most 100 messages.
  • Calendar: {"object": "events", "start": "2026-10-01", "end": "2026-10-15", "text": "QBR", "attendee": "corvanta.com", "calendar": "primary"}. start defaults to now and end to 30 days later, at most 366 days apart; at most 250 events, soonest first, with repeating events listed one by one. Times are in UTC.
  • Calendars: {"object": "calendars"}.
  • Searching everything: where it is on, Searching everything also searches your mail, together with your other systems.
  • get_record with messages and an id returns the plain-text body (up to 20,000 characters) and attachment names; with events, the full description (up to 8,000 characters).
  • Drafts: propose_change with object drafts and fields to, subject, body (plain text), and optionally cc and bcc (at most 50 recipients); then the person confirms.
  • Events (Google Calendar): propose_change with object events, then the person confirms. See below.

Making, changing and cancelling events

Ask in plain words, in the chat or in an agent: "Put a 30 minute renewal call with Ann and Bob at Corvanta on Monday at 9am", "Move the QBR to Tuesday at the same time", "Cancel tomorrow's sync". SourceLace shows a preview first: the title, the time, who is invited, and a note saying who Google will email. Nothing is made or sent until the person clicks Apply (or, in an agent, until an approver does; see Approvals). An admin can let one agent act without approval, as for any other change.

  • Make an event: title, start and end are needed. Optional: attendees (email addresses; Google emails each an invitation), location, description, calendar (default: the person's main calendar; it must be one they can change), video_call (true adds a Google Meet link), notify (false: Google does not email the people invited, though the event still appears on their calendars) and time_zone.
  • Times: a time with its zone, such as 2026-10-12T09:00:00-07:00, or a time without one plus time_zone such as America/Los_Angeles. An all-day event uses dates, such as 2026-10-12, and ends the day after its last day; end may be left out for a single day. SourceLace tells the AI the time now and the time zone of the person's calendar, so "Monday at 9am" becomes a real time; if it does not know, it asks.
  • Change an event: propose_change with operation update, the event's id from an events query, and only the fields to change. To move an event give both start and end. attendees replaces the whole list. The preview shows each field as it is now and as it will be. If the event changed in Google after the preview, SourceLace stops and asks to propose again.
  • Cancel an event: operation delete, or update with status set to cancelled (agents cancel this way: they never delete). Google emails a cancellation to the people invited, unless notify is false.
  • Limits: only events the person organizes; one occurrence of a repeating event at a time (never the whole series); at most 50 people invited per event; a cancelled event cannot be changed. To answer an invitation someone else sent, use Google Calendar.
  • In an agent: add a Change records action on the Google source with the object events, the operations (create, update) and the fields the agent may set (add status to let it cancel). Its key in Agent settings is source|events.

When something goes wrong

Gmail and Google Calendar

What you see What it means What to do
"Sign-in was not completed: admin_policy_enforced. Your Google Workspace admin's policy blocks SourceLace from Gmail and Google Calendar ..." Your Workspace blocks unconfigured apps, or Gmail or Calendar for them. A super admin trusts SourceLace (step 2).
"Sign-in was not completed: access_denied. You chose Cancel on Google's page ..." The person cancelled, or left a box unticked. Connect again and allow every permission.
"Gmail is turned off for this Google account ..." Gmail is off for the person's organizational unit, or their account has no Gmail. Turn Gmail on (step 3), or connect with an account that has Gmail.
"Google did not grant .... Connect again and tick every box on Google's consent screen." A box was unticked. Connect again and tick every box.
"Google did not let SourceLace change calendar events, which your admin turned on. ..." The person unticked the permission to change events. Connect again and tick every box.
"Google: this sign-in does not allow that. Connect the source again and tick every box." (when changing an event) The person connected before an admin turned on events. Connect the source again once, and tick every box.
"SourceLace changes or cancels only events you organize. ..." The event belongs to someone else. Respond to it in Google Calendar, or ask its organizer.
"That is a whole repeating series. ..." The id is of the repeating series, not one occurrence. Use the id of one occurrence from an events query.
"That event is already cancelled." The event was cancelled before. Nothing to do.
"This event changed after you saw the preview. Propose the change again ..." Someone changed the event between the preview and Apply. Ask again; the new preview shows the event as it is now.
"start 'x' has no time zone. ..." or "'x' is not a time zone name. ..." The time has no zone or offset, or the zone name is not one Google knows. Give the time with its offset, or a time_zone such as America/Los_Angeles.
"You can only read the calendar '...', so SourceLace cannot add events to it." The person can only view that calendar. Choose a calendar they can change, or ask its owner for access.
"Google: this sign-in does not allow that. Connect the source again and tick every box." A permission was not granted. Connect again.
"Google: not found, or you cannot see it." The message, event or calendar does not exist, or the person cannot see it. Use ids from a query.
"Your Google sign-in has expired." The sign-in ended, or was revoked in the Google account. Connect again.
"Google sent back something other than data." or "SourceLace refused to make that call to Google." Google answered with something SourceLace cannot read as data (such as a web page), or the call was to an address outside Google, which SourceLace never makes. Try again shortly. If it repeats, contact support.

Outlook (Microsoft 365)

What you see What it means What to do
"Sign-in was not completed: AADSTS65001 ... Your Microsoft Entra admin approves SourceLace once ..." (or AADSTS65004, AADSTS90094, "Need admin approval") Your tenant does not let people approve apps, and no admin has approved SourceLace yet. An Entra admin grants admin consent (step 1).
"Microsoft sign-in failed: ..." Microsoft's own reason follows. Check step 1.
"Your mailbox is not in Exchange Online ..." The mailbox is on-premises, inactive, or the account has no Exchange Online licence. A Microsoft 365 admin checks the licence and where the mailbox is (step 2).
"Microsoft 365: not found, or you cannot see it." The message, event or calendar does not exist, or the person cannot see it. Use ids from a query.
"Microsoft 365: ..." (another message) Microsoft Graph's own words, such as an invalid filter. The AI usually fixes the query itself.
"Your Microsoft sign-in has expired." The sign-in ended. Connect again.
"SourceLace's Microsoft sign-in is not set up correctly." SourceLace's own Microsoft app is not configured properly on SourceLace's side. Contact support.
"Microsoft Graph sent back something other than data.", "Microsoft Graph returned an unexpected link." or "SourceLace refused to make that call to Microsoft Graph." Microsoft answered with something SourceLace cannot read as data, or pointed to an address outside Microsoft Graph, which SourceLace never calls. Try again shortly. If it repeats, contact support.
"Microsoft Graph did not say which draft it made." Microsoft did not confirm the draft SourceLace asked it to create. Look in your Drafts folder before trying again, to avoid a duplicate. If it repeats, contact support.

Both

What you see What to do
"SourceLace only creates email drafts here: use object drafts. It never sends email." Only drafts can be created in mail (Google Calendar events are the object events).
"SourceLace only changes or deletes drafts that it created." Drafts the person wrote themselves cannot be changed through SourceLace.
"Allow changes is on for ..., but Objects that can be changed is empty ..." or "Writes to drafts are turned off for ..." (or "Writes to events ...") A SourceLace admin turns on Allow changes with the object drafts (or events, on Google).
"The google_workspace connector is not set up on SourceLace yet..." (or microsoft365) SourceLace's Google or Microsoft app is not ready yet. Contact support.
"The files come to ..., more than Gmail's limit of 25 MB together ..." (or Outlook's) An agent tried to attach more than a draft can carry and still be sent. Nothing was made. Send fewer or smaller files, such as one file per draft.
"Files go only on a new draft." An agent may attach files only to a draft it makes, never to an existing one.
"Google asked SourceLace to wait and try again later." or "Microsoft 365 asked ..." (a delivery shows Retrying) Google or Microsoft is limiting requests for now. Nothing to do: SourceLace tries again by itself for up to a day.
"Microsoft Graph sent the upload to an unexpected address; stopping." Outlook answered a large file's upload in a way SourceLace does not trust. Nothing was sent; the half-made draft is removed on the next try. Retry from the run's Deliveries list; if it keeps happening, contact SourceLace support.