WebApp
Browser pages—forms, wizards, self-service portals, internal tools
WebApp portal flow
Login → content → form → ProcessFlow → CRM
01 Login02 Content03 Form04 WebApp05 CRM
Partner Portal · apps.acme.example
Acme Partner
Sign in to continue
partner@nordic-supply.se
••••••••
Sign in
session issued · secure cookie · tenant acme-ops
Simulated flow — mobile portal on your brand, governed ProcessFlow backend, CRM and DataPool writes
User-facing surfaces
“WebApps are the front door. ProcessFlow is the engine. Everything else connects through it.”
Platform
WebApps — publish experiences backed by governed automation
Forms, portals, webhooks, and document review on your brand—each linked to ProcessFlow so submissions and inbound events run through the same secure automation layer as the rest of the platform.
You design the experience. ProcessFlow handles the logic. The platform handles hosting, versioning, logging, and release control.
Teams usually split this across a frontend for forms, a backend API for business rules, separate webhook endpoints for partners, and another pipeline for file uploads—WebApps collapse that into one publishable surface with one automation backend.
A WebApp can be a customer form, a partner webhook endpoint, a branded portal page, or a document review experience. Each links to ProcessFlow on the same tenant as integrations and Datapools.
- Publish forms, portals, webhooks, and review experiences—without a separate app stack per use case
- One publishable surface with one ProcessFlow backend—faster to ship and fully tenant-scoped
- Browser pages, webhooks, callbacks, WebSockets, and document viewers in one model
- Custom HTML/CSS/JS or schema-driven component library with version-pinned CDN delivery
- Sync for immediacy; async queue stub and SSE for scale and live UX
- JSON, redirect, custom HTTP, session cookies, and HTML response patterns
- Multipart and chunked file uploads; signed download delivery with expiry
- Versioned drafts, explicit publish, execution logs, CSP, and webhook signature support
Production patterns
Portals, webhooks, uploads, and APIs—one surface model behind each.
custom domain
→ redirect welcomeCustomer onboarding portal
Branded form on custom domain → validate in process → create records → redirect to welcome page.
Stripe webhook
signature verifyStripe / payment webhooks
Inbound webhook WebApp → verify signature → update DataPool → return JSON acknowledgment.
multipart upload
OCR · DataPoolInvoice upload & processing
Multipart upload WebApp → OCR and validation in process → store in DataPool → email confirmation.
document viewer
annotationsContract review
Document viewer WebApp → annotations and threaded comments → status tracked for admins.
API WebApp
201 + headersPartner API
API-style WebApp returns 201 with custom headers—external clients integrate without a separate service.
End-to-end flow
Mobile login, portal content, form submit—ProcessFlow pushes to CRM.
A partner signs into a branded portal on a custom domain, reviews onboarding status, completes a vendor intake form, and submits to the Tealfabric WebApp. ProcessFlow validates, enriches from DataPool, calls CRM integrations, and returns a redirect—with full request and execution logs.
WebApp portal flow
Login → content → form → ProcessFlow → CRM
01 Login02 Content03 Form04 WebApp05 CRM
Partner Portal · apps.acme.example
Acme Partner
Sign in to continue
partner@nordic-supply.se
••••••••
Sign in
session issued · secure cookie · tenant acme-ops
Simulated flow — mobile portal on your brand, governed ProcessFlow backend, CRM and DataPool writes
Capabilities
Surfaces without sprawl—backend included, ship with confidence.
Faster to ship than separate frontend and API projects; easier to operate with versioning, publish control, and per-request execution logs.
page · webhook
callback · viewerOne surface model, multiple patterns
Browser pages, webhooks, callbacks, WebSockets, and document viewer experiences.
WebApps are not only mini websites—each type defines how the outside world connects. Customer forms, partner webhook endpoints, branded portal pages, and document review flows share one publishable model.
HTML/CSS/JS
component libraryCustom pages and component library
HTML/CSS/JS or schema-driven UI—speed vs full control.
Build with standard web technologies or ship faster with a declarative component library loaded from CDN. Production teams pin versions for predictable releases.
ProcessFlow
per WebAppEvery surface backed by ProcessFlow
Submissions and webhook payloads become process input—not orphan page logic.
User input or inbound events run through the same secure automation layer as the rest of the platform. Business rules live in the sandbox, not scattered in client-side JavaScript.
sync default
async queue stubSync and async execution
Immediate responses for validation; queue stub for long-running work.
Most form submissions run synchronously and return in the same request. Heavy integrations, LLM calls, and batch jobs queue the real workflow and return a queue ID—the UI polls or streams status.
JSON · redirect
SSE streamingResponse contracts for every caller
JSON, redirect, custom HTTP, session cookies, HTML, and SSE streaming.
Process output becomes the user-facing or machine-facing response. Webhooks get structured acknowledgments; portals redirect after submit; live experiences use Server-Sent Events.
multipart upload
signed downloadFile intake and secure delivery
Multipart and chunked uploads; signed downloads with expiry and limits.
Uploads land in tenant-scoped storage and are available to process steps. Processes publish downloadable files with time-limited, HMAC-protected links—not files emailed or embedded in API responses.
draft · publish
execution logsVersioned publish workflow
Draft vs published, rollback points, and API-managed lifecycle.
Only published versions are public; drafts stay safe. Create, update, publish, and inspect via API for CI/CD pipelines. Every request logs method, status, timing, and linked process execution.
custom domain
CDN assetsOn your brand
Tenant URLs, custom domains, and CDN-delivered static assets.
Each app gets a stable public address when published. Serve on your own hostname with DNS and SSL through platform configuration. Static images, styles, and assets via global CDN URLs.
Surface types
Webhook
Inbound HTTP from payments, CRM events, and partner callbacks
Callback
Structured callback endpoints with JSON-oriented responses
WebSocket
Low-latency, bi-directional scenarios where the model fits
Document viewer
Collaborative document review and annotation experiences
How WebApps connect to the platform
ProcessFlow
User input or webhook payload becomes process input; step output drives the response
Integrations
Processes call configured CRM, email, storage, and API connections
DataPool & tenant data
Processes read and write governed data from the backend
Platform API
API-router WebApps map HTTP paths to process logic or proxy authenticated calls
File storage
Uploads land in tenant-scoped storage and are available to process steps
Public file delivery
Signed links with expiry, download limits, and policy metadata
Security & trust
Tenant isolation
Every WebApp and execution scoped to the organization
Custom security policy (CSP)
Per-app content security rules
Referrer policy
Control how browsers send referrer information
Webhook signature support
Raw body capture for provider signature verification
Signed download links
Time-limited, HMAC-protected file access
Role-gated management
Create, publish, and delete limited to authorized tenant admins
Fits the platform
WebApps are what users and partners interact with. ProcessFlow is business logic. Integrations call external systems. DataPool holds structured data the app reads and writes. Monitor gives cross-platform visibility alongside process and integration logs.
Publish on your brand
See WebApps with ProcessFlow backends, webhooks, and versioned publish.
We walk through portal forms, partner webhooks, file uploads, custom domains, execution logs, and CRM integration steps—on the same runtime as governance and Datapools.