Developer
Start a motion when your system says so.
Send an event and a motion can act on it. Subscribe to events here and your systems learn what happened commercially — an opportunity created, a meeting booked, an approval requested, a deal won.
What connects
Signed HTTP webhooks, in both directions.
What crosses the boundary
- Into the platform: your event payload, treated as data and never as instruction.
- Out of the platform: signed commercial lifecycle events.
- Never: credentials, or another organisation's events.
What this makes possible
- Lets an event in your own product start a commercial motion
- Tells your systems when a commercial outcome occurs
Setting it up
- 1Register an endpoint and store its signing secret.
- 2Choose which events you want.
- 3Point a motion's trigger at your event type.
- 4Verify signatures on every delivery.
Permissions
Inbound events are authenticated and scoped to your organisation. Outbound deliveries are signed. An inbound event can start a motion; it cannot change what that motion is permitted to do.
Where it stops
An event triggers work; it does not grant anything. A payload cannot widen an agent's authority, change a communication policy or alter an approval rule — it is data. Delivery is at-least-once, so handlers must tolerate a duplicate. Events are not instant: this platform works in minutes, and a motion is the wrong tool for something needing a sub-second response.
Developer
Others in this category.
Make sure every opportunity gets a next action.
Let AI handle the repetitive engagement, keep follow-up moving, and bring your team in when a customer needs a real conversation.
Agents identify themselves on every call · Nothing commits without you · [email protected]