Trigger historical exports for a Cleanroom Flow Run node

post

https://api.habu.com/v1/cleanrooms/{cleanroomId}/cleanroom-flow-runs/{cleanroomFlowRunId}/nodes/{nodeIdentifier}/exports/historical

Re-exports the output of a completed flow run node to its configured export destinations. The node's run must be complete, the question must be analytical, the run must be within the 90 day retention window, and the clean room type and organization must both support historical exports. The export jobs to trigger must be named explicitly, at most 5 per request. Each is queued independently; the response reports the outcome per job.

Path Params

cleanroomId

string

required

The Cleanroom ID to which the flow run belongs

cleanroomFlowRunId

string

required

The Cleanroom Flow Run ID

nodeIdentifier

string

required

Identifier of the node in the flow. You can pass either the node’s UUID (recommended), or the node’s Question Display ID–based label (for example, Q-004368). If the same question is used multiple times as different nodes in the same flow, the label is suffixed with a number (for example, Q-004368_1, Q-004368_2). In those cases, using the UUID is the safest way to avoid ambiguity.

Body Params

exportJobIds

array of strings

required

length between 1 and 5

Export jobs to trigger, between 1 and 5 per request. Each must be an active export job on the node; a paused or unrecognized identifier rejects the whole request, and a repeated identifier is exported once. Destinations are never inferred, so the jobs to run must be named explicitly.

exportJobIds*

Headers

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

Language

Credentials

OAuth2

Loading…

Response

Choose an example:

application/json

200Historical exports queued. Inspect each result for its individual outcome.

400Bad Request - Incorrect syntax or request

401Authorization information was missing or invalid

404The specified resource was not found

500Internal Server Error