Configure Connection
Quickbase guide
Prepare a Quickbase service account, configure the connection in NIM, and collect report data to verify access.
Before you startDirect link to Before you start
Create a service account following the Quickbase user setup documentation. Quickbase requires the API user to be provisioned and assigned an application role that allows access to the intended data.
NIM requires Hostname, App ID, and Token. The connector is read-only and collects report data for use in NIM and downstream systems.
Verify access by collecting data
The connector currently always returns success for Test Connection. This result does not verify connectivity or credentials. Run a collection from the system to test the connection.
Set up the service accountDirect link to Set up the service account
- Provision a dedicated Quickbase service account using the vendor instructions linked above.
- Assign an application role that allows the account to read the reports and underlying data your NIM process needs.
- Obtain the API token for the integration and confirm that it permits access to the intended application.
- Record the Quickbase hostname, App ID, and token.
Enter the connection settingsDirect link to Enter the connection settings
- In NIM Studio, open Systems > Overview and add a Quickbase system, or select the existing system.
- Open its Connection screen.
- Enter the following settings and save the connection.
| NIM setting | Value |
|---|---|
| Hostname | The hostname of the Quickbase environment NIM will access. |
| App ID | The identifier of the Quickbase application containing the report data. |
| Token | The API token configured for access to the intended application. |
Test access by collecting report dataDirect link to Test access by collecting report data
- Run a collection from the Quickbase system in NIM. Test Connection currently always returns success and cannot be used to verify access.
- Confirm that collection completes successfully and inspect the returned report data.
- Check that the report filters, columns, and returned records match the data your process needs.
- If collection fails, verify the Hostname, App ID, Token, service account access, and application role permissions.
- Validate matching rules and intended operations in each destination system before using Quickbase data for downstream provisioning.
Step 1 of 3