DOCUMENT OPS
Run the README quickstart against each GitLab release and comment the result
When a release tag is pushed in GitLab, runs the README quickstart end to end against the tagged build and comments a pass/fail report on the associated merge request.
How it runs
The automated pipeline, trigger to output.
- TriggerRelease tag pushed in GitLabGitLab
- ActionCheck out tagged commit and extract quickstart blocksGitLab
- ActionRun quickstart sequentially in a sandboxShell
- LogicPass or fail from combined exit status
- OutputComment the verdict on the release MRGitLab
What it does
Makes the README quickstart a release-time acceptance test. On a new GitLab tag, it checks out exactly that revision, runs the documented quickstart as a real user would, and writes the outcome back as a merge request comment so a broken first-run experience can't ride out in a release.
When to use it
Use it for projects released on GitLab where the README quickstart is the contract with new users. Especially valuable when releases bundle dependency or API changes that can break the very first example.
How it works
- 1A tag push (release) event fires in GitLab.
- 2The workflow checks out the tagged commit into a clean sandbox.
- 3It extracts the quickstart code blocks from the README in order.
- 4It runs them as a single sequential script in the sandboxed shell, capturing exit codes and output.
- 5A branch decides pass or fail from the combined exit status.
- 6It posts a formatted comment on the release's merge request with the verdict and, on failure, the first error encountered.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Document Ops workflows
Narrate new Dropbox PDFs into MP3 audio versions
When a PDF lands in a watched Dropbox folder, extract its text and generate an ElevenLabs voice narration.
On-demand PDF narration via webhook with emailed audio link
Accepts a PDF URL through a webhook, generates an ElevenLabs narration with the requested voice, stores the MP3, and emails the requester a download link.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Batch-narrate a Google Drive PDF folder in multiple languages
On a schedule, finds PDFs in a Google Drive folder that lack audio, then generates ElevenLabs narrations in each configured language and files them into per-language subfolders…
Executed Contract Exhibit & Initials Completeness Gate
When a signed contract lands in a Dropbox intake folder, verify every required exhibit, schedule, and initialed page is present.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.