Skip to main content

Real-time PulsePoint emergency alerts to iMessage with AI summaries

Workflow preview

Workflow preview
100%
Real-time PulsePoint emergency alerts to iMessage with AI summaries preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Emergency Alerts Reporter to iMessage This n8n template fetches real time emergency incident alerts from PulsePoint for a specific agency and delivers them directly to any phone number via iMess...

Best for

  • Personal Productivity automation workflows
  • AI Summarization automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.httprequest, n8n-nodes-base.manualtrigger, n8n-nodes-base.scheduletrigger, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.code, n8n-nodes-base.if, @n8n/n8n-nodes-langchain.lmchatopenai

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by David Harvey.

Original n8n.io source

1.1 Workflow description

Title
Real-time PulsePoint emergency alerts to iMessage with AI summaries
Workflow name
Real-time PulsePoint emergency alerts to iMessage with AI summaries

🚨 Emergency Alerts Reporter to iMessage

This n8n template fetches real-time emergency incident alerts from PulsePoint for a specific agency and delivers them directly to any phone number via iMessage using the Blooio API. It's designed to keep users informed with clear, AI-summarized reports of emergency activity near them—automatically and reliably.

Use cases are powerful and immediate:

  • Get real-time fire/medical alerts for your neighborhood.
  • Use it for family, local safety groups, or even emergency response teams.
  • Convert technical dispatch data into readable updates with emojis and plain English.

🧠 Good to Know

  • You’ll need a PulsePoint agency ID (see instructions below).
  • iMessages are sent using Blooio’s API (which supports Apple’s iMessage and fallback RCS/SMS).
  • Messages are AI-enhanced using OpenAI's o4-mini model to summarize incident reports with context and urgency.
  • The workflow runs every hour, but this can be configured to match your needs.
  • Each report is sent only once, thanks to persistent tracking of seen incident IDs in workflow static memory.

⚙️ How it Works

  1. Trigger: A Schedule Trigger (every hour) or manual start kicks off the flow.
  2. Get Alerts: A code node fetches the latest PulsePoint incidents for a specified agency and decrypts the data.
  3. Filter New Incidents: We store previously seen incident IDs to prevent duplicate alerts.
  4. Merge Incidents: All new incident details are merged into a single payload.
  5. Condition Check: If there are no new incidents, nothing is sent.
  6. AI Summary: The incident data is passed to an AI agent for summarization with human-friendly emojis and formatting.
  7. Send Message: The final summary is sent via Blooio’s API to your phone using iMessage.

📝 How to Use

  1. Get Your PulsePoint Agency ID:

    • Visit https://web.pulsepoint.org.
    • Find your agency by location or name.
    • Inspect the API call or browser network log to get the agencyid (e.g. 19100 from a URL like ?agencyid=19100).
  2. Set Up Blooio for Messaging:

    • Sign up at https://blooio.com.
    • Go to your account and retrieve your Bearer API Key.
    • Pricing details available on their pricing page.
    • Add your key to the HTTP Request node as a Bearer Token.
  3. OpenAI API:

  4. Add Your Phone Number:

    • Replace +1111112222 with your actual number (international format).
    • You can also modify the message content or prepend special tags/emojis.

✅ Requirements

  • PulsePoint agency ID – See usage instructions above
  • OpenAI API Key – Get API Key
  • Blooio Account & Bearer Token – Get Started
  • Phone number for iMessage delivery

🔧 Customizing This Workflow

  • Change the schedule to get alerts more or less frequently
  • Add filters to only get alerts for specific incident types (e.g. fires, traffic accidents)
  • Send to groups: Expand to send alerts to multiple recipients or use Slack instead of iMessage
  • Use different AI prompts to get detailed, humorous, or abbreviated alerts depending on your audience

With just a few credentials and a phone number, you’ll have real-time incident alerts with human-friendly summaries at your fingertips.

🛠️ Stay informed. Stay safe.

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Send Message

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 3 - When clicking ‘Execute workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 4 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 5 - AI Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 2

Block 6 - Merge all

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 7 - If

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 8 - OpenAI Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.2

Block 9 - Get alerts

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 10 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 11 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Real-time PulsePoint emergency alerts to iMessage with AI summaries
Complexity intermediate
Nodes 11
Categories Personal Productivity, AI Summarization
Author David Harvey
Published 01 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/5533/5533.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Frequently asked questions

What does Real-time PulsePoint emergency alerts to iMessage with AI summaries do?

Emergency Alerts Reporter to iMessage This n8n template fetches real time emergency incident alerts from PulsePoint for a specific agency and delivers them directly to any phone number via iMess...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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, AI Summarization use case.