A complete content creation and approval workflow managed from Asana. The system uses n8n and OpenAI to generate a campaign 'tone of voice' for approval, then creates all copy (blog posts, emails, ads) based on that tone. All drafts and feedback loops are handled within Asana tasks, with final blog posts automatically published to WordPress.
Marketing teams that already plan work in Asana often still produce content in a scatter of documents, chat threads and email chains. A campaign brief becomes a Google Doc, drafts are pasted into Asana comments, feedback happens in three places and the final blog post is copied manually into WordPress, sometimes with formatting lost. Nobody is quite sure which version was approved, and the tone drifts between the blog, emails and ads.
AI writing tools speed up drafting but make the coordination problem worse if used ad hoc. Each person prompts differently, so outputs vary in voice and quality, and there is no record of what brief or tone guidance a draft was based on. Managers end up re-reading everything closely. The team needs AI drafting built into the process they already use, with one agreed tone per campaign and approval steps that trigger the next action automatically.
A manager creates a campaign from an Asana template, filling in audience, offer, key messages and channels; a webhook starts the n8n workflow.
The OpenAI API drafts a campaign tone of voice and messaging guide, which is attached to an approval task for the manager.
Once that task is approved, n8n generates draft blog posts, emails and ad variations based on the approved tone and populates the corresponding Asana tasks.
Reviewers comment in Asana; a revision request triggers a redraft that incorporates the comments, keeping every version in the task history.
When the blog task is marked approved, n8n publishes the post to WordPress through its REST API as a scheduled or draft post with categories and metadata.
A marketing manager initiates a campaign from an Asana template. The n8n workflow generates a brand tone, which is approved in a task. The AI then populates other Asana tasks with draft emails and ad copy. When the blog post task is marked 'approved', the system automatically publishes it to the company's WordPress site.
n8n, Asana API, OpenAI API, WordPress REST API, Webhooks
Claims in blog posts, emails and ads must be accurate and substantiated under the Australian Consumer Law, so reviewers remain responsible for facts, prices and comparisons even when the AI drafts them. Marketing emails are commercial electronic messages under the Spam Act 2003, requiring consent, sender identification and an unsubscribe link, which the email templates should include by default. AI-generated text with little human input may not attract copyright protection under the Copyright Act 1968, so meaningful editing strengthens your position. Avoid pasting customer personal information into prompts.
This solution requires careful evaluation of cost-benefit ratio. Consider implementation only after thorough analysis and risk assessment.
Yes. The same pattern works with Monday.com, ClickUp, Trello or Notion, as long as they offer webhooks and an API. Asana suits it well because custom fields, templates and task approvals map neatly onto content stages, but the n8n logic can be adapted to other project tools.
There are many moving parts, including webhooks, status logic, redraft loops and publishing, which make the design complex. But each part uses well-documented APIs, so an experienced n8n builder can assemble and test it quickly. The time depends mostly on how clearly your approval process is defined.
Only if you configure it that way, which is not recommended. Publishing is triggered by a person marking the blog task approved, and a safe setup publishes to draft or scheduled status so someone previews the post in WordPress before it goes live.
Get expert guidance on implementing AI Content Lifecycle Automation for your business
Contact Our AI Experts