OpenRuna
Sign in
← Workflows

Log errors and avoid sending too many emails

16 nodes · error, postgres, emailSend, pushover, manual, executeWorkflow

Engine
n8n
Nodes
16
Trigger
scheduled/triggered
Source file
1777_Error_Postgres_Send_Triggered.json

Workflow flow

IntegrationsErrorPostgreSQLEmailSendPushoverManualExecuteWorkflowIFCodeNoOp
100%
TRIGGER

Error Trigger

Error

Principal E-Mail

EmailSend

Fallback E-Mail

EmailSend

Push mobile notification

Pushover

TRIGGER

Sometimes... just cleanup

Manual

Call this Sample - Prepend to your error catcher

ExecuteWorkflow

TRIGGER

See below to prepend this at your error handling

ExecuteWorkflow

Insert Log

PostgreSQL

Count for 5 minutes

PostgreSQL

Truncate Log Database

PostgreSQL

If there is no logs in 5 minutes

IF

CleanUp execution. See below if you will prepend this workflow

Code

Insert your error handling logic after this

NoOp

13 steps · flows top to bottom, branches left to right

Browse by integration

errorpostgresemailSendpushovermanualexecuteWorkflow
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Log errors and avoid sending too many emails is a free n8n workflow on OpenRuna — 16 nodes connecting error, postgres, emailSend, pushover, manual, executeWorkflow. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

Built in n8n, "Log errors and avoid sending too many emails" chains 16 nodes to move data between error, postgres, emailSend, pushover, manual, executeWorkflow. 16 nodes · error, postgres, emailSend, pushover, manual, executeWorkflow It starts from a scheduled/triggered trigger and routes data through every node in order. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Study how data moves from error to postgres before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the error stack.
  • Import "Log errors and avoid sending too many emails" into n8n, reconnect credentials for error, postgres, emailSend, pushover, manual, executeWorkflow, and run the same automation in your own workspace.
  • Use it as a starting template when wiring error, postgres, emailSend, pushover, manual, executeWorkflow — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "Log errors and avoid sending too many emails" exposes 16 configured nodes. Trigger type: scheduled/triggered. Integrations: error, postgres, emailSend, pushover, manual, executeWorkflow. Set your credentials on the error node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "Log errors and avoid sending too many emails" JSON into a plain-English runbook, node by node. It can flag where error rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for error, postgres, emailSend, pushover, manual, executeWorkflow. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Log errors and avoid sending too many emails" — extract error IDs and secrets into environment variables without changing the 16-node structure.

Frequently asked questions

How do I import "Log errors and avoid sending too many emails" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Log errors and avoid sending too many emails" use?
It uses: error, postgres, emailSend, pushover, manual, executeWorkflow. The flow diagram above shows how each service connects across the 16 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own error and postgres credentials in n8n after import.
What trigger type does "Log errors and avoid sending too many emails" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Log errors and avoid sending too many emails" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for error, postgres, emailSend, pushover, manual, executeWorkflow.

Related resources