Send earthquake safety checks to employees with P2PQuake, LINE, and Google Sheets
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 15 nodes and runs on a schedule (every 30 minutes) (plus 1 other trigger). Along the way it connects Google Sheets. It also calls api.p2pquake.net and api.line.me over HTTP.
How it runs
Trigger: On a schedule (every 30 minutes) (plus 1 other trigger).
- Fetch Earthquake Information (HTTP Request): calls api.p2pquake.net
- Route LINE Message (Switch): routes items into 3 branches
- Get Latest Earthquake (Limit): keeps the first few items
- Update Status - Safe (Google Sheets): update
- Update Status - Needs Help (Google Sheets): update
- Update Status - Other (Google Sheets): update
- Register Employee (Google Sheets): append
- Get Last Earthquake ID (Google Sheets): uses Google Sheets
- Is New Earthquake? (If): checks a condition and branches into true / false
- Get Employees (Google Sheets): uses Google Sheets
…plus 3 more steps. See the full node list below.
Services it uses
HTTP calls to: api.p2pquake.net, api.line.me
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Limit
n8n-nodes-base.limit - Google Sheets
n8n-nodes-base.googleSheets - If
n8n-nodes-base.if - Switch
n8n-nodes-base.switch - Webhook
n8n-nodes-base.webhook
From the author
Quick overview This workflow polls the P2PQuake earthquake API every 30 minutes, checks impacted employees stored in Google Sheets, and sends targeted safety check messages via the LINE Messaging API, while also recording employee registration and response…