Event id: deal.updated
The catch-all deal trigger. It fires on field-level edits that are not covered by the more specific deal triggers.
When it fires
When your CRM tells Doris that one or more tracked fields on a deal changed. Some CRMs send one notification per changed field, so a single edit in the CRM interface can produce several events.
What the flow receives
- Deal — The updated deal, expandable into its full context
- Changed fields — The CRM field names that changed on this event
- Action — Whether the CRM reported this as a create or an update
Good uses
- Watch the close date and flag a push, especially a repeated one
- Notice an amount changing late in the cycle and tell the manager
- Re-check hygiene rules when a field the rules depend on is edited
- Keep a Doris record in step with a custom CRM field your team uses
Things to know
- This is the noisiest deal trigger. Always add a Continue if on the changed field, and lean on the flow’s cooldown so one editing session does not produce a run per keystroke-worth of change.
- Stage moves and closes have their own triggers. Use Deal stage changed and Deal closed for those rather than filtering them out of this one.
- Field names are your CRM’s internal property names, not the labels shown in its interface. Check the property name in the CRM before filtering on it.
- Bulk edits and CRM data imports fire this for every affected deal.
If you find yourself filtering this trigger down to one field, check first whether a more specific trigger already covers the case. Fewer runs and less filtering is always the better flow.
