7
Integrations I built the setup for
- Zoho
- Salesforce
- HubSpot
- Facebook Lead Ads
- WhatsApp Business
- AWS S3
- Google Cloud Storage
One integration dialog
- Migration style
- Incremental (modules stayed online)
- Integrations on it
- 7: Zoho, Salesforce, HubSpot, Facebook Lead Ads, WhatsApp Business, S3, GCS
What it does
Ops teams use the admin web surface for bulk ingestion, allocations, API config, and CRM integrations. Those flows had grown as one-off views: parsing, column mapping, validation, loading states, and error handling were re-implemented per page. Forms lost state on accidental dismissals; wizards re-fetched the same org metadata on every step.
I replaced that with shared import, validation and setup components, and moved views over one module at a time so the admin app stayed usable throughout.
Scope note: Runo also runs a separate, older admin module in Vue.js, managed independently: this migration is the Flutter-web admin surface specifically, not a rewrite of that Vue codebase. The bulk upload/delete flows for customers and lead allocations run their validation client-side, backed by AWS Lambda functions rather than a monolith endpoint, chosen for cost, isolation, and reliability on spiky admin traffic. API keys for the downstream CRM/lead-source integrations (Meta, WhatsApp Business API, HubSpot, Zoho, Salesforce) are managed through this same admin surface.
The constraints, design decisions and outcomes are in the full case study.
What it demonstrates
- Platform migration under continuous operational use
- Turning a page-by-page pattern into one flow that every new integration starts from
- Treating form-state loss as a product bug, not a UX nicety


