I’m having trouble getting Make.com to interpret variables that I created within a long email template. Specifically, I’m trying to use dynamically generated placeholders, but Make is not resolving them as expected.
Here’s an example from the long string:
plaintext
Hello {{56.PH_FirstName}} {{56.PH_LastName}}
If I manually place this anywhere in Make (for example, in the email module directly), the fields get resolved and populated dynamically. However, when this placeholder is part of a dynamically created text (for instance, coming from a JSON structure or built through text functions), Make always returns the placeholder itself as a plain string, without filling in the actual values.
I’ve tried several approaches, such as parsing the text as JSON or using different text modules (like Formatter or Text Parser), but I can’t seem to get the placeholders dynamically resolved.
My question is:
Is there a way to make placeholders dynamically resolve when they’re part of a long, dynamically generated string in Make.com?
In my opinion, it could be possible by using Make’s API and blueprint importing.
This way, the scenario will recognize variables in the text correctly; otherwise, they’re just treated as part of the string.
Hi mszymkowiak,
Thanks for taking the time
Unfortunately the Text will be generated a 100 times dynamically.
The blueprint idea is more of a 1time solution for 1 text, or?
Hi,
I am grabbing a standard text with placeholders from notion.
Those placeholders like Firstname and Lastname will be transformed to make variables. I am using textparse functions.
After that the text contains variables EXACT in a structure that Make could interprete them.
When I copy such a variable somewhere in make it will be recognized.
But as long as the variables are hidden in one long text Make just print the variablenames with all the brackets instead of exchanging them with the value of the variable.
