Skip to content

[Opportunity webhooks] - Multiple calls for a single change #27

Description

@Cobeas

When working with opportunities there is a series of webhooks sent that are either unnecessary or redundant. This is a big issue if you have a(n) expensive function(s) running as a result of this webhook.

What webhooks are sent on which occasion

  • Creating an opportunity : [ opportunityCreate, opportunityUpdate ] <- no need for update
  • Updating an opportunity without changing the monetary value: [ opportunityUpdate ] <- correct way of doing this
  • Updating an opportunity including the monetary value: [ opportunityUpdate, opportunityMonetaryValueUpdate ] <- no need for update only monetary value update IMO
  • Updating an opportunity status: [ opportunityUpdate, opportunityStatusChange ] <- ?why?
  • Deleting an opportunity: [ opportunityDelete, opportunityUpdate ] <- again why do we get the update?
  • Changing the stage of an opportunity: [ opportunityUpdate, opportunityStageChange ] <- no need for update IMO
  • Changing the assigned user to the opportunity: [ opportunityUpdate, opportunityAssignedToUpdate ] <- no need for update

Why is this an issue

If I, for example, update an opportunity's name ánd the monetary value in one go I would only get the two webhooks [ opportunityUpdate, opportunityMonetaryValueUpdate ] but if I would filter out the first one because that is not needed for the monetary value update I would miss out on that change. But if I were to handle both webhooks every time the monetary value updates I do a lot of work for nothing.

What do I like to see

It would be very helpful if we could just get the webhook for what really happens when you do something with an opportunity and not get a bunch of things and then 'just figure out yourself what happened'

Product Area

opportunities

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions