How to Create Routines & Automations in Google Home

In the Google Home app, a routine is a saved set of actions that runs when something you choose happens — you say a phrase, a clock hits a time, the sun sets, or a device changes state. You build one by opening the Automations area of the app, picking a starter (the trigger), adding one or more actions, and saving. Google offers two paths: simple Household routines built with taps, and more powerful script-based automations for advanced conditions. This guide walks through both, explains why a routine sometimes silently fails, and shows how to keep them reliable.

Before you start: what you need

Routines live inside your Google Home structure, so a little setup pays off. If you're brand new to the ecosystem, our guide on setting up Google Home & Nest for the first time covers the groundwork.

• The latest Google Home app on your phone or tablet. Routine tools have moved between tabs over the years, so use the current build rather than following old screenshots.
• A speaker or display if you want to trigger routines by voice — "Hey Google" phrases need an Assistant-enabled device or your phone.
• Your smart devices already added to the home. You can't add a light to a routine until Google Home can see it. If a device won't join, our piece on smart devices that won't connect during setup may help.

Understanding starters and actions

Google's model is simple once named correctly: a starter is what kicks the routine off, and an action is what happens. A routine can have multiple actions, and script-based automations can even combine multiple starters and conditions.

Create a simple Household routine (tap-based)

This is the path most people want. It builds a routine without any code.

1. 1Open the Google Home app and go to the Automations area
2. 2Start a new routine and give it a clear name
3. 3Choose one or more starters (a voice phrase, a time, sunrise/sunset, or a device event)
4. 4Add your actions in the order they should run
5. 5Save, then test it by triggering the starter

1. Open Automations. In the Google Home app, look for the Automations section (it has lived under its own tab and inside settings at different times — browse the main tabs if you don't see it).
2. Create a new routine and name it something you'll recognize, like "Movie night" or "Leaving home."
3. Add a starter. For a voice routine, type the exact phrase you'll say — and add variants ("good night," "goodnight," "bedtime") so a slightly different wording still works.
4. Add actions. Common ones include adjusting lights, setting a thermostat, playing media, broadcasting a message to speakers, or having Assistant read your calendar and weather. Actions run top to bottom, so order media and announcements thoughtfully.
5. Save and test. Trigger the starter and watch what happens. Adjust the action order or add a short delay if things fire out of sequence.

Build an advanced automation with the script editor

When the tap builder can't express what you want — say, "turn on the porch light at sunset only if someone's home" — Google Home offers a script editor that uses a structured YAML-style format with starters, condition, and actions blocks.

• Multiple starters: any one of them can launch the automation.
• Conditions: logical checks (time ranges, device states, AND/OR) that must be true for the actions to run.
• Sequential and parallel actions: finer control than the tap builder allows.

The editor validates your script before saving and flags errors with line hints. It's text-based but approachable — start by copying one of Google's example scripts and changing the device names to your own. If you mix ecosystems, see how Matter multi-admin lets one device live in Google, Alexa, and Apple Home at the same time, which affects which device names appear here.

Why a routine doesn't run — and how to fix it

Routines fail quietly far more often than they error out loudly. Work through these in order:

1. Trigger device offline. If a sensor or plug is the starter and it dropped off Wi‑Fi, the routine never fires. Confirm the device shows as connected in the app first.
2. Phrase mismatch. Voice starters need a close match. Add extra phrasings and avoid words that sound like other commands.
3. Wrong home address or time zone breaks sunrise/sunset and scheduled routines — check your home settings.
4. Action device unavailable. The routine may start but skip an action whose device is unreachable. Test each device with a direct voice command.
5. Account or sharing mismatch. Members of a home may not see or trigger routines created by the owner depending on how they're scoped.

Coming from the other big ecosystem? The concepts map closely to Alexa's — our step-by-step Alexa routines guide and our Alexa vs Google Assistant comparison are worth a look if you run both.

Frequently asked questions

What's the difference between a routine and an automation in Google Home?

Google uses "Household routines" for the simple, tap-built kind and "automations" more broadly, including the script-editor type. In practice they're the same idea — a trigger plus actions — but the script editor adds conditions and multiple starters the basic builder can't handle.

Can a routine run on a schedule while I'm away?

Yes. Time, sunrise, and sunset starters are evaluated by Google's cloud, so they run whether or not your phone is nearby. Voice starters obviously require you to be within earshot of an Assistant device.

Why can other people in my home not use my routine?

Visibility and control depend on how the routine and the home are shared. Personal routines are tied to your account, while household routines are generally available to members. If a family member can't trigger one, confirm they're added to the home and that the routine isn't scoped to you alone.

Do I need a Nest hub for automations to work?

Not for voice and time-based routines. But some device-event starters, local conditions, and Thread-based devices benefit from — or require — a hub that doubles as a Thread border router. If device-triggered automations behave inconsistently, a hub often resolves it.

Sources

• Google Nest Help Center
• Connectivity Standards Alliance — Matter
• Thread Group — What is Thread