Integrations
You don’t have to move where you write.
Paste text, send a file, open one Google Doc or connect through the API.
Getting your words in
Four ways to bring work in
READING IT
Checking it against Northwind’s rules as it arrives.
- Paste it
- Nothing to install
- Send a file
- Word, Markdown, plain text
- Open it from Drive
- One file, no share link to loosen
- Send your guidelines
- Once — they become the rules
Try it on your own copy. /start needs no account, and nothing leaves your browser.
What should this plug into first?
One tap · no email
Where this sits
Check work before it reaches the scheduler
Your scheduler keeps its job. Inkstand checks the draft before publication.
inside this product
- Made
- Cleared
The rules, the check, the release record and the sign-off.
leaves here
Approved copy, and the release record behind it
out and back
Text and a rule set out; findings and severities back
arrives here
Guidelines, each proposed rule carrying its source
nothing crosses
Sign-off is bound to the content and stays here
whatever you already run
- Scheduled
- Published
- Archived
And the automation runner, brand system and work tracker around them.
What crosses the boundary
Every connection is one of four shapes
The check is a live HTTP endpoint under your own account’s rules. What crosses is fixed here; which tool sits on the far end is yours.
| Tools on the other side | Direction | What crosses |
|---|---|---|
Publishing and scheduling
| leaves here | Approved copy, and the record behind it: what it was checked against, who signed it off, and anything let through. |
Automation
| out and back | Copy out, findings back — so the next step in your process can branch on the answer. |
AI workflows
| out and back | The same endpoint, called by whatever runs your assistant: it drafts, gets judged, and rewrites until it passes. You wire that up; there is nothing to install. |
Brand systems
| arrives here | Your guidelines, read where they already live. Each rule quotes the line it came from; anything unsourced is thrown away. |
Work management
| nothing crosses | Nothing. Sign-off covers the exact words and stays here, so it outlives the thread it was asked in. |
Archiving
| leaves here | The record: who published what, when, under which rules, and the written reason for anything waived. |
Build your own
Connect your own stack
The check, called from anywhere
Copy in, findings back, each one pointing at the words that broke a rule — under the rules your account already holds.
How that works →The register, out as a file
Every release, waiver and signature, as CSV for a spreadsheet or as JSON with the hashes intact — so somebody else can verify it without our help.
What is in the file →Your closed periods, in their calendar
One subscription URL will carry every embargo and quiet period into Google Calendar, Outlook or Apple Calendar, and a window added here will appear there on its own. The feed is written and not yet deployed — it is the one thing on this page you cannot call today.
Your turn
Which connection should we build next?
Tell us which connection would help your team.