Run Send Email Flow steps, identifying the Email via forms data written to person fields.

[Greg_W]

First forum post from a longt-ime Eloqua users trying to convert to Marketo! 

To simplify life I am looking to build a program that can handle lots of different forms, and conditionally run flow steps.  The first step is an 'always' step, and it's to take the 18 digit SFDC Campaign ID and write it to a person field, along with the status. The Add to Campaign flow step is then configured with the lead tokens for those two fields - and it works like a dream. 

Now for the other flows steps. If form includes hidden fields to indicate if an email should be sent, and another to define which email should be sent, then execute that flow step - using the 'data' in the form to identify the email.   

The first part is straightforward, set up the form with a Boolean Field called sendEmail checked to true. The second, include a hidden field called emailToSend and pass a value to identify the email. On a program we have zero issue to add a Flow Step called email, add a condition to send a specific email (selected from a drop down) if sendEmail using is true. But instead of selecting a specific email from the email selector dropdown, we want to be able to define the email to send using info from the form, written to a field on the person (in this case emailToSend).   

We also want similar for Send Alert (but have a fallback), Call Webhook (but not tested to see if you can pass the Webhook via a person token either).  

Is this possible - and should we be:

1. Passing the Email Asset Name
2. The ID
3. Giving up and moving on

We can create separate triggers to watch for fields with specific values and then send the relevant emails.

Really hoping there is someone out there who's cracked this. No more creating unique programs or triggers just to fire notifications and trigger emails. 

Greg

[SanfordWhiteman · Accepted solution]

---

1. Passing the Email Asset Name
2. The ID
3. Giving up and moving on

3.

It’s not possible to do this with a flow step alone.

And in fact it’s not even possible to do with the API, because the Request Campaign API call expects an existing campaign that’s tied to a known Asset ID (that is, you’re back where you started).

However, if you only care about the content of the email and not necessarily having different email assets, you could have a single asset and then dynamically inject the content as a {{my.token}} while calling the Request Campaign API. If you can accept this, then the whole thing can be automated by calling a webhook-compatible service which (1) retrieves or received the field from the form, (2) fetches the corresponding content, which might be stored in other email assets, and (3) calls Request Campaign.

[Greg_W]

@SanfordWhiteman  - I won't say that the headline was to pique your interest - but glad to see it did! Figured you would be the one person who would know for sure. 

I was really hoping someone had managed to crack that nut... it would make things so much scalable.  I get the workaround, but there's probably as much (or more) work creating that corresponding content. Back to the drawing board on that one. We'll just go with building standalone campaigns for these autoresponders (or test and see if there's benefit to actually sending them).