Sync data from
PostgreSQL to Close
Connect your data from PostgreSQL to Close with Hightouch. No APIs, no months-long implementations, and no CSV files. Just your data synced forever.
Trusted by data teams at
Integrate your data in 3 easy steps
Add your source and destination
Connect to 15+ data sources, like PostgreSQL, and 140+ destinations, like Close.
Define your model
Use SQL or select an existing dbt or Looker model.
Sync your data
Define how fields from your model map to Close, and start syncing.
Model your PostgreSQL data using any of these methods
dbt Model Selector
Sync directly with your dbt models saved in a git.
Query using looks. Hightouch turns your look into SQL and will pull from your source.
Create and Edit SQL from your browser. Hightouch supports SQL native to PostgreSQL.
Select available tables and sheets from PostgreSQL and sync using existing views without having to write SQL.
For less technical users, pass traits and audiences from PostgreSQL using our visual segmentation builder.
Does this integration support in-warehouse planning?
Yes, if you integerate PostgreSQL and Close using Hightouch, in-warehouse planning is supported.
Great, but what is in-warehouse planning?
Between every sync, Hightouch notices any and all changes in your data model. This allows you to only send updated results to your destination (in this case Close). With the baseline setup, Hightouch picks out only the rows that need to be synced by querying every row in your data model before diffing using Hightouch’s infrastructure.
The issue here is this can be slow for large models.
Warehouse Planning allows Hightouch to do this diff directly in your warehouse. Read more on how this works here.
Why is it valuable to sync PostgreSQL data to Close?
Close is the backbone of your sales org. It's where you manage all of your contacts, accounts, and deals. The problem is that most of your CRM data has to be manually input by individual sales reps, so it doesn't show you an accurate 360-degree view of your customer. You only have access to basic information and historical interactions.
All of your Close data, in addition to the rich behavioral data captured through your app/website already, exists in PostgreSQL. Most of the time, this includes core metrics your data team has defined around lifetime value, workspaces, subscriptions, playlists, average order value, last login date, etc. There's a high chance you're probably even consuming this data in a dashboard, and your sales reps can't answer key questions like:
- Which accounts have the highest lifetime value?
- Which users have the highest utilization in our product?
- When did user X last log in to the app?
- Which leads/accounts should I be prioritizing?
- Which accounts are at risk of churning?
- What is the average order value of account X?
Your sales team doesn't want to hop back and forth between your various SaaS tools to answer these questions. They want to take action in Close, and that means enriching your CRM with data directly from your warehouse.
Why should you use reverse ETL to connect PostgreSQL and Close data?
Conventionally moving data from Snowflake to Close meant downloading ad hoc CSV files and uploading them manually or forcing your data team to integrate with the Close API and build and maintain custom pipelines. In reality, CSVs are not scalable, and in-house data pipelines and custom scripts break constantly.
Other point-to-point solutions create a weave complex web of pipelines to and from various SaaS applications and customer data platforms (CDPs), forcing you to pay for another layer of storage in addition to your data warehouses.
Reverse ETL solutions like Hightouch query against Snowflake and sync that data directly to Close. You don't have to worry about CSVs or APIs. You can leverage your existing tables, data models, and audience segments. All you have to do is define your data and map it to the appropriate columns in Close. You can schedule your syncs to run manually or even trigger them to run sequentially based on criteria that you define.
Hightouch automatically diffs data between syncs to ensure your only ever syncing the freshest data, and if any rows fail, Hightouch will automatically retry them later. A live debugger lets you analyze your API payload requests/responses and failed runs in real-time.
Push lead info from your warehouse into Close to enable executives to go after the right accounts
Push product data to enable account managers to know what actions are being taken in the app
Enable account executives to create more relevant and timely outbound campaigns
PostgreSQL, also known as Postgres, is a free and open-source relational database management system emphasizing extensibility and SQL compliance.Learn more about PostgreSQL
Close is the inside sales CRM of choice for startups and SMBs. Make more calls, send more emails and close more deals starting today.Learn more about Close
Other PostgreSQL Integrations
Other Close integrations
Hightouch Playbooks: Best practices to leverage reverse ETL
Read more about Hightouch
What is Operational Analytics & Why You Should Use It
Operational Analytics shifts the focus from simply understanding data to taking action on it in the tools that run business processes. Instead of using dashboards to make decisions, Operational Analytics is focused on turning insights into action – automatically.Read
Activate data to any of your marketing and advertising tools
This might be one of the greatest inventions for technical marketers since the advent of legacy CDPs back in 2015.
Head of Marketing Technology
Your data is always secure
SOC 2 Type 2 compliant
Your data stays secure, available, and confidential. To see our report, .
If you’re in the EU, your data is only processed on EU data centers.
Healthcare companies like ThirtyMadison, Chapter Health, and Headway trust Hightouch.
To see our DPA (Data Processing Addendum), .
increase in return on ad spend
improvement in email engagement
lift in customer acquisition