Wink Routines · Free & open

AI that clocks in on time.

A growing library of routines that handle the recurring work — on your schedule, in the cloud, while you focus on the rest of your day.

The routines available today.

Two production-tested routines. More on the way.

☀️

Daily Brief

Your inbox and calendar, briefed before you wake up.

Pulls today's calendar and the last 24 hours of email. Filters newsletters, marketing, and bulk-sender noise. Surfaces follow-ups versus FYI. Flags overlap between calendar attendees and email senders. Two minutes to read.

Cadence
Every morning, 6:00 AM local
Delivers to
Calendar event · Gmail email · Notion archive
📬

Weekly Catch-All

A 14-day audit of what slipped through.

Scans 14 days of inbound and outbound email. Identifies four signals: replies you owe, replies owed to you, direct questions waiting on you, and lane-relevant misses. Tiers them — top 5 act this week, next 10 decide on Monday, count of the rest.

Cadence
Every Wednesday, 3:00 PM local
Delivers to
Calendar event with 5-hour reminder · Gmail email · Notion archive

How it works.

Three steps. Then it runs by itself.

01

Paste a prompt into Claude.

Open the Claude routine config, drop in a prompt template, fill in 6 values (your name, email, timezone, business lanes, calendar event start and end). Save.

02

Claude runs it on a schedule, in the cloud.

Anthropic fires the routine at your chosen time. It runs on their servers, reads from your authorized Google and Notion accounts, and produces the brief.

03

The result lands on your phone.

A calendar event buzzes with the brief in the description. The same content arrives as an email. A Notion page joins your archive. You read whichever surface you'd reach for first.

What you’ll need.

Four accounts. Three of them you already have.

Claude account
With Code access — required for cloud routines.
Google account
Gmail and Calendar are read at runtime; events get created on your behalf.
Notion workspace
Any plan, including free. Hosts the searchable brief archive.
GitHub account
Used once to attach a private repo to the routine. The 90-second sign-up is the only hurdle.
~15 minutes per routine

The full setup.

Eight steps, browser-only. Same flow for both routines.

  1. 1

    Create a Notion parent page

    1 min

    In your Notion workspace, create a page titled exactly Daily Briefs with a ☀️ icon. Empty page is fine — the routine fills it on each run.

  2. 2

    Create an empty private GitHub repo

    2 min

    At github.com/new, name it daily-brief-routine, set Private, check Add a README, click Create. The README seeds a default branch — required for routines to attach.

  3. 3

    Grant the Claude GitHub App access

    1 min

    Visit github.com/apps/claude and install. Choose Only select repositories, pick the new repo, save. This step is the most common setup snag — make sure the install happens while signed into both GitHub and Claude.

  4. 4

    Create the routine in Claude

    3 min

    At claude.ai/code/routines, click New routine, choose Remote. Pick a name (daily-brief or weekly-catch-all). Select your repo. Set the trigger — Daily 6:00 AM local for the brief, or Weekly Wednesday 3:00 PM local for the catch-all. Connectors: Gmail, Google Calendar, Notion. Model: Claude Sonnet 4.5 to start.

  5. 5

    Paste the prompt

    2 min

    Open the relevant prompt template from the GitHub repo. Find/replace the 6 placeholders with your values. Paste the result into the routine's Prompt / Instructions field. Save.

  6. 6

    Authenticate the connectors

    3 min

    On the routine page, each connector shows an Authenticate button. One click each — Gmail goes through Google sign-in, Calendar typically inherits the same session, Notion asks for workspace access.

  7. 7

    Test run

    3 min

    Click Run now. Wait 1–3 minutes. Verify the calendar event landed, the email arrived, and the Notion page was created. If anything is missing, the run session URL shows the log — most failures trace to connector auth.

  8. 8

    Confirm the autonomous run

    Tomorrow

    Close your laptop tonight. Tomorrow morning, your phone calendar buzzes with the brief — no machine on, no manual trigger. That's the proof the deployment is real.

The full playbook with troubleshooting and offboarding notes lives on GitHub.

Open the playbook on GitHub →

Two ways forward.

Pick whichever fits how you work.

🛠️

Set it up yourself

Open the GitHub repo. Follow the 2-page playbook. ~15 minutes per routine, browser-only. Free to use, free to adapt — credit Wink Intelligence in your fork.

View on GitHub →
🤝

Have me set it up

I’ll deploy the routines on your account, tune the prompts to your business lanes and inbox shape, and stay on a Slack thread for the first week to refine the output. Custom variants for sales teams, ops teams, or executive offices on request.

Questions you’re asking.

Your laptop's state has no effect. The routine runs on Anthropic's infrastructure. Close it, leave it home, factory reset it — the brief still arrives.

The routine fires against your existing Claude Code usage. Each plan has a daily routine run cap visible in your Claude dashboard. One daily routine plus one weekly routine sit comfortably under any tier's cap.

Claude reads your inbox to do the job, then reports back. The Anthropic connectors handle the auth — your credentials live in your Claude account, encrypted by Anthropic. Your data stays in your Google and Notion accounts. The routine doesn't store anything outside those surfaces.

Yes. The full prompt lives in your routine config in the Claude dashboard, in a single text field. Tweak it whenever you want — new filter rules, additional categories, a different tone, custom logic for your industry. Changes apply on the next scheduled run.

The run fails and shows up red in your routine history. Re-authenticate the connector at claude.ai/code/connectors (a one-click flow), and the next run picks up cleanly. A weekly glance at the run history catches these before they pile up.

Yes. The Daily Brief and Weekly Catch-All are the first two — built and tested live in my own consulting practice. As I build more (sales pipeline reviews, pre-meeting briefs, content audits, weekly metrics rollups), they'll appear here under the same setup pattern.