Clarify method of listening for postgres changes in trigger node and required database permissions for Postgres triggers #3823
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a note on database permissions for creating listing events in PostgreSQL, and how listening for those events works under the hood.
Note
Clarifies how the Postgres Trigger node listens for events and the database permissions required to enable it.
docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postgrestrigger.md):TRIGGERprivilege;CREATEon target schema.Written by Cursor Bugbot for commit 1f6edea. This will update automatically on new commits. Configure here.