Stitch Documentation
has moved!

Please update your bookmarks to https://www.stitchdata.com/docs

If you're not automatically redirected after 5 seconds, click here.

Connecting Close.io

Connecting your Close.io data to Stitch a four-step process:

  1. Genereate a Close.io API Key
  2. Add Close.io as a Stitch Data Source
  3. Defining the Historical Sync
  4. Define the Replication Frequency

Generating a Close.io API Key

  1. Log into your Close.io account.
  2. Click the user menu (your icon) in the top right corner.
  3. Click Settings.
  4. In the Company menu (located under the You menu), click Your API Keys.
  5. In the Your API Keys section, click the Generate New API Key button.
  6. A new API Key will display. Keep this handy; you’ll need it in the next step.

Adding Close.io as a Stitch Data Source

  1. From the Stitch Dashboard page, click the Add an Integration button.
  2. Click the Close.io icon. This will open the Close.io credentials page.
  3. 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 data warehouse.

    For example, the name “Stitch Closeio” would create a schema called stitch_closeio in the data warehouse.
  4. Paste your Close.io API Key into the API Key field.
  5. Click the Save Integration button.

Defining the Historical Sync

The Sync Historical Data setting will define 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 sync data beyond Close.io’s default setting of 1 year. For a detailed look at historical syncs, check out the Syncing Historical SaaS Data article.

Defining the Replication Frequency

The Replication Frequency controls how often Stitch will attempt to replicate data from your Close.io integration. By default the frequency is set to 30 minutes, but you can change it to better suit your needs.

Note that the more often Close.io is set to replicate, the higher your row count will be. Even though all the tables in Close.io integrations use Incremental Replication, replicating data frequently will increase your usage.

Stitch & Replicating Close.io Data
Before setting the Replication Frequency, we recommend checking out the structure & Replication Methods for this integration’s tables. Tables that contain nested structures will lead to a higher number of replicated rows.

To help prevent overages, we recommend setting the Replication Frequency to something less frequent - like 6 hours instead of 30 minutes.

For more tips on reducing your row count, check out the Reducing Your Row Count article.

After setting the Replication Frequency, click Save Integration to wrap things up.

Related:

Was this article helpful?
0 out of 0 found this helpful

Comments

Questions or suggestions? If something in our documentation is unclear, let us know in the comments!