# A faculty member puts three kinds of email on scheduled Gemini Spark runs: invitations into the calendar, around 70 quota requests per term answered, and events compiled into a sheet

Gemini Spark · Reddit · No income, savings or cost is disclosed. The author names one access limit - Spark needs an AI Pro plan - without a price. The around 70 is email volume, not an amount.

## Business summary

Reddit user u/Cr-EEM, who describes himself as faculty, wrote up three Gemini Spark schedules he runs daily. First: he receives many mandatory meeting invitations and used to copy them into his calendar by hand; now a schedule recognises email from certain senders, reads it, and if it is an invitation that is mandatory to attend it adds it to his calendar along with the Zoom link or the place. Second: at the start of every semester he receives around 70 emails asking to increase his course quota, and the answer is always the same - he cannot do it, only the coordinator can - so a second schedule answers them. Third, and the one he says matters most to him: faculty have to record the activities, talks and events they attend, and he always forgot to put them in a sheet; now Spark searches his email, finds every event he confirmed he would attend and lists them in a Google Sheet. The only limitation he names is that Spark comes with an AI Pro plan. No income, savings or cost is disclosed, and the post gives no accuracy or failure rate for the automatic answers.

## Business value

The value is in how narrow the triggers are. The author never pointed Spark at the whole inbox; each rule matches specific senders or a specific subject, which is what keeps the cost of a misjudgement small. The second rule is the only one that sends anything outward, which makes it the riskiest: the same reply sent to the wrong person costs an apology, so it has to stop at a draft even though the original post describes it as automatic.

## Workflow

Keep the three email types as three separate rules, never one combined rule.

Each rule matches only specific senders or specific keywords.

Calendar writes can be automatic, but every event must carry a link back to the source email.

Automatic replies stop at drafts; nothing is sent without confirmation.

The activity list must carry source email and date so the backfill can be checked.

Log explicitly which messages were skipped and why.

Run a week in preview mode before enabling any write action.

## Preparation and limitations

The post gives no accuracy rate, no failure rate, no mis-send cases, no price and no token spend. It does not say how Spark decides that an invitation is mandatory, nor how the Google Sheet is connected. The workflow, prompt, synthetic example and pitfalls here are AgentFlow's proposals, untested.

## Starter prompt

````text
You are my email handling assistant, working to the three rules I define. You may read email, write to my calendar and sheets, and draft replies. You do not send any email or message, and you do not touch email outside the rule triggers.

[INPUT]
Rule A (invitations): trigger senders [list]; condition [for example must be a mandatory invitation]; write to calendar [name], including [time / place or meeting link / link to source email]
Rule B (repeated enquiry): trigger subject keywords [keywords]; standard reply points [for example I cannot change it, only the coordinator can]; output form [draft, sent only after I confirm]
Rule C (activity log): search scope [mailbox and time range]; target sheet [sheet and tab]; fields [event name / date / source email]
Left to me: confirming the judgement, confirming and sending any outward reply, checking the backfill

[EXECUTION STEPS]
1) Restate the three rules' trigger scope and targets; begin after that is acknowledged.
2) Handle only email matching a trigger. Skip anything else explicitly, recording how many were skipped and why; make no extra judgement.
3) Rule A: read the email and decide whether it is a mandatory invitation. If yes, write the calendar event with a link to the source email; if no, skip and record.
4) Rule B: for each matching email produce a reply draft listing recipient, the key point of the original, and the draft body, marked pending confirmation, not sent. Then stop and wait for me.
5) Rule C: find the events and talks I confirmed I would attend and write them to the sheet with source email and date.
6) Every run ends with a log: how many matched, how many were handled, how many skipped, and any email whose classification was uncertain.

[OUTPUT]
- Calendar writes: event / time / place or link / source email link.
- Reply drafts: recipient / key point of original / draft body / status pending confirmation, not sent.
- Sheet writes: rows added / each row event / date / source email.
- Run log: matched / handled / skipped with reason / uncertain message ids.

[HUMAN CONFIRMATION]
- Send no email, message or invitation reply; Rule B output stays pending.
- Do not touch email outside the trigger scope and do not widen the sender list or keywords.
- Any email whose classification is uncertain must be listed and handed back to me, never handled as the most likely case.
- Do not modify or delete existing calendar events or existing sheet rows.

[FAILURE AND MISSING INPUT]
- If a body cannot be read, a calendar write fails, or sheet permission is missing, record and skip; do not retry and do not guess content.
- If senders or keywords are missing, ask me; do not widen to related email.
- If Rule A finds an invitation but time or link is missing, put it in a pending list rather than creating the event.

[SYNTHETIC EXAMPLE - not real data, format only]
Input: Rule A senders Example Department Office; Rule B keyword course quota; Rule C search last term, write to Example Activity Sheet
Output (Rule A): Example weekly meeting / 04-24 14:00 / meeting link / source email msg-001
Output (Rule B): recipient Example student / key point requests a quota increase / draft "I cannot adjust the quota, please contact the coordinator" / pending confirmation, not sent
Output (Rule C): 3 rows added - Example lecture / 04-10 / msg-014; Example seminar / 04-18 / msg-027; Example defence / 04-22 / msg-033
Output (run log): matched 12 / handled 9 / skipped 2 (sender not on list) / 1 uncertain
````

## Costs and pitfalls

The post gives no accuracy rate, no failure rate, no mis-send cases, no price and no token spend. It does not say how Spark decides that an invitation is mandatory, nor how the Google Sheet is connected. The workflow, prompt, synthetic example and pitfalls here are AgentFlow's proposals, untested.

## Source and attribution

Cr-EEM（Reddit 用户 u/Cr-EEM，自述为高校教职，原帖作者本人） (u/Cr-EEM)
https://www.reddit.com/r/GeminiAI/comments/1wore7c/there_i_said_it_this_is_the_only_useful_feature/
2026-09-24
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
