AI Central

Automate Your Repeat Work With AI

Download
AI Central
Review AI summary

Automating repeat work with AI is mostly writing, not tooling. AI Central's guide spends its first three steps choosing one task, writing it down as a recipe and testing it, before any schedule, connected app or automation platform appears. Steps 4 to 7 only run what steps 1 to 3 wrote and tested.

The problem is the restart, not the task

The guide opens on three familiar jobs: the Monday report, the inbox sort, the meeting prep. Each one starts from zero every week. Asking AI is faster, but still by hand, and the example chat shows why: 46 support tickets pasted with "use last week's format", and the assistant has to ask which format and what counts as urgent. The brief lives in your head, so you explain it again every time.

Explained again every Monday, let's turn it into a recipe

Pick the task before you write anything

Step 1 lists every task you did twice or more this week and scores each one on how often, time spent, clear rules and low risk if wrong. The prompt hands the AI your pasted week and asks for the top 3 to automate first, with reasons. The filter it produces holds for everything after: frequent, fixed and low risk goes first, and you start where a mistake is cheap to fix.

The recipe has four parts

A recipe, in the guide's words, is the brief the AI follows every time. The worked example, a weekly support report, shows each of its four labelled parts doing one job.

  • Input: what you paste or connect, here this week's tickets exported from the help desk.
  • Steps: what to do, in order: group by topic, count each group, flag anything about refunds or legal.
  • Output: the exact format you want back, a table plus 3 lines to read out at the Monday team call.
  • Rules: what it must never do. Never guess a number, and put unclear tickets under Unclear.

The Rules line carries the most weight. A ban on guessing plus a named bucket for unclear items turns a confident wrong answer into a visible gap you can check.

Test it on weeks you already know

Step 3 runs the recipe by hand on 3 past weeks where you know the answer. In the example the reader counted 12, 9 and 15 refund tickets. The AI counts 11 for week 2, because two tickets ask for a return, not a refund, and asks whether returns should count. The answer goes into the rules, because the guide says to fix the recipe, not just the answer. Three clean runs, then automate.

Save it, then put it on a schedule

Step 4 ends the pasting. Create a project in ChatGPT or Claude, or a Gem in Gemini, paste the recipe into its instructions and add the files it needs, such as past reports and the refund policy. From then on you paste the tickets and type "run": one project per recipe, one word to run it.

Step 5 lets the AI start the work on time. The guide lists scheduled tasks in ChatGPT on every plan, scheduled tasks in Claude on paid plans and scheduled actions in the Gemini app. Its example is a Monday 8 am web search for news on 5 carriers and 3 competitors, capped at 5 items with a link and one line each, and it allows a one-line answer when nothing matters that week.

Connect your apps, then move to an automation platform

Step 6 connects Gmail, Calendar or Drive in settings and starts with read, sort and draft. The weekday meeting brief reads today's calendar and the last 2 weeks of email with each attendee, lists who, why, what they last asked for and one question to ask, drafts replies, and ends with a hard rule: do not send anything.

Step 7 is for work that must run on every event, not on a timer. The guide names Zapier as the simplest start with the most apps, Make as a visual map that is good for branches, and n8n when you want to host it on your own server. Its example takes each new website form, has an AI step sort it into quote, support, partner or spam, keeps the quotes, and creates a Gmail draft and a row in a sheet.

Keep a human on send

The pro tip draws the line plainly. AI alone may read, sort, summarise and draft. You approve anything that sends, publishes, pays or deletes. Log every run in a sheet with the input, the output and your fix, and review that log every Friday.

Why: a wrong recipe is wrong every week

Where to start

The picker page says to start where you are, not at step 7. With no idea what to automate, begin at step 1. With a recipe that already works, go to steps 4 and 5. The closing page gives the whole method in three lines:

  • Pick one task you repeat every week.
  • Write the recipe, test it 3 times.
  • Schedule it, keep the send button.