§ INTEGRATIONS
What I’ve wired together.
Integrations across client ecommerce, my own products and AI tooling. Pick one to see what it connects, what moves through it, and how it runs.
- game feeds, nightly
- 14
- marketing platforms
- 3
- licensed metadata
- IGDB
- server built for AI agents
- MCP
14 NZ game shops, one catalogue
FIG. I-01 · STORE FEED INGESTION
DATA FLOW
- 14 SHOPSnightly feeds
- ADAPTERSone per store
- RAWappend-only
- CANONICALpg_trgm matched
- RELEASE PAGESprice + stock
A product is only marked removed after a complete read of that store
- shop integrations
- 14
- price and stock refresh
- Nightly
- removal threshold that halts a run
- 20%
CONNECTS
14 NZ shops’ storefronts, into Kiwi Game Bazaar.
WHAT FLOWS
Prices, stock and listings for physical games, matched to one canonical record per release.
HOW IT RUNS
Nightly, robots.txt-respecting polls through a per-store adapter. Stores can opt out, and the raw layer is append-only.
Licensed game metadata from IGDB
FIG. I-02 · METADATA LICENSING
DATA FLOW
- IGDBgame database
- LICENSED IMPORTsigned agreement
- CANONICALone record per release
- RELEASE PAGESSSR + schema.org
Signed data-licensing agreement with IGDB
- signed licence
- IGDB
- server-rendered release pages
- SSR
- structured data
- schema.org
CONNECTS
IGDB’s game database and Kiwi Game Bazaar’s canonical release records.
WHAT FLOWS
Game metadata for filling gaps in the canonical records, and cover art.
HOW IT RUNS
Imported under a signed licence, then rendered server-side with schema.org structured data so search engines can read every release.
Email & SMS consent into Dotdigital
FIG. I-03 · MARKETING-CONSENT MAPPING
DATA FLOW
- CLIENT SITEits own consent fields
- CONSENT MAPPERwritten per client
- DOTDIGITALemail + SMS consent
CONNECTS
Client ecommerce sites and Dotdigital’s email and SMS marketing platform.
WHAT FLOWS
Contacts and their marketing-consent status for email and for SMS.
HOW IT RUNS
Consent-mapping logic written per client, because every site recorded consent differently, and reworked as Dotdigital’s API evolved.
ERP, POS and inventory sync
FIG. I-04 · COMMERCE SYSTEMS SYNC
DATA FLOW
- ERP / POSclient system of record
- INTEGRATIONmapped field by field
- STOREFRONTproducts + stock
- ORDERSback to the ERP
Real field names are confirmed against the client system before anything is built
CONNECTS
Client ecommerce sites and their ERP, POS and inventory systems.
WHAT FLOWS
Products, stock levels and orders, in both directions.
HOW IT RUNS
Client-specific integration logic, with field mappings checked against what the system actually sends.
Bloomreach & Mailjet
FIG. I-05 · MARKETING PLATFORM FEEDS
DATA FLOW
- STOREFRONTclient ecommerce
- INTEGRATIONper platform
- BLOOMREACHmarketing platform
- MAILJETmarketing platform
- marketing platforms, with Dotdigital
- 3
- of client integrations
- 5 yrs
CONNECTS
Client storefronts with Bloomreach and Mailjet.
WHAT FLOWS
Customer and catalogue feeds to Bloomreach, and client-specific data for each platform, set up per client.
HOW IT RUNS
Platform-specific integrations, with discrepancies between client data and each platform investigated and traced.
Legacy sites onto new platforms
FIG. I-06 · DATA MIGRATION
DATA FLOW
- LEGACY SITEthe client’s old site
- STAGING COPYrehearsal on live data
- RECONCILErecord totals checked
- NEW PLATFORMcutover
Every migration rehearsed on a staging copy of live data first
CONNECTS
Clients’ legacy sites and the newer platforms replacing them.
WHAT FLOWS
Products, customers and orders.
HOW IT RUNS
Rehearsed on a staging copy of live data, with record totals reconciled before cutover, which caught missing fields and failing orders ahead of go-live.
Live brackets on every screen
FIG. I-07 · REAL-TIME BROADCASTING
DATA FLOW
- QR SIGNUPplayers’ phones
- SNAKE DRAFTskill-weighted teams
- REVERBbroadcast events
- SCREENSbracket + admin
CONNECTS
Players’ phones, the admin portal and the displays at a live weekly gaming event.
WHAT FLOWS
Signups, balanced team draws and bracket results, live as they happen.
HOW IT RUNS
Laravel Reverb broadcasting to Echo clients, deployed on Laravel Cloud with a custom domain.
MCP: admin actions as agent tools
FIG. I-08 · AGENT TOOLING
DATA FLOW
- CLAUDEAI agent
- MCP SERVERtyped, guarded tools
- ADMIN ACTIONSConsoleCore
- NIGHTWATCHproduction health
Agents act through named tools. Merges and deploys still need my approval
CONNECTS
Claude with ConsoleCore’s admin and with Nightwatch monitoring for Kiwi Game Bazaar.
WHAT FLOWS
Admin actions as tools an agent can call, and production health for a daily automated check.
HOW IT RUNS
An MCP server built into the tournament platform, and Nightwatch added as an MCP connector.
Used music stock, matched to one album
FIG. I-09 · FEEDS TO A CATALOGUE
DATA FLOW
- SHOP FEEDSpublic product feeds
- SIGNED READSWeb Bot Auth
- BARCODE MATCHone album each
- ALBUM CATALOGUEDiscogs CC0 dumps
- barcoded CDs matched one album
- 87%
CONNECTS
NZ music shops’ public product feeds, and the Discogs CC0 data dumps.
WHAT FLOWS
Each shop’s used listings, matched to one album by barcode.
HOW IT RUNS
Reads signed with Web Bot Auth, only after the shop was asked; the album catalogue from the data dumps, never the Discogs API.
Climate data onto a globe, licence-audited
FIG. I-10 · OPEN DATA TO THE GPU
DATA FLOW
- ERA5climate reanalysis
- IBTRACS · CHELSAcyclones · rainfall
- TERRAIN TILESpre-cut, own origin
- PYTHON PIPELINEpandas
- WEBGPU GLOBE39 pins
Station normals are only a check: a count is withheld at a 1.5× disagreement
CONNECTS
Copernicus ERA5 reanalysis, IBTrACS cyclone tracks, CHELSA rainfall and AWS Terrain Tiles.
WHAT FLOWS
Monthly climate fields and terrain, cut for the browser, with day counts for 39 destination pins.
HOW IT RUNS
A Python/pandas pipeline with every dataset licence-audited for commercial use; station normals used only as a check.
§ AT A GLANCE · CLICK TO OPEN









