Get started with a free trial today
Already have an account? Sign in
Stitch’s Quick Base integration replicates data using theQuick Base HTTP API. Refer to theSchema section for a list of objects available for replication.
A high-level look at Stitch's Quick Base (v1) integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release status | Released on June 27, 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 | Supported | Column selection | Supported |
| Select all | Supported | ||
| TRANSPARENCY | |||
| Extraction Logs | Supported | Loading Reports | Supported |
To retrieve your URL, sign into your Quick Base account.
You’ll need to enter the URL that displays in your browser into Stitch. You should include thehttps:// portion, and omit anything afterdb/.
For example: Based on the URL in the image below, we’d enterhttps://stitchdata.quickbase.com/db/ into Stitch:

Next, you’ll retrieve the ID of the Quick Base app you want to replicate data from.
In Quick Base, click the desired app in theMy Apps section.
When the app opens, the URL in your browser will now contain the app’s ID. This is the alpha-numeric string afterdb/. In this example, the app ID isbngf9ix7e.

QuickBase user tokens
Quick Base user tokens are linked to the user who creates them. This means that Stitch will only be able to access the same data in Quick Base as the user who creates the token.
Before proceeding, verify that you can access the tables and fields in Quick Base that you want to replicate.
StitchThe token will display in theToken field of theMy User Tokens page. Keep this page open for now - you’ll need it to complete the next step.
On the Stitch Dashboard page, click theAdd Integration button.
Click theQuick Base 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 Quick Base” would create a schema calledstitch_quick_base in the destination.Note: Schema names cannot be changed after you save the integration.
https://stitchdata.quickbase.com/db/bngf9ix7eThe Sync Historical Data setting defines the starting date for your Quick Base integration. This means that dataequal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond Quick Base’s default setting of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.
In theReplication Frequency section, you’ll create the integration’sreplication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
Quick Base 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 theUnderstanding and Reducing Your Row Usage guide for tips on reducing your usage.
After you finish setting up Quick Base, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, aPending status indicates that Stitch is in the process of scheduling the initial replication job for the integration.This may take some time to complete.
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 theAnchor Scheduling documentation for more information.
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.
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 forversion 1 of this integration.
This is the latest version of the Quick Base integration.
Every table in a Quick Base app will display as a selectable table in the Stitch app. Tables are named according to this convention:[app_name]__[table_name].
For example: If an app namedevent_handling containedcustomers,events, andrsvps tables, you could expect the following tables to be created in your destination:
event_handling__customersevent_handling__eventsevent_handling__rsvpsThe schema of Quick Base tables will contain the fields the user linked with theuser token has access to, along with a handful of other fields:
| rid STRING | The unique record ID.This is the Primary Key for the table. |
| record_id STRING | The unique record ID. |
| date_created DATE-TIME | The date the record was created. |
| date_modified DATE-TIME | The date the record was last modified. This is the column Stitch will use as aReplication Key. |
| last_modified_by STRING | The ID of the user who last modified the record. |
| record_owner STRING | The ID of the user who created the record. |
Some destinations restrict the use of special characters and spaces in column names. While Quick Base doesn’t restrict the use of these characters in their app, attempting to load column names as-is from Quick Base may cause issues.
To prevent loading issues, Stitch’s Quick Base will perform the following on column names:
-) with underscores (_)! or#Below are a handful of examples of how Quick Base column names will appear in Stitch:
| Column name in Quick Base | Column name in Stitch |
| Customer Name | customer_name |
| Is a VIP? | is_a_vip |
| EmAiLAdDrEsS | emailaddress |
| Street!Address | streetaddress |
| Phone #number | phone_number |
| Related | Troubleshooting |
Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.