HR Automation for Teams

HR is a pile of writing and reading: postings, applications, candidate updates, onboarding plans, the same policy questions every week. For a team without an HR department, it all lands on someone who has another job. This page is the HR set of our AI automation hub, a group of build guides that hand the writing and reading to a workflow so a person spends their time on the people.

Every build pairs Claude for the writing with the plumbing that watches your sheets and forms. And one line runs through all of it: AI drafts and organizes, but it never judges a person. Applications are summarized for a human to compare, not scored or rejected; candidate emails and HR answers are drafted, not auto-sent. The decisions about people stay with people.

What is HR automation, in plain English?

It is a short chain that does an HR chore. A role, an application, a status change, a new hire, or a question appears, an automation tool carries it through a step or two, and you get back a posting, a summary, a drafted email, an onboarding plan, or an answer. Claude does the writing; the tool does everything around it; you make the calls that affect people.

Across these builds the AI step does one of a few jobs:

• Writes a job description from a short brief.
• Summarizes each application the same way, for a human to compare.
• Drafts warm candidate updates and policy answers.
• Plans a personalized first week for a new hire.

What can you automate first?

Each guide takes one real HR chore from an empty canvas to a working automation, with a screenshot of the finished build and a free importable template. Start with the easy wins:

Build	What it does	Who decides?
Write job descriptions	A role brief becomes a full posting in a Doc	You edit and post
Summarize applicants	A neutral, consistent summary per applicant	You compare and decide
Candidate status emails	Warm updates drafted for each status	You send
Onboarding plans	A first-week plan in Notion per hire	The manager reviews
Answer HR questions	Replies drafted from your policy text	You confirm and send

Why pair Claude with an automation tool?

Because they are good at opposite things. Claude is strong at writing a posting, summarizing an application, or drafting a kind email. It is not built to watch your sheets and forms, create Docs and Notion pages, or save drafts. That is plumbing, and a tool like Make does plumbing.

So the tool handles every step that needs no judgment, and Claude handles the writing. Think of the tool as the assistant who files and routes, and Claude as the one who drafts. Neither replaces the other, and neither replaces you: the call on who to hire, what to pay, and how to handle a person is yours, every time.

Is it fair and legal to use AI in hiring?

Used the way these builds use it, yes. The screening build only summarizes applications into a consistent format and is told to ignore name, age, and gender; it never scores, ranks, or rejects, because automated hiring decisions are both unfair and, in many places, regulated. Keep AI to organizing and drafting, keep a human deciding, and check the hiring law where you operate. Done that way, AI makes hiring more consistent, not less fair.

How much does it cost to start?

Less than most people expect. Make’s free plan covers 1,000 operations a month. Claude charges per use, and writing a posting, summary, or email costs a fraction of a cent. A form tool, Notion, and Gmail are likely already on your stack. For a team without HR budget, these builds give back the most expensive thing you have: a busy person’s time.

Do you need to know how to code?

No. Every guide is connecting boxes on a visual canvas and writing a plain-English prompt for the AI step. The judgment lives in your prompt, your voice, your policies, your fairness rules, not in any code. Our Make AI scenarios roundup and the AI Tools Directory are good next stops.

Common questions

Which build should I start with?

Job descriptions or candidate emails, the lowest-risk, highest-relief wins. Move to applicant summaries and onboarding once you trust the pattern.

Will AI decide who to hire?

No. The screening build summarizes applications for a human to compare; it never scores, ranks, or rejects. Every hiring decision stays with you.

Is this legal?

Summarizing and drafting are generally fine; automated hiring decisions are regulated in many places. Keep AI to organizing and drafting, and check your local law.

Do I need an HR system?

No. These run on a sheet, a form, Gmail, and Notion. If you have an ATS or HRIS, you can swap those in.

Is the Claude chat app the same as the API?

Same models, different door. The automations talk to the API, so you need a key from the Claude console.

Sources and official documentation

• Make Help Center
• Claude API overview (Anthropic)
• EEOC guidance on AI in hiring
• Notion API (developers.notion.com)
• HR management — Grokipedia

Last reviewed: May 2026. These tools update often, and hiring law varies by place; check the official docs above and your local rules.

You may also like

• AI Automation for Beginners (the main hub)
• Write job descriptions with Claude
• Qualify inbound leads with Claude
• How to use Claude AI
• Make.com Complete Beginner’s Guide
• Zapier vs Make vs n8n
• The AI Tools Directory