Creating Automations
Automations create recurring events on a weekly schedule and can send scheduled emails to your roster before each event. Use them for league nights, weekly tournaments, and anything else that repeats on a fixed cadence.
What an Automation Does
A Live Tourney automation:
- Creates a copy of an event template on a recurring weekly schedule (every 1, 2, 3, or 4 weeks)
- Creates each event either a set number of days before it is played, or the whole season at once the moment you turn the automation on
- Opens and closes registration on a window you set relative to each event
- Sends one or more emails before each event runs
- Optionally adds the new event to one or more seasons
There is one type of automation. There is no SMS, no conditional logic, no manual trigger, and no run history beyond a total run count.
Before You Start
You need an event template — a regular event you've already configured (game type, course, settings) that the automation will clone each time it runs. Create that event first, then come back here. Keep that event: if it is deleted, the automation stops creating events until you pick another template.
If the template has automatic score posting set in Post Scores, each new event copies that setting. Otherwise each new event follows your account default in Settings → Account → Automatic Score Posting.
Accessing Automations
- Go to Automations in the sidebar
- Click Create New in the top right (or Create Your First Automation if the list is empty)
Creating an Automation
The create page is a single form with five sections.
Basic Information
| Field | Description |
|---|---|
| Automation Name | Required. Supports dynamic fields (see below) so each created event gets a unique name |
| Description | Required. A short note about what this automation is for |
Dynamic name fields — click these chips below the name input to insert merge tags that resolve when each event is created:
@DayOfWeek— e.g., Saturday@Month— e.g., May@Day— day of month@Year@Count— incrementing run number
Example name: @DayOfWeek Skins — @Month @Day becomes Saturday Skins — May 9.
Schedule
| Field | Options |
|---|---|
| Repeat every | 1, 2, 3, or 4 weeks |
| Event Time | Time of day the created event starts |
| Time Zone | Pacific, Mountain, Central, or Eastern |
| Days of the week | Required. Click any combination of Mon–Sun |
| Season Window | Optional. A First Event Date and/or Last Event Date |
Each combination of selected days runs at the chosen interval. For example, Mondays + Wednesdays at "every 2 weeks" creates events on those two weekdays every other week.
Season Window
Set a First Event Date and Last Event Date to bound the automation to your season. No events are created before the first date or after the last date, so you don't need to add skip dates before the season starts. After the last event date passes, the automation pauses itself automatically — you don't need to remember to disable it. Both dates are optional and can be used independently; clear a date to remove the bound.
The Last Event Date becomes required when you choose to create the whole season up front (see When to create events below), since the automation needs to know where the season ends.
Skip Dates
Block specific dates (holidays, course closures) from running. Pick a date and click Add. Skipped dates appear as a list of pills you can remove.
Event Settings
| Field | Description |
|---|---|
| Event Template | Required. The existing event the automation clones each run |
| When to create events | As the season goes (default) creates each event a set number of days before it is played (1–30 days). Whole season up front creates every event in the Season Window as soon as the automation is turned on |
| Registration window — Opens | Either Immediately, or N days/hours before the event |
| Registration window — Closes | N days/hours before the event (must close after it opens) |
| Add to Seasons | Optional. Check any seasons to add each created event to |
Whole season up front
Choose this when you want the full schedule visible ahead of time — on a season portal, for example — while emails still go out on each event's own cadence.
- A Last Event Date is required, and the season can cover at most a year.
- The form previews how many events will be created and their dates (click Show dates). Events are created when you turn the automation on from the Automations list; the card counts them up as they appear, usually within a minute.
- Every event is created from the template with the registration window, seasons and name you set. The
@Countfield numbers events in date order. - Because the events already exist, emails and registration opening can lead each event by up to 30 days instead of being capped by the create timing.
- Editing later: changes apply to events created from then on. Events already created keep their name, time and settings — edit those individually from the dashboard. Extending the Last Event Date or removing a skip date creates the newly scheduled events on save. If the new schedule drops dates that already have events (a new skip date, a shorter season, a removed weekday), you'll be asked whether to delete those events; events with registrations are always kept.
- Deleting an event from the dashboard by hand does not recreate it.
Email Notifications
Click Add Email to add a scheduled email. Each email has:
- Name — internal label
- Send before event — days and hours before the event starts (cannot be earlier than the event is created)
- Description — internal note
- Manage Templates — opens the template manager, where you can apply a saved template, save the current email as a new template, or delete templates
- From Name
- Reply-To Email — where player replies go; if left blank, your account email is used
- Subject — supports dynamic fields
- Body — rich text, supports dynamic fields
- Recipients — see below
Email dynamic fields
Click any chip below the Subject or Body to insert. Available fields:
@FirstName, @LastName, @Email, @GHIN, @PlayerHandicap, @EventName, @URL, @PersonalURL, @PlayerCode, @PlayerURL, @ScorecardCode, @StartTime, @StartingHole, @CourseTee, @CourseHandicap, @PairingDetails, @GameType, @Flight, @Month, @Day.
Recipients
| Option | Sends To |
|---|---|
| All Event Players | Everyone registered or assigned to the event |
| All Roster | Your entire roster at the time the email sends — new members added after setup are automatically included |
| [Club Name] | Members of a specific club from your roster |
Saving
Click Save at the bottom. If any required field is missing (name, description, at least one day of week, event template), you'll see a toast message indicating which field needs attention.
Managing Automations
The automations dashboard shows each automation as a card. Each card displays:
- Name and description
- Schedule (selected days, interval, event time, days-before-create or "Whole season created up front")
- Next event date and preview name
- Email sequence timeline
- Season badges, skip-date badges, and a season window badge (when set)
- Total run count — or, for an up-front season, an N events badge that lists every created event with a link to it, plus a "Creating N…" badge while the season is still being created
- A Calendar toggle that expands to show scheduled, skipped, and creation dates (up-front seasons also distinguish created events from dates not yet created)
Enabling and Disabling
Each card has a toggle switch in the top right. Toggle it to enable or disable the automation. Disabled automations stay in the list but stop creating events.
You can tell at a glance whether an automation is active:
- Active automations have a green ribbon across the top reading LIVE · NEXT RUN IN N DAYS (or "running today" / "running tomorrow" when imminent), a solid green border, and a soft green wash on the card. Up-front seasons count down to the next event instead, and read LIVE · CREATING N EVENTS… while the season is being created.
- Paused automations have a gray hatched ribbon reading PAUSED · NOT RUNNING, a dashed gray border, and a flat gray card background.
The next-run countdown is based on when the automation actually fires, which is the days-before-create offset ahead of the event date — not the event date itself. Up-front automations fire once, when turned on, so their countdown is to the next event.
Turning an up-front automation off pauses its emails but leaves the created events in place. Turning it back on resumes emails and creates any newly scheduled dates.
Editing
Click the three-dot menu in the top right of a card and choose Edit.
Deleting
Click the three-dot menu in the top right of a card and choose Delete. Confirm in the dialog. Events the automation already created stay on your dashboard as regular events and stop receiving automation emails. For an up-front season, the dialog also offers to delete the upcoming events it created; events with registrations are always kept.
Troubleshooting
Automation isn't creating events
- Check the toggle on the card — disabled automations don't run
- Confirm at least one day of the week is selected
- Confirm the event template still exists. If the template event was deleted, the card shows a red Not creating events banner; click Choose a template, pick another event under Event Template and save
- Check that today isn't in the Skip Dates list
- Check the Season Window — events aren't created outside the first/last event dates, and the automation pauses itself once the last event date passes
- For a whole-season-up-front automation, events are created only once the automation is turned on; the card shows "Creating N…" until they all exist. If the count never finishes, open the automation and save it again to retry
Emails didn't send
- Open the event the automation created and confirm the recipient list isn't empty
- For All Roster, remember the list is evaluated at send time, not when the automation was set up
- Email send time cannot be earlier than the "create event timing" — if you set the email to send 5 days before but the event is only created 3 days before, it can't go out (this limit doesn't apply when the whole season is created up front)