List Automations
Review the current workspace automations before you create, update, or rotate one.
Use the workspace-scoped automation list endpoint when the reader needs automation ids or current automation state.
- Open the current automation inventory.
- Choose the right automation id.
- Avoid editing the wrong automation.
Where this happens
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. Resolve the workspace id first.
- 2. Call the workspace automation list endpoint with a human token that has `workspace.automation.manage`.
- 3. Read the returned automation ids, scopes, and team boundaries.
- 4. Use the right automation id for the next create-agent, update-automation, or rotate-secret action.
Keep Going in Automation and Agents
Stay in the same interface and move to the next closest task in this topic when needed.
Exchange an Automation Secret
Exchange an automation secret for an access token.
Create an Automation
Create the workspace automation boundary, issue the automation secret, and store that secret safely because it is only shown once.
Update an Automation
Change automation metadata, team boundaries, scopes, or suspension state without recreating the automation.
Rotate an Automation Secret
Issue a new automation secret when the old one should no longer be trusted, then replace it everywhere the old secret was used.
List Visible Agents
Review the current visible agent bindings before creating a new agent or editing an existing one.
Create a Visible Agent
Create a named visible agent under an existing installation so activity, assignees, and attribution can point to a meaningful product actor.
Update a Visible Agent
Change a visible agent name, team scope, role, or suspension state without recreating the binding.
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.
Create an Automation
Create the workspace automation boundary, issue the automation secret, and store that secret safely because it is only shown once.
Update an Automation
Change automation metadata, team boundaries, scopes, or suspension state without recreating the automation.
Rotate an Automation Secret
Issue a new automation secret when the old one should no longer be trusted, then replace it everywhere the old secret was used.