Repository navigation
Conversation
Regenerate the schema from argos-ci/argos#2787 (branch claude/arg-539-webhook-support-a3eaa7), which is not deployed yet. It adds the account webhook endpoints: list, create, get and delete a webhook, list and get its deliveries, and resend one. It also adds that PR's project events feed (`listProjectEvents`) and the payload of each event under `webhooks`. Because the event payloads are used as request bodies, the generator now emits output variants of a few shared schemas (`UserOutput`, `AccountOutput`, `AgentOutput`, ...), and `Comment`, `Project`, `TeamMember`, `ProjectContributor` and `BuildReviewers` reference those. Both variants have the same shape. The regeneration also picks up fields production already serves: `description` on screenshots and `githubDeploymentEnabled` on projects. Refs ARG-539 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`argos webhook list|get|create|delete` manage an account's webhooks on
`/accounts/{accountSlug}/webhooks`. `create` takes `--url`, `--events`
(one or more of build.completed, build.reviewed, deployment.created,
deployment.ready) and `--projects` (every project, including future
ones, by default), and prints the signing secret: Argos returns it once.
`argos webhook delivery list|get|resend` inspect what Argos sent:
`list` filters on `--status` and `--event-id` and follows pagination up
to `--limit`, `get` prints the request body and the start of the
response, and `resend` sends the event again as a new delivery.
Every command takes `--account` (or ARGOS_ACCOUNT) and needs a personal
access token or an `argos login` session with Admin access, like the
other account commands. Response bodies and failure reasons come from
the endpoint, so they are sanitized before reaching the terminal; a new
`sanitizeTerminalBlock` keeps their lines.
The argos-cli skill covers the commands, the secret and a debugging flow.
Needs argos-ci/argos#2787 deployed: the endpoints answer 404 until then.
Refs ARG-539
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gregberge
added a commit
to argos-ci/docs
that referenced
this pull request
Nov 20, 2026
Follow argos-ci/argos-javascript#429: add a "Manage webhooks from the CLI" section to the webhooks page (create, then find and resend failed deliveries), and a "Managing webhooks" section to the CLI reference, with the commands in its table and webhook delivery list among the paginated lists. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
argos-ci/argos#2787 no longer splits the schemas shared with the event payloads into input and `…Output` copies (fixed in its commit 802637754), so `UserOutput`, `AccountOutput`, `AgentOutput` and the other copies are gone. `Comment`, `Project`, `TeamMember`, `ProjectContributor` and `BuildReviewers` reference `User`, `Account` and `Agent` again, as in production. The webhook endpoints and their schemas are unchanged. Next to production, the schema now only adds the webhook endpoints, the project events feed and the event payloads. Refs ARG-539 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds webhook management to the
argosCLI, on the REST endpoints from argos-ci/argos#2787.Important
Merge and release this after argos-ci/argos#2787 is deployed. Until then every
webhookcommand gets a 404.Commands
All of them take
--account <slug>(orARGOS_ACCOUNT),--tokenand--json, and need a personal access token or anargos loginsession with Admin access (account:admin), like the other account commands.argos webhook listargos webhook get <webhookId>argos webhook create --url <url> --events <events...> [--projects <names...>]build.completed,build.reviewed,deployment.created,deployment.ready. Without--projects, the webhook gets every project, including future onesargos webhook delete <webhookId>{ deleted: true, webhookId }with--jsonargos webhook delivery list <webhookId> [--status pending|success|failed] [--event-id <id>] [--limit <n>]--limit(100 by default)argos webhook delivery get <webhookId> <deliveryId>argos webhook delivery resend <webhookId> <deliveryId>--eventsand--projectstake several values after one flag (--events build.completed build.reviewed) or a repeated flag.--projectsfollowsargos account project-token create; it is not--project, which meansowner/projecteverywhere else in the CLI.webhookis a top-level command, likeautomation, rather thanaccount webhook, so the delivery commands stay three words deep.Sample output of
argos webhook delivery get:The response body and failure reason come from the endpoint, and the request body carries branch names and other user text, so they go through a new
sanitizeTerminalBlock: it strips escape sequences likesanitizeTerminalTextbut keeps line breaks.API types
packages/api-client/src/schema.tsis generated from the argos branchclaude/arg-539-webhook-support-a3eaa7, since production does not serve these endpoints yet. Besides the webhook endpoints, it brings:GET /projects/{owner}/{project}/events,listProjectEvents, no CLI command here) and each event payload underwebhooks.descriptionand projectgithubDeploymentEnabled.No existing schema changes: next to production, the file only adds. The first regeneration (c542e75) briefly had
…Outputcopies of shared schemas from a bug in argos-ci/argos#2787; 3144d16 regenerates without them, so c542e75's message still mentions them. Squash-merge, or reword c542e75 before merging, to keep that out of main.Docs
argos-cliskill lists the commands, sayswebhook createprints a secret once, and adds a create and a debug flow.Tests
commands/webhook/index.test.tsruns each command through Commander against a stubbedfetchand checks the method, path, query and body sent, plus the output.format.test.tscovers every formatter;terminal.test.tscoverssanitizeTerminalBlock.Refs ARG-539
🤖 Generated with Claude Code