CONTENT CREATION

Build a Full Campaign Calendar from a Pillar Post with a Content Agent

An agent reads a pillar blog post, decides how many channel assets each angle warrants, drafts a sequenced two-week campaign with per-channel tone.

CategoryContent Creation
Enginepaperclip
Difficultyadvanced
Triggermanual
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOperator starts agent, points at pillar post
  • ActionRead post, extract distinct anglesNotionNotion
  • LogicAgent decides asset count + sequencing per angle
  • ActionDraft per-asset copy in channel toneOpenAI
  • LogicAssign publish dates across two-week cadence
  • OutputCreate scheduled tasks in Asana campaignAsanaAsana

What it does

Uses an agent to plan, not just transform: it reads a long pillar post, identifies the strongest sub-angles, decides how many posts each angle deserves across channels, and builds a sequenced campaign calendar as dated tasks.

When to use it

You have a flagship post and want a thought-out drip campaign rather than a flat dump of four reposts. Best when the right number and order of assets isn't fixed in advance.

How it works

  1. 1An operator kicks off the flow and points the agent at the Notion pillar post.
  2. 2The agent reads the post and extracts distinct angles worth their own asset.
  3. 3It reasons over channel fit and decides asset count and sequencing per angle — this branching judgment is why it runs on the agent engine.
  4. 4For each planned asset it drafts copy in that channel's tone (LinkedIn, X, newsletter).
  5. 5A logic step assigns publish dates across a two-week cadence.
  6. 6Output: the agent creates one scheduled, copy-filled task per asset in Asana, grouped under a campaign project.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect NotionPages, databases, comments.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect AsanaTasks, projects, milestones — everywhere.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.