All hashtags you can add to calendar event descriptions to control Stellar's behavior.
#stellar-series and #stellar-train tags are only acted on for
calendars Stellar scans for hashtags. A calendar is scanned automatically when it's the
source of a sync rule, or when it already has a Stellar series/plan on it. For any other
calendar, turn on the “scan” checkbox next to it in Your Calendars
on the dashboard. You can also un-check “scan” to stop Stellar on a calendar — that removes
the generated series/plan events from it, just like turning off a rule.
Any hashtag in an event description can be used as a filter in a sync rule. When a rule is set to copy events with a specific hashtag, only events whose description contains that tag will be copied.
The hashtag can be anything you like — #personal, #travel,
#busy, #share. The tag name is just a label you choose;
it has no special meaning to Stellar beyond matching.
#stellar-series)Add these hashtags to a "master" event to expand it into a separate calendar event for each date in your list. See What can Stellar do? for examples.
| Hashtag | Description |
|---|---|
#stellar-series |
Required trigger. Marks this event as a series master. Must appear somewhere in the description. |
#title: template |
Title template for child events. Use %s for the performance name from the #event: line, and %c for the calendar name.Example: #title: %s — Benedum CenterIf omitted, the master event's own title is used for all children. |
#url: url |
A URL to include in every child event's description — useful for ticket links, venue pages, etc. |
#event: … |
One line per event you want generated. Format:YYYY-MM-DD [HH:MM [HH:MM]] | Name | Notes (optional)Examples: #event: 2026-10-15 19:30 21:30 | Hamilton | Row G, seats 12–13#event: 2026-11-28 14:00 | Nutcracker#event: 2026-12-31 | New Year's ConcertDate is required; start time, end time, and notes are optional. If you omit the time, the master event's time is used. |
# lines) is treated as a body template and
copied into every child event's description. Useful for venue directions, parking notes, etc.
#stellar-train)Add these hashtags to a race event on your Google Calendar to generate a training plan. Stellar reads the tags each time it syncs and regenerates the plan if you change anything.
| Hashtag | Description |
|---|---|
#stellar-train |
Required trigger. Activates training plan generation. Add a distance tag on the next line. |
#marathon |
Marathon (26.2 mi) distance. Used with #stellar-train. |
#half |
Half marathon (13.1 mi) distance. Used with #stellar-train. |
#10k |
10K distance. Used with #stellar-train. |
#5k |
5K distance. Used with #stellar-train. |
#goal:H:MM:SS |
Your goal finish time. Used to calculate all training paces via the VDOT method. Examples: #goal:3:30 (3 hr 30 min), #goal:1:45:00
|
#priority:A / B / C |
Race priority when you have multiple races in a season. A = goal race (sets the training block). B = tune-up race with modest taper. C = fitness test with minimal disruption. Default is B. |
#level:beginner / intermediate / advanced |
Your experience level. Determines training volume and workout mix. Default is intermediate. |
#days:N |
Number of running days per week (2–7). Selects the matching training template. Default is 5. |
#long-run:day |
Day of the week for your long run. Example: #long-run:saturday. Default is Saturday. |
#units:mi / km |
Distance units for workout descriptions. Default is miles. |
Questions? Email support@stellarcalendar.com. · See examples →