Content Agent

Generate content from themes, call intelligence, or instructions; quality-loop it to a score; schedule it for review and notify reviewers in Slack.

Task type: Content Agent

Use Content Agent to produce reviewed-ready content on demand or on a schedule. It picks ideas, drafts each requested asset type with SEO/AEO research, revises until the quality score reaches your threshold, places pieces on the content calendar in Review, and notifies reviewers in Slack.

Run behavior

Side effects: This task is read-only or computation-only by default. It returns data for later steps rather than directly writing records or sending messages.
Credit usage: This task is not classified as credit-billed by the workflow task registry.

When to use this task

Generate a weekly article from the active content theme every Monday.
Turn recurring call objections into FAQ or comparison pages.
Produce a batch of Social posts from a free-form brief.

Setup tips

Optionally select a saved Content Agent profile in Content Engine > Agents so rules and skills are shared across workflows, Library, and Calendar.
Add a Timer trigger to the workflow for cron-based runs; use Run Workflow for on-demand runs.
Configure reviewers or a Slack channel so people know when content is ready.
Tune content skills on the Content Engine settings page; the agent follows them per asset type.

Examples

Every Monday, write one article from the active weekly theme plus two Social posts derived from it, each revised to a score of 75+.

Outputs

run_id and status "queued". Assets, calendar items, and score history are recorded on the run.

Common pitfalls

Adding a Slack step after the task — it would fire before the content is ready.
Setting a very high minScore, which increases revision rounds and credits without guaranteed gains.
Requesting many pieces per run on a frequent cron.

Reference details

These details are generated from the workflow task registry and match the fields available in the builder.

Required fields

ideaSource
assetTypes

Variable-aware fields

Fields that accept variable references ({{ inputs.x }}, {{ steps.N.y }}) from the workflow's variable graph:

instructions

Liquid template fields

Fields that are rendered through Liquid (variables plus filters and control flow):

instructions

Model guidance

Pair with a Timer trigger for scheduled runs. The task returns immediately; the run notifies reviewers itself.

Builder guidance

When the Workflow Builder Genie configures this task, it follows this guidance:

Pick ideaSource from the request (theme / intelligence / instructions). Keep piecesPerRun small for cron runs, always set reviewers or a Slack channel, and do not add a downstream Slack step expecting finished content.

Default configuration

New instances of this task start with the following configuration:

{
  "name": "Content Agent",
  "outputKey": "content_agent",
  "taskType": "Content Agent",
  "description": "",
  "ideaSource": "theme",
  "themeScope": "auto",
  "instructions": "",
  "assetTypes": [
    "article"
  ],
  "piecesPerRun": 1,
  "requireEvidence": false,
  "relatedContent": {
    "assetTypes": [
      "social_post"
    ],
    "countPerType": 1
  },
  "quality": {
    "minScore": 75,
    "maxIterations": 4,
    "maxSteps": 30
  },
  "schedule": {
    "windowStartOffsetDays": 1,
    "windowDays": 7,
    "timezone": "America/Los_Angeles"
  },
  "notify": {
    "reviewerUserIds": [],
    "emailUserIds": [],
    "emails": []
  },
  "skillIds": [],
  "excludeSkillIds": []
}

Content Agent

On this page