Connect an App Builder Page to a Workflow

What this integration does

RAPTIX can connect an App Builder page to a workflow from the workflow's Start node. When you save the integration, RAPTIX scans the page's supported data-entry widgets and creates or updates a workflow connector on that page. It also links an existing submit button, or creates one when needed.

The deployed connector can:

• collect values from supported data-entry widgets on the page;
• add the configured entity value and file context;
• start the configured workflow;
• upload selected files after the workflow instance is created; and
• show a success or failure message on the page.

This feature changes an App Builder page and is available only to Enterprise organizations.

Transition note: Some current Flow Builder screens still display the technical label Appsmith Integration (HTTP). In this guide, that option is called App Builder Integration. It is not the native /f/:token workflow-form feature.

Before you start

Confirm that:

• your organization has Enterprise access;
• you can edit the workflow in Flow Builder and have approved change authority for the target App Builder page;
• the target page contains only the data-entry widgets that the connector is allowed to submit;
• widget names are stable and unique; and
• the App Builder integration secret has been configured by the platform operator.

Use a test page or duplicate before deploying to a live application. The deployment updates the page connection and can publish unrelated pending edits. Review or clear every unrelated unpublished change before deployment.

Important: Selecting a page is not approval to change it. Use the deployment only through your organization's approved page-change process.

Connect the page

1. Open Applications, locate the workflow, and open it in Flow Builder.
2. Open the workflow's Start node.
3. Select the App Builder Integration start option. In the current product this option is labeled Appsmith Integration (HTTP) — select that.
4. Select Connect, then choose the App Builder workspace, application, and page.
5. Review the page inventory. The current deployment scans supported data-entry widgets on the page, so confirm that the page contains only the fields intended for this workflow.
6. Optionally identify the Entity widget. Its value becomes the business record identifier for the run.
7. If the UI offers a Main document selection, record it for the workflow design, but do not rely on that selection to limit what the current generated connector scans.
8. Enable workflow-variable generation if downstream nodes need named values from the page.
9. Choose whether the page UI requires a signed-in user. Require Authentication is a client-side check in the generated connector, not a complete server-side authorization boundary. Do not expose this integration to untrusted users; use a native Private form for sensitive intake.
10. Select Save Start Properties.

RAPTIX shows whether the connector was created or updated and whether the submit button was created or linked. Open the page in App Builder and refresh it before testing.

Test the integration

1. Confirm that the deployment updated the intended page and that no unrelated unpublished change went live.
2. Enter distinctive test values in every supported data-entry widget on the page.
3. Add a small test file if the page includes a file widget.
4. Select the deployed submit button once.
5. Confirm that the success response includes a workflow instance identifier.
6. In RAPTIX, open the workflow run and verify the submitted values, initiator context, entity identifier, and documents.

Test the signed-in-user behavior and the page's intended audience. For sensitive or external intake, prefer a native workflow form with the appropriate Private or Public setting.

What happens when you redeploy

Saving the same integration again replaces or updates generated connector data instead of requiring a second manual setup. Each redeploy can publish the entire unpublished page. Redeploy when you:

• add, remove, or rename a supported data-entry widget;
• change the entity widget or file-handling design;
• change the workflow name or start configuration;
• change the authentication setting; or
• rotate the App Builder integration secret.

Refresh the App Builder page after every deployment. Do not assume a page already open in another tab has loaded the new configuration.

Security and the integration secret

The App Builder connection uses a credential configured by the platform administrator. Treat the connected page as a trusted deployment and never copy the credential into documentation, screenshots, tickets, logs, or manually maintained page settings.

Do not publish the connected page to an unapproved audience. For external or sensitive intake, use a native Private or Public workflow form reviewed for that purpose.

The integration endpoint rejects requests:

• if the secret is not configured, App Builder integration calls are rejected as unavailable;
• if the secret is missing or incorrect, calls are rejected as forbidden; and
• after the secret changes, every affected App Builder page must be redeployed so its generated connector uses the new value.

Credential validation does not replace user and page access. Require Authentication is one part of the generated page behavior, so keep normal Applications permissions and organizational access controls in place.

Use the current tenant domain and the URLs generated by RAPTIX. Do not hard-code a retired product domain in page scripts.

Native workflow forms at /f/:token use a different security model. Private forms require a signed-in RAPTIX member; public forms use an opaque share token, anti-bot verification, rate limits, and server-side workflow safety checks. They do not depend on the App Builder integration secret. See Private and Public Workflow Forms.

Troubleshooting

No workspaces or pages appear

Confirm Enterprise entitlement and App Builder access. A native Applications workspace is not automatically an App Builder workspace.

The integration saves but the page did not change

Refresh App Builder, confirm that the correct page was selected, and deploy again. Check the success summary for the connector and submit-button status.

The submit button is not linked

Verify that the page has a usable button and that widget names have not changed. Redeploy after correcting the page.

Submission returns unavailable or forbidden

Ask the platform operator to verify the App Builder integration secret. If it was recently set or rotated, redeploy the page.

The workflow starts without expected values

Return to the Start node, inventory every supported data-entry widget on the page, review generated variables, save again, and test with new values.