Create a workflow that fires once per day for each contact
SOLVE
Hello,
I'm trying to create a workflow that automatically sends an email to each enrolled contact after event sign-in.
Because we sometimes have multiple events on one day, I want to make sure the workflow will only "fire" once the day after they complete event sign-in. I.e. someone attends events A and B on one day, but they only receive an email for signing into event A the following day (trying to remove duplicative emails from this process).
I've tried in enrollment settings and with branching, but can't seem to figure it out. Thanks!
That totally makes sense, if someone attends two events on the same day, you don’t want them receiving multiple emails. Here’s how I’d approach this:
Add a Filter for Last Marketing Email Sent:
In your workflow, add a filter that checks the Last Marketing Email Sent Date. This is a property on Contact Object that will help you ensure that an email was only sent if the last one was sent more than one day ago.
So, when the workflow fires, it’ll check if the contact has received any marketing emails recently. If they haven’t received an email in the past 24 hours, the system will send the next one. If they’ve already received one that day, it’ll skip the next email.
Turn Off Re-Enrollment:
Make sure you turn off re-enrollment for the workflow. If re-enrollment is on, the workflow might send an email the next day once that date condition updates.
Example Flow:
Let’s say a contact attends Event A. The workflow checks if they’ve had a form submission (assuming event sign-in is tracked that way).
If no marketing email has been sent in the last 24 hours, they get their first email.
The system updates the Last Marketing Email Sent Date to today.
Now, if that same contact attends Event B on the same day, the workflow will trigger again, but this time it’ll check if the Last Marketing Email Sent Date is more than a day old. Since it was updated earlier today, they won’t receive another email for Event B.
Add More Conditions if Needed:
You can get more specific by adding conditions for contacts who belong to certain campaigns or events, but the core logic remains the same.
If you need me to take a closer look at the flow and suggest anything more specific, feel free to share more details. I’ve worked on similar workflows, so happy to help refine it.
That totally makes sense, if someone attends two events on the same day, you don’t want them receiving multiple emails. Here’s how I’d approach this:
Add a Filter for Last Marketing Email Sent:
In your workflow, add a filter that checks the Last Marketing Email Sent Date. This is a property on Contact Object that will help you ensure that an email was only sent if the last one was sent more than one day ago.
So, when the workflow fires, it’ll check if the contact has received any marketing emails recently. If they haven’t received an email in the past 24 hours, the system will send the next one. If they’ve already received one that day, it’ll skip the next email.
Turn Off Re-Enrollment:
Make sure you turn off re-enrollment for the workflow. If re-enrollment is on, the workflow might send an email the next day once that date condition updates.
Example Flow:
Let’s say a contact attends Event A. The workflow checks if they’ve had a form submission (assuming event sign-in is tracked that way).
If no marketing email has been sent in the last 24 hours, they get their first email.
The system updates the Last Marketing Email Sent Date to today.
Now, if that same contact attends Event B on the same day, the workflow will trigger again, but this time it’ll check if the Last Marketing Email Sent Date is more than a day old. Since it was updated earlier today, they won’t receive another email for Event B.
Add More Conditions if Needed:
You can get more specific by adding conditions for contacts who belong to certain campaigns or events, but the core logic remains the same.
If you need me to take a closer look at the flow and suggest anything more specific, feel free to share more details. I’ve worked on similar workflows, so happy to help refine it.
