DOCUMENT OPS
Re-run README examples on dependency-bump PRs and report to Discord
When a dependency-update PR is opened, re-runs the README install and import examples against the bumped versions and posts the result both as a PR comment and to a Discord…
How it runs
The automated pipeline, trigger to output.
- TriggerPull request openedGitHub
- LogicOnly continue for dependency-update PRs
- ActionInstall bumped deps and run README examplesShell
- LogicPass or fail from the run
- ActionComment the verdict on the PRGitHub
- OutputPost the result to DiscordDiscord
What it does
Catches the most common silent drift: a dependency bump that breaks the documented install or import. When a bot opens a dependency-update PR, this workflow checks out that branch, runs the README's install and import examples against the new versions, and reports pass or fail to both the PR and a Discord channel.
When to use it
Use it if you rely on Dependabot or Renovate and have been burned by upgrades that changed an import path, renamed an export, or dropped a documented flag. It makes "does the README still work after this bump" an automatic answer.
How it works
- 1A pull request is opened on GitHub.
- 2A filter keeps only PRs from your dependency-update bot or branch prefix.
- 3The workflow checks out the PR branch and installs against the bumped lockfile in a sandbox.
- 4It extracts and runs the README's install and import example blocks in the sandboxed shell.
- 5A branch determines pass or fail from the run.
- 6It posts a status comment on the PR and a matching message to Discord with the verdict and any error output.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect DiscordCommunity channels + voice + bots.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.
