Named Variables#

There are times when we have a single field in a trigger that contains info you want split out into multiple fields, or maybe you only want part of that field to come through to the action. We use a special function called named variables to help make this possible.

Note: For named variables to work you MUST have control over the data in your trigger. If your trigger data is an email that was automatically generated and you can't change the formatting, named variables won't be able to help you.

Let's see an example of named variables in action. Let's say I create a new note in Evernote, but I want to use data from that note to populate different fields in a Salesforce lead. In the body of my note I'll put the data I want a variable for in parentheses like this:

Evernote Note

Now when I check the available fields to use in the action of my zap, I can see the Named Variable fields available to choose from:

Zap fields

I'll select those fields just like I would with any other standard field from Evernote. And when I send my test note to Salesforce, here's the end result:

Salesforce Lead

You can use this for any field you like, just make sure that you can add in the names and parentheses for your trigger data and you don't mind that the trigger service has the names and parentheses formatted that way. Also, make sure the named variable only has letters, numbers, or underscores. For example, id() will work as a named variable, id#() will not.

Tip: Remember, to be able to find the Named Variable fields when setting up the action of your Zap, we'll need to have seen a sample of them first. So make sure you submit a trigger with those in it before checking the action of your Zap. For example, if you are using these in an email, send in a new email with your named variable fields first.

↑ Was this documentation useful? Yes No (Suggest Edits)
Get Help