An AI assistant connects to generic email, calendar, and permission symbols on a desk

Availability is the first question

On July 24, Meta announced a set of agent-style features powered by Muse Spark 1.1. The company says Meta AI can connect with email and calendar apps, plan multi-step work, produce scheduled briefings, run recurring tasks, research topics, and create slides.

The rollout began in select markets in the Meta AI app and at meta.ai. Meta did not publish a complete market list in the announcement, so the post is not confirmation that every account—or South Korea specifically—has access. More countries and surfaces, including WhatsApp, were described as coming in the following weeks.

A connection screen is a permission decision

Connecting an inbox or calendar may involve more than using an account to sign in. Google says third-party apps can request basic profile information or, depending on the granted scope, permission to view, modify, create, or delete Google Account data.

Read the products and actions listed on the consent screen one by one. If the requested scope feels broader than the job you want done—or the wording is unclear—you can stop without connecting it. The useful question is not how impressive the feature sounds, but whether you understand the access it needs.

A magnifying glass highlights one item in a generic connected-app permission list

Gmail and Google Calendar are details reported by Axios

Meta’s own announcement refers broadly to email and calendar apps. Axios identifies the connected services as Gmail and Google Calendar and reports that the assistant can use them for daily updates and research support. Keeping that attribution visible prevents a publication’s added detail from being mistaken for Meta’s exact wording.

The announcement also describes steering a report or presentation while it is being produced. Those are Meta’s descriptions of the intended experience, not independent proof that every integration performs equally well or can complete any open-ended task without supervision.

Start with a task that is easy to check

Use a low-risk calendar overview or a simple summary for the first run. Check the time zone, duplicated items, missing events, and where the result appears before you let the same instruction repeat.

Payments, contracts, health details, workplace secrets, and other sensitive material are poor first tests. Even if the assistant can be redirected while it works, a person should still review important decisions, messages, and calendar changes in the original service.

Recurring jobs need an end condition

Meta says a daily briefing or weekly plan can be set once and delivered on a schedule. That may reduce repetitive setup, but an old instruction can keep processing information after it stops being useful.

Write down what the task reads, when it runs, where the result is delivered, and when you will review or end it. Check every run during the first week, then keep only the automations that still have a clear purpose.

A checklist, clock, and simple workflow illustrate how to review a recurring AI task

Google provides a separate place to remove access

Google’s third-party connections page lets you select a linked app and inspect the Google Account access you granted. If you no longer use the connection, you can remove that access from its details.

Google warns that removing access can stop features that depend on the connection. Before disconnecting, decide whether you need to save any useful output. Then check the Meta AI side as well so an old recurring instruction is not left behind.

One last check

Five checks before connecting an inbox or calendar

  1. 01

    Confirm that the feature is actually available for your market and account.

  2. 02

    Read which email or calendar data the connection requests—not just the integration name.

  3. 03

    Begin with one low-risk recurring job whose output you can verify.

  4. 04

    Check dates, sources, and original calendar or email entries before relying on a briefing.

  5. 05

    Review the connection afterward and remove access when the integration is no longer useful.

Sources

Sources used for this article

Sources checked on July 27, 2026. Feature descriptions and rollout timing come from Meta’s July 24 company announcement. The specific Gmail and Google Calendar detail is attributed to Axios. Google’s help pages describe general third-party account controls; they do not verify Meta AI’s performance or data practices. Availability and requested permissions may vary by market and account. The article images are editorial concepts, not real Meta or Google screens.

Was this guide useful?

This browser can leave one heart per article.