sumsub-create-workflow — Claude Code skill for Sumsub workflows

What sumsub-create-workflow does

The skill builds an ApplicantWorkflow JSON payload from a compact node/edge spec, runs a dry-run validation, saves the result as a draft and then publishes it with PUT /{id}/revisionStatus. It reports back name (kind), revision, revisionStatus and id. There are three kinds: default runs for every verification, actions runs for applicant actions, and test is isolated — launched manually per applicant and never publishable. Every save adds a revision to that singleton rather than creating a new workflow.

Drafts route no traffic, so creating, updating and validating them is safe. A publish is a different matter: it makes the revision live for all production traffic and auto-archives the previous one. A sandbox sbx: token does not help here, because revisions are shared between live and sandbox and only applicants are isolated. That is why publishing default or actions goes through an exposure gate. When the published revision's levels show more than 400 recent applicants, or the count cannot be read, the skill wants a clean validation, a diff against the current published revision, an explicit yes and SUMSUB_ALLOW_WORKFLOW_PUBLISH=1. The threshold can be overridden with SUMSUB_PUBLISH_TRAFFIC_THRESHOLD. Counts are level-derived, so revisions sharing level names report overlapping numbers.

You need an App Token carrying the manageWorkflows permission plus a sandbox pair: SUMSUB_APP_TOKEN in the sbx:... form and SUMSUB_SECRET_KEY.