TriggersComing soon

Anyone who can use plugins can start a run from the plugin's page with Write a brief: "What should it write, for whom, and what must it mention?" They can also pick a Repository (optional), for work that is about one repository's changes. triggers adds more ways to start a run.

Manual brief formCopy Anchor Link

triggers:
  - on: manual
    form:
      brief: text
      channels: [linkedin, blog, email]

Each form field is text (a box to write in) or a list of choices to pick from. The run receives the answers and who asked. That person can never approve the run's output.

ScheduleCopy Anchor Link

triggers:
  - on: schedule
    cron: "0 14 * * MON"

cron has five fields: minute, hour, day of month, month, day of week. A scheduled run that finds nothing to do should say so and save nothing; write that into the agent's instructions. Turning a plugin off, or removing it, stops its schedules.

ReleaseCopy Anchor Link

triggers:
  - on: github.release

Runs when a release is published on a GitHub repository the team connected. The run gets the release notes CoderHelm wrote for it.

RunsCopy Anchor Link

Every run is listed under Plugins → Runs, with what started it (manual, schedule or release), the plugin version, who asked, the tokens used and the drafts it saved. A run is queued, running, completed, failed, or refused (for example when a limit is reached), with the reason.

Adding a trigger in a new version waits for an admin. See Versioning and updates.