Is there a way to store e-mail content *including* variables in a table instead of in an automation?

Hey @0800-grizzly 

Sounds like a great move to centralize email templates and streamline the automation setup. To achieve this, I’d suggest setting up a dynamic templating system within Airtable, storing email templates in a dedicated table. We can use placeholders like <first name> in the templates, then reference these dynamically using "Find Records" steps and a scripting action to replace them with actual values at runtime.

To bypass the "Invalid data" error, I’ll help format the templates within Airtable’s long text fields, making use of Airtable's formula functions where possible. This ensures placeholders are correctly processed before sending, and you’ll have an easy-to-update central repository for all email content.

And you don’t even need to use scripting for this if you don’t want to, You can just create formulas that substitute the variables of your email templates with record values.

But you would need to lookup those templates into the table where you want to use them, by creating a linked record field and linking every record to the template.

Hope this helps! If you’d like to hire an expert Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Thanks for you reply. Do I understand your approach right, that it would mean using CONCATENATE fields that would sum up the mail content, then to be placed into the formula via a Find Records step? If yes, it doesn't sound appealing due to the amount of different cases and therefore amount of fields. 

Rgds,

Björn

You don't need a find records step. You would just create a formula using nested SUBSTITUTE() functions to substitute your <<merge fields>> with whatever fields you would like to use instead.

Thanks for your reply. Do I understand you right, that the actual template record would have e.g. <FirstName> in place of the first name, then in the automation a script step would identify real variables in the earlier Find Records steps, and substitute the <FirstName> with it's real variable? Sounds tricky to maintain, I guess all "value pairs" would need to be hard code defined, non?

Rgds,

Björn

I'm sorry, I don't understand. In the automation "Message" box I can insert a dynamic token to fetch data from a table, and that requires identifying it in a previous step. How else would we recognise it if not with a Find Record?

Further, wouldn't my variables in the data still not get recognised by the automation?

Rgds,

Björn

@Sachin_191 and @ScottWorld, sorry to disturb. Could I ask for you elaborate on my questions above?

Cheers,

Björn