@MelissaC 

Below are approaches for the 2 use-cases you have shared:

• Welcome Email (JO): This can be achieved by fetching the required data sets under the query builder; One approach could be:
  1.  First Data-set: Fetch the Won opportunities attributes from SFDC → Opportunity object along with SFDC Account id.
  2. Second Data-set: Fetch Person attributes from Company Person object along with SFDC Account id.
  3. Third Data-set: Left Merge First and Second Data-set using SFDC Account id.

The third data-set gives you all the contact records to who you want to send a Welcome Email.

• Trigger a Success Plan: You can use rules-engine to achieve this, and while you create a rule, you can fetch the required data sets in the step-2 by following the below steps:
  1.  First Data-set: Fetch the Won opportunities attributes from SFDC → Opportunity object along with SFDC Account id.
  2. Second Data-set: Fetch Company attributes from the Company object along with SFDC Account id.
  3. Third Data-set: Left Merge First and Second Data-set using SFDC Account id.

The third data-set gives you all the company records for which you want to create a Success Plan.

Further, you can follow this article to know how you can create Success Plan using the “Success Plan 2.0” action type.

In-case you need further help in configuring the use-cases, then you can reach out to your CSM or Technical resource at Gainsight.

Hi @MelissaC, @achandak’s response is on point.

If I may add, you might want to use Data Designer for both and build one unique data design (and turn it into a data space) to serve both purposes, since the data sets are very similar. This would save you maintenance overheads. With that in mind though, you’d need two things:

• Make sure your data design looks like the following recommendation:

Trigger a Success Plan: You can use rules-engine to achieve this, and while you create a rule, you can fetch the required data sets in the step-2 by following the below steps:
 First Data-set: Fetch the Won opportunities attributes from SFDC → Opportunity object along with SFDC Account id.
Second Data-set: Fetch Company attributes from the Company object along with SFDC Account id.
Third Data-set: Left Merge First and Second Data-set using SFDC Account id.

• Fetch company person details as a fourth step, and append them as a fifth step.

It means that you’ll be able to:

• Use the final (5th) data set in JO (set a syncing schedule that makes sense (it needs to be in sync with your JO syncing) - so you fetch your data space from query builder
• Use the third data set in horizon rules engine to create an action

That’s one data set for two purposes, maintenance reduced, and consistency in emails/success plans being sent/created ensure.