|
expand INTEGER, BOOLEAN |
|
text STRING |
Already have an account? Sign in
Close.io (v1)
Last updated: 9/15/2026Information note
Close.io extraction is supported by Stitch
This integration is powered by Singer's Close.io tap and certified by Stitch. Check out and contribute to the repo on GitHub.
For support, contact Support.
This integration is powered by Singer's Close.io tap and certified by Stitch. Check out and contribute to the repo on GitHub.
For support, contact Support.
Close.io integration summary
Stitch’s Close.io integration replicates data using the Close.io REST API . Refer to the Schema section for a list of objects available for replication.
Close.io feature snapshot
A high-level look at Stitch's Close.io (v1) integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release status |
Released on September 17, 2018 |
Supported by
|
|
|
Stitch plan
|
Standard |
API availability
|
Available
|
| Singer GitHub repository | |||
| REPLICATION SETTINGS | |||
|
Anchor Scheduling
|
Supported
|
Advanced Scheduling
|
Supported
|
|
Table-level reset
|
Unsupported
|
Configurable Replication Methods
|
Unsupported
|
| DATA SELECTION | |||
|
Table selection
|
Unsupported
|
Column selection
|
Unsupported
|
|
Select all
|
Unsupported
|
||
| TRANSPARENCY | |||
|
Extraction Logs
|
Supported
|
Loading Reports
|
Supported
|
Connecting Close.io
Step 1: Generate a Close.io API Key
- Sign into your Close.io account.
- Click the user menu (your icon) in the top right corner.
- Click Settings.
- In the Company menu (located under the You menu), click Your API Keys.
- In the Your API Keys section, click the Generate New API Key button.
- A new API Key will display. Keep this handy; you’ll need it in the next step.
Step 2: Add Close.io as a Stitch data source
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the Close.io icon.
-
Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch Close.io” would create a schema called
stitch_closeioin the destination. Note: Schema names cannot be changed after you save the integration. - In the API Key field, paste your Close.io API Key.
Step 3: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your Close.io integration. This means that data equal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond Close.io’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.
Step 4: Create a replication schedule
Information note
Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the Replication Scheduling documentation for more information.
In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
Close.io integrations support the following replication scheduling methods:
-
Advanced Scheduling using Cron (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.
Initial and historical replication jobs
After you finish setting up Close.io, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.
Information note
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.
Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
Information note
Replication will continue after the seven days are over. If you’re no longer interested in this source, be sure to pause or delete the integration to prevent unwanted usage.
Close.io replication
Replicating activity data
Every time Stitch runs a replication job for Close.io, the last 24 hours’ worth of data will be replicated.
This is applicable to all tables in the integration.
As Close.io doesn’t currently provide a way to query for activities based on modification time, Stitch replicates data in this way to ensure updated activities are captured. A list of available querying methods can be found in Close.io’s documentation.
Setting the Replication Frequency to a higher frequency - like 30 minutes - can result in re-replicating recent data and contribute to greater row usage. Selecting a lower frequency can help keep your row count low.
Refer to the documentation for each of these tables in the next section for more info.
Attribution window examples
In the tabs below are examples of attribution windows behave during historical (initial) and ongoing replication jobs.
For historical and full re-replications of Close.io data, Stitch will query for and extract data newer than or equal to the date defined in the Start Date field in the Integration Settings page.
The Start Date, in conjunction with the Attribution Window, defines the minimum date Stitch should query for when extracting historical data. This is calculated as:
Start Date - Attribution Window = Minimum Extraction Date
Example
During the initial set up, the Start Date field is set to 07/03/2017, or ``.
To account for the Attribution Window, Stitch would calculate the Minimum Extraction Date value as: 2017-07-03 00:00:00 - 24 hours = 2017-07-02 00:00:00
If you were to write a SQL query using this date for the activities table, it might look like this:
SELECT *
FROM closeio.activities
WHERE date_created >= '2017-07-02 00:00:00' /* Min. Extraction Date */
ORDER BY date_created
For ongoing replication jobs, Stitch will query for and extract data using the last saved maximum value in the table’s Replication Key column and the Attribution Window for the table.
Note: This applies to every replication job that takes place after the historical replication job.
Example
The last maximum saved Replication Key value for the activities table is 2017-10-01 00:00:00.
To account for the Attribution Window of 24 hours, we’d subtract this from the last maximum saved Replication Key value:
2017-10-01 00:00:00 - 24 hours = 2017-09-30 00:00:00
In this case, Stitch would query for and extract data that is newer than or equal to 2017-09-30 00:00:00 and older than or equal to 2017-10-01 00:00:00.
If this were a SQL query, it might look like this:
SELECT *
FROM activities
WHERE date_created >= '2017-09-30 00:00:00'
/* max Replication Key value - Attribution Window */
AND date_created <= '2017-10-01 00:00:00'
/* max Replication Key value from previous job */
ORDER BY date_created
Historical event log data limitations
Due to how Close.io’s API functions, only 30 days of historical data is available for event logs:
Most actions in Close.io that change an object are logged in the event log. For example, creating a lead, sending an email, or deleting a note will create an event log entry. The event log API allows you to access these events, up to 30 days back in history.
This means that despite what the integration’s Start Date is set to, Stitch will only be able to retrieve 30 days of historical data from the connection date for the event_log table.
Additionally, note that if you ever reset the integration, this will also apply to the date the integration is reset.
Close.io table reference
Information note
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for version 1 of this integration.
This is the latest version of the Close.io integration.
Information note
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs > customers), while case is maintained in PostgreSQL destinations (CusTomERs > CusTomERs). Refer to the Loading Guide for your destination for more info.
activities
The activities table contains info about various activities in your Close.io account.
An activity belongs to a lead and can represent any type of activity that was performed on a lead or its contact. This includes calls, emails, notes, and so on.
Attribution window
When Stitch replicates data for this table, it will use an attribution window of 24 hours to fetch updated activities.
This means that every time a replication job runs, the last 24 hours’ worth of data will be replicated for this table. This is because Close.io doesn’t provide a way to query for activites based on a modification time, only when activities are created. A list of available querying methods can be found in Close.io’s documentation.
Refer to the Replication section for more info and examples of how the attribution window is used to query for data.
|
Append-Only Incremental |
|
|
Primary Key |
id |
|
Replication Key |
date_created |
| Useful links |
custom_fields
The custom_fields table contains info about the custom fields in your Close.io account.
Custom fields allow you to store arbitrary data on leads in Close.io. Refer to Close.io’s documentation for more info.
|
Key-based Incremental |
|
|
Primary Key |
id |
|
Replication Key |
date_updated |
| Useful links |
event_log
The event_log table contains info about events generated in your Close.io account. This could include creating a lead, sending an email, or deleting a note.
Historical data limitations
Due to how Close.io’s API functions, only 30 days of historical data is available for this table from the initial connection date.
Refer to the Replication section for more info.
|
Key-based Incremental |
|
|
Primary Key |
id |
|
Replication Key |
date_updated |
| Useful links |
leads
The leads table contains info about the leads in your Close.io account.
Leads represent a company or organization and may contain contacts, tasks, opportunities, and activities. In Close.io, a lead is synonymous with “account” in other CRMs.
|
Key-based Incremental |
|
|
Primary Key |
id |
|
Replication Key |
date_updated |
| Useful links |
tasks
The tasks table contains info about the tasks in your Close.io account. Tasks are action items with a given date that are assigned to a sales rep.
|
Key-based Incremental |
|
|
Primary Key |
id |
|
Replication Key |
date_updated |
| Useful links |
users
The users table contains info about the users in your Close.io account.
In Close.io, users are typically your co-workers and sales reps, or those inside your company.
|
Key-based Incremental |
|
|
Primary Key |
id |
|
Replication Key |
date_updated |
| Useful links |