About

Below is a paste‑ready, hard‑core job post for Upwork. I’ve split it into the fields you’ll see in the UI (Title, Summary, Deliverables, etc.). It reflects the final 01–07 spec set and is public‑safe (no personal emails). Attach your one‑pager PDF + extended spec DOCX when you post.  ⸻ Job Title Trello/Butler + Make.com Automation Engineer — Build 6 Production‑Ready Features on Live CRM Board ⸻ Summary (About the job) We run a live Trello‑based CRM and need an expert to implement six specific, production‑grade features across an internal board and a public pipeline board. The build centers on Custom Fields + Butler automations + Make.com (Typeform/Tally webhooks), with clean UX on the card back and a branded, action‑oriented public board. You’ll work from a clear one‑pager (tickets 01–07) and deliver tested automations, buttons, and flows that our team can operate without code. No PII leaks and zero board downtime— use a duplicate/staging board and promote changes safely. ⸻ Deliverables (what you will build) 1. Priority enforcement (internal board) • Single‑select Priority CF (No/Urgent/High/Medium/Low). • Butler rules to block cards leaving Staging until Priority is set; sort button; hourly nudge for unset. 2. External intake (public → internal) • Typeform/Tally submission → Make.com → create card in To Review lane; dedupe; email notify; auto‑ack. 3. Public comments mirroring (moderated) • Public comments on board cards → webhook → internal audit comment + email notify; optional PII redaction. 4. Public board polish + CTAs • Branded board, “Start here / How to help” card, clean list set, Offer Intro button on every card (prefill fund). 5. Internal card‑back UX (single movement path) • Butler buttons: Next Stage, Back to Staging, Schedule Meeting & Move; remove unused power‑ups; reorder CFs. 6. Calendar single source of truth • Meeting Date (CF) ↔ Due date sync rules; meetings surface correctly in Calendar view. 7. Rollout + QA • Implement fields/rules/buttons; smoke test flows; handover docs (readme + rule list + env/configs). You’ll get a specs one‑pager and an extended doc. Build strictly from the one‑pager; extended doc is ⸻ Scope of Work (how we’ll collaborate) • Create a staging clone of the current boards; develop and test there. • Implement tickets 01–07 exactly; document Butler rules, Make scenarios, and CF schema. • Handoff: short runbook (activation, rollback, troubleshooting), plus source exports (Butler/Make). • Stay within email‑only notifications (we’ll provide a project alias at kickoff). ⸻ Acceptance Criteria (Definition of Done) • Priority enforced: cards entering Staging blocked until Priority ≠ No priority; “Sort Staging by Priority” orders Urgent→High→Medium→Low→No. • Intake: form submission creates card in To Review, de‑duped; approval moves to Staging with Priority flow; decline emails submitter. • Comments: public comment mirrored internally with link; email alert fired; PII not posted to public. • Public board: branded, Start‑Here card with CTAs (Submit, Calendar, Contact); lists = Introductions Welcome → Targeting → In Discussion → Meeting Scheduled → Committed; Offer‑Intro button prefilled. • Card‑back UX: guided buttons working; unused power‑ups removed; CF order = Priority, Meeting Date, Last Interaction, then contacts. • Calendar: editing Meeting Date or Due date keeps both in sync; events visible on Calendar view. • QA: 3 form submissions, 2 public comments, 5 Staging entries, 3 scheduled meetings — all emails received; no PII on public; no broken rules. ⸻ Required Skills • Trello Butler (advanced rules, board/card buttons, scheduled commands) • Make.com (Integromat) (webhooks, Trello modules, Typeform/Tally, Gmail/Email) • Trello Custom Fields & Power‑Ups; board architecture & UX • Typeform or Tally (prefill links, validation) • Webhooks, regex/PII detection (nice‑to‑have) • Optional: Trello Power‑Up (Node/Express) for future hard‑blocking UI (not in this sprint) ⸻ Experience • CRM/Kanban systems at production scale • Public‑facing Trello boards, moderation & anti‑spam • Calendar integrations; date logic; time‑zones