Work
API Integration Hub
Why I built it
Every team was writing the same brittle glue code against the same six APIs. I built the hub so integration became a product decision, not an engineering tax. The moments below are the three interactions that made it stick.
Year
'24
Client
Enterprise (NDA)
Service
Product Strategy & Design
The build, live
Don’t read about it. Click it.
Ambient sync
Off
Manual only — nothing moves without you.
01
Connections you can trust
The toggle is the whole pitch: turn an integration on and watch the status confirm it’s live. No YAML, no deploy, no ticket.
02
Health at a glance
Signal, adoption, cost — the three questions every director asks about an integration. One control, honest answers.
Signal
Adoption
Cost
Weekly signal volume, normalized.
Capture the intent
One field, no form. The system infers the rest from context instead of asking.
Back
Next
03
Setup as a guided flow
The setup wizard shows its tradeoffs inline. Engineers stopped reading docs because the flow was the documentation.
Decision log
What I chose, and what it cost.
Config over code
90% of integrations are the same shape. Making that declarative freed engineers for the weird 10%.
Power users hit the ceiling of the config model and need escape hatches.
Status is a first-class surface
Trust dies in silence. If the hub can’t tell you it’s healthy, nobody builds on it.
Honest status means visible failures — uncomfortable, but correct.
One hub, opinionated defaults
Choice paralysis was the old failure mode. Defaults encode the org’s hard-won lessons.
Some teams felt railroaded until the defaults proved themselves.
Artifacts
