Stop writing glue code for every project.
Connect Formio forms to Camunda 8 with a visual mapper, then run tasks, watch every case live and keep an audit trail, in one product.
| Ref | Process | Current step | Started | Status |
|---|---|---|---|---|
| #1042 | Patient admission | Doctor assignment | 14:32:07 | Running |
| #1041 | Student enrolment | Completed | 14:20:45 | Done |
| #1040 | Loan application | Credit check | 14:14:30 | Incident |
| #1039 | Leave request | Manager approval | 13:58:12 | Due today |
Sample data
Every Formio + Camunda project starts the same broken way.
2 to 5 days of custom glue code per project: webhook endpoints, variable serialisation, type coercion, error handling, written by hand every time.
// Manual webhook handler, written from scratch again
@PostMapping("/webhook/formio")
public ResponseEntity<?> handle(
@RequestBody Map<String, Object> payload) {
// pray the field names match...
String name = (String) payload.get("patient_name");
// snake_case or camelCase this week?
Object raw = payload.get("doctor_id");
Long doctorId = Long.parseLong(raw.toString());
// TODO: null, type errors, missing fields...
// TODO: retries, error notification...
// TODO: version pinning when the BPMN changes...
}3 days later: the wrong process version was started. No audit trail. No alert.
| Formio field | Camunda variable | Match | Transform | OK |
|---|---|---|---|---|
| patient_name | patientName | 100% | — | |
| diagnosis_code | diagnosisCode | 100% | — | |
| doctor_id | doctorId | 100% | toNumber | |
| admissionDt | admissionDate | 88% | toISO | |
| priority_lvl | priority | 91% | — |
Visual mapper, version pinning, instant failure alerts. Setup: 45 minutes.
Design it. Run it. See every case.
The whole lifecycle of a workflow, in one product.
Draw it, then deploy it.BPMN workflows, Formio forms and DMN decisions are built in the browser, with drafts, version history and an editor lock, and deployed to Camunda 8 in one click.
Every task in one inbox.Tasks sorted into deadline lanes: Late, Due today, This week, To claim. Each opens with its form, its context and the history of the case.
Every case, live.Instances move on their real BPMN diagram, incidents surface with a one-click retry, and the slowest steps light up on the heatmap.
Every case leaves a trail.
Every variable that enters a process, every change and every decision is recorded, so “who did this, and when?” takes a minute to answer.
See the audit trail- 00:00FORM_SUBMITapplicant_income=84000, loan_amount=320000
- 00:03TASK_ASSIGNEDassignee=underwriter
- 02:41VAR_UPDATEDrisk_score=72, ltv_ratio=0.81
- 02:43FORM_PRE_FILLEDdecision_form ← risk_score, ltv_ratio
- 03:10TASK_COMPLETEdecision=APPROVED
- 03:10VAR_PERSISTEDdecision → Camunda 8 context
6 entries · 3 m 10 s · 7 variables tracked
Sample data
What you will forget.
Bridge is not one more screen to learn. It replaces the daily frictions of running Camunda 8 with one place that already knows your processes, your forms and your people.
One workspace
Jumping between Operate, Tasklist, the Modeler and spreadsheets to follow one process.
Monitor, tasks, design, analytics and admin live in one sidebar, and each person only sees what their role allows.
Task Inbox
Re-typing a long form because the tab closed or the session dropped.
What you type is saved as a draft and restored when the form opens again. Later forms are prefilled from earlier steps.
Workload
Emailing around to find out who is holding a task, and who is free.
Every open task sits under the person who holds it, unassigned first. Dispatchers assign in a click.
Heatmap & SLA
Finding out why a process is slow after the deadline was missed.
The heatmap shows the slowest steps, and the SLA tracker warns you at a threshold you set.
Token Replay
Digging through logs to rebuild what happened to one case.
Replay any instance step by step: who did what, how long it took, and the variables at each step.
Variable Mapper
Days of hand-written glue code between each form and each process.
Map form fields to process variables visually, with automatic mapping, and test it without writing a webhook.
Still on Camunda 7? Move to 8 one process at a time.
Bridge sits between your forms and the engine, so changing the engine underneath does not mean redesigning your forms or your task experience. Camunda 7 history stays readable in a Historic Archive.
How the migration worksCamunda 7
Java API · History DB
Camunda 8
Zeebe · Cloud-native
Built for every team around the process.
Pick your role or your sector to see what Bridge changes for you.
By role
Questions technical leads ask first
Do we need to rebuild our BPMN diagrams or forms?
No. Bridge sits alongside your existing Formio forms and Camunda process definitions. You connect them through the visual mapper; nothing about your BPMN diagrams or form schemas needs to change.
Does this replace Camunda Tasklist and Operate?
For day-to-day use, yes: monitoring, task completion and analytics all happen inside Bridge. Camunda's own tools stay available for deep engine-level administration when your team needs them.
We're still on Camunda 7. Is that a blocker?
No, it's a reason to start now. Bridge supports an incremental, process-by-process migration path to Camunda 8, so you are not stuck doing a single risky cutover.
Can we try it before committing?
Yes. Request a free trial and test Bridge on your own, or book a live 30-minute demo. The usual next step is a scoped pilot on a single workflow before a wider rollout.
How is Bridge deployed?
Bridge runs in your own infrastructure, so process and form data stay under your control. Tell us your constraints (on-premise, private cloud) when you request a trial and we will confirm the setup that fits.
Ready to ship your first integration this week?
Test it on your own, or book a free 30-minute live demo: a real Formio submission starting a Camunda 8 process, mapped, monitored and audited, in under an hour.