Block 1 - Cron
- Type / Role
- n8n-nodes-base.cron - cron
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Problem: It is difficult to manually track changing flight prices and quickly identify the best time to book a ticket. Many travelers miss deals or spend too much time monitoring fares for their ...
n8n-nodes-base.cron, n8n-nodes-base.httprequest, n8n-nodes-base.function, n8n-nodes-base.if, n8n-nodes-base.gmail
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Yash Choudhary.
Original n8n.io source🚨It is difficult to manually track changing flight prices and quickly identify the best time to book a ticket. Many travelers miss deals or spend too much time monitoring fares for their specific routes and travel dates.
Takes 5-10 minutes to set up
Input: Origin: “JFK” (New York) Destination: “SEA” (Seattle) Outbound Date: “2025-09-06” Price Threshold: $250 Notification Email: [email protected]
Output: If flight from JFK to SEA on 2025-09-06 drops to $250 or below, you’ll receive an email notification: “Hi! The flight price to Seattle just dropped to $242. Book your ticket now!”
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 | Monitor flight price drops and send email alerts with SerpAPI and Gmail |
|---|---|
| Complexity | intermediate |
| Nodes | 5 |
| Categories | Personal Productivity |
| Author | Yash Choudhary |
| Published | 26 Jul 2025 |
Use the JSON export at /data/workflows/6503/6503.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.
Problem: It is difficult to manually track changing flight prices and quickly identify the best time to book a ticket. Many travelers miss deals or spend too much time monitoring fares for their ...
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 Personal Productivity use case.