Skip to content

Create an Automation

Create the workspace automation boundary, issue the automation secret, and store that secret safely because it is only shown once.

Best for Workspace manager Updated April 3, 2026
CLI In this interface
4 steps Steps
3 interfaces Available in
Use this path when

The CLI create command can also store the newly issued secret as the active token when that is convenient for the next step.

What you'll finish here
  • Create the automation boundary correctly.
  • Choose scopes and team limits deliberately.
  • Capture the secret safely the first time.

Where this happens

LabelValueNotes
Command./backlog.sh admin automations create [options]Creates an automation.

Same Task, Other Interfaces

Use the version that matches where you are working now. The subject matter stays the same; the delivery changes by surface.

Do the work

  1. 1. Run the create command with `--name` first, then add `--provider-type`, repeated `--team-id`, repeated `--scope`, and `--credential-label` if needed.
  2. 2. Add `--use` if the current CLI profile should immediately switch to the new automation secret.
  3. 3. Review the JSON response and capture the automation id.
  4. 4. Continue with exchange or visible-agent creation only after the secret is stored safely.

Keep Going in Automation and Agents

Stay in the same interface and move to the next closest task in this topic when needed.

Nearby Guides

These guides stay close to the current workflow so you can keep moving without restarting discovery.