Scheduled work that reads the same record you do
A scheduled job can read the decisions you made. You can read what it kept.
The Problem
Automations run when nobody is looking. A workflow that calls a model starts from its own prompt. The rules you settled in a chat last week are not in it.
So the automation does something sensible but not what you decided, or you copy the rule into every workflow and then keep copies in step.
How Stompy Helps
A Stompy project is a record any tool that can make an HTTP request can read. That covers n8n, Zapier and Make, and workflow engines such as Temporal, Prefect, Dagster, Airflow and Inngest.
A workflow searches the project for the rule that applies and includes it in its prompt. The rule lives in one place, and you change it in one place. If a workflow should keep something, it locks an entry, and the entry is visible to you and to every other tool.
Keep the writing deliberate. Reading is safe to give to anything. Writing is worth giving to few workflows, because the record is only useful while it stays short enough to read.
Integration Walkthrough
Create a project API key for the automation
A key is scoped to one project. A project API key is minted by the project's owner while signed in, and works for that one project only. Read the project's own contexts and search with it; managing the project still needs a signed-in user.
# sent as a header on every requestAuthorization: Bearer $STOMPY_PROJECT_KEY
Read the rule that applies
An HTTP request step: GET with a query. The response lists matching entries with their content.
curl -G https://api.stompy.ai/api/v1/projects/my-project/search \-H "Authorization: Bearer $STOMPY_PROJECT_KEY" \--data-urlencode "query=refund policy" \--data-urlencode "limit=3"
Keep a result, only where you want one
An HTTP request step: POST with a topic and content.
curl -X POST https://api.stompy.ai/api/v1/projects/my-project/contexts \-H "Authorization: Bearer $STOMPY_PROJECT_KEY" \-H "Content-Type: application/json" \-d '{"topic": "weekly_report_findings", "content": "Finding: ... Measured: ... Verify by: ..."}'
What You Get
- A rule lives in one place and is changed in one place
- Anything that can make an HTTP request can read the record
- Keys are scoped to one project, so an automation sees only what it needs
- You can read and correct whatever an automation kept
Start your own record
Join the waitlist and we will tell you when your place is ready.