Hi @gariva,
when using the Postgres Trigger Node to listen for events on a table it will automatically create a postgres trigger and function to listen to events. Both will be created if you manually run your workflow or if you activate your workflow. Also both will be deleted once a manuel execution finished or you deactivate you workflow. If n8n restarts it will reuse the previously created postgres trigger and function. Each Trigger node will create their own postgres trigger and function.
In regards to your problems mentioned here I am surprised to hear that the trigger worked once and than didn’t work a second time giving an error “must be owner of relation alertas_rastreo”.
- Are you sure that your postgres user also has access to “alertas_rastreo”?
- Did you try activating your workflow and checking the executions view to see if multiple events were fired (workflow setting Save successful production executions must be enabled)?