All projects
AI Automation / n8n / Content Operations

ContentOps Review Automation

An n8n workflow that removes the back-and-forth between content reviewers and editors. When someone comments on an Asana task, AI reads the feedback, rewrites the draft, updates or regenerates the featured image, and posts a confirmation — without anyone opening WordPress.

Year
2025
Engagement
Workflow automation
Focus
Automation, Generative AI
Status
Open source
ContentOps Review Automation — architecture overview

01 — The problem

Content review is a queue of small handoffs. A reviewer leaves a comment, an editor reads it days later, applies it in WordPress, maybe swaps the image, then tells the reviewer it is done. The work is trivial; the waiting is not.

02 — Our solution

The Asana comment becomes the trigger. AI interprets the feedback as an instruction, applies it to the draft, handles the featured image, pushes the update to WordPress and confirms back on the task — so the reviewer's comment and the published change become the same action.

Architecture

How it works

The pipeline, step by step — from the first input to the final output.

  1. 01

    Asana trigger

    A new comment on a content task starts the workflow with the task context attached.

  2. 02

    Feedback interpretation

    AI reads the comment and decides what change is actually being requested.

  3. 03

    Draft rewrite

    The draft is rewritten to satisfy the feedback while preserving voice and structure.

  4. 04

    Featured image

    The featured image is updated, or regenerated when the feedback calls for something new.

  5. 05

    WordPress update

    The revised post and image are pushed through the WordPress API.

  6. 06

    Confirmation

    A confirmation is posted back on the Asana task so the reviewer sees the result in place.

Features

What we built

Comment-driven trigger — no new tool for reviewers to learn
AI interpretation of free-form feedback into concrete edits
Automatic featured image update or regeneration
Direct WordPress publishing via API
Confirmation written back to the source task
Impact

The outcomes

01

Review feedback and published change collapse into one step

02

No manual WordPress editing left in the review loop

03

Reviewers stay in Asana; the system meets them there

Engineering notes

Challenges we solved

Feedback is not an instruction

"This intro drags" is not an edit. Turning conversational review notes into a specific, bounded change was the core of the prompt design.

Not every comment is a request

Threads contain questions, agreement and chatter. The workflow has to decide when to act and when to stay quiet.

Technology stack

n8nOpenAIAsanaWordPressImage GenerationREST APIs

Want results like these?

Book a free 30-minute discovery call. We'll map out your project, recommend the right stack and send a fixed quote within 48 hours.