A meetup group running weekly or monthly shouldn't mean rebuilding the invite every time. Build it once with a Venue, Add to calendar, and RSVP block, then put it on a recurring send — MailInApp re-evaluates the group each run and reaches only members who haven't already RSVP'd for that occurrence.
Recreating the same invite by hand every week is the kind of busywork that eventually gets skipped, and a skipped invite is a smaller meetup. Building it once and letting a schedule handle the repetition removes that failure mode entirely.
Build the invite once
A Venue block carries the usual spot's address and directions, an Add to calendar block builds the timezone-correct calendar links, and an RSVP block takes headcount with whatever capacity the venue actually holds. None of that needs to change week to week unless the details do.
Let the schedule do the repeating
A recurring send re-evaluates your audience filter against the data source's current rows on every run, reaching only members not already covered by a past send for that same schedule — the same rolling-window pattern any MailInApp recurring send uses. Set it once for a weekly or monthly cadence and it keeps running.
Update the one thing that actually changes
If the venue moves for a single occurrence, update the Venue block's address before that send goes out — every future run picks up whatever's currently saved, so a one-off change doesn't mean rebuilding the whole invite from scratch.
Know the numbers before the day
Each occurrence gets its own RSVP, so the Responses dashboard shows confirmed, waitlisted, and declined counts per send — a reliable headcount well ahead of every single gathering, not just the ones somebody remembered to track by hand.
Getting started
Add a Venue block, an Add to calendar block, and an RSVP with a capacity matching your usual space. Put the whole thing on a recurring send and disable it any time the meetup goes on hiatus.