Automations and Content Loops
Beyond weekly reports: Autonomous Operator jobs that act through one granted tool, Content from data loops that turn a source into published pieces, and Scripts for deterministic sync work.
Reports and tickets are the weekly loop. Automations are for work that should happen without a weekly human pass: a job that acts through one tool you have greenlit, a loop that turns a data source into a stream of content, or a script that syncs data on a schedule. Turn these on after the weekly loop produces tickets you trust.
Automations are enabled per workspace by the Cogny team. If you do not see New Automation or Content from data under Reports → Create new, ask your onboarding contact.
Autonomous Operator jobs
An operator job is a scheduled agent with one granted write tool. Reports → Create new → New Automation opens "Create Autonomous Operator Job":
- Job name and operator instructions: what to check and what to do.
- Autonomous operator toggle.
- Integration and tool: the single write action the job may take, on the one connected server. You can pin it to a constraint, such as one Discord channel or one campaign.
Each run is recorded as a ticket, so the board shows what the job did and the analysis step evaluates it. The first run starts as soon as you create the job.
What operator jobs are good for:
- Posting a daily "what we shipped" summary to a Discord channel (a built-in template, Shipped Announcement, does exactly this).
- Keeping negative keyword lists updated from search-term reports.
- Pausing ads that breach a cost-per-lead ceiling, with the pause tool granted and nothing else.
- Filing a ticket when a metric moves beyond a threshold.
The grant is enforced at call time inside the execution engine, not only in the prompt, so an instruction cannot talk the job into a second tool. Start with a read-mostly job and one low-risk write, watch the tickets it creates for a week, then widen.
Content from data loops
A content loop turns a source into individual pieces, one ticket each. Reports → Create new → Content from data. The wizard shows a preview of the source rows, produces a test piece first, and nothing is published until you turn the schedule on.
Sources
- A BigQuery table in your warehouse (a daily summary, a product feed, an event list). You pick the cursor column that identifies new rows.
- An RSS or Atom feed: news, releases, a partner's blog.
- A document in the context tree, split into sections, each becoming a piece from a different angle.
- Best-performing pages from Search Console, to localise winners into other languages.
- Custom SQL for advanced cases.
Keywords for each piece come from a context-tree node (a keyword plan), Search Console's top queries, Google Ads keyword ideas, or the writer's own choice.
Publish targets: a table in your Supabase project, a WordPress or Ghost draft, Webflow, Framer or Sanity, a Shopify blog article, a Lovable site, or a GitHub repository through the coding agent as a pull request.
Limits and safety: at most five pieces per run, the last 200 source rows are considered, and the loop remembers what it has already covered so nothing is published twice. Three consecutive source failures pause the loop. Each piece is a ticket, so you can keep approval on the ticket or let YOLO handle pieces above your threshold.
The flagship pattern is the SEO and localisation loop: produce content, watch Search Console for what ranks, rewrite titles and descriptions to match, add product links and calls to action once clicks arrive, then clone the winners into other languages. A Nordic apparel brand went from about 50 ranking articles to translations in dozens of languages this way, with organic becoming the main revenue channel. Doing that by hand on a thousand pages is impossible; in Cogny it is a couple of approvals a week.
A programmatic example: a platform's own backend rows (projects, listings, releases), classified and turned into one how-to page each, published to the repository.
Paid-to-crawl for new pages
Google crawls a fresh domain rarely. If you launch many new pages, buy a small amount of traffic into them (Google, X or LinkedIn) to raise crawl budget. Expect two to three months for a new domain versus weeks on an established one. This is a strategy note for the growth strategy field, not a feature.
Scripts
Scripts are deterministic JavaScript jobs with no language model in the loop, for work that loops are too slow and expensive for: a nightly export into BigQuery, a backfill, a cursor-based sync from an API. They run in a sandbox with access only to the Cogny SDK: read tools always, write tools only with a grant, your own BigQuery, and a small state store.
Scripts are feature-flagged per workspace and managed through chat or MCP tools rather than a page: the agent creates the script, dry-runs it, you enable it. Failures do not retry silently; they file one deduplicated ticket with the error, the log tail and a sample payload, and the schedule pauses after three consecutive failures. With auto-repair on, the ticket is pre-approved for the agent with just enough tools to fix the script. Scripts are not metered.
Ask for Scripts if you find yourself wanting a nightly sync of something into your warehouse.
Solo loops
Solo-tier workspaces have a lighter loop feature designed for a single operator with their own agent. It is not part of Cloud; Cloud uses operator jobs and content loops described above.
Reading this with an AI agent? Fetch the raw markdown at /docs/automations-and-content-loops/index.md or see llms.txt.