Gemini Spark is Google's assistant for jobs that run in the background, and a job starts as a sentence typed into the Gemini app. Because it runs in Google's cloud, it keeps working when your phone is off. In the US it comes with the $20 a month Google AI Pro plan. Everywhere else it needs a $100 to $200 Ultra plan, and it is not offered in the European Economic Area, the UK, Switzerland or Nigeria.
A rule that reads the message first
The photographer's job above has three steps: decide that an email is a real inquiry, pull out the name and date, and put them in two places. A person does the first step in a second, and it is the step a mail rule cannot do. Spark does it by reading the email the way a person would, which is why the other two steps can follow without anyone watching.
Gemini already had scheduled actions since June 2025, which run a prompt you choose at a time you choose, such as a morning summary of your calendar and unread mail. That works like an alarm clock. The example above works like a doorbell: it reacts to something arriving, then carries the work across Gmail, Sheets and Drive. Joining those steps together was possible before with automation tools, but someone had to build and maintain the chain. Now the build is the sentence.
The same shape fits many small jobs
Think of the jobs in a small business that never justified software and never got done well. A recruiter could ask Spark to log each application that arrives, with the name, the role and the date, and to save the CV in a folder for that role. At 40 applications a week and two minutes each, that is about an hour and twenty minutes back every week. A warehouse shift manager could have supplier delay emails turned into one sheet of late deliveries, so the morning plan starts from a list instead of an inbox.
Once a rule works, the wording is worth keeping. Google is replacing Gems with skills, which are reusable instructions you can add to a prompt by typing a forward slash and the skill's name. A recruiter's intake rule, written once and tested, then becomes something a colleague can use as well.
Start where a wrong answer is cheap
Spark will sometimes misread an email, and Google's own guidance is to keep logins and payment details out of the task thread. It also warns that when a job runs while you are offline, you may not be able to stop a wrong action before it finishes. A task you can follow from the progress panel in the thread, step by step, is safer than one you only see the result of.
That points to how to choose the first job. The best one is where the worst outcome is a wrong row in a sheet that you can fix on Friday. Jobs that send messages to customers or move money can wait until you have watched Spark get the small ones right for a few weeks.