Docs

Save Dataflow Gen One As Dataflow Gen Two

POST

Query

Field selectionChoose which fields should be included in the response. Learn more
string

Comma-separated response fields to include.

Body

Arguments
stringrequired

The workspace (group) ID of the gen1 dataflow

stringrequired

The object ID of the Gen1 dataflow to save as a native artifact

string

Optional description for the new artifact. If not provided or empty, the description from the source dataflow will be copied. Maximum length: 4000 characters

string

Optional display name for the new artifact. If not provided or empty, the system will generate a name based on the source dataflow name with a suffix like "\_copy1", "\_copy2", etc. to avoid naming conflicts. Maximum length: 200 characters

boolean

Whether to include the refresh schedule from the source dataflow in the migration. If true, attempts to copy the existing schedule to the new artifact in disabled state. If false, the new artifact will be created without a schedule.

string

Optional target workspace ID where the new artifact will be created. If not provided or empty, the new artifact will be created in the same workspace as the source dataflow.

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is
One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.
Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.
Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.