Will adopting Enerflo v2 impact any of my existing integrations?

Question #1)

Do you have any existing v1 webhook subscriptions that are listed in the middle circle of figure 1.1?
(complete_survey,new_survey,update_survey,site_survey_complete,new_survey_file,new_proposal,update_proposal,update_lender_application)

• Recommended Action Replace events with equivalent v2 event subscriptions.
• Why? These events will not trigger for v2 deals.

---

Question #2)

Do you have any existing subscriptions to the v1 new_install event? If yes, determine which scenario describes your use case:

Scenario 1: I am fully transitioning to v2 and have no need of ongoing support for v1 deals

• Recommended Action
  • Create workflows that respond to the v2 events (deal.projectSubmitted or deal.projectReceived). See https://docs.enerflo.io/docs/v2-events-in-place-of-v1-new-install for more details.
  • Turn off your v1: new_install event subscription
  • Why? The new_install event will continue to trigger in a v2-hybrid workflow, but is a candidate for future deprecation. The best-practice for future-proofing your workflows is to leverage the v2 events.

Scenario 2: I am transitioning to v2 but I will need to continue supporting v1 deal flow

• Recommended Action
  • Create workflows that respond to the v2 events (deal.projectSubmitted or deal.projectReceived). See https://docs.enerflo.io/docs/v2-events-in-place-of-v1-new-install for more details.
  • Leave your your v1: new_install event subscription active, but adjust your workflow so that it does not process any v2 deals. If you need help adjusting that workflow, please "Chat Support" at the top of this page.
  • Why? The new_install event will continue to trigger in a v2-hybrid workflow. Suppressing v2 deals from your workflows that expect a v1-style install payload will avoid duplication of processing.

---

Question #3)

Are you currently using Enerflo's Private Zapier App? (see figure 2.1)

If so, is your Zap trigger based on these events (New Survey, Update Survey, New Install)?

• Recommended Action Decommission the Zap and re-integrate using v2 event subscriptions that relay data to a new Zap.
• Why? The underlying Enerflo events are are v1 events and will not trigger for v2 deals.

---