Let the close trigger the rest of the work
Cord already tells you what happens (email, Slack, webhooks) and its public API lets you build anything on top. What's missing is the middle step: chaining actions without writing code.
What we're building:
- Integration catalog: ready-made connections to the tools your operation already lives in, instead of a webhook someone has to program.
- Conditional flows: "if the quote is above a certain amount, request approval and notify the leadership channel"; "if the client doesn't open the link in 3 days, send the reminder." Rules that are visible, editable, and auditable.
- Chained actions: approval triggering the invoice, the client record, and the follow-up task, without anyone doing them by hand.
Why it isn't here yet:
An automation that fails silently is worse than not having one. Before opening it up, we want every flow to record what fired, when, and with what result, and to be retryable.
How it works
Choose a source event and define visible conditions.
Select one or more actions and test the flow before enabling it.
Review every execution, its result, and a retry option when it fails.
Availability and scope
Future initiative built on the existing API, webhooks, email, and Slack. It aims to enable automation without writing code.
Clear limits
It will not ship without execution history, actionable errors, and idempotency. A silent automation cannot move a sale or invoice without evidence.