Weekday morning brief texted to your iMessage

By General Input

Every weekday at 7am, get one short iMessage with today's meetings, your top issues, and a watch-out callout. No more cracking open three tabs before coffee.

Integrations

  • LoopMessage
  • Google Calendar
  • Linear

Type

Agentic Task

Categories

  • Personal Productivity
  • Operations

Build me a personal morning brief that runs on a cron schedule, every weekday (Monday through Friday) at 7am in my local timezone, and texts me one cohesive iMessage with the day ahead.

Each run, the agent should:

1. Call Google Calendar List Events on my primary calendar for today's date range (00:00 to 23:59 in my timezone), expanding recurring events into instances. Capture each event's title, start time, attendees, and whether it has a description or agenda.

2. Call Linear List Issues filtered to issues assigned to me with state In Progress or Todo and a due date within this week (today through Sunday). Capture title, identifier, due date, priority, and the Linear URL.

3. Synthesize the two sources into a short, scannable brief that highlights: the top 3 meetings for today with their times and a couple of attendee names, the top 3 Linear issues I should push on (sorted by overdue first, then priority, then due date), and a single one-line "watch out for" callout if any meeting is missing an agenda or any issue is already overdue. If there's nothing notable to call out, omit the watch-out line rather than padding it.

4. Send the result via LoopMessage Send Message as a single iMessage to my own contact (I'll provide the phone number when I set this up). The whole message must stay under 1000 characters so it renders as one bubble. Use compact formatting (short labels, no markdown headings, line breaks instead of bullets).

Important LoopMessage rules to respect: do not include any links, email addresses, phone numbers, or currency amounts if this is the first message of a new conversation, because the initial opt-in path forbids them. If LoopMessage indicates we're already in an active conversation with this contact (i.e. they've replied recently), it's fine to include short Linear issue URLs inline for the top issues; otherwise leave URLs out entirely.

Handle light days gracefully: if I have zero events and zero open issues for the week, send a one-line message saying it's a quiet morning rather than skipping the send. If either API call fails, send a brief fallback message noting which source was unavailable so I know to check manually, rather than failing silently.

At setup, ask me for my timezone, the iMessage contact (phone in +E.164 format) to text, and confirm which Linear workspace and Google account to use.

Related prompts

Explore more prompts
iMessage campaign console with pre-flight checks and delivery boardFront desk appointment confirmation board for the next 3 daysLead response desk with a running clock on every new leadCatch feature flags that never got switched on in productionWeekly alert noise review board for incident.io on-callMorning triage board for your Kernel browser agent runsTrack every half finished LaunchDarkly rollout in one boardAppointment confirmation board built on WhatsApp repliesFind the customers stuck contacting support again and againTurn shipped Linear work into Intercom product announcements