Northwind's CRM has no webhook — onboarding sync must poll on a 15-minute cycle
Discovered in week one. The whole automation design depends on it and it is not negotiable on their side.
The record
Northwind runs a self-hosted CRM two major versions behind, with no outbound webhooks and no plan to upgrade inside this engagement. The sync polls every fifteen minutes, which sets the floor on how fresh any downstream state can be. Do not design a Northwind workflow that assumes sub-minute freshness, and set the client's expectation on latency at kickoff rather than at handover.
Applies to
- Company
- AI Automation Agency
- Department
- Delivery
- Agent
- No single agent
Context bound to one project, from kickoff to close. Readable by: Everyone on the project.
Provenance
Northwind technical discovery, 03 Jul 2026
Conversation · human in the loop
logs/agency/job_1802.json
- Recorded by
- Delivery Manager
- First learned
- 03 Jul 2026
- Last updated
- 20 Jul 2026
Index state
Not embedded- Index
- project-active
- Vector id
- —
- Model
- —
- Indexed at
- —
- Rank weight
- 1.00
No vector store is connected, so this record has no embedding. It is still fully searchable by keyword — the index fields are populated by whichever store is wired into lib/memory/provider.ts.