Getting Started

This guide walks through a first workflow that takes a ticket and posts an agent's plan back to it as a comment. It doesn't change any code, so it's a low-risk way to see how the pieces fit. Plan for about 30 minutes.

Before you start

• Preview access turned on for your account.
• Your catalog includes the services your tickets relate to, with owners.
• Your ticketing tool's API key, such as Linear, so the workflow can comment on tickets.

1. Create an Automation

1. Go to Automations and select New Automation.

2. Name it "Refine ticket into plan."

3. Add instructions, for example:

   Review the ticket's title and description. If there's enough information
   to act on, return a short plan: the likely cause, the files to change,
   and how to test the fix. If not, list the questions that need answers.

4. Choose a built-in agent and model, then save.

See Automations for more on instructions and settings.

2. Create a workflow

1. Go to Workflows and select New workflow.
2. Add two kickoff inputs: IssueId and Description.
3. Add an Automation step that runs "Refine ticket into plan," passing in the ticket description.
4. Add an HTTP request step that posts the Automation's output as a comment on the ticket. If you've saved a reusable HTTP request for this, choose it.
5. Select Save workflow.

3. Run it manually

1. Open the workflow and start a run.
2. Enter a real ticket's ID and description when asked.
3. Watch the run on the workflow's Runs tab, then check the ticket for the comment.

See Workflow runs for how to read a run's steps, output, and logs.

4. Start it automatically

Once the manual run looks right, add a webhook trigger so tickets start runs on their own. For example, start a run whenever a ticket gets a specific label. See Triggers for the condition and input mapping setup.

Next steps

• Add a second Automation that generates a code change when the plan is ready, with an approval step before the pull request. See Use cases and examples.
• Review agents in the Agent Registry.