Understanding the Problem

When teams running Journey Builder hit this issue, they often consider triggering the second flow based on lead creation. However, this approach may not work in all cases, especially when form submission does not always equal lead creation, and may sometimes update an existing contact to avoid duplicates.

Therefore, a more flexible approach is needed to handle form submissions in a different way.

Solution Overview

The solution involves creating a data cloud triggered flow that listens for form submissions and then triggers a reusable notify user action. This approach allows teams to decouple the notify user action from individual flow emails and make it more generic and reusable.

Step-by-Step Solution

To implement this solution, follow these steps:

create_data_cloud_triggered_flow.js

var flow = Platform.Function.CreateDataCloudTriggeredFlow();
flow.setName("Form Submission Notify User");
flow.setTriggerType(Platform.Function.TriggerType.FormSubmission);
// Add notify user action to the flow
var notifyUserAction = Platform.Function.CreateSendEmailAction();
notifyUserAction.setTemplateName("Notify User Email");
flow.addAction(notifyUserAction);

The root cause of this issue is the lack of a generic and reusable approach to notify internal users via email about new form submissions, leading to duplicated effort and potential errors.

Best Practices and Next Steps

To take this solution to the next level, consider the following best practices and next steps:

Checklist

• Create a separate data cloud triggered flow for each form submission type to handle different scenarios.
• Use a reusable notify user action across multiple flows to reduce duplicated effort.
• Test and validate the solution to ensure it works as expected.
• Monitor and analyze the performance of the solution to identify areas for improvement.
• Consider integrating the solution with other Marketing Cloud features, such as Journey Builder and Automation Studio.

What is the benefit of using a data cloud triggered flow?

The benefit of using a data cloud triggered flow is that it allows teams to decouple the notify user action from individual flow emails and make it more generic and reusable.

How do I handle form submissions that update existing contacts?

To handle form submissions that update existing contacts, consider creating a separate data cloud triggered flow that listens for updates to existing contacts and triggers a notify user action accordingly.

Can I use this solution with other Marketing Cloud features?

Yes, this solution can be integrated with other Marketing Cloud features, such as Journey Builder and Automation Studio, to create a more comprehensive and automated marketing workflow.

What are the potential limitations of this solution?

The potential limitations of this solution include the need for careful testing and validation to ensure it works as expected, as well as the potential for duplicated effort if not implemented correctly.