What it is.
A Schedule Trigger runs daily, pulls trial users from MongoDB, works out how far into the trial each one is, then a Switch node sends the matching email through Gmail. Four messages: day 3 encouragement, day 7 mid-trial, day 13 near-expiry, and a final one on the last day.
It's a small template, and the logic is a date calculation plus a Switch. Swapping MongoDB for Postgres, or for an HTTP call to your own API, is a single node change.
What you get.
- Four trial emails on a set schedule, at day 3, day 7, day 13, and the last day.
- A daily Schedule Trigger, so nothing depends on your product firing a webhook.
- A batching loop, so a large user table gets processed in chunks.
- Plain JavaScript date logic you can read and change.
How to set it up.
Point the MongoDB node at your users collection and name the field holding the trial start date.
Set the Gmail credential, since the template sends from whichever account you connect. Use a monitored one.
Edit the Code node to match your own trial length, because the day thresholds are written into it.
Rewrite the four email bodies in the Gmail nodes before you enable anything.
Set the Schedule Trigger to a time your users are awake in their own timezone.
Run it against a test record at each of the four day marks before you point it at live users.
Use cases
Trial sequence with no marketer
Read the start dates and let the four emails go out on their own schedule.
Nudge before the trial ends
Catch the last day with a message while the account is still open.
Run it off your own database
Trigger from the dates you already store instead of syncing to a sending tool.
Best for
A trial with no lifecycle tool
Before a dedicated messaging platform is worth the spend, four scheduled emails cover most of the value.
Products with no event tracking
It works off a date field, so you need no event tracking at all.
Testing trial messaging
Changing one of four emails and reading the conversion difference is a cheap experiment.