Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Quickbase

Quickbase integration for Flows360 workflows.

CategoryProductivity
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Quickbase with Flows360

Quickbase integration for Flows360 workflows.

Use the Quickbase connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 7 actions and 2 triggers.

Available actions

  • Create Record
  • Update Record
  • Delete Record
  • Find Record
  • Find or Create Record
  • Create / Update Records From Array
  • Custom API Call

Available triggers

  • New Record
  • New or Updated Record

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Quickbase
  • Package: @activepieces/piece-quickbase@0.2.0
  • Exact artifact digest: sha256:5c99c3ca9364d2efaa30917a03a5e85f8ad88e082d0193d3c4a38c2db620f69a
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Record (create_record), Create a new record in a Quickbase table Classification: read.
  • Update Record (update_record), Update an existing record in a Quickbase table Classification: read.
  • Delete Record (delete_record), Delete a record from a Quickbase table Classification: read.
  • Find Record (find_record), Search for records in a Quickbase table using filters Classification: read.
  • Find or Create Record (find_or_create_record), Find an existing record or create a new one if not found Classification: read.
  • Create / Update Records From Array (create_update_records_bulk), Bulk create or update multiple records based on a merge key Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Record, polling.
  • New or Updated Record, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects9
Supported actions7
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Realm Hostname Required
  • User Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Record Yes No Create a new record in a Quickbase table
Update Record Yes No Update an existing record in a Quickbase table
Delete Record Yes No Delete a record from a Quickbase table
Find Record Yes No Search for records in a Quickbase table using filters
Find or Create Record Yes No Find an existing record or create a new one if not found
Create / Update Records From Array Yes No Bulk create or update multiple records based on a merge key
Custom API Call Yes No Make a custom API call to a specific endpoint
New Record Yes No polling trigger declared by the pinned package.
New or Updated Record Yes No polling trigger declared by the pinned package.

Supported actions

Create Record · Read

Create a new record in a Quickbase table

create_record · Risk: low · Retry: safe

Inputs

  • appId · string · Required, Select the Quickbase app
  • tableId · string · Required, Select the table
  • fields · object · Required, Select and set values for table fields
Update Record · Read

Update an existing record in a Quickbase table

update_record · Risk: low · Retry: safe

Inputs

  • appId · string · Required, Select the Quickbase app
  • tableId · string · Required, Select the table
  • recordId · string · Required, Select a record from the table
  • fields · object · Required, Select and set values for table fields
Delete Record · Read

Delete a record from a Quickbase table

delete_record · Risk: low · Retry: safe

Inputs

  • appId · string · Required, Select the Quickbase app
  • tableId · string · Required, Select the table
  • recordId · string · Required, Select a record from the table
Find Record · Read

Search for records in a Quickbase table using filters

find_record · Risk: low · Retry: safe

Inputs

  • appId · string · Required, Select the Quickbase app
  • tableId · string · Required, Select the table
  • filters · object · Optional, Filter criteria to find records. Use field names or field IDs as keys.
  • sortField · string · Optional, Field to sort records by (optional)
  • sortOrder · string · Optional, Order to sort records
  • maxRecords · number · Optional, Maximum number of records to return
Find or Create Record · Read

Find an existing record or create a new one if not found

find_or_create_record · Risk: low · Retry: safe

Inputs

  • appId · string · Required, Select the Quickbase app
  • tableId · string · Required, Select the table
  • mergeField · string · Required, Field to use for matching existing records (for upsert operations)
  • fields · object · Required, Map the fields to update. Use field names or field IDs.
Create / Update Records From Array · Read

Bulk create or update multiple records based on a merge key

create_update_records_bulk · Risk: low · Retry: safe

Inputs

  • appId · string · Required, Select the Quickbase app
  • tableId · string · Required, Select the table
  • mergeField · string · Required, Field to use for matching existing records (for upsert operations)
  • records · array · Required, Array of records to create or update
  • mergeFieldBehavior · string · Required, How to handle existing records when upserting
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Record · Poll

Triggers when a new record is created in a Quickbase table

Inputs

  • appId · string
  • tableId · string
New or Updated Record · Poll

Triggers when a record is created or updated in a Quickbase table

Inputs

  • appId · string
  • tableId · string

Setup

Setup

  1. Add the Quickbase connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Realm Hostname (realmHostname), required.
  • User Token (userToken), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-quickbase@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Quickbase connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-quickbase@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com