Skip to main content
MethodAI Setup & ProductivityPersonal productivityIntermediate

Turn a manual process into an automation

An automation design for Zapier, Make, n8n or Power Automate: trigger, steps, data mapping, errors and tests.

This is a practical, copy-paste process for a repetitive task eats hours every week.. Use it when you want a clear structure, then add your own details and the linked evidence.

Published by Deepstory Research. Reviewed Sep 2026.

How to use this method

  1. 1. Copy or downloadCopy the prompt below, or download the method file and attach it to your chat.
  2. 2. Paste into any AIChatGPT, Claude, Gemini or Copilot. Replace each [PLACEHOLDER] with your details, or let the AI ask you.
  3. 3. Add evidenceAttach the evidence files listed on this page so the AI works from sourced numbers, not guesses.

The prompt

Paste it as-is. The AI will ask for anything still in [BRACKETS].

Download .md
# Turn a manual process into an automation
Method by Deepstory Research: deepstoryresearch.com/method/sop-to-automation

You are a no-code automation engineer. Follow the method below step by step. Goal: An automation design for Zapier, Make, n8n or Power Automate: trigger, steps, data mapping, errors and tests.

## My inputs
- Manual process: [MANUAL_PROCESS]  (example: copy form leads into CRM and send welcome email)
- Tools involved: [TOOLS_INVOLVED]  (example: Typeform, HubSpot, Gmail)
- Automation platform: [AUTOMATION_PLATFORM]  (example: Zapier / Make / n8n)
- Volume: [VOLUME]  (example: 50 per day)

Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source.

## Steps to follow
1. Map the manual steps.
2. Choose trigger and actions.
3. Map fields between tools.
4. Add filters, error handling and logging.
5. Define human-approval points.
6. Write a test plan.

## Deliver the output in this structure
- Process map
- Automation blueprint
- Field mapping
- Error handling
- Test plan

## Quality rules
- Keep humans in the loop for anything sent to customers or payments.
- Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION.
- If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED].
- End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.

What you need to give the AI

InputPlaceholderExample
Manual process[MANUAL_PROCESS]copy form leads into CRM and send welcome email
Tools involved[TOOLS_INVOLVED]Typeform, HubSpot, Gmail
Automation platform[AUTOMATION_PLATFORM]Zapier / Make / n8n
Volume[VOLUME]50 per day

Use it when

  • A repetitive task eats hours every week.

What you get

  • Process map
  • Automation blueprint
  • Field mapping
  • Error handling
  • Test plan

The procedure, step by step

Read this before you run it, so you can check the AI actually followed the method.

  1. 1

    Map the manual steps.

  2. 2

    Choose trigger and actions.

  3. 3

    Map fields between tools.

  4. 4

    Add filters, error handling and logging.

  5. 5

    Define human-approval points.

  6. 6

    Write a test plan.

Quality checks built into the prompt

  • • Keep humans in the loop for anything sent to customers or payments.
  • • Every number labelled FACT, ESTIMATE or ASSUMPTION; claims outside attached evidence tagged [UNVERIFIED].

Evidence for this method

This method runs on your own material: your files, brief or code. If your task needs market or economic numbers, attach a sourced context file from the evidence library alongside the prompt.

Browse evidence

Run next

Methods that chain well after this one.

Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment decisions need a qualified professional.