SECOPS
Log approved license exceptions to a Confluence compliance ledger
Receives license-decision events via webhook and appends each approved copyleft exception — package, license, repo, approver, and rationale.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives license decisionHTTP webhook
- LogicValidate and filter to approved exceptions
- ActionRead current compliance ledger pageConfluence
- OutputAppend exception row to Confluence ledgerConfluence
What it does
This workflow is the system of record for your license exceptions. It listens on a webhook that your PR gate or legal-approval flow calls whenever a copyleft dependency is approved into a codebase. Each event carries the package name, version, license, repository, the approver's identity, and a short rationale. The workflow normalizes that payload and appends a new row to a structured table on a Confluence compliance ledger page, timestamped and attributed. Over time the page becomes a complete, searchable record of every copyleft package your organization knowingly accepted and why.
When to use it
Use it when auditors, customers, or your own legal team need evidence that copyleft usage is deliberate and documented rather than accidental. It pairs naturally with an approval workflow: that flow makes the call, this one writes it into the permanent record. Ideal for regulated industries or vendors who must demonstrate OSS governance during due diligence.
How it works
- 1An incoming webhook receives a license-decision payload from your gate or approval workflow.
- 2A logic step validates the payload and ignores anything that is not an approved copyleft exception.
- 3The workflow reads the current Confluence ledger page and appends a new row with package, version, license, repo, approver, rationale, and timestamp.
- 4It writes the updated page back to Confluence, preserving the full history.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 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 SecOps workflows
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Page on-call when a WAF rule mass-blocks legitimate traffic
On demand or every few minutes, it detects a single Cloudflare WAF rule suddenly blocking a broad spread of ASNs and paths (a likely false-positive storm).
PII Content Scan on New Dropbox External Share
When a file gets an external Dropbox link, it reads the file content, uses an AI classifier to detect PII or secrets.
Compile a weekly WAF tuning review with trends to Confluence
Every week an agent rolls up Cloudflare WAF block clusters by rule and ASN, compares them to prior weeks for trend direction.
Sensitive Dropbox Link Owner Remediation Loop
When a newly created Dropbox shared link points to a sensitive file, this workflow DMs the file owner, gives them a deadline to justify or revoke it.
GitLab Push Secret Detection to Block and History Purge
On a GitLab push that contains a detected secret, it revokes the exposed credential, opens a tracking issue with git-history purge instructions.
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.