Query Execution
Run a query against a connected database service. Query Runner resolves credentials (user or team, layered on the service’s admin config), dispatches the query as a workflow, and streams results to object storage for retrieval.Trigger a Query
POST /v1/collate/apps/queryRunner/trigger accepts query, serviceName, workflowName, and transpile in the request body. Collate enriches the request server-side with the resolved user ID, config ID, connection type, auth type, and a maximum result size before dispatching it.
Optional query parameters:
string
Run using a specific team’s credentials instead of the calling user’s own config.
boolean
default:"false"
Skip the user’s own credentials and use the team config even without an explicit
teamId.Stop a Query
PUT /v1/collate/apps/queryRunner/stop takes a body of { "workflowName": "..." } (required) and cancels the running workflow through the configured execution backend, marking it FAILED.
Fetch Results
GET /v1/collate/apps/queryRunner/results/{workflowId} returns a page of results by workflow ID. It’s paginated with page (default 0) and size (default 50, max 10000).
A companion POST /v1/collate/apps/queryRunner/results/{workflowId} endpoint exists for the execution worker to stream results into storage. It isn’t a client-facing endpoint.