Title: IntakeFlow – Client Intake, Multi-Step Forms & Secure Document Collection Author: iakdev Published: 7 de junio de 2026 Last modified: 15 de junio de 2026 --- Buscar plugins ![](https://ps.w.org/xpressui-bridge/assets/banner-772x250.png?rev=3563894) ![](https://ps.w.org/xpressui-bridge/assets/icon-256x256.png?rev=3573106) # IntakeFlow – Client Intake, Multi-Step Forms & Secure Document Collection Por [iakdev](https://profiles.wordpress.org/iakpressteam/) [Descargar](https://downloads.wordpress.org/plugin/xpressui-bridge.1.0.96.zip) * [Detalles](https://es-mx.wordpress.org/plugins/xpressui-bridge/#description) * [Opiniones](https://es-mx.wordpress.org/plugins/xpressui-bridge/#reviews) * [Instalación](https://es-mx.wordpress.org/plugins/xpressui-bridge/#installation) * [Desarrollo](https://es-mx.wordpress.org/plugins/xpressui-bridge/#developers) [Soporte](https://wordpress.org/support/plugin/xpressui-bridge/) ## Descripción **IntakeFlow** lets you embed multi-step forms and document-intake workflows built with the [IntakeFlow console](https://intakeflow.dev/) 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:// api.intakeflow.dev` (or your custom console URL) to sync project schemas, download workflows, and verify subscription status. * Outbound sync requests include an API Token (`X-Api-Token`) generated from your IntakeFlow dashboard. * 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. 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`. ## Capturas [⌊The submission list with status badges, project filter, and row actions.⌉⌊The submission list with status badges, project filter, and row actions.⌉[ The submission list with status badges, project filter, and row actions. [⌊The submission detail view with payload fields, status workflow, and assignment panel.⌉⌊The submission detail view with payload fields, status workflow, and assignment panel.⌉[ The submission detail view with payload fields, status workflow, and assignment panel. [⌊The Manage Workflows page showing installed packages and project settings.⌉⌊The Manage Workflows page showing installed packages and project settings.⌉[ The Manage Workflows page showing installed packages and project settings. [⌊A workflow embedded in a page using the [xpressui] shortcode — inline rendering, no iframe.⌉⌊A workflow embedded in a page using the [xpressui] shortcode — inline rendering, no iframe.⌉[ A workflow embedded in a page using the [xpressui] shortcode — inline rendering, no iframe. ## Instalación 1. Download the plugin `.zip` from the WordPress Plugin Directory or from [intakeflow.dev](https://intakeflow.dev/). 2. In your WordPress dashboard, go to **Plugins › Add New › Upload Plugin**, then select the downloaded `.zip` file and click **Install Now**. 3. Click **Activate Plugin**. 4. In your WordPress dashboard, go to **Submissions › Workflows** and enter your API Token in the **Console Sync** section (generate it in your Console under Profile API Tokens). 5. Click **Load from Console** and then **Sync** next to the workflow you want to import. 6. Insert `[xpressui id="your-project-slug"]` in any page or post to embed the form. ## Preguntas frecuentes ### How do I import my workflows from the Console? Connect your WordPress site to the IntakeFlow Console using your API Token in the** Console Sync** section of the Workflows admin page. You can then sync all your custom workflows with a single click. ### What does the [xpressui] shortcode accept? * `id` (required) — the project slug, matching the uploaded package folder name. Example: `[xpressui id="loan-application"]` ### Where are submissions stored? Submissions are stored as private WordPress posts of the custom post type `xpressui_submission`, directly in your site’s database. No data is sent to external servers. ### Can I export or delete submissions? Submissions can be deleted directly from the wp-admin list (Trash Delete permanently). When a submission is permanently deleted, its uploaded files are deleted too. Export and bulk actions are on the roadmap. ### Does the plugin send emails? Only if you configure a notification email address for a project under **Submissions› Workflows › Project Settings**. The plugin uses WordPress’s built-in `wp_mail()` function, so it respects any SMTP plugin you have installed. ### What file types can submitters upload? File uploads are handled by `media_handle_upload()`, which respects the WordPress file type allow-list configured under **Settings › Media**. By default, this includes common document, image, and archive formats. ### Is the REST endpoint publicly accessible? Yes — the `/wp-json/xpressui/v1/submit` endpoint accepts POST requests without authentication. This is intentional: form submissions originate from visitors who are not logged in. Each submission is stored as a private post and is only visible to authorised users inside wp-admin. ### What happens to uploaded files when a submission is deleted? Uploaded files are stored as WordPress media attachments. When a submission is permanently deleted, the plugin also permanently deletes the files linked to that submission. Trashing a submission does not immediately remove the files; permanent deletion does. ### What happens if I reinstall or delete the plugin? Workflow packs can be re-synced without deleting submissions. If you delete and reinstall the plugin itself, submissions are preserved by default. To permanently remove submission data during uninstall, define the `XPRESSUI_BRIDGE_DELETE_SUBMISSIONS_ON_UNINSTALL` constant and set it to `true` before deleting the plugin. ### Does the plugin call any external API at runtime? No. Once a workflow package is installed, the plugin operates entirely within your WordPress site. The IntakeFlow console at intakeflow.dev is only used to design and export packages — it is not contacted during form rendering or submission processing. ## Reseñas No hay reseñas para este plugin. ## Colaboradores y desarrolladores Este software es de código abierto. Las siguientes personas han contribuido a este plugin. Colaboradores * [ iakdev ](https://profiles.wordpress.org/iakpressteam/) [Traduce “IntakeFlow – Client Intake, Multi-Step Forms & Secure Document Collection” a tu idioma.](https://translate.wordpress.org/projects/wp-plugins/xpressui-bridge) ### ¿Interesado en el desarrollo? [Revisa el código](https://plugins.trac.wordpress.org/browser/xpressui-bridge/), echa un vistazo al [repositorio SVN](https://plugins.svn.wordpress.org/xpressui-bridge/) o suscríbete al [registro de desarrollo](https://plugins.trac.wordpress.org/log/xpressui-bridge/) por [RSS](https://plugins.trac.wordpress.org/log/xpressui-bridge/?limit=100&mode=stop_on_copy&format=rss). ## Registro de cambios #### 1.0.96 * Use secure transient database storage for admin notices instead of raw query parameters to pass Plugin Check. #### 1.0.95 * Rename plugin to IntakeFlow – Client Intake, Multi-Step Forms & Secure Document Collection. * Remove manual ZIP upload feature in favor of secure API Console Sync. #### 1.0.94 * SaaS migration to unified standalone wordpress plugin with API token connection. #### 1.0.93 * Frame style: new appearance option (Card / Plain) to drop the form’s card frame and inherit the host theme’s container, avoiding a double frame on themes that already wrap content in a card. * Use the full plugin name “Multi-Step Forms & Client Document Intake – XPressUI Bridge” consistently with the header, description and wordpress.org listing. * Packaging: exclude .gitattributes from the distributed ZIP (hidden files are not permitted on WordPress.org). #### 1.0.86 * Keep the plugin name “XPressUI Bridge” consistent across the plugin header, description and admin UI (menu, labels) to match the wordpress.org listing and slug. #### 1.0.85 * Rename the product from XPressUI to IntakeFlow in metadata and the admin UI; regenerate the translation template (POT). * Restore print-only / download-only workflow settings support. * Fix the mobile capture dialog (close on session failure, scope the dialog lookup to the form). * Harden workflow ZIP validation and escape shortcode output with wp_kses. #### 1.0.83 * Remove SVG from the workflow ZIP allowed-extensions list; SVG files can embed JavaScript and are therefore code-like assets not permitted in user-uploaded packages. * Remove bundled shortcode-example.php from the document-intake starter workflow to prevent executable code files from being written to the uploads directory on first install. * Rebuild the bundled light runtime from the included xpressui-src sources during packaging. * Include readable runtime sources in the WordPress.org package while excluding generated dist files and dependency folders. #### 1.0.81 * Fix xpressui-src/package.json build scripts: remove prebuild/build:css steps that required dev-only files; npm run build now correctly builds the light runtime only. #### 1.0.80 * Update plugin site URL to https://intakeflow.dev/. #### 1.0.79 * Sanitize uploaded file MIME types with sanitize_mime_type() in addition to sanitize_file_name() for file names. * Fix field label resolution for camelCase field names (e.g. primaryDocument) in notification emails and admin preview. * Store signature field values as WordPress media attachments; render URL-based signatures in emails and admin preview. * Improve admin submission file display: image thumbnails (100×75 px grid) and document list with icons and links. * Compiled PHP templates: eliminate non-WordPress (standalone) branches at compile time; wrap inline CSS with phpcs annotations. * Bundled XPressUI light runtime updated to 1.0.14. #### 1.0.77 * Cleaned legacy Pro-related strings from the free package. * Clarified public messaging around the free bridge and the separate Pro add-on. * Internal cleanup to keep the WordPress.org build focused on the free operational bridge. #### 1.0.70 * Custom workflow ZIP upload is available in the free plugin. * Removed license and Pro-only gating from the WordPress.org build. * Packaging now keeps the readable `xpressui-src/` sources while excluding dependency folders from release archives. #### 1.0.21 * Native inline rendering: the [xpressui] shortcode now renders the form directly inside the WordPress page without an iframe. * Bundled XPressUI light runtime served from plugin assets — no JavaScript loaded from uploads or external URLs. * Form CSS scoped to the embed container to avoid conflicts with the active WordPress theme. * Runtime and init script enqueued via wp_enqueue_script for correct dependency ordering and deduplication. #### 1.0.0 * Initial release. * Custom post type for submissions with status workflow (New, In review, Done). * Status history log per submission. * Team assignment and My Queue page. * Project Inbox overview page. * [xpressui] shortcode embed with bundled runtime. * REST endpoint for receiving submissions and file uploads. * Per-project email notifications via wp_mail(). * Per-project post-submit redirect URL. * Manage Workflows page with ZIP upload and project settings. ## Meta * Versión **1.0.96** * Última actualización **hace 11 horas** * Instalaciones activas **Menos de 10** * Versión de WordPress ** 6.0 o superior ** * Probado hasta **7.0** * Versión de PHP ** 8.0 o superior ** * Idioma * [English (US)](https://wordpress.org/plugins/xpressui-bridge/) * Etiquetas: * [client portal](https://es-mx.wordpress.org/plugins/tags/client-portal/)[document collection](https://es-mx.wordpress.org/plugins/tags/document-collection/) [file upload](https://es-mx.wordpress.org/plugins/tags/file-upload/)[intake form](https://es-mx.wordpress.org/plugins/tags/intake-form/) [Multi-Step Form](https://es-mx.wordpress.org/plugins/tags/multi-step-form/) * [Vista avanzada](https://es-mx.wordpress.org/plugins/xpressui-bridge/advanced/) ## Valoraciones Aún no se han enviado valoraciones. [Your review](https://wordpress.org/support/plugin/xpressui-bridge/reviews/#new-post) [Ver todas las valoraciones](https://wordpress.org/support/plugin/xpressui-bridge/reviews/) ## Colaboradores * [ iakdev ](https://profiles.wordpress.org/iakpressteam/) ## Soporte ¿Tienes algo que decir? ¿Necesitas ayuda? [Ver el foro de soporte](https://wordpress.org/support/plugin/xpressui-bridge/)