WarpBuild
The WarpBuild integration lets Helios agents search and call the entire WarpBuild API to manage runners, builders, cloud connections, and monitor build infrastructure.
What your agents can do
Helios agents don't work from a fixed list of WarpBuild actions. They semantically search WarpBuild's entire API and call any endpoint directly, with your access token injected server-side - so anything the WarpBuild API exposes, an agent can do for you.
- Manage runner images, instances, and pools
- Configure builders, builder profiles, and build sessions
- Connect and manage GCP, AWS, and Azure cloud providers
- Track jobs, usage, and daily cost snapshots
- Manage stacks, snapshots, and VCS integrations
Authentication
| Method | Type | Description |
|---|---|---|
| Personal Access Token | PAT | Authenticate with a WarpBuild Personal Access Token |
See Integration authentication for how credentials are stored and injected.
Personal Access Token
Authenticate with a WarpBuild Personal Access Token (wb_pat_…), supplied as the accessToken.
- Go to your WarpBuild dashboard.
- Open your account settings.
- Generate a Personal Access Token (format:
wb_pat_xxxxxxxxxxxxxxxxx). - Paste the token into Helios as the access token and save.
Triggers
WarpBuild does not emit event triggers into Helios. Only GitHub, Slack, and Plain do. Use WarpBuild from chat, or from a workflow started by a schedule, webhook, or manual trigger.
Last updated on