Paste these into Muse after the Remote for Muse connector is set up. Start with "Start here": the first three make Muse check your wrist often and keep the watch quiet unless something needs you, and the fourth asks Muse what it could do for you. Then add the automations you want, change them to fit, and write your own. Each one says exactly what it will send to your wrist.
New here? Start with Make it your own: what Muse can do
on your Garmin, and how to write instructions of your own. Every automation follows
the noise contract. Entries marked
New in 1.1 use what Remote for Muse 1.1 added (workouts, routes, the Ride data field). 1.1 is out now: keep the app up to
date, and add the Remote (Ride) for Muse field from the Connect IQ store for the ride entries. New here?
Pair your device first.
Make it your own
Remote for Muse gives Muse a set of things it can do on your Garmin, and Muse decides when to use them from what you tell it. Out of the box, that's a reply when you ask something. Tell Muse more, in plain words, and your watch becomes what you need: a second screen for your business, a to-do list you can talk to, a coach that plans around your calendar, a way to answer people mid-ride. You say it once and Muse keeps doing it, together with everything else it can reach for you: your calendar, email, Slack or CRM. The more you tell Muse, the more your watch does for you.
What Muse can do on your Garmin
Replies
Answers in the conversation, with up to 3 follow-up buttons. send_reply
Cards
Briefings, recaps, meeting prep and travel cards. What Garmin measured stays apart from what Muse suggests. post_card
Questions
Up to 4 options to tap. Your tap is your answer. ask_question
Approvals
The action, the recipient, the cost and the details, with a confirm step. Muse acts only after you approve. request_approval
Tasks
What Muse is working on, with progress. Pause, resume or cancel from the watch. upsert_task
Status line
One short line on the glance, the watch face and the Ride data field, without a buzz. set_status
Quick prompts
Your Ask Muse menu: the 6 things you ask most. set_presets
Workouts
Structured sessions in your watch's own Workouts list. send_workout
Routes
Courses with waypoints for food, water and climbs, on a watch or an Edge. send_course
What Muse can see
Health data only if you share it, category by category, on the watch.
Your requests
What you say, type, note or tap on the watch. claim_inbox
Your body
Heart rate, resting heart rate, stress, Body Battery, Pulse Ox, respiration, steps, recovery time and VO2 max. get_latest_vitals, list_vitals
Your training
Finished workouts, and when you start and stop one (with the Ride data field). list_activities
Your settings
Quiet hours, coaching style and private display, so Muse stays inside them. get_preferences
Write your own
Write it the way you’d brief a sharp assistant, in four parts:
When
A time, a workout starting or ending, an email, a meeting, a number crossing a line, or a word you send from your wrist.
Do what
The work, with any app Muse can reach: check the calendar, draft the email, look up the account, plan the session.
Show what
What lands on your Garmin: a card, a question with options, an approval, a task, a status line, a workout or a route.
How loud
When it may buzz, and when it should wait or stay silent. The noise contract covers the rest.
Fill in, then paste into Muse
When <something happens>, <what you should do, and with which of my apps>. On my watch, <show me a card / ask me with options / ask for my approval / track it as a task / set my status / send a workout or route>. Buzz me only if <...>; otherwise <use low priority / wait for my evening wrap-up / send nothing>.
For example: “When a customer on my key-accounts list emails about an outage, check our status page and their open tickets. On my watch, ask me with options: "Call them", "Send update", "Later". Buzz me only during work hours; otherwise hold it for my morning briefing.”
Ideas to start from
Say any of these to Muse as it is, or change the names, numbers and times to yours.
Business
“When a deal over $50k moves stage in my CRM, post one card with the account, the new stage and the next step.”
“When someone asks me to sign off on a quote or an expense, send it to my watch as an approval.”
“Ten minutes before a customer call, put the account's last three emails and open tickets on one card.”
“On travel days, keep my flight on my watch: gate, boarding time, and a buzz only for changes.”
“Every Friday at 16:00, ask me which open deals to follow up on, and draft the emails I pick.”
Productivity
“When I send "Focus 50", mute Slack for 50 minutes and tell me afterwards what came in.”
“Every weekday at 7:30, put my three most important tasks on my watch.”
“Turn every voice note that starts with "idea" into a page in my notes, filed by project.”
“When I send "Walk inbox", show me today's email one at a time: archive, reply yes or later.”
“If my step count hasn't moved in two hours of work, find a gap and suggest a 10-minute walk.”
Workouts
“I'm training for a half marathon on 12 April. Plan my weeks around my calendar and send each session to my watch the evening before.”
“If my Body Battery is under 30 in the morning, swap my hard session for an easy one and tell me why.”
“After every long run, compare it with my last three and give me one thing to change.”
“When I'm travelling and have a free hour, send me a 20-minute hotel-room workout.”
“Before a race, send me the pacing plan as a workout, one step per split.”
Recovery
“If my stress has been high for an hour during work, suggest a 5-minute break at the next gap.”
“If my resting heart rate is 5 above my 7-day average, move my hardest workout and keep today light.”
“Every Sunday, show me my resting heart rate and Body Battery for the week on one card.”
Travel and outdoors
“When I arrive in a new city, send a 5 km running loop from my hotel to Courses.”
“On rides over 3 hours, warn me if a café on the route closes before I get there.”
“On evening runs, tell me when sunset is 30 minutes away.”
Home and family
“When the school messages me during a workout, show it right away; everything else can wait.”
“When I finish a ride, tell my partner I'm on my way, with my arrival time.”
“When I note something for the house ("call the plumber"), add it to our shared list.”
Keep teaching it
Name what matters: the people, accounts, numbers, places and times. "Email from my VIPs" works once Muse knows who they are.
Correct it from your wrist. Send "too much", "more like this" or "never buzz for that", and Muse keeps it as a rule.
Add one or two at a time and live with them for a few days. Each entry below says what it sends.
Whenever you connect a new app to Muse, ask it for ideas again ("Ask Muse what it could do for you", under Start here).
Once a month, ask Muse to list the standing instructions it follows for Remote for Muse, and drop the ones you don't use.
No need to repeat the safety rules: with the noise contract in place, anything that spends money, messages people for you or changes your calendar waits for your approval on the watch.
Nothing by itself; it's how your wrist messages reach Muse.
Needs
Approve get_audio in the Muse app the first time you send a voice message
Paste into Muse
Create a recurring scheduled task that runs every minute if you're allowed, otherwise every 5 minutes: call claim_inbox on Remote for Muse and handle every item. text and voice are requests (fetch voice with get_audio and transcribe it); note is something to save; activity_started and activity_stopped mean I began or ended a workout; activity_done carries the summary; control means pause, resume or cancel a task. Answer in the context of replyTo or taskId, with send_reply and inReplyTo. Then ack_inbox what you handled (a repeat with a higher attempt: just ack it). Stay silent when the inbox is empty. If you need my approval to use get_audio or another Remote for Muse action, tell me with send_reply. Tell me which interval you set.
Fewer, better buzzes: only approvals, questions and tasks that need me are high priority.
Paste into Muse
Rules for everything you send to Remote for Muse:
1. Only approvals, questions and tasks needing my input may interrupt me; the rest are normal or low priority.
2. At most 6 interruptions a day; between activity_started and activity_stopped, only approvals I asked for and safety or weather warnings.
3. Never send "nothing new"; if nothing changed, stay silent.
4. Several updates within 30 minutes become one card.
5. Read get_preferences daily; respect quietHours, coaching and privateDisplay.
6. Cards: at most 3 short sections. Replies: under 200 characters.
7. Don't repeat what's on my watch; dismiss stale cards.
8. Spending money, messaging for me or calendar changes need request_approval first, with cost and recipient.
Set my Remote for Muse presets to the 6 things I'm most likely to ask from my wrist. Start with: "What's next?", "Out running", "Back", "Coffee within 5 km", "Check my recovery", "Take a note". Every Sunday, replace any I haven't used with ones I'd actually use.
Nothing until you pick; then what the ones you pick say.
Paste into Muse
Look at the apps, calendars and data you can reach for me, and at what Remote for Muse lets you do on my Garmin: cards, questions, approvals, tasks, my status, quick prompts, workouts, routes, and my vitals and activities. Suggest 8 standing instructions that would save me the most time or help my training, across work, productivity, training and home. For each: when it runs, what you'd do, what reaches my wrist and whether it buzzes. Follow the noise contract. Set up nothing until I pick; then set up the ones I choose and tell me how to change or stop each.
Everyday tasks
Muse does the work; you only get a notification on your Garmin and answer it there. On a long run or ride you stay connected to your personal assistant: no taking out your phone, no waiting until you're back at your computer. Anything that books, pays or sends for you still waits for your approval.
One question with up to 3 options, one approval with the price, then a one-line confirmation.
Needs
Booking and calendar connectors in Muse
Paste into Muse
When I ask from my wrist to book something (a table, a bike service, a class, a court), find the 2-3 best options that fit my calendar and ask me with ask_question, one line each with time and price. Then request_approval for the one I pick, with the cost and who it's with, and book only after I approve. Track it with upsert_task so I see progress on my watch, add it to my calendar, and confirm with one send_reply under 120 characters.
While I'm training, for email from people who matter
What reaches your wrist
One question per important email, with short reply options; nothing for the rest.
Needs
Email connector in Muse
Paste into Muse
While I'm in an activity, or after I send "Out running", watch my inbox for email from my VIPs or anything marked urgent. For each, ask me with ask_question: the sender and a one-line summary, with options like "Yes, works", "Next week", "Call me later" and "Later". Draft a short reply in my tone for the option I pick and request_approval with the recipient before sending. Hold everything else for one summary after the workout.
One question; a message goes out only after you approve it.
Needs
Calendar and messaging connectors in Muse; the Ride data field for automatic starts
Paste into Muse
If my workout is going to make me late for my next meeting (activity_started and my calendar tell you, or I say so), ask me with ask_question: "Push 15 min", "Push 30 min", "Tell them I'm late" or "Join by phone". Do what I pick: move the event, or send the organiser a short note, with request_approval for anything that messages people. Confirm in one line.
When family or close friends message me while I train
What reaches your wrist
One question per message with quick replies; nothing is sent until you tap one.
Needs
Messaging connector in Muse
Paste into Muse
When someone on my family list messages me while I'm in an activity, show it on my watch with ask_question: who, the message in one line, and quick replies like "On my way", "Back in 30 min", "Call you later" and "Not now". My tap is my approval for that exact reply: send it word for word and nothing else. Anything longer or different goes through request_approval. If it sounds urgent, start the line with "Urgent:".
When I note something to buy, and when I finish a workout
What reaches your wrist
No buzz for notes; one low-priority card after the workout; an approval before any order.
Needs
Shopping list or store connector in Muse
Paste into Muse
When I send a note like "buy chain lube" or "out of coffee", add it to my shopping list without replying. When activity_stopped arrives, or at 18:00 if I haven't trained, post one low-priority card with what's on the list. If I ask you to order it, pick my usual product and request_approval with the price and delivery time before ordering.
One approval with payee, amount and due date; nothing is paid without it.
Needs
Bank or payments connector in Muse
Paste into Muse
When a bill, invoice or deposit is due within 3 days, request_approval on my watch with the payee, amount, due date and what it's for. Pay only after I approve, then log_action with one line. If I decline, remind me once the day before it's due. Never pay anything you can't show me a bill for.
When I ask something from my wrist mid-workout (trail conditions, sunset time, opening hours, a score, a fact to settle a bet), answer with one send_reply under 160 characters, answer first. Add up to 2 followUps only if a next step is likely. If it takes longer, set_status with what you're doing and reply when you have it.
Every day at 6:30, read get_latest_vitals and today's calendar, then post one Remote for Muse briefing card: what Garmin measured in a garmin section, your plan for today in a muse section, and anything missing in a missing section. If I'm not sharing vitals, base it on my calendar only and say so.
At most one question a day, only when a change would help.
Needs
Calendar connector in Muse
Paste into Muse
If my Body Battery is under 30 before 9:00, or my stress has been high for an hour during work time, propose one calendar change as an ask_question with two or three options (move, shorten, or keep). Prefer moving my hardest workout or an optional meeting. Change nothing until I answer; then do exactly what I chose and log_action it.
At most one card, low priority. Skipped on quiet days.
Paste into Muse
Every day at 20:00, if anything is still open (tasks, questions, tomorrow's first meeting or workout), post one low-priority recap card with at most 3 lines. If nothing is open, send nothing.
When an activity_done item arrives, wait until get_latest_vitals has a sample from after it, then post a debrief card: what Garmin measured, how it compares with my last similar session from list_activities, and one suggestion for tomorrow. Coaching, not medical advice.
When I ask, and the evening before planned sessions
What reaches your wrist
No alert; the workout appears in the watch's Workouts list.
Paste into Muse
When I ask for a session, or the evening before a session in my plan, build it with send_workout: warm-up, main set and cool-down as steps, with heart-rate, pace or power targets from my recent activities. Name it so I recognise it ("Thu tempo 3x10"). Don't send duplicates; check list_downloads first.
A question only when tomorrow's session looks too hard.
Paste into Muse
Each evening, if get_latest_vitals shows recovery over 48 hours or Body Battery under 25, ask me with ask_question whether to swap tomorrow's hard session for an easy one. If I agree, send the easier workout with send_workout and move the calendar block.
No alert for workouts (they land in your Workouts list); one question when the plan needs to change.
Needs
Calendar connector in Muse
Paste into Muse
I'm training for <event> on <date>; my goal is <a time, or to finish>. Build a week-by-week plan from my recent list_activities. Each Sunday, fit next week's sessions into free slots in my calendar; the evening before each, send it with send_workout (warm-up, main set, cool-down, with targets). If my recovery is over 48 hours, my Body Battery is under 25 or I miss a session, ask me with ask_question how to adjust. Taper in the last two weeks. Coaching, not medical advice.
Keep a running total of kilometres per pair of shoes and per bike from my activities (assume the current ones start today). At 650 km for shoes, or every 2,000 km for chain service, request approval to order or book it, with the price.
One card the evening before; the route lands in Courses.
Needs
Routing source in Muse
Paste into Muse
The evening before any ride longer than 2 hours in my calendar: build the route with send_course (with food and water waypoints), check the forecast along it, and post one card with start time, weather, kit and a fuel plan (grams of carbs per hour and what to carry).
When I ask for a route ("90 km gravel loop with a café at halfway"), plan it, then send it with send_course using points or GPX, with waypoints for food, water and big climbs. Reply with the distance and elevation in one line.
Only safety and weather warnings during the ride; one summary card after.
Needs
Remote (Ride) for Muse data field on the activity screen, with Share workouts on
Paste into Muse
While I'm in an activity (after activity_started, before activity_stopped), hold everything except approvals I asked for and safety or weather warnings. Use set_status for ride cues instead of alerts: it shows on my Remote (Ride) for Muse screen without buzzing. After activity_stopped, send one card with whatever you held.
No buzzes; the status line on the ride screen changes.
Needs
Remote (Ride) for Muse data field on the activity screen, with Share workouts on
Paste into Muse
During a ride, every 45 minutes after activity_started, set my status to a short fuel cue ("Eat: gel 2 of 5", "Drink 500 ml") based on the fuel plan. Clear the status after activity_stopped.
One warning only when rain, storms or strong wind arrive within 30 minutes.
Paste into Muse
During a ride, check the forecast for my area every 20 minutes. Only if rain, a storm or wind over 40 km/h is due within 30 minutes, post one card with priority high saying what and when. Otherwise send nothing.
When I send "Coffee within 5 km", find the best open café near my current ride and reply with the name and distance in one line. Then send it with send_course as a short course so I can navigate there.
None on the wrist; your Slack and email status change.
Needs
Slack and email connectors in Muse; the Ride data field (with Share workouts on) for automatic starts
Paste into Muse
When activity_started arrives, set my Slack status to "Out training, back around <end of my planned session>" and turn on an email auto-reply for VIPs only. When activity_stopped arrives, clear both. Also do this when I send the "Out running" and "Back" presets.
One card per meeting, normal priority, only for meetings with something to prepare.
Needs
Calendar and email connectors in Muse
Paste into Muse
Ten minutes before a meeting with an agenda or a decision, post one card: who, the one thing to decide, and the last relevant email in a line. Skip routine meetings.
When a note or voice item sounds like a to-do ("remind me to send the deck"), add it to my to-do app with a due date if I said one, and reply "Added: <task>". If it's just a thought, save it to my notes without replying.
Productivity
Use the watch for the quick parts (capturing, deciding, a word to start something) and let Muse do the follow-through with your to-do app, email and Slack.
No buzz in the morning: three tasks on your watch. One question at 17:00 if any are still open.
Needs
To-do app, calendar and email connectors in Muse
Paste into Muse
Every weekday at 7:30, pick the three things that matter most today from my to-do app, calendar and email, and put each on my watch with upsert_task (a title under 40 characters, state working). Mark one done when my to-do app or email shows it is, or when I tell you from my wrist ("done: deck"). At 17:00, if any are still open, ask me with ask_question: "Tomorrow", "Tonight" or "Drop it", and do what I pick.
A status line while you focus; one card when it ends with what came in.
Needs
Slack connector in Muse
Paste into Muse
When I send "Focus 50" (or another number of minutes), set my Slack to do not disturb for that long, set_status to "Focus until <end time>", and hold everything except approvals I asked for and messages from my VIPs. When the time is up, clear the status and post one card with what came in, most important first. Add "Focus 50" to my presets if it isn't there.
One question at a time, only while you keep answering.
Needs
Email connector in Muse
Paste into Muse
When I send "Walk inbox", go through today's unread email that needs me, most important first, one at a time: ask_question with the sender, a one-line summary and the options "Archive", "Reply yes", "Reply later" and "Flag". Do what I tap. For "Reply yes", draft a short reply in my tone and request_approval with the recipient before sending. Stop after 15 emails or when I don't answer for 10 minutes, and send one line with what's left.
Business
A second screen for your business: the numbers you care about, the customers who matter, and the sign-offs that can't wait. Muse works with the connectors you already gave it and brings only the decisions to your wrist.
When something changes in your CRM or support tool
What reaches your wrist
One card for a big move; one question when a customer needs you; the rest in a Friday summary.
Needs
CRM and support connectors in Muse
Paste into Muse
Watch my CRM and support tool. When a deal over <amount> changes stage, closes or slips, post one card: the account, what changed and the next step. When a customer on my key-accounts list escalates or has been quiet for 14 days, ask me with ask_question: "Call them", "Draft reply", "Ask the team" or "Later". Do what I pick; anything that messages the customer goes through request_approval first. Everything else waits for one summary card on Friday at 16:00.
One approval each, with who asked and the amount; nothing is approved without your tap.
Needs
Slack, email and the tools you approve things in, connected to Muse
Paste into Muse
When a teammate asks me in Slack or email to sign off on something (an expense, a quote, a discount, a document), send it to my watch with request_approval: what it is, who asked, the amount and up to 3 details. Approve or reject it in their tool only after I answer, then tell them in one line. Contracts and anything over <amount> don't go to the watch: post one card saying they're waiting for me at my computer.
One card a day, low priority unless a number moved a lot.
Needs
Analytics, finance or CRM connectors in Muse
Paste into Muse
Every weekday at 7:45, post one card with the 3 numbers I care about most (for example yesterday's revenue, new sign-ups and open support tickets), each with the change since the same day last week. Use priority low, unless one moved more than 20 percent: then normal, with one line on why. If a source isn't available, say so in a missing section.
One card before you leave; a buzz only for a gate change, a delay or a cancellation.
Needs
Calendar, email and travel connectors in Muse
Paste into Muse
On days with a flight in my calendar or email, post one travel card 3 hours before departure: flight, gate if known, boarding time and when to leave for the airport, and set my status to the flight and gate. Buzz me (priority high) only for a gate change, a delay over 30 minutes or a cancellation. For a cancellation, ask me with ask_question whether to find the next flight, and request_approval before booking anything. After landing, send one line on how to get to my hotel.
Every Sunday at 19:00, post one recap card: training load and best session from list_activities, recovery trend from list_vitals, hours in meetings, one thing that went well and one goal for next week. Ask me with a question if I want next week's sessions sent to my watch.
When activity_stopped or activity_done arrives for a run or ride over 60 minutes, send <name> a short message: "Back from my <sport>, <distance> done." The first time, request approval with the exact wording; after that, send it without asking unless I say stop.
Messaging connector in Muse; the Ride data field, with Share workouts on
Paste into Muse
If an activity runs more than 45 minutes past its planned end, ask me on the watch "All OK?" with "Yes" and "Need help". If I answer "Need help", or don't answer within 20 minutes, message <name> with my last known plan. This is not an emergency service; my watch's own incident detection stays on.