Workflows in Event Temple automate follow-ups, reminders, and tasks across the booking lifecycle.
Each workflow action can be triggered by specific timing rules, allowing your team to automate steps based on workflow start dates, booking dates, or previous actions.
Available Workflow Triggers
When creating or editing a workflow action, you can choose from the following trigger options under “This task will be created…” or “This email will be sent…”
1. After Workflow Starts
The action triggers a set number of days after the workflow begins.
Commonly used for initial tasks like:
“Qualify Lead”
“Send Proposal”
“Follow up after inquiry”
🕓 Example:
“Send Proposal” → 0 days after workflow starts.
“Proposal Follow-Up” → 3 days after previous step complete.
2. Before Booking Start Date
The action triggers a set number of days before the booking start date.
Ideal for pre-event preparation tasks such as:
Requesting final numbers
Sending Banquet Event Orders (BEOs)
Notifying Operations teams
🕓 Example:
“Request Event Details” → 60 days before booking start date.
“Distribute BEOs to Ops” → 45 days before booking start date.
3. After Booking Start Date
The action triggers a set number of days after the booking begins.
Typically used for early event-day reminders or check-ins.
🕓 Example:
“Greet Event Contact” → 0 days after booking start date.
4. Before Booking End Date
The action triggers a set number of days before the event concludes.
Useful for final confirmations or wrap-up reminders.
🕓 Example:
“Confirm Post-Event Details” → 1 day before booking end date.
5. After Booking End Date
The action triggers a set number of days after the booking has ended.
Commonly used for post-event follow-ups, thank-you emails, or surveys.
🕓 Example:
“Send Event Follow-Up Email” → 1 day after booking end date.
6. After Previous Step Complete
The action triggers once the previous step in the workflow is completed.
Perfect for chained workflows, ensuring one step follows another.
🕓 Example:
“Send Contract” → 0 days after previous step complete.
“Contract Follow-Up” → 3 days after previous step complete.
Summary Table
Trigger Type | Description | Common Use Case |
After Workflow Starts | Runs based on the day the workflow is activated | Lead follow-up, proposal send |
Before Booking Start Date | Runs a set number of days before the event | Prep tasks, BEO creation |
After Booking Start Date | Runs after the event begins | Onsite check-ins |
Before Booking End Date | Runs shortly before event ends | Final confirmations |
After Booking End Date | Runs post-event | Thank-you or feedback emails |
After Previous Step Complete | Runs after a prior action finishes | Sequential automations |
Tip:
Use a combination of triggers to fully automate your event lifecycle — from lead qualification to post-event follow-up — ensuring no steps are missed.