Turn Notion incident entries into on call alerts and keep both tools in sync. Teams that track issues in Notion can notify responders in SIGNL4 fast, then close alerts by updating simple checkboxes.

A Notion trigger watches for new pages and sends an alert to SIGNL4 with the page ID as the external reference and optional location data. A scheduled scan also runs on an interval to find new records that are not marked as read, sends alerts, and then marks them as read. Another scheduled path looks for open records marked as Up to resolve the matching SIGNL4 alert and update the Notion page. A webhook accepts status callbacks and writes the status message into the Notion Description using a small function to map fields.

Set up a Notion database with Name, Read checkbox, Up checkbox, and a Description rich text field. Connect Notion and SIGNL4 credentials in n8n, then point your alert source to the webhook if you want status updates written back. Expect faster response times, fewer missed alerts, and cleaner records. Useful for IT on call, plant floor machines, and service desk triage.

• Notion event trigger sends SIGNL4 alerts when a new page is added to a chosen database.
• Interval trigger scans the database on a schedule to find new records and mark them as read after alerting.
• Second scheduled scan finds open items marked as Up and resolves the matching SIGNL4 alert.
• Webhook endpoint receives status updates and a function maps the payload to update Notion fields.
• Notion updates write the s4Status into the Description rich text field for clear context.
• Alerts include the Notion page ID as the external ID to link alerts and records one to one.
• Optional location data is attached to alerts to help responders understand where the issue is.

• Reduce alert dispatch time from several minutes to under 1 minute with automatic triggers and scheduled scans.
• Eliminate manual paging by sending alerts from Notion entries with one source of truth.
• Close alerts faster by resolving directly from a Notion checkbox instead of switching tools.
• Improve data accuracy by syncing status back to Notion through the webhook with the correct external ID.
• Connect Notion and SIGNL4 seamlessly so teams see the same incident status in both systems.

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Notion and SIGNL4. See the Tools Required section above for links to create accounts with these services.
3. Prepare your Notion database: add properties Name title, Read checkbox, Up checkbox, and Description rich text. Copy the database ID from the Notion URL.
4. In the n8n credentials manager, create Notion credentials. Double click any Notion node, choose Create new credential, and follow the on screen steps to connect your Notion workspace.
5. Open the Notion Trigger node and select your database. Set the event to page added to database and confirm the poll time is one minute.
6. Open the Interval node and set the interval to match your needs. The template uses 20 units so adjust the unit and value to control scan frequency.
7. Configure the Notion Read New and Notion Read Open nodes to use your database ID and ensure the filters reference the exact property names Read and Up.
8. Create SIGNL4 credentials in n8n. Double click a SIGNL4 node, select Create new credential, and follow the steps to add your team secret or API key from your SIGNL4 account.
9. In the SIGNL4 Alert nodes, keep the external ID mapped to the Notion page ID. Update the message text if you want different alert titles.
10. Open the Webhook node and copy the production URL. Configure your alert source to POST to this URL and include alert.externalEventId and a status field that your function expects.
11. Check the Function node that processes the webhook. Confirm it reads the incoming status and sets a field like s4Status that the Notion Update node uses.
12. Test end to end: add a new page in Notion. Verify that an alert appears in SIGNL4, then toggle Up and Read in Notion to watch the resolve path update both systems.
13. Troubleshoot: if alerts do not send, verify Notion filters and property names. If resolves fail, confirm the external ID in SIGNL4 matches the Notion page ID. For webhook issues, send a sample POST with Postman and watch the n8n execution log.