Block 1 - Schedule Trigger
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.3
How it works This workflow runs on a daily schedule to monitor users currently on a trial plan. It fetches user data from MongoDB, calculates their trial stage, and assigns a trigger label such as ...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.mongodb, n8n-nodes-base.code, n8n-nodes-base.splitinbatches, n8n-nodes-base.switch, n8n-nodes-base.merge, n8n-nodes-base.gmail, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Avkash Kakdiya.
Original n8n.io sourceThis workflow runs on a daily schedule to monitor users currently on a trial plan. It fetches user data from MongoDB, calculates their trial stage, and assigns a trigger label such as Day 3, Day 7, Day 13, or Last Day. Based on this stage, the workflow sends a targeted email using Gmail. This ensures consistent engagement and improves trial-to-paid conversion without manual effort.
Fetch and filter trial users
Schedule Trigger – Runs the workflow daily at a fixed time.
Find documents – Retrieves users with an active trial plan from MongoDB.
Code in JavaScript – Calculates trial progress and assigns a trigger type (day_3, day_7, day_13, last_day).
Send stage-based emails
Loop Over Items – Iterates through each filtered user.
Switch – Routes users based on their trigger type.
Send day 3 email – Sends onboarding encouragement email.
Send day 7 mail – Sends mid-trial engagement email.
Send day 13 mail – Sends near-expiry reminder email.
Send Last day email – Sends final urgency email before trial ends.
Merge – Combines all branches and continues looping for remaining users.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Send SaaS trial follow-up emails with MongoDB and Gmail |
|---|---|
| Complexity | intermediate |
| Nodes | 13 |
| Categories | Lead Nurturing |
| Author | Avkash Kakdiya |
| Published | 26 Mar 2026 |
Use the JSON export at /data/workflows/14356/14356.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
How it works This workflow runs on a daily schedule to monitor users currently on a trial plan. It fetches user data from MongoDB, calculates their trial stage, and assigns a trigger label such as ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Lead Nurturing use case.