From 8a99bd5b24123c2cacdae6f1a80fdffe64f6beb5 Mon Sep 17 00:00:00 2001 From: Brian Fritton Date: Wed, 29 Oct 2025 16:32:08 -0500 Subject: [PATCH 1/3] Clarify method of listening for postgres changes and required database permissions for Postgres triggers Added a note on database permissions for creating listing events in PostgreSQL, and how listening for those events works under the hood. --- .../trigger-nodes/n8n-nodes-base.postgrestrigger.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md index c4cb60e12e4..25c97b95856 100644 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md +++ b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md @@ -27,6 +27,13 @@ You can configure how the node listens for events. * Delete * Select **Listen to Channel**, then enter a channel name that the node should monitor. +**Note on database permissions to creating listing events**: +* To listen for trigger events, n8n automatically creates a Postgres trigger on the target table to monitor for the event. This trigger rule on the table is added when your workflow is activated and removed when it is deactivated. +* If your workflow is not active, it is added any time you test your workflow by listening for a test event, and automaticcally deleted again when the test event listening stops. +* The Postgress trigger calls an automatically-created procedure to tell n8n about the event. +* The user in your Postgres credential must have permissions to create and execute triggers and procedures. In PostgreSQL, only superusers or the table owner (or those with TRIGGER privilege) can create triggers on that table. The user must also have CREATE privilege on the schema where the procedure will reside. + + ## Related resources n8n provides an app node for Postgres. You can find the node docs [here](/integrations/builtin/app-nodes/n8n-nodes-base.postgres/index.md). From dcee39cf309ab0012560ebea9b8eb7d3e29ac83b Mon Sep 17 00:00:00 2001 From: Brian Fritton Date: Wed, 29 Oct 2025 16:43:42 -0500 Subject: [PATCH 2/3] Fixed spelling / reworded note on n8n PostgreSQL trigger events Clarified note on how n8n listens for PostgreSQL changes and updated database permissions requirements. --- .../builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md index 25c97b95856..864d695ebcf 100644 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md +++ b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md @@ -27,9 +27,9 @@ You can configure how the node listens for events. * Delete * Select **Listen to Channel**, then enter a channel name that the node should monitor. -**Note on database permissions to creating listing events**: -* To listen for trigger events, n8n automatically creates a Postgres trigger on the target table to monitor for the event. This trigger rule on the table is added when your workflow is activated and removed when it is deactivated. -* If your workflow is not active, it is added any time you test your workflow by listening for a test event, and automaticcally deleted again when the test event listening stops. +**Note on how n8n listens for postgrest changes and database permissions required**: +* To listen for trigger events, n8n automatically creates a Postgres trigger on the target table to monitor for the event. This trigger on the table is added when your workflow is activated and removed when it is deactivated. +* If your workflow is not active, it is added any time you test your workflow by listening for a test event, and automatically deleted again when the test event listening stops. * The Postgress trigger calls an automatically-created procedure to tell n8n about the event. * The user in your Postgres credential must have permissions to create and execute triggers and procedures. In PostgreSQL, only superusers or the table owner (or those with TRIGGER privilege) can create triggers on that table. The user must also have CREATE privilege on the schema where the procedure will reside. From c30ea2021b4fa225a94875c0056232dbdc6539cd Mon Sep 17 00:00:00 2001 From: Brian Fritton Date: Wed, 29 Oct 2025 16:44:35 -0500 Subject: [PATCH 3/3] spelling correction --- .../builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md index 864d695ebcf..de8836219cf 100644 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md +++ b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md @@ -27,7 +27,7 @@ You can configure how the node listens for events. * Delete * Select **Listen to Channel**, then enter a channel name that the node should monitor. -**Note on how n8n listens for postgrest changes and database permissions required**: +**Note on how n8n listens for Postgres events and database permissions required**: * To listen for trigger events, n8n automatically creates a Postgres trigger on the target table to monitor for the event. This trigger on the table is added when your workflow is activated and removed when it is deactivated. * If your workflow is not active, it is added any time you test your workflow by listening for a test event, and automatically deleted again when the test event listening stops. * The Postgress trigger calls an automatically-created procedure to tell n8n about the event.