Oct 24, 2024 07:40 PM
Looking to create one or more sales email campaigns leveraging email templates. Campaign could be triggered against criteria in a project table.
I was thinking the email templates might reside in their own table, potentially with the identified campaign name, subject, body, sequence number, cadence etc.
Assume 3 emails in campaign with the cadence as follows: Email 1 sends on startdate, Email 2 startdate+2, Email 3 startdate+5
For example, "Campaign Name" = "Lost Deal", "Email Campaign Status" = "Active", "Email Campaign Startdate" = 2024-10-24
Project table contains the primary contact name, but no email info. Primary Contact Email address is contained in the contacts table associated with the project. Subject field and Body field along with Campaign Name in "Email Templates" table.
Is it possible to reference these fields and automate sending the 3 emails using the referenced fields on scheduled dates based on their cadence?
Oct 24, 2024 08:38 PM
Hey @beebad2
This sounds like a great project, and I have a smooth plan to automate the email campaigns you're aiming for. I’ll set up an Airtable workflow where the Email templates are stored in a dedicated table with fields like campaign name, subject, body, and cadence. The automation will link the Contacts and project data to pull in relevant information (e.g., emails from the Contacts table) and trigger emails based on your defined schedule.
Each campaign will run seamlessly:
Email 1 triggers on the start date
Email 2 on start date + 2 days
Email 3 on start date + 5 days.
I’ll automate this using Make.com ( formerly Integromat ) or Zapier, depending on your preference. This ensures emails go out without manual intervention, with error-handling built-in
Oct 25, 2024 11:28 PM
re: Is it possible to reference these fields and automate sending the 3 emails using the referenced fields on scheduled dates based on their cadence?
Yeap, you can. You'd need to link the email template records to the Project records, use lookups to pull them over, and formulas to subsitute the project data into the template, and the automation would use that data to send out the emails, and you'd use conditionals to figure out which one to send
Seems much simpler if you just put the template into the email automation action (i.e. "Send email" etc) itself, really. I take it there's a business reason you don't want to do that?