Works / MARA · Auto-Ticket Creation

The Automation That Turns Slack Requests Into Asana Tickets

The team drops marketing requests in a Slack channel. MARA keeps the real ones and turns each into a full Asana ticket — parent, every subtask, owner, priority, dates — then replies to whoever asked and keeps them posted from queue to done.

Client: Marketing Team · Role: Automation Engineer · Year: 2026 · Stack: n8n · Slack · Asana · Supabase · Claude

The story

The before: Every request meant reading the post to see if it was a real ask, then hand-building the whole ticket — board, title, description, priority, due date, owner, every subtask — and messaging the requestor. Easy to miss a piece.

The turn: So I had MARA take it. It keeps the real requests, builds the full ticket in Asana, replies to whoever asked, and keeps them posted till it's done.

How it works

  1. Real Request?: MARA reads every post in the channel and sorts out the real requests — only an actual ask moves forward, so the board stays clean.
  2. Build the Ticket: It builds the whole Asana ticket by the team's rules — board, title, a clean description, priority, the due date from the timetable, the right owner, and every subtask.
  3. Tell the Requestor: It replies in the thread with a clean overview — what was made, who owns it, when it's due — and tags the people involved.
  4. Keep Them Posted: From there it updates the requestor on progress, and pings the moment it's done.

The hard part isn't building the ticket — it's knowing which posts are even requests. A question, a thanks, a half-formed idea — none belong on the board. So MARA's first job is telling a real ask from the noise; only those become tickets.

What changed

is this post even a real request? did every subtask get built right? what's happening with my request now?

The numbers: 1 message — a whole ticket tree, built and tracked.

Fair questions

will it get the whole ticket right — subtasks and all?

Yes — parent and every subtask build together in one pass, up to three levels, each with its owner and due date, so nothing lands half-made. (from the build)

will it ping the whole team every time?

No — a routine request just confirms to the people involved; only a genuinely urgent one alerts the channel. (from the build)

will I know what's happening after it's made?

Yes — it replies with the overview, keeps you posted on the key progress, and pings when it's done. The honest catch: it structures and tracks the ticket; a human still does the work.

The reel continues

Previous: MARA · Activity Tracker · Next: Scout · Content Gap Analysis Automation · open my notebook?

Got a full ticket to build for every request, campaign, launch, ask? Ticket It — or discover my mastery.