Agent and MCP guides ยท 2026-08-28
Gemini Spark with Gmail and Calendar: schedules, pausing and approval
Prepare a meeting plan from Gmail conversations with Gemini Spark, separating drafts, sending, calendar changes, schedules and stopping a task.
Start with preparation for Gmail and Calendar
To use Gemini Spark, begin with a task that reviews specific conversations, suggests suitable times and prepares reply text. Treat sending messages and creating events as separate decisions. Spark is the personal agent in Gemini Apps, not an LLMTR model or a developer API.
As checked on August 28, 2026, Spark requires a personal Google Account, age 18+, Google AI Pro or Ultra and Keep Activity; work/school accounts are unsupported. Check regional eligibility, plus the Google Workspace connection and available actions under Connected Apps.
A concrete task: prepare a book club meetup
Start with a single run that turns personal book club conversations into a meetup proposal. Replace the calendar name with the one in your account. This is an example instruction.
A bounded instruction to adapt in a Spark task
Review up to five Gmail conversations about the book club received in the past seven days.
Suggest two 45-minute slots next Saturday between 14:00 and 18:00 on my Personal calendar. Use Istanbul time.
Use only calendars and conversations you can access; do not assume other participants are available.
Show the reply text and proposed event title, date, time and participants only in this task. Do not save a Gmail draft.
Do not send or forward email; create, change or delete events; make reservations or payments. Ask for my separate, explicit approval first.
Do not open attachments or transfer data to other sites. Ask about missing information; say if no suitable time exists.Preparing a draft and changing an account are different steps
Google says Spark is designed to request review and confirmation for certain actions, including communications and data changes. Do not assume every step waits for approval. Prompt boundaries are not a perfect security guarantee either; supervise sensitive tasks.
Check recipients, dates and time zones before accepting. Someone mentioned in a conversation is not automatically an invitee. Old availability information may be outdated. A gap in your calendar does not prove everyone else is free.
| Stage | Requested output | User check |
|---|---|---|
| Review conversations | Short summary and open questions | Are any messages irrelevant or outdated? |
| Prepare a reply | Text shown only in the task | Are recipient, tone and date correct? |
| Propose an event | Title, duration and two options | Are calendar and participants correct? |
| Send or create | A separate, explicitly defined action | Review the full content and approve separately |
Schedule the task after checking its first result
Spark schedules support times or new messages matching a Gmail filter. Here, requesting the same preparation every Monday at 09:00 Istanbul time is easier to inspect than open-ended monitoring. Request the schedule in the existing task; check that saved instructions retain the sending and calendar restrictions.
Run times can be approximate; avoid this workflow for urgent invitation responses. Review the time and instructions under Schedules, checking for duplicates before creating another entry. For a daily digest, Scheduled Actions in Gemini chat are a separate option, not the same feature as Spark schedules.
Choose the appropriate pause or stop control
To pause future runs, open the entry under Schedules in Spark and choose Pause from More; Resume restarts it. To also end the current task, use Stop in the Spark text box.
Stop in the Chrome side panel may only halt browsing; Spark can try another tool or a remote browser. Do not treat shutting down your device as cancellation. Remote browser work can continue, and being offline may prevent you from interrupting an unexpected action.
Compare the completion message with the actual result
Compare the proposal with the source conversations. Resolve missing dates before accepting completion. If you later authorize sending or creation, open the relevant Gmail message or Calendar entry yourself to verify it.
Stopping does not necessarily retract a sent message or delete a created event. Check the existing state before rerunning to avoid duplicate invitations. Initially, exclude conversations containing health, payment or private customer information.
Frequently asked questions
Does a prepared reply get sent automatically?
This example asks for text only within the task. Sending is separate. Do not issue broad instructions on the assumption that the product requests confirmation for every action.
Will a task run immediately when an email arrives?
Gmail monitors can trigger on matching messages, but exact instantaneous execution is not guaranteed. Monitor urgent correspondence yourself.
Does Pause cancel a run already in progress?
Distinguish pausing a schedule from stopping an active task. Use Pause for recurring runs and Stop inside Spark to cancel the current task completely.