This article explains how to add the Quickbase integration to a global workflow in FastField. After you add the integration, responses in FastField forms are sent to a Quickbase table.
In this article
Builders add the Quickbase integration to global workflows to connect data. This sends form responses from FastField to an app in Quickbase. During setup, builders map the fields between the form and the app, and can set up conditions to trigger automated workflows.
Before adding the integration to a workflow, you need to set up an integration in FastField by linking your accounts with a user token. Learn more about setting up an integration in FastField.
Add the integration to a new global workflow
- In the FastField Portal, expand the Workflow menu, and then select Global Workflow.
- Select + New Workflow and then enter a name for your workflow.
- Select a form to use for the workflow. Then select the Send to Quickbase action.
To send a file of a report to an attachment field within a Quickbase table, select Send file to Quickbase.
- Add a name for this action. Then select an existing Quickbase integration or create a new one.
This requires linking your FastField and Quickbase accounts with a user token.
- Enter, and then validate your Quickbase App ID.
This selects the app that form responses are sent to. - Select the Quickbase table, and then select Add Quickbase table mapping.
- Map the fields to use.
This selection sends data from the FastField form field to the Quickbase table field. - Save your changes.
This adds the integration to your workflow and starts sending data.
Add the integration to an existing global workflow
- In FastField, expand the Workflow menu, and then select Global Workflow.
- Select the name of a workflow to edit it.
- Select + New Action Set, and then add a name for your action.
- Select your Quickbase integration or create a new one, and then validate your Quickbase App ID.
- Select the Quickbase table, and then select Add Quickbase table mapping.
- Map the fields to use.
This selection sends data from the FastField form field to the Quickbase table field. - Save your changes.
This adds the integration to your workflow, and starts sending data.
Field mappings
This table explains the current field mappings supported by this integration.
| Quickbase field type | FastField field type |
| Text | Text |
| Text Multi-line | Text |
| Rich Text | Text |
| Text Multiple Choice | List |
| Numeric | Numeric |
| Checkbox | Switch |
| Currency | Numeric |
| Date | Date |
| Duration | Numeric |
| File Attachment |
Single Photo (Allow Camera) |
|
Single Photo (Allow File Library) |
|
|
Video |
|
|
Embedded Photo |
|
|
Audio |
|
| Street 1 |
Location/GPS |
|
Text |
|
| City |
Text |
| State |
Text |
| Postal Code |
Text |
| Country |
Text |
| Phone Number |
Formatted Numeric (US Phone) |
| Record ID # Key Field |
Add Related Quickbase Table Mapping |
| Reference field |
Data Table |
Troubleshooting
| Problem | Solution |
| Missing fields | Close and re-open the workflow |
| Validation error | Remove and re-add app ID and user token |
Limitations
Submission failure notifications
If a FastField form submission fails to upload a new or updated record to a Quickbase table, no alert is sent to notify anyone of this failure. An Upsert Failure log displays in the Submissions activity log within FastField, however.
We are planning to add notifications for upsert failures in the future.
Field mappings
Currently, the following fields cannot be mapped with complete accuracy between Quickbase and FastField.
- Multi-choice fields that pull choices from another field or table are mapped as Text fields with no choices to select
- Lookup cannot be mapped
- User fields cannot be mapped
- Attachment fields in Quickbase cannot be mapped to a Document Viewer field in FastField
- Rating fields are not mapped to Quickbase when the N/A option is selected