Go-to-market workflows

Two catalog AgentWorkflows help you tell people about what you ship. Both draft; neither posts, publishes or sends anything on its own. Both spend model tokens on every run, so neither runs until an org opts in.

AgentWorkflow	Runs	Ships
Release	Once each time a Release cuts its tag (release.cut)	Disabled
GTM weekly	Thursdays at 14:00 in the org's time zone	Enabled, but runs on schedule only while the org's scheduled runs are on

Both arrived with catalog v0.6.0. A catalog upgrade keeps whether each AgentWorkflow is enabled, so in an org seeded from an earlier catalog, where release was enabled, it stays enabled and runs on every cut tag. Switch it off there if you don't want the drafts.

Announcement drafts for each Release

When a Release cuts its tag (step 3 of Release and promote), Infrared starts every enabled AgentWorkflow in the org that has an event: release.cut trigger, once, for that Product and version. The Release lists the runs in status.cutRuns, and each run's trigger reads event:release.cut:<product> <version>. Promotion carries on alongside; the runs don't hold the Release up.

The catalog's release AgentWorkflow is the one that listens:

A run started by release.cut has no Change, so each agent step works in report mode: it reads the Product's repo and the Release and opens an issue with its draft. The socializer ships disabled, so social-drafts is Skipped until you enable that AgentRole. A person reviews every draft at approve-announcements.

:::note Publishing is still yours A release.cut run has no pull request, so publish has nothing to merge: once the drafts are approved it closes the run with verdict DONE. The approved drafts are in the issues the steps opened; post them yourself. Publishing to the marketing site and social networks is planned. :::

Turn it on or off. An org admin uses Agents → AgentWorkflows → Enable (or PATCH /v1/orgs/{org}/agentworkflows/release/enabled with {"enabled": true}). Once it's enabled, the next cut tag starts a run.

Any AgentWorkflow you write can listen for the same event:

triggers:
  - type: event
    event: release.cut

GTM weekly

gtm-weekly runs two steps side by side, each in report mode:

Step	AgentRole	Leaves behind
social-listening	Social listener	A digest of the week's mentions of the Product, with drafted replies, as an issue when a mention needs a person.
newsletter-draft	Newsletter	The week's newsletter draft from merged Changes and Releases, as an issue for a person to edit and send.

A step that fails doesn't stop the other. Failures that need a person go to @platform/marketing. One run at a time.

It runs every Thursday at 14:00 in the org's time zone, once per Product, but only while the org's scheduled runs are on (Settings → Scheduled runs, off by default). To try it without turning schedules on, choose Run now on the AgentWorkflow in Agents. See Triggers and scheduling.