Flag meeting invites and keep them in your inbox

The Calendar invites template keeps any email with an .ics file attached in your inbox and flags it, so invites are not swept up by other rules.

The Calendar invites template as it comes
Decides by
Conditions only, no AI
Only if
The email has an attached file ending in .ics
Then
Keeps it in your inbox
Flags it

Protecting invites from your other rules

An invite can look like a newsletter or a notification, and a broad rule might move it. Calendar invites matches first on something exact, an attached .ics file, keeps the email where it is and flags it. It is a condition-only rule, so it is instant and free.

When to change it

The .ics match is broad. Booking confirmations with “add to calendar” files are caught too. If you want those in Travel instead, put Travel above this rule, or add a condition on the sender.

01

What it catches

  • Meeting invites and updates that attach an .ics file.
  • Booking confirmations and event tickets that attach an .ics file, too.
02

What it leaves alone

  • Invites that carry the calendar data only inside the message, with no attached .ics file.
  • Invites sent as a link, with no file at all.
  • Any email a higher rule has already settled.
03

What you can change

  • Add a condition on the sender or domain to limit it to invites from your workplace.
  • Drop the flag if you only want invites protected from other rules.
  • Drag it below Travel if you want bookings with calendar files filed instead.

Questions

Does it accept or decline the invite?

No. It keeps the email in your inbox and flags it. Replying to the invite is up to you.

Does it need an AI model?

No. It checks the attachment's file extension, so it runs without a model and costs nothing to run.

Does it move anything?

No. Keep in Inbox makes no change on the server. The only change is the flag.

Tell your inbox what to do. Then stop thinking about it.

Self-host free from GitHubJoin the cloud waitlist