← Back to library

Start an agent routine from an iPhone automation

Michael Fenech (@Michael_Fenech_) starts a Grok Bot daily briefing from his iPhone rather than a clock. Stopping his morning alarm runs a Shortcuts automation that posts to a webhook the bot already created. He also names other triggers, such as leaving work or tapping a tag. We show his setup steps word for word with credit.

  • OutcomeHave your agent create a briefing job that waits for an incoming webhook rather than a timer, then use the iPhone Shortcuts app to fire that webhook when you stop an alarm, leave a place, connect to the car, arrive home or tap a tag, so the work begins from something that already happened in your day.
  • SetupUnder an hour
  • LevelStarter
  • CreditMichael Fenech (@Michael_Fenech_)
View original
Works with
Grok BotChatGPT agentClaude CoworkCustom agent

Published Nov 8, 2026Updated Nov 8, 2026AI dry run on sample input: passed Nov 8, 2026Source verified Nov 8, 2026

When should you use it?

  • You want a morning brief ready by the time you pick up your phone, without opening the agent first
  • A scheduled routine often runs when you are not ready, or sits idle on days you do not need it
  • A real event, such as leaving the office or sitting in the car, is a better start signal than a clock

Not for: Android phones, which do not have this Shortcuts automation path; Jobs that must run at an exact minute whether or not you are awake; Anyone unwilling to store a webhook address and its authorization header on the phone

What do you need, and what do you get?

You need

  • An agent that can expose a webhook URL and an authorization header for a routine
  • An iPhone with the Shortcuts app and the event you want to use as the start signal
  • A clear description of the job that should begin when that event fires

You get

  • A routine that waits for an incoming webhook rather than a timer
  • A Shortcuts automation that posts to that webhook when the chosen event happens
  • A first briefing or task run that starts without you typing a prompt

How does it work, step by step?

  1. Ask for a webhook jobTell the agent to build the briefing or other routine so it starts from an incoming webhook, then copy the URL and authorization value it gives you.
  2. Make the phone automationIn Shortcuts, create an automation for the event you care about, such as an alarm stopping, and turn off extra prompts so it can run on its own.
  3. Send the webhookAdd a request action, paste the URL, use POST, attach the authorization header and a small JSON field that names the trigger, then save it.
  4. Run a testTrigger the event once while you watch. Confirm the agent starts the job and that nothing else on the phone fired by mistake.
  5. Add only what you will useOther events, such as leaving work or tapping a tag, can start different jobs. Add them one at a time after the first one is reliable.

The prompt

The original prompt by Michael Fenech (@Michael_Fenech_), word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Grok Bot, ChatGPT agent, Claude Cowork and others. Values in lime are placeholders.

Original prompt by Michael Fenech (@Michael_Fenech_)

Word for wordby Michael Fenech (@Michael_Fenech_)
STEP 1: Set up Grok Bot

Ask Grok Bot to create a daily briefing routine triggered by a webhook instead of a schedule.

Get the webhook URL and Authorization header.

STEP 2: Connect your iPhone

Open the Shortcuts app and create a new Automation.

1: Select Alarm → Is Stopped and choose your morning alarm.

2: Toggle Automation on and notify off.

3: Add the action Get Contents of URL.

4: Paste your Grok Bot webhook URL.

5: Set the method to POST.

6: Add a header: Authorization with the value provided by Grok Bot. (Bearer <value>)

7: Set Request Body to JSON, and add a Text field: 
Key = source 
Text = iphone-alarm

8: Save the automation and disable Ask Before Running if shown.

Exactly as published by Michael Fenech (@Michael_Fenech_) in X post: start a Grok Bot briefing from an iPhone Shortcuts automation.

Our adapted version (optional)

Fill in the blanks (optional; the copied prompt uses your values)

Adapted prompt5 variables
Create a {job} that starts only when a webhook is called, not on a timer.
Give me the URL and the authorization header to send.
When the JSON body says source={trigger_name}, gather {sources} and write a short brief covering {sections}.
If a source is missing, say so instead of guessing.
Then list the Shortcuts automation settings I should use on iOS to call that URL with POST and the header when {iphone_event} happens, and tell me how to test it once without waiting for the real event.

What can go wrong?

  • The authorization header lives on the phone. Anyone who unlocks it could fire the same job, so treat that value like a password and rotate it if the phone is shared or lost.
  • If Shortcuts still asks you to confirm each run, the automation will not start on its own. Turn that prompt off after you trust the setup.
  • A webhook with no shared secret, or one posted in a screenshot, can be called by anyone who finds the URL.
  • The agent still needs access to the calendar, mail or files the briefing uses. A working trigger does not fix a missing connection.

Our take

A clock is a blunt way to start agent work. Plenty of useful jobs should begin when you actually start your day, leave a place or sit down in the car, not at 7:00 whether you are awake or not. Fenech's setup is appealing because it uses tools already on the phone and does not ask you to install another app. The webhook is the important seam: the agent owns the job and the secret, and the phone only announces that something happened. That split keeps the hard part (what to gather, what to skip, where to write it up) inside the agent, where you can edit it later without touching Shortcuts again. We would treat the authorization header with more care than the original post spells out, because a screenshot or a shared phone would let someone else start the same job. We would also begin with one event and one routine, then add others only after a week of clean runs, since a pile of automations is hard to debug. In our dry run for a fictional cafe owner, stopping the weekday alarm posted to the webhook and the agent drafted a briefing from yesterday's sales sheet and the day's staff calendar, while a weekend test correctly did nothing because that alarm was not set.

Where the time goes back: The briefing starts from something you already do, so you stop opening the agent to type the same morning prompt, and you avoid scheduled runs on days the event never happened.

FAQ

Does this only work with a morning alarm?
The alarm is only the example he tested. The same webhook pattern can start from other iPhone automations, including leaving a location, connecting to CarPlay, arriving home or tapping an NFC tag.
Can I use this with an agent that is not Grok Bot?
Yes, if that agent can give you a URL to call and a header that proves the call is yours. Many scheduled-agent products support incoming webhooks.
Will the briefing run if my phone is offline?
The Shortcuts step needs the phone to send the request. If the phone has no connection at that moment, the job will not start until a later successful call.

Source and credit

The original prompt on this page is by Michael Fenech (@Michael_Fenech_), shown word for word with a link to where it was published. The summary, notes and adapted version are ours.

Original
X post: start a Grok Bot briefing from an iPhone Shortcuts automation
Creator
Michael Fenech (@Michael_Fenech_)
Published on
X
Original date
Nov 5, 2026
License
Not openly licensed; the original prompt is shown word for word with credit and a link to the original
Originally for
Grok Bot
AI dry run
Nov 8, 2026: passed. Dry-run tested by our AI test agent on sample input. Webhook job created, phone steps listed, weekday brief cited sources and flagged a gap, Sunday correctly did nothing.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Nov 8, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Audit how you manage your agent team, not only the agents

Have your chief-of-staff agent review the last 30 days of how you delegated, clarified, interrupted, corrected, assigned, approved and followed up across your agent team, score eight management areas with evidence, list your three biggest weaknesses, and draft a seven-day improvement plan, without changing any bot, routine or instructions until you approve.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminPrompt✓ AI dry run

Brief an agent with nine fields, not a how-to

Before you hand a job to an agent, fill in nine short fields that name the result, the sources it may use, the deadline, what it may do alone, what needs your say-so, what it must never do, how to prove the work is finished, what to do when it gets stuck, and where to put the deliverable, then add a line that tells it to pick the simplest reliable method.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Operations & AdminPrompt✓ AI dry run

Brief your agent on the outcome, not every step

Hand a new job to your lead agent by describing the finished result instead of the steps, and have it confirm what success looks like, ask only for context it cannot find itself, pick the simplest dependable approach, state what it will do alone and what needs your approval, and check the result against your goal before calling it done.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Operations & AdminWorkflow✓ AI dry run

Forward an email and let an assistant book the meeting

Forward a meeting request to a labeled inbox and have an AI assistant coordinate a time with the other person and add a video link.

Credit: Eddie Soehnel (@edsoehnel)

Under an hour
Operations & AdminWorkflow✓ AI dry run

Drive desktop apps when an integration is blocked

Get work done through apps you cannot connect by API, by letting an agent control your desktop and operate them the way you would, with you approving sends.

Credit: Prasid

Under an hour