Skip to main content

Close Setup

This guide walks you through setting up Close on Sequin.

In just a couple of minutes, you'll have a Postgres database with all your Close data, syncing in real-time.

Connect with Close

First, add a Close API key to Sequin:

Step 1: Create a new Sequin account at

Step 2: Select Close as the platform you want to sync.

Step 3: Provide us with a Close API key:

Enter your Close API key

You can generate a new API key for Sequin by going to your Close API settings. You'll need to supply Sequin an admin API key when using Sequin in production. More here.

Step 4: Select the tables you want to sync. By default, we'll sync all the tables. You can adjust which tables you sync at anytime.

Step 5: Select the destination database you want to sync your data to. By default, we'll sync to a new Postgres Database we host for you. Or, we can sync to a new schema in a database you've created with Sequin or that you host:

Create your Sequin database

Step 6: Click Create.

After you click Create, we'll immediately connect to Close and begin back-filling all your data.

Sync complete

Connect to your Postgres database

As soon as your database is provisioned, you can connect to it and start querying.

If you chose to sync your data to a Sequin provisioned database, then your database is hosted on AWS RDS. If you chose to sync to a database you are hosting, then you or a database admin will know the details of your hosting.

For this setup guide, we'll use TablePlus as an example.

Step 1: Download and install TablePlus from

Step 2: Open TablePlus and click Create a new connection...

Step 3: Click the Import from URL button.

Step 4: Copy and paste the Connect URL from Sequin into the Connection URL in TablePlus then click Import.

Step 5: Then name your TablePlus connection and click Create.

Close to TablePlus

Query Close with SQL

You'll now see all your Close data represented in Postgres. To start querying, click the SQL button and write your first statement:

select (sum(opportunity."value")/100.00)::money as "pipeline_value"
from opportunity
inner join opportunity_status on = opportunity.status_id
where opportunity_status.type = 'active';