Allow trigger tokens in Webhook flow actions

[Anonymous]

We have a client with a number of fields not synced to their CRM. They would like to be able to detect a data value change and use the name of the field that was updated to determine which webhook to call like this:


Marketo appears to accept this value in the flow action, but when the campaign is run on a test lead it produces the following:


Is there any possibility to allow that token inside that field?
 

[Grant_Booth]

Hey Charlie,

I believe this would be similar to using a token in a choice or constraint, or in a smart list filter - tokens only write values. Even though it looks and feels like it's writing a value to a field in this situation, I believe it's actually using the name to query the database for the webhook's id.

Maybe you could use that token to write values to a custom field in a Change Data Value flow step immediately before, then have choices in the Call Webhook flow step to call different webhooks depending on the value of the custom field? In the screenshot below, I'm using "Favorite Animal" as the custom field:

[Anonymous]

@Charles, what are you thoughts on Grant's workaround? 

[Anonymous]

That's the approach we began to pursue when we learned that the other one was not an option. The issue was that we have 240 different possibilities for values inside the trigger token and Marketo doesn't like more than 100 choices in a single flow. Fortunately, the value being passed is always Boolean, and since Marketo doesn't register a value change unless the value always changes, we can simply detect the change without passing a value and then toggle the value on the other end of the webhook.