Posting a job
How to write a post experts actually bid on, what happens to it after you submit, and the limits that apply.
Posting a job puts your project in front of approved experts, who send proposals you then compare. You do not have to find anyone yourself. The quality of what comes back is almost entirely determined by the post, so it is worth ten minutes.
What a good post contains
Experts are choosing which jobs to spend their time bidding on. A vague post attracts either no proposals or generic ones, because nobody can estimate work they cannot picture.
- A specific title. “Sync Shopify orders to a Google Sheet and alert Slack on failures” gets bids; “Need automation help” does not.
- The business problem, not just the technical ask — an expert who understands why often proposes something better than what you asked for.
- The concrete pieces: which apps, which data, roughly what volume, and any hard constraints.
- What a good outcome looks like, so both of you can tell when it is done.
- A timeline and, if you can, a budget range. A range is not weakness; it filters out mismatches before they cost either side time.
- Attachments where they help: a screenshot, a brief, an existing workflow export.
Attracts good proposals
- Names the apps and the trigger.
- States the volume ("~200 orders/day").
- Says what "done" means.
- Gives a budget range and a deadline.
- Mentions what has already been tried.
Attracts silence, or guesswork
- "Need an n8n expert" with no scope.
- No apps named, so nobody can estimate.
- No budget signal at all.
- "ASAP" with no actual date.
- Contact details instead of requirements.
What happens after you submit
Automatic policy screen
Your post and every attachment are checked against the content policy as they are created. Most posts pass and go straight to the board.
Human review, if flagged
If the automated check is unsure or recommends rejection, the post is held for a person to look at rather than being silently deleted. A human decision overrides the automated one in both directions.
Live on the board
Approved experts can see it, open it, and send proposals. You are notified as they arrive.
You review and select
Compare proposals, message candidates, then select one — which creates a contract to fund.
If your post is held for review
You will not see it on the public board yet. That is the hold working, not a bug. The usual cause is contact details or an off-platform link in the description — edit those out and it clears.
Limits worth knowing
- A job accepts up to 10 proposals by default. Once full, it stops taking more — which is in your interest, because 40 proposals is not 4 times more useful than 10.
- Free accounts can post 3 jobs by default; after that a subscription is required. Ordering services and accepting offers are never limited.
- A minimum engagement value may apply. If one is set, a proposal below it cannot become a contract, so mention your range to avoid wasting a bid.
Attachments are scanned
You can attach images, documents, and workflow JSON. Each file is checked before it is stored. Files carrying contact details, off-platform links, or policy-breaking content are rejected. Workflow JSON is worth attaching where it exists — it is the single most useful thing an expert can see when estimating.
Keep it on-platform
Do not include phone numbers, email addresses, or links to contact you directly. Posts are visible to every approved expert, and moving the engagement off-platform removes your escrow and dispute protection entirely.
34 articles · Ask a question