Email token in Send Email Campaign Flow Step

[jayherman]

We have a need to have a single smart campaign, but we need to email to be different each time the campaign is executed. I noticed that the "Send Email" step in Flow step in Smart Campaigns seems to accept tokens, like so:

But I can't get it to work. I'm filling out the token (via the API) with the folder name and email name like so: My Folder.My Email

Has anyone been able to get this to work with a "my" token?

Thanks. 

[SanfordWhiteman]

Neither the temporary/runtime {{my.token}} nor a permanent {{my.token}} can be used there. It’ll be interpreted as a meaningless string, not dereferenced to the actual email asset.

[jayherman]

That is what I was afraid of. 

We've tried what was suggested in the examples and filled out our email detail using a template/email and a token. But the problem is that the lead tokens in the detail will not work then. We were hoping to find an answer to that. 

[SanfordWhiteman · Accepted solution]

A combination of Velocity and a runtime {{my.token}} can do that.

[lianef]

Hi @SanfordWhiteman,
Can you expand on the solution you provided, the combination of a velocity and runtime token?

I created a Google Spreadsheet that marketers can use to check a box and trigger a campaign to run in Marketo that will send an email in that row, the email is different in each row. All of it works fine except for the send email flow step. 
I have tried trigger tokens and a my.token but am curious how I could accomplish this with your approach. 

Email asset ID is what we are using as the value to send to the tokens.  

[SanfordWhiteman]

Schedule Campaign and Request Campaign let you override the {{my.token}} on a per-API-call basis. That’s what I refer to as a “runtime" token.

You can then export that {{my.token}} into Velocity to manipulate it further. For example, we do this by passing a JSON string as the {{my.token}} and then break that down using Velocity to format it as a table (in combination with other $lead.fields).