Short answer: Drop the "QuickBase → Query QuickBase Records" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Table ID tableId | string | Required | Table ID |
Fields (IDs) select | string | Optional | Comma-separated field IDs to return |
Filter (query) where | string | Optional | QuickBase query syntax |
{"tableId": "{{trigger.tableId}}","select": "3,6,7,8","where": "{3.EX.'Active'}"}
{"data": [{"3": {"value": "Active"},"6": {"value": "John Doe"},"7": {"value": "john@example.com"}}],"fields": [{"id": 3,"label": "Status"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.