Claude Code for Non-Engineers: Your First Automation

You don't need to learn to code. You need to learn to describe what you want. That single sentence is the entire thesis of this guide, and I've proven it with over 100 people who had never opened a terminal before sitting down in my training sessions.

If you can write a clear email, you can build an automation with Claude Code. The terminal is just where you type. Claude Code does the rest.

What We're Building (And Why It Matters)

Your first automation should solve a real problem you actually have. Not a tutorial exercise. Not a to-do app. Something that saves you time this week.

Here's the example we'll walk through: you have a CSV file of customer data (name, email, company, plan type) and you need to generate personalized email drafts for each one. Maybe it's a renewal reminder, a check-in, or a product announcement tailored by plan tier. Right now you're doing this manually, copying and pasting between a spreadsheet and your email client. It takes an hour.

We're going to build a script that reads your CSV, generates a personalized email draft for each row, and saves them all as text files you can review and send. Total build time: about 20 minutes.

Terminal Basics (Just Enough to Start)

If you've never used a terminal, here's everything you need to know. Nothing more.

Opening the terminal: On a Mac, press Cmd + Space, type "Terminal", hit Enter. On Windows, search for "PowerShell" in the Start menu. You'll see a blank screen with a blinking cursor. That's it. That's the terminal.

Three commands you need:

• cd foldername moves you into a folder. Like double-clicking a folder in Finder.
• ls (Mac/Linux) or dir (Windows) lists the files in your current folder. Like looking at a folder's contents.
• mkdir foldername creates a new folder.

That's the entire list. Three commands. You don't need to memorize flags, pipes, or any of the other stuff engineers use. Claude Code handles it all once you're inside a session.

Getting Claude Code Running

If you haven't installed Claude Code yet, follow the complete setup guide. It takes about 5 minutes. You'll install Node.js and then Claude Code itself.

Once installed, create a folder for your project and start Claude Code:

mkdir email-automation && cd email-automation
claude

You'll see Claude Code's interface appear in your terminal. It looks like a chat window. You type messages, Claude responds, and it can create and edit files on your computer. That's the entire interaction model. For a deeper walkthrough of how to use it, check the how to use Claude Code guide.

Your First Prompt

Here's the exact prompt to type. You can copy it word for word or adjust the details to match your situation:

I have a CSV file called customers.csv with columns: name, email,
company, plan_type (values are "starter", "growth", or "enterprise").

Build a script that:
1. Reads the CSV file
2. For each customer, generates a personalized email draft based on
   their plan type:
   - Starter: highlight upgrade benefits and offer a demo call
   - Growth: share tips for getting more value from current features
   - Enterprise: invite to an exclusive quarterly review session
3. Saves each email draft as a text file in an "output" folder,
   named by the customer's email address

Use a friendly, professional tone. Keep each email under 150 words.
Include the customer's name and company in each email.

Notice what this prompt does. It describes the input (CSV with specific columns), the logic (different email for each plan type), and the output (text files in a folder). No code. No technical jargon. Just a clear description of what you want to happen.

Claude Code will write a TypeScript (or Python) script, create the output folder, and probably ask you to confirm before running it. Say yes.

Preparing Your CSV

Before you run the script, you need the CSV file. Create customers.csv in your project folder. If you want to test with sample data first, just tell Claude:

Create a sample customers.csv with 10 rows of realistic test data.

Claude Code will generate the file for you. Once you've confirmed the script works with sample data, swap in your real CSV.

What Happens Next

Claude Code will create your script and run it. In the output folder, you'll find one text file per customer. Open a few and read them. They'll be personalized by name, company, and plan type.

Probably not perfect on the first pass. That's expected and fine. Iterate:

The enterprise emails sound too formal. Make them warmer, like you're
writing to someone you've met in person.

Also add a P.S. line to the starter emails with a link to our
pricing page: https://example.com/pricing

Claude Code updates the script and regenerates all the emails. Each round of refinement takes about 30 seconds. Keep going until the tone and content feel right.

When Something Goes Wrong (And What to Do)

Something will go wrong. A file path won't resolve. A column name won't match. The CSV format will be slightly off. Every beginner hits this, and it's completely normal.

Here's the rule: copy the error message and paste it back to Claude Code. That's it. You don't need to understand the error. You don't need to fix it yourself. Claude Code reads the error, figures out what went wrong, and fixes it.

Common issues and what they look like:

• "File not found" or "ENOENT": the CSV file isn't where Claude expects it. Tell Claude the actual file path or move the file into your project folder.
• "Cannot parse CSV" or column errors: the column names in your CSV don't match what the script expects. Tell Claude what your actual column headers are.
• "Permission denied": the script can't create the output folder. Tell Claude and it'll fix the permissions or use a different approach.

In 95% of cases, pasting the error message back to Claude Code resolves the problem in one round. The other 5%, Claude asks you a clarifying question and then resolves it.

Leveling Up: More Automations You Can Build

The email draft generator is a starting point. Once you've built one automation, the pattern is the same for everything else: describe the input, describe the transformation, describe the output. Here are real automations my students have built on their first day:

• Weekly report generator: pulls data from a Google Sheet, calculates key metrics, formats a summary as a polished HTML email
• Invoice processor: reads a folder of PDF invoices, extracts amounts and dates, produces a summary spreadsheet
• Meeting notes formatter: takes raw meeting notes from a text file, organizes them into action items, decisions, and follow-ups
• Data cleanup tool: reads a messy CSV with duplicates and inconsistent formatting, produces a clean version with standardized fields
• Slack-ready announcements: takes a product changelog and reformats each entry as a Slack message with proper formatting and emojis

Every one of these follows the same three-step pattern. Describe the input. Describe what you want to happen to it. Describe the output format. Claude Code writes and runs the code.

The Mindset Shift

Coding used to be a skill you either had or didn't. It took months of study to write even a basic script. That barrier is gone.

The new skill is clear communication. Can you describe what you want precisely enough for Claude Code to build it? That's a skill you already use every day when you write emails, create briefs, or explain a process to a colleague. You've been training for this your whole career without knowing it.

The people who get the most out of Claude Code aren't engineers. They're clear thinkers who know exactly what problem they're solving. That's you.

Ready to build more? In ClaudeFluent, we take you from first automation to deploying full web apps, with hands-on exercises and live instruction. Start with the best practices guide to pick up the habits that make everything easier.