The useful mental model: the trigger and the Alexa routine can come from different places
Alexa is still responsible for the smart-home routine. Buttons for Alexa stores the command that starts it. The automation layer only decides when that saved command should be executed.
Example
Your Android phone detects that you have arrived home. The automation invokes Buttons for Alexa. Buttons for Alexa runs your existing Welcome home Alexa routine. The routine can keep controlling the lights, thermostat or other devices already configured in Alexa.
Three practical automation paths
Dedicated integration
Tasker
Add Buttons for Alexa as a Tasker plugin action, select the saved routine, then let a Tasker profile decide when to run the task.
Open the Tasker setup guideGeneric Android integration
External intents
Buttons for Alexa exposes external Android intents so another compatible app or automation engine can invoke a saved action without using the Tasker plugin.
Cross-ecosystem workflow
Google Home
When your Google Home automation setup can hand off to the exposed Android intent, Google Home can provide the trigger and Buttons for Alexa can continue the workflow by starting the Alexa routine.
Real automations that remove an actual repeated step
The best automations are not complicated demos. They remove a manual action you already repeat.
Arrive home → entrance lights and home scene
Problem: you arrive after dark and immediately open an app or speak the same command.
Automation: let a reliable arrival/presence trigger invoke the saved Welcome home Alexa routine.
Leave home → run your existing Away routine
Problem: checking lights, plugs and heating is one more thing to remember while leaving.
Automation: an Android or Google Home leaving-home workflow can call the Buttons for Alexa intent and trigger the Alexa Away routine you already trust.
Bedside NFC / shortcut → Bedtime
Problem: you want the night routine without speaking or navigating a smart-home app.
Automation: an NFC or shortcut workflow can invoke Buttons for Alexa and start Bedtime.
Alarm dismissed → start the morning routine when you actually wake up
Problem: a fixed 07:00 routine is wrong when your wake-up time changes.
Automation: let the phone event become the trigger for the Alexa Good morning routine.
Google Home event → Alexa-only routine
Problem: the event you want is available in your Google Home workflow, while the action/device you need is already organized inside Alexa.
Automation: use the Google Home side as the trigger, hand off through the external Android intent, then let Buttons for Alexa launch the Alexa routine.
Smartwatch button → Alexa routine while the phone stays in your pocket
Problem: the phone is nearby but your hands are occupied.
Automation: a compatible watch action can trigger the Android automation or external intent that calls Buttons for Alexa.
Context change → heating or cooling preset
Problem: you repeatedly switch between the same Home / Night / Eco smart-home presets.
Automation: let a time, presence or another trusted Android condition trigger the corresponding saved Alexa routine.
One external automation → a complete Alexa scene
Problem: your automation tool detects the right context, but Alexa already contains the best multi-device scene.
Automation: do not recreate the smart-home logic. Call Buttons for Alexa and reuse the existing Alexa scene.
How Google Home fits into the workflow
Think of Google Home as one possible trigger source, not as a replacement for Alexa. Buttons for Alexa is useful when your automation starts in the Google ecosystem but the smart-home action you want to reuse already exists as an Alexa routine.
The exact Google Home hand-off depends on the automation workflow you configure. Buttons for Alexa exposes the Android intent target; it does not replace Google Home's trigger logic or Alexa's routine editor.
Using external Android intents
Use the external-intent path when the app that should trigger the routine can invoke Android intents. Keep the setup simple:
- Create and test the routine in Alexa.
- Save and test its trigger command in Buttons for Alexa.
- Configure the external-intent integration for that saved action using the values exposed by Buttons for Alexa.
- Configure the other automation app to invoke that intent.
- Test the intent manually before attaching it to an automatic condition.
Do not copy random intent strings from the web
Use the current intent/action information exposed by the installed Buttons for Alexa version. This page intentionally does not hard-code package extras or parameters that could become stale.
Automate convenience; keep security-sensitive actions deliberate
Location and presence are useful triggers for lights, heating and scenes. For gates, garage doors, locks, alarms or other access-control actions, prefer an explicit tap or confirmation rather than an unattended geofence action.
If Alexa asks for a predefined PIN or another second input, configure Advanced → Optional answer to Alexa in the saved routine. See the follow-up answer guide.
For a gate or garage from the car, Buttons for Alexa now also provides a direct Android Auto integration, which is usually a clearer manual trigger than an automatic location rule.
Frequently asked questions
Can I automate an Alexa routine from Android?
Yes. Buttons for Alexa can expose a saved Alexa routine command to Android automation. You can use the dedicated Tasker integration or an external Android intent from another compatible automation workflow.
Can Google Home trigger a Buttons for Alexa routine?
Yes, when your Google Home automation setup can hand the action off to the external Android intent exposed by Buttons for Alexa. Google Home supplies the trigger; the intent calls Buttons for Alexa on Android; Buttons for Alexa then executes the saved Alexa routine command.
Do I have to use Tasker?
No. Tasker has a dedicated Buttons for Alexa plugin integration, but it is not the only automation path. External intents are available for compatible apps and workflows that can invoke Android intents.
What is the difference between Tasker and an external intent?
The Tasker plugin gives Tasker a dedicated routine-selection action. An external intent is a more general Android interface that other compatible automation tools can invoke. Both ultimately trigger an action already saved in Buttons for Alexa.
Can I automatically open my garage when I arrive home?
Technically an automation may be able to use location or another event as its trigger, but security-sensitive actions such as gates, garage doors, locks or alarms are better kept behind an explicit user action or confirmation. For a gate or garage while driving, the direct Android Auto integration is usually the clearer option.
Can a smartwatch trigger an Alexa routine?
Yes when the watch or its companion app can launch a compatible Android automation or external intent on the phone. The wearable is the trigger; Buttons for Alexa remains the Android bridge to the saved Alexa routine.
