Automate your inbox, content calendar, and research in under two hours. Here is exactly how to build it from scratch.

The most powerful productivity upgrade available right now isn't a new app. It's connecting the apps you already use to AI — so the repetitive, rule-based parts of your workflow happen without you.

This guide walks you through building three connected automations using Zapier and Claude. You don't need to write code. You do need a Zapier account (free tier works for two of the three) and a Claude API key.

What you're building

Each of these runs automatically, 24/7, without you touching them. Once set up, the cumulative time saving is 2–4 hours a week for most people.

Before you start: getting your Claude API key

Go to console.anthropic.com, create an account, and generate an API key. Keep it somewhere safe — you'll need it in Zapier.

The Claude model to use for Zapier automations is claude-haiku-4-5 for simple tasks (categorisation, summaries) and claude-sonnet-4-6 for anything requiring creative output (content drafts). Haiku is significantly cheaper and fast enough for most background tasks.

"The goal is a system that does the mechanical thinking so you can save your attention for everything else."

Automation 1: Smart email triage

Trigger: New email in Gmail

In Zapier, create a new Zap. Set the trigger to Gmail → New Email. Choose the inbox you want to filter (you can narrow it by label or sender if needed).

Action: Claude categorises it

Add a Webhooks by Zapier action (POST). Set the URL to the Claude API endpoint: https://api.anthropic.com/v1/messages. In the headers, add your API key as x-api-key.

In the body, pass the email subject and first 500 characters of the body to Claude with a prompt like: "Categorise this email as one of: URGENT (needs response today), NORMAL (can wait 48h), or FYI (no response needed). Reply with just the category and a one-line reason."

Action: Apply the right Gmail label

Add a Filter step — if the Claude response contains "URGENT", apply a Gmail label called "⚡ Action Today". This is what surfaces the emails that genuinely need you, filtered from the rest.

Automation 2: Article summary to notes

Trigger: New item saved to Pocket

Set the trigger to Pocket → New Item. This fires every time you save something to read later.

Action: Claude reads and summarises

Pass the article URL and title to Claude with a prompt: "Summarise this article in exactly three bullet points. Then add a fourth bullet starting with 'Worth knowing:' with one insight I might have missed. Keep each bullet under 25 words."

Action: Create a note in Notion/Obsidian

Use the Notion action to create a new page in a "Reading Summaries" database with the title, URL, date saved, and Claude's summary. You now have a searchable archive of everything you've ever saved to read — already summarised and ready to reference.

Automation 3: Topic to social draft

Trigger: New row in Google Sheets

Create a Google Sheet with columns: Topic, Platform, Tone, Status. Set the Zap trigger to fire when a new row is added.

Action: Claude writes the draft

Pass the topic, platform, and tone to Claude with a prompt tailored to the platform. For Instagram: "Write a 150-word Instagram caption about [topic] for a tech lifestyle brand. Tone: [tone]. Include a hook in the first line, practical value in the body, and a question at the end to drive comments. No hashtags in the caption itself."

Action: Add the draft back to the sheet

Use the Google Sheets Update Row action to write Claude's output back into a "Draft" column. Change the Status to "Ready for Review". Your content queue now fills itself — you just need to approve.

Time to build: Allow 90 minutes for all three. Automation 1 is the most fiddly (API setup). Automations 2 and 3 are faster once you've done the first. The Zapier interface is intuitive enough that you won't need to reference this guide after the first pass.

Troubleshooting the common issues

Claude returning unexpected output: Tighten your prompt. Be explicit about the exact format you want. Adding "Reply with only [X], nothing else" dramatically improves consistency.

Zap failing on the API call: Check your API key is in the right header. The Claude API requires anthropic-version: 2023-06-01 in the headers as well as the API key.

Gmail automation catching too many emails: Add a filter step after the trigger to narrow the scope — filter by sender domain, label, or keywords.

Where to take it next

Once these three are running, the obvious next step is connecting them. A summary from Automation 2 becomes input for Automation 3 — you save an article, it gets summarised, and Claude drafts a social post based on the summary. That's a full content production pipeline that starts when you press save on an article.

That's the real value of systems thinking with AI. Not one automation in isolation, but connected workflows that compound over time.