ENGINEERING
Maintain an approved-models registry in Notion as PRs clear license checks
When a PR that adds a Hugging Face model merges and the model's license passed policy, it upserts the model into a Notion approved-models registry with its license, task.
How it runs
The automated pipeline, trigger to output.
- TriggerPull request merged to mainGitHub
- ActionExtract added HF model IDs from diffGitHub
- ActionConfirm license and task from model cardHugging Face
- LogicKeep only approved-license models
- OutputUpsert model into Notion registryNotion
What it does
Builds and keeps current a single source of truth for which Hugging Face models are cleared for use. Every time a license-compliant model lands on the main branch, it is recorded in a Notion database so the team can see exactly what is approved, under what license, and when it was vetted.
When to use it
Use it when you need a durable, browsable record of vetted models for onboarding, audits, or to stop engineers from re-litigating a model someone already cleared. It complements the PR-time gate by capturing the outcome of every passing check.
How it works
- 1A GitHub pull request merged event triggers the run.
- 2Hugging Face model IDs added in the merged PR are extracted from the diff.
- 3The Hugging Face API confirms each model's license and task tags from its model card.
- 4A logic step keeps only models whose license is on the approved allowlist, so nothing non-compliant is recorded.
- 5Each approved model is upserted into the Notion registry with its license, task, source PR link, and approval date — updating the row if the model already exists.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Connect NotionPages, databases, comments.
- 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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.