Changes to how Zaps interpret curlies

We’re updating how Zapier handles field values that are wrapped in double curly braces {{ }}. This change is required to keep your data safe.

In Zaps, when you wrap values in double curly braces, like {{value}}, the Zap will interpret it as a special kind of element, called a curly. Curlies are a special kind of syntax that tells the Zap to interpret the value within a double curly brace as an input. The Zap will then attempt to turn it into a mapped field, as explained in this Zapier Community post.

What’s changing

Today: If a step in your Zap has a set of double curly brackets nested within another set of double curly brackets, Zapier will try to interpret both sets as curlies.

After the update: Zapier will only interpret the outermost set of double curly brackets as a curly. Any other set of doubly curly brackets within it will remain plain text, including the brackets.

For example, if you have:

• Step A that outputs the value “apple”.
• Step B that references step A in a curly, {{stepA_output}}, it will also output “apple”.
• Step C that references step B in a curly, {{stepB_output}}, the Zap will output “{{stepA_output}}” instead of "apple". This is because it will view it as {{{{stepA_output}}}} and only interpret the outermost set of double curly brackets.

Learn more about troubleshooting curlies.

Note

This information was accurate at the time of publication. Please check out the latest product update notes for any updates or changes.