IntakeFlow – Client Intake, Multi-Step Forms & Secure Document Collection
IntakeFlow – Client Intake, Multi-Step Forms & Secure Document Collection

IntakeFlow – Client Intake, Multi-Step Forms & Secure Document Collection

0/5 (0 ratings) — active installs Updated Jun 21, 2026
The submission list with status badges, project filter, and row actions.

The submission list with status badges, project filter, and row actions.

IntakeFlow lets you embed multi-step forms and document-intake workflows built with the IntakeFlow console directly in your WordPress pages.

Export a workflow package from the IntakeFlow console as a .zip file, upload it to WordPress in one click, then embed it anywhere using the [xpressui] shortcode. The form renders natively inside your page — no iframe, no external dependencies at runtime. Submissions are stored as private posts in a dedicated wp-admin inbox, directly in your site’s database.

If you need advanced field types, direct Console Sync, or cloud workflow management, those are available by connecting the plugin to your IntakeFlow SaaS account at intakeflow.dev.

Key features

  • One-click installation — upload the exported .zip file from the IntakeFlow console directly inside wp-admin.
  • Shortcode embed[xpressui id="your-project-slug"] works in any page, post, or block-editor paragraph block. The form renders inline, inheriting your theme’s page layout.
  • Submission inbox — all submissions land in a private wp-admin post list with status badges, filtering by project, status, and assignee, and detailed review metaboxes.
  • Status workflow — mark submissions New, In review, or Done from the list or the detail view. Every status change is recorded in a per-submission history log.
  • Team assignment — assign any WordPress user to a submission. The My Queue page shows each reviewer their personal backlog at a glance.
  • Email notifications — configure a notification address per project and receive a plain-text summary email the moment a new submission arrives.
  • Post-submit redirect — optionally redirect the visitor to a thank-you page after a successful submission. Configured per project from wp-admin.
  • File uploads — uploaded files are stored as WordPress media attachments and linked back to their submission.
  • REST API endpoint — submissions are received via a standard WordPress REST route (POST /wp-json/xpressui/v1/submit). No extra server configuration required.
  • Bundled runtime — the XPressUI standard runtime is bundled inside the plugin. No JavaScript is loaded from the uploads directory or external CDNs.

Who is this for?

Businesses and developers who use the IntakeFlow console to build document-intake or multi-step application forms and want to manage the collected data inside their existing WordPress environment without an external SaaS inbox.

The Ultimate Alternative for Team Intake

Unlike generic form builders (like Contact Form 7, WPForms, or Gravity Forms), IntakeFlow is built specifically for client intake and document collection.
* No paywall on team inbox: Assign submissions to specific WordPress users without upgrading to expensive Enterprise plans (unlike JotForm or Typeform).
* No bloated iframes: Forms render natively in clean, fast HTML/JS, inheriting your active theme’s styling.
* 100% GDPR-compliant: Your submissions and uploaded files are stored entirely in your local database. No data is stored on third-party servers.

External Services

This plugin can optionally connect to the IntakeFlow SaaS platform (hosted at intakeflow.dev) to enable real-time cloud synchronization, advanced field types, and centralized workflow management.

When connected to IntakeFlow:
* The plugin makes outbound HTTP requests to https://app.intakeflow.dev (or the custom console URL you configure under Settings) to verify your subscription status, sync project schemas, and download workflow packages.
* Outbound requests include an API Token (X-Api-Token) generated from your IntakeFlow dashboard so the service can identify your account.
* When you connect an account, the plugin sends the token to validate it and to look up the owner of the account.
* When you use the Form Importer with an account connected, the structure of the imported Contact Form 7 / Gravity Forms form (field names, labels and types — not visitor submissions) is sent to the console to create the corresponding workflow, which is then downloaded back to this site.
* No visitor or submission data is transmitted to the IntakeFlow console unless specifically configured by the administrator for cloud backup or webhook routing.

A connection is required to sync custom workflows. The bundled starter workflow functions fully offline without a connection.

Use of the IntakeFlow service is governed by its terms and privacy policy:
* Terms of Service: https://intakeflow.dev/terms
* Privacy Policy: https://intakeflow.dev/privacy

The bundled XPressUI standard runtime (JavaScript) is served directly from the plugin directory — it is never loaded from a CDN or external URL.

Privacy

This plugin stores data submitted by your site visitors (form field values, uploaded files, and metadata such as submission timestamps). All data is stored locally in your WordPress database and media library. No data is transmitted to external servers. When a submission is permanently deleted, its linked uploaded files are deleted as well.

Users may request access to or deletion of their personal data. This plugin integrates with the WordPress Personal Data tools (Tools › Erase Personal Data and Tools › Export Personal Data).

For full details on what data is collected and how to manage it, refer to your site’s privacy policy.

Source Code

The full source code for this plugin is available at:
https://github.com/lybaba/xpressui-wordpress-bridge

Bundled JavaScript runtime

The file runtime/xpressui-*.umd.js is the compiled output of the XPressUI library. The unminified TypeScript source files used to produce this bundle are included in the xpressui-src/ directory of this plugin.

To rebuild the runtime from those sources:

  1. Navigate to the source directory: cd xpressui-src
  2. Install dependencies: npm install
  3. Build the runtime: npm run build
  4. The output file is produced in xpressui-src/dist/xpressui-*.umd.js.