integrations
Upstream of the scheduler
Clearance is the part worth handing to another tool. Here is where this product sits in a publishing stack, and what each connection carries across the boundary.
Where this sits
Two of the five stages, and no ambition on the other three
- Made — this product
- Cleared — this product
- Scheduled
- Published
- Archived
Scheduling is a crowded, solved category and being a worse Buffer is not a plan. Archiving sits on the wrong side of publication for a tool whose whole job happens before it. So the thing worth handing to another tool is the check, not the editor.
The rule engine has never known that the text came from slides — /check runs it on anything you paste, with no account and nothing leaving the browser. That makes a connection a small surface rather than a rewrite.
What crosses the boundary
Every connection is one of four shapes
Copy and a rule set go one way; findings, their severities, which tier decided each one, and whether anything blocking is unresolved come back. Everything below is a variation on that.
Tools
Direction
What crosses
Publishing and scheduling
Buffer · Hootsuite · Later · Sprout Social · Sprinklr
leaves here
Approved copy, and the release record behind it — what it was checked against, who signed it off, and whether any blocking rule was waived.
So the person who presses publish can see the clearance rather than take it on trust. No calendar gets built on this side.
Automation
n8n · Make · Zapier
out and back
Text and a rule set out. Findings, severities and an unresolved-blocks flag back, so the next node can branch on the answer.
Three runners reach almost everything else you already have, so a check step here is a check step in whatever tool the rest of your process lives in.
AI workflows
MCP server
out and back
The check and a brand kit, offered as tools an assistant can call. It drafts, gets judged, and rewrites until it passes.
Judged against your actual banned phrases, disclaimers and closed periods, with no editor in the loop at all. The check is the defensible part, so it belongs in drafting tools we did not write.
Brand systems
Frontify · Brandfolder
arrives here
Guidelines, read where they already live. Each proposed rule carries a page number and a verbatim quote; anything unsourced is discarded and counted.
So an edit to the guidelines becomes a proposed rule change here, instead of a document nobody re-reads.
Work management
Slack approvals · Asana · Monday · Notion
nothing crosses
Nothing. Sign-off is bound to a fingerprint of the content and lives here, so it survives the thread it was asked in.
Change a headline and approval flips back to needs re-approval without anyone remembering to. Pushing the request into Slack would move where it gets asked, not where it gets recorded.
Archiving
Smarsh · Global Relay · Proofpoint
leaves here
The release record: who exported what, when, which rules were snapshotted at the time, which blocking rules were waived, and the written reason given.
These systems capture published communications and this one sits before publication, so the overlap is narrow and worth naming precisely rather than inflating. Handed over, it puts the evidence from before publication next to the artefact from after it.
One of these is not hypothetical: reading a guidelines PDF already works today. Upload the document and it proposes voice rules, each carrying a page number and a verbatim quote, with anything it cannot source discarded and counted. A brand-system connection is that same job without the upload.
Build your own
If none of the above is your stack
The check, over HTTP
Blocks of text and your own address for each one in; findings back, each carrying that address unchanged, the tier that produced it, and a character span into the text you sent. Under the rules your account already owns.
How the review engine works →A signal when the record changes
A release gets recorded, or an approval stops being true because somebody improved a headline. Those are the two moments another system needs to hear about, and everything a connector would do with them starts there.
Your turn
Which of these would you actually use?
Pick as many as apply. Not a waiting list and not a signup — your answers weigh on what gets attention, and nothing else happens unless you leave an address.