How to Create a Frequency-Triggered (Roundup) Automation

Frequency-triggered automations (also called roundups) let you automatically send a roundup of upcoming events on a recurring schedule -- weekly, monthly, or at whatever cadence makes sense for your audience.


Step 1: Create a New Frequency Automation

From your automations dashboard, click the Create Frequency Automation button.


Step 2: Name Your Automation

Give your automation a name and optional description. This is for your internal reference only -- it will not appear in the email your subscribers receive.


Step 3: Set Your Send Frequency

Choose how often this automation should send:

  • Every day -- best if you have a very high volume of events
  • Every week -- common for active venues or organizations
  • Every two weeks -- a good middle ground
  • Every month -- one of the most common choices

If you select monthly, you will also choose which day of the month the send should trigger (for example, the 1st, the 15th, etc.).


Then set your send time and time zone.


Step 4: Configure Event Selection Criteria

This section controls which events get pulled into your roundup.

  • Look-ahead window: How far into the future to pull events. For example, entering 10 weeks will include any events occurring within the next 10 weeks.
  • Maximum number of events: The cap on how many events can appear in a single send. You can set this high (or very high) if you want to include everything available.
  • Sort order: Choose between Soonest Upcoming (chronological) or Most Recently Added.
  • Minimum required events: If the number of eligible events is below this threshold, the automation will not send. A setting of 1 to 3 is typical.
  • Skip if no new events: If all eligible events have already appeared in a previous send, the automation skips that cycle. This is optional and generally not recommended -- consistency in your send cadence tends to be more valuable than avoiding repeat events.

Click Save and Continue.


Step 5: Build Your Email in the Block Builder

You will now enter the block builder, which works similarly to the single-event automation builder with a few key differences:

  • Variables are based on multiple events, not a single event
  • The Single Event block is not available here
  • A new Event List block is available instead

Using the Event List Block

Drag the Event List block into your email. Inside this block you can:

  • Show as much or as little detail about each event as you like
  • Customize the call to action button text

    Choose a display style:

    • Full Cards -- each event gets its own card with complete details
    • Compact -- a condensed layout with smaller images (thumbnail-sized), ideal when you want to pack many events into one email

      Toggle Recurring Events on or off:

    • Off (default): Shows the start and end date range for recurring events; subscribers can click through to see individual occurrences
    • On: Each individual occurrence of a recurring event appears as its own item in the list

Using Dynamic Variables

The following variables are available in the frequency automation builder:

  • [Company Name]
  • [Event Count]
  • [Month]  (the calendar month of the send)

Example usage: "In [Month], we have [Event Count] events coming up -- check them out!" This would render as something like: "In January, we have 5 events coming up -- check them out!"


Adding Images

In the frequency automation builder, you can upload multiple images. The system will randomly select one image per send, which adds variety to recurring emails. Note that because selection is random, the same image could occasionally be chosen two sends in a row.



Tips

  • Make sure your events are added to your account before the automation triggers -- either manually or through one of the available import options.
  • Consistency matters more than perfection. Even if some events repeat across sends, keeping a reliable cadence builds audience habit.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.