Coordinate is an event log. Your tools, your apps, and your agents write events to it; you and your agents read it with SQL; and triggers act when an event arrives or a query's result becomes true. Everything Coordinate does is itself written to the log, so what happened and why is always a query away.
The parts
- Sources append events: GitHub, Notion, Linear, Cloudflare, Granola, Todoist, Gmail, Claude Code, Claude Managed Agents, your own apps over HTTP, agents with
emit, and pollers that read any API on a schedule (web pages and feeds, Vercel, and GitHub pull request readiness are built-in pollers). - The log keeps every event in order, hash-chained, in an open format you can export and verify yourself.
- Queries are read-only SQL over the log, for people and agents.
- Triggers watch the log: when an event matches, or a query's result goes from false to true, then run actions: send a webhook, message Slack or Discord, send an email, call any API, record an event, start a Claude agent session, or text through Poke.
Where to go next
- Quickstart: from sign-in to your first trigger in five minutes.
- Triggers and Actions: the two halves of automation.
- Searching the log: the SQL schema and example questions.
- Connect an agent: give Claude, Cursor, Poke, or any MCP client access to your log.