What are content automations?

Content automations let you set up repeatable flows where an AI agent generates content automatically in response to a trigger or on a schedule. Instead of manually asking the assistant to draft a changelog entry every time you ship a feature, you configure the automation once and the agent handles it going forward.

Setting up an automation

  1. Navigate to Settings > Agents > Automations in your workspace.
  2. Click New automation.
  3. Give the automation a descriptive name, such as "Weekly feedback summary" or "Changelog entry on release."

Choosing a trigger

Every automation starts with a trigger — the event that kicks off the content generation:

  • Event-based — Fires when something happens in your workspace. Examples: new feedback submitted, feature request status changed, new release tagged.
  • Schedule-based — Fires on a recurring schedule. Examples: every Monday at 9 AM, first of the month, every Friday afternoon.
  • Manual — No automatic trigger. You run the automation on demand from the automations list. Useful for semi-regular tasks you want to standardize without fully automating.

Configuring the output

After selecting a trigger, configure what the agent should produce:

  1. Output type — Choose the kind of content: help center article, changelog entry, announcement, feedback response, or custom text.
  2. Prompt template — Write the instructions the agent should follow. Use placeholders for dynamic data. For example: "Write a changelog entry for {{feature_name}} released on {{release_date}}. Keep it under 200 words and use a friendly tone."
  3. Destination — Specify where the output goes: a specific collection in the help center, a changelog category, or the agent inbox for review.

Review settings

Decide whether the generated content should be published automatically or routed to the inbox for review:

  • Auto-publish — The content goes live immediately. Use this only for low-risk, well-tested automations.
  • Send to inbox — The content appears in the agent inbox as a proposal. A team member reviews and approves it before publication. This is the safer default.

Testing your automation

Before activating, use the Test button to simulate the trigger and see what the agent produces. Review the output carefully. If it does not meet your expectations, adjust the prompt template and test again.

Activating and managing

Toggle the automation to Active when you are satisfied with the test results. You can pause, edit, or delete automations at any time from the automations list. Pausing an automation stops it from firing without losing your configuration.

Tips

  • Start with inbox review. Route output to the inbox until you are confident in the quality.
  • Keep prompts specific. Vague prompts produce inconsistent output. Include tone, length, audience, and format instructions.
  • Combine with guidance. Your agent guidance settings apply to automations too, so set those up first for consistent results.

Was this page helpful?