Sync Leads feature --> abort when an existing lead is found, add webhooks?

[daisycrego]

Sync Leads feature --> abort when an existing lead is found, add webhooks?

Currently the Sync Leads feature will run for all the leads (>40,000) and update all of them. Without webhooks in place, this is the reliable way to know whether or not a lead has changed. However, we don't want to necessarily do the updating like that. Maybe having a webhook is going to be useful in this case as well, because it's going to lead to less mass-elimination and replacement of data.

[daisycrego]

Adding Webhooks on top of the Sync Leads Feature

• Separate from syncing the leads, which we will leave as an option, I am adding in some webhooks for peopleCreated and peopleStageUpdated. It might also be wise to add in a webhook for peopleUpdated, instead actually of having the peopleStageUpdated webhook, because that way the system will truly be in sync with the live FUB system. However - this may mean many more requests coming in in comparison to the requests coming in just for stage updates. That might be something to discuss with Dan. For now, the safest bet is to focus on the purpose of the app - keeping the STAGES in sync. Not all the data. So use the peopleCreated and peopleStageUpdated webhooks, and leave the manual sync options as well, that will be sufficient.
• It still seems like an individual Sync Lead button is going to be needed to manually sync, just in case the webhook didn't get processed, etc.

[daisycrego]

Final Tasks for Sync Leads Feature

Spoke to Dan, for now we will not use the webhooks for the Leads side of the app at all. It's likely the admin is going to be running the Sync Leads button once a week, and that should be sufficient.

• [x] Focus should be on providing more feedback to the frontend of the progress of the sync, if possible. As it's going to be many leads updated every week.

• [x] Remove webhooks related to people, only keep the events webhook.