PostgreSQL Help & Support

  • How to Get Started with PostgreSQL
  • Popular Things To Do With PostgreSQL
  • Common Problems with PostgreSQL

How to Get Started with PostgreSQL

The hardest part of connecting to PostgreSQL is getting the connection settings right. When connecting a new PostgreSQL account these are the fields you are presented with:

Connect Fields

Host The IP address or hostname (db.example.com) of where your database instance resides. Make sure it is accessible from outside your network. We send out database connections from the IP addresses listed here.

Port 5432 is the default for PostgreSQL. Change if you run on a different port

Database Name of the database to read data out of.

Schema The schema inside PostgreSQL to search for tables.

Username Username with access to the database. We recommend creating a brand new Zapier-specific user with highly limited permission scope.

Password Similar to the username, make this a unique strong password (check out https://random.org). This password should not contain spaces.

Note: all fields are stored encrypted in our database. Of course, we have the encryption keys on hand but they are stored separately to minimize risk. Nonetheless, we recommend not hooking a production database to Zapier. Instead, set up an intermediary database to connect with Zapier then dump data back to your main production database using some out-of-band process.

Popular Things To Do With PostgreSQL

  • Create new rows on Google Sheets for new custom query matches on PostgreSQL

    PostgreSQL + Google Sheets

    Try It
  • Send new rows on Google Sheets to PostgreSQL

    Google Sheets + PostgreSQL

  • Get Slack messages for new custom query matches on PostgreSQL

    PostgreSQL + Slack

  • Add new rows to PostgreSQL for new Typeform entries

    Typeform + PostgreSQL

  • Send updated rows on Google Sheets to PostgreSQL

    Google Sheets + PostgreSQL

  • Post Slack messages for new rows added to PostgreSQL

    PostgreSQL + Slack

Common Problems with PostgreSQL

Existing columns causing an error when using Custom Query

Double-check if your column names contain any uppercase characters. This will cause an error, as by default they are converted to lowercase. To fix your query, you’ll need to wrap the column name in double quotes.

In the example below, you’ll want to put double quotes around the column named myStatus.
SELECT id, “myStatus” FROM my_table LIMIT 50;

Connect the apps you use every day

Get started with a Free account

Or
By signing up, you agree to Zapier’s Terms of Service