Event id: commitment.created
Fires the moment a promise is captured, either yours or the buyer’s.
When it fires
When Doris extracts a commitment from a processed meeting or a classified email and records it. It fires once per commitment, so a call that produced four commitments fires four runs.
What the flow receives
- Commitment — The promise as Doris captured it
- Owner type — Whether the rep or the buyer owes it
- Due date — The date it is due, when one was stated or implied
- Deal — The deal it belongs to, expandable into full deal context
- Source meeting — The meeting it came from
Good uses
- Create a task in the CRM for every rep commitment, so nothing lives only in Doris
- Send the rep a same-day list of what they just committed to
- Flag commitments captured with no due date, which are the ones that get forgotten
- Post buyer commitments into a channel so the team knows what to chase
Things to know
- One meeting can fire this many times. If you want a single digest instead of one run per promise, use a Daily schedule flow that lists open commitments, or trigger on After a deal meeting and list the meeting’s commitments in one step.
- Add a Continue if on owner type to separate what your team owes from what the buyer owes. They usually deserve different treatment.
- Commitments captured from email arrive whenever that email is classified, which may be well after the call.
- Doris does not chase the buyer. A flow on this trigger ends at a person on your side, never at an automated message to the buyer.
Filtering on owner type is almost always right. A rep commitment wants a task; a buyer commitment wants a human to follow up.
