How to write an Upwork job post for an automation

The short answer

Your job post is the brief. Freelancers decide whether to apply from it, price from it and, if you hire them, build from it. A post that says “need an automation expert for my business” gets proposals about the freelancer’s favourite tool. A post that says what should be true when the job is done, what starts it, what it connects and how you will check it gets proposals about your job.

Write the post as a short brief: one measurable goal, the trigger, the systems, the rules, what happens on failure, what you get at handover and the acceptance test. Then add two or three screening questions that separate people who have built your kind of workflow from people who have not.

Why a specific post gets better proposals

On Upwork, freelancers spend Connects to send a proposal. Upwork’s help center lists Connects at $0.15 each, sold in bundles. That small cost means a freelancer reading your post is deciding whether it is worth applying.

A clear post helps the right people decide yes. Someone who has built a form-to-CRM routing workflow will recognise it in two lines and reply with something relevant. A vague post does the opposite: it attracts broad, copy-paste proposals, because nobody can tell whether they fit.

The same logic applies to your first message on any platform. My own first messages to sellers have been short: a greeting, the project I wanted to start, and a question about whether they had done something like it before. What I decided on was the reply, specifically the similar past work the seller attached. A job post is that first message, sent to everyone at once.

What goes in each field

Upwork’s help center lists the fields of a job post. Here is what to put in each for an automation (checked October 2026):

Field	What Upwork asks	What to write for an automation
Title	A title for the job	The task and the result, not the tool: “Route website form enquiries into our CRM and alert the right salesperson”
Skills	Up to 10; 3–5 recommended	The systems it touches (your CRM, email, sheets) and one or two platforms you are open to
Size	Large, Medium or Small	Small (a few weeks or less) for a single workflow
Experience level	Entry, Intermediate or Expert	Match the risk: Intermediate for a simple two-tool workflow, Expert if it sends, posts or charges something
Budget	Hourly rate or fixed project budget	A fixed budget range for a defined workflow; hourly with a weekly cap if the scope is still open
Description	Free text	The brief below
Screening questions	Optional questions freelancers answer when they apply	Two or three questions about your kind of workflow

Once the post is live you can also invite freelancers whose profiles fit, instead of waiting only for proposals to arrive.

The description: a brief in seven lines

Use the same fields as the workflow automation brief, shortened:

The acceptance line is the one most posts leave out, and it is the one that changes the quote. A freelancer who knows you will revoke a token to see what happens will build the alert; one who does not will build for the demo. The reasons are in the acceptance checklist for unattended automations.

Screening questions that do the filtering

Generic questions (“Why are you the right fit?”) get generic answers. Ask about your workflow instead:

• “What is the closest workflow to this one you have built? A short description and a screenshot or recording is enough.”
• “If the CRM refuses a record, what should happen to that enquiry, and how would I find out?”
• “Which platform would you build this on, and who pays for and owns that account?”
• “After delivery, how do you handle fixes when a connected tool changes, and at what rate?”

The second question matters most. In my own scheduled jobs, an invalid access token left a publishing job starting on schedule for two days while nothing went out. Someone who answers “it alerts you, and here is how” has thought about the part a demo never shows.

The last question opens the maintenance conversation while you still have something the freelancer wants. The maintenance guide has the six lines to agree.

A job post you can copy

Title: Route website form enquiries into [CRM] and alert the right salesperson

What should be true when this works: every enquiry from our website form is in [CRM] within five minutes, assigned to the right person, and that person gets an email.

Trigger: a new form submission on [form tool].

Systems: [form tool], [CRM], [email]. All accounts are mine; you will get access I can remove. If you recommend a platform (n8n, Make, Zapier or other), it runs on an account I own.

Rules: [3–5 rules with an example each].

If something fails: the enquiry is not lost, and I get an alert within the hour.

At handover: the workflow export, a one-page run-book and a list of credentials with what each is for.

Acceptance: I release the final payment after three runs fired by real submissions, one forced failure that alerts me and one duplicate submission that does not create a second record.

After delivery: please quote fixes for the first 30 days and a rate after that.

Budget: [range], fixed price. Open to a smaller first version if that fits better.

Where it goes wrong anyway

• Naming the tool instead of the job. “n8n expert needed” attracts people who know n8n, not people who have built your workflow. Name the task first.
• No accounts line. If the post does not say the accounts are yours, some proposals will assume they host everything. That is hard to undo later; see who should own the accounts.
• A wish list instead of one workflow. Five automations in one post get a big, vague quote. Post the first one; the second post is quicker once you know who to send it to.
• Choosing on the cover letter. A polished cover letter shows writing skill. The answer to your failure question and the similar past work show building skill.

Wrap-up

Write the post you would want to answer: the result, the trigger, the systems, the rules, the failure behaviour, the handover and the test. Ask screening questions only someone who has built it can answer. The proposals you get back will be fewer, and much easier to compare. When the seven lines are written, post the job on Upwork and add your screening questions.