Publish to Poki
Poki is a Release workflow destination for a web application directory, such as a Godot web export. Each upload needs a Game ID and version metadata. Pipelab uses the authentication cache created by Poki's browser sign-in flow.
Configure the destination
- Add Poki as a destination and enter the Poki project Game ID, Version name, and Release notes.
- Connect a web application directory artifact and run the Release workflow.
The three publishing fields are required and checked before execution. The action stages the artifact in a temporary directory, writes the Poki CLI configuration, and runs the pinned @poki/cli upload command. Sign in first with pipelab settings integrations poki login. The command prints Poki's browser sign-in link, exchanges the returned sign-in code, and saves the CLI-compatible auth cache under Pipelab's third-party configuration directory. On a server without a browser, open the printed link on another device and paste the final URL from that browser into the waiting terminal command. The command only signs in; it does not upload a build. Poki authentication is account-wide, so this command does not need a Game ID. If a workflow has no cached login, it stops before uploading and prints the sign-in command. CLI, network, authentication, and upload errors appear in step logs. The action declares no output variables; the Release workflow records delivery metadata.
The official Poki CLI supports these upload commands:
npx @poki/cli init --game <game-id> --build-dir dist
npx @poki/cli upload --name "<version>" --notes "<release notes>"Pipelab's sign-in command completes the browser authentication before any workflow upload. Once the CLI has cached the login, workflow uploads can run without opening a browser while the cached session remains valid.
Minimal destination values
project: <Poki Game ID>
name: 1.0.0
notes: Initial web buildCreate and configure the game in the Poki Developer Portal first. The game ID, version label, and notes must correspond to that project.