Workflow automation / Workflow

iPermit

From a new job to a city-ready permit payload. One clear path through a complex process.

Workflow architecture · Dublin pilot

Animated workflow walkthrough - illustrative data~72 seconds · silent

Explore a path

IPERMIT / PROCESS EXPLORERFictional job · DEMO-1042

DEMO-1042 →

ZohoJob intake

→

n8nPrepare + route

→

UiPathBrowser automation

NEW JOB / ZOHO API

A permit starts here.

Job: DEMO-1042
Company: Example Contractor
City: Dublin
Project: Illustrative improvement

Ready for intake

01 / 08

A job arrives

A fictional Zoho job enters one shared intake. Keep the source information together before preparing it for the city.

Reduced motion is on. Use the scene controls to explore the complete story at your own pace.

Read the complete step-by-step story

A job arrives
A fictional Zoho job enters one shared intake. Keep the source information together before preparing it for the city.
Make the data usable
Split the job from the incoming batch, trim extra spaces, and normalize city and company fields.
Validate and enrich
Check company information, identify the city, then retrieve and merge contractor details. Required fields must be complete.
One router. The right city.
The parent workflow routes this supported pilot job to Dublin. Other or inactive city routes go to review.
Prepare the Dublin payload
The child workflow applies city configuration, maps permit types and fees, and assembles the payload and PDF-fill request.
Ready for a handoff
A readiness check separates incomplete jobs for review. A complete job becomes a prepared UiPath queue item.
UiPath takes the browser work
Conceptual downstream scene: UiPath uses the prepared data for browser/UI automation. The screenshots establish preparation, not a completed run.
Designed to grow city by city
Keep the shared intake. Add city-specific child workflows as future expansion. Dublin is the pilot shown in the evidence.

BEHIND THE BUILD

From the problem
to the system.

01 / THE PROBLEM

What needed to work better.

Permit work starts with scattered job and contractor information. Each city needs a different set of fields, formats, and checks.

02 / AARON'S CONTRIBUTION

Design the connection.

Aaron designed the parent intake and city-router workflow, the Dublin child workflow, and the data preparation architecture for a UiPath handoff.

03 / THE SOLUTION

A deliberate flow.

n8n receives Zoho API data, normalizes job information, validates the company, enriches contractor details, and routes a complete payload to the city-specific workflow. Review branches catch incomplete information and unsupported routes.

04 / WHAT THE EVIDENCE SHOWS

Parent intake and city-router workflows are documented in the supplied screenshots.
Dublin-specific mapping, PDF-fill preparation, and a prepared UiPath queue item are visible.
Additional city workflows can extend the architecture; Dublin is the only city shown.

Evidence & context

The screenshots document payload and queue-item preparation. They do not independently establish queue submission, a completed UiPath run, or production permit processing.

Content reviewed 2026-09-05

Explore the architecture & technologies