Use Converted Alteryx Apps

PlaidCloud converts Alteryx analytic app questions into controlled workflow variables. Users can set those variables before a run, then PlaidCloud applies the values to formulas, filters, file paths, conditions, macro parameters, and downstream step settings.

The App Runner Front-End

Converting an Alteryx analytic app (.yxwz) also materializes its interface as a published Panel “App Runner” — a working input form that collects the same values the Alteryx questions did and runs the converted workflow with them. You get this front-end automatically as part of conversion; an app with no input widgets is skipped.

The app’s questions become App Runner widgets: text, numeric, date, check box, radio button, drop-down, list box, tree, file browse, and folder browse. Each widget writes to the workflow variable the converted step reads, so a run from the App Runner drives the same logic as setting the variables by hand. A widget that does not bind to a real workflow variable is shown with a visible note rather than silently collecting a value that goes nowhere — review it and point it at the intended variable.

You can still run the workflow directly by setting its variables, as below; the App Runner is an additional, app-style way in.

Converted Input Types

PlaidCloud converts common Alteryx app controls to typed workflow inputs:

Text boxes become text variables.
Numeric controls become numeric variables.
Date controls become ISO date variables.
Check boxes, radio buttons, drop-downs, list boxes, and trees become controlled choice variables.
File browse controls become Document file variables.
Folder browse controls become Document folder variables.

The converted workflow uses these variables anywhere the Alteryx app used the original question value.

Set Values Before A Run

Before running a converted app workflow:

Open the converted workflow.
Review workflow variables.
Set required text, numeric, date, choice, file, and folder values.
Confirm Document file and folder paths point to the imported dependency location or another approved Document path.
Run the workflow.

For scheduled runs, save the variable values that should be used each time the schedule runs.

Conditions, Warnings, And Errors

Alteryx app conditions and error checks convert to PlaidCloud step conditions. A condition can:

Allow the workflow to continue.
Emit a warning message.
Stop the workflow with a clear error when the app rule calls for it.
Route execution through a different branch.

Use this behavior to preserve app-level validation while running the workflow in PlaidCloud.

File And Folder Inputs

File and folder questions use Document paths:

File inputs select a file from Document.
Folder inputs select a Document folder.
Imported desktop dependencies are stored at the Document path selected during import.
Dynamic input steps can use variables to resolve the final Document path at runtime.

This keeps converted apps portable across users and scheduled runs.

Macro Parameters

When a converted app calls a macro, app variables can feed macro parameters. PlaidCloud passes those values into the generated macro workflow through macro input and control parameter handling.

Concurrent macro runs are isolated, so multiple workflow runs can use the same converted macro without sharing intermediate state.

Validation Checklist

For each converted app, confirm:

Every expected question appears as a workflow variable.
Defaults match the original app where defaults were configured.
Controlled lists contain the expected choices.
File and folder variables point to Document paths.
Conditions produce the expected messages, warnings, or stop behavior.
Output parity passes for the selected variable values.