Set Event Start Date in Sparkforge Workflows

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Set Event Start Date action defines a reference date inside a Sparkforge workflow so later Wait steps can fire a fixed amount of time before or after that event — ideal for webinars, renewals, and birthdays.

The Set Event Start Date action anchors a workflow to a specific date and time. Subsequent Wait for Event/Appointment Time steps then run relative to that anchor — a week before, a day after, an hour out, whatever you need.

What It Does

Once an event date is set on the contact, every downstream Wait step measures from that date instead of the workflow start time. That makes it the right tool for webinars, conferences, renewal cycles, birthdays, and any campaign with a fixed reference date.

When to Use It

Webinar reminders. Anchor on the webinar date, then schedule emails for one week, one day, and one hour before.
Renewals. Pull the renewal date from a custom field and trigger a 30-day-out nurture.
Birthdays and anniversaries. Use any date field on the contact as the anchor.
Recurring events. Reset the date each cycle to keep the same workflow firing weekly or monthly.
Post-event follow-up. Send a thank-you or survey two days after the event date.

Configure the Action

Step 1: Add the Action

Open the workflow, click the + on a step, and search for Set Event Start Date/Time.

Step 2: Set the Date

Pick a static date, a custom field on the contact, or a value pulled from the trigger. Confirm the time zone matches what the contact expects.

Step 3: Add Wait Steps

Drop a Wait for Event/Appointment Time step after the anchor and choose an offset (e.g., 1 day before or 2 hours after). Repeat for every reminder or follow-up you need.

Recurring Events

For weekly webinars or monthly check-ins, end the workflow with another Set Event Start Date step that pushes the date forward, then loop the contact back through. Each pass uses the new anchor.

Time Zone Behavior

If the workflow respects contact time zones, the event date is interpreted in the contact's local time. If not, it uses the sub-account default. Mixed audiences should run in contact time zone so 9 AM means 9 AM for everyone.

Frequently Asked Questions

Can I use Set Event Start Date for recurring events?

Yes. Reset the date at the end of each cycle and route the contact back to the start of the workflow.

Can I set multiple event dates in one workflow?

Yes. Each Set Event Start Date step overwrites the previous one, so later Wait steps measure from the most recent anchor.

What happens if a contact enters the workflow after the event date has passed?

Wait steps that point to a past time fire immediately, so any pre-event reminders are skipped. Post-event steps still run on schedule.

Do I need a Wait step after Set Event Start Date?

Without a Wait for Event/Appointment Time step the action does nothing visible — it only sets the anchor that later steps reference.

How does the action handle contact time zones?

If the workflow is set to respect contact time zones, the event date converts to each contact's local time. Otherwise the sub-account default applies.