All work
Browser extension · 2026

PinFlow

A one-click Pinterest publisher (Chrome MV3) — captures media from any site and creates real pins via DOM automation reverse-engineered from recorded traffic.

Type
Browser extension
Year
2026
Stack
JavaScript · Manifest V3 · DOM automation
JavaScriptManifest V3DOM automationHAR analysisChrome Extension APIs
PinFlow
The problem

Publishing images to Pinterest in volume is slow, repetitive, and error-prone — and Pinterest has no public API for creating pins, so every publisher has to drive the web UI like a human would.

Constraints
  • 01

    No official API for pin creation — the DOM is the only interface.

  • 02

    Pinterest runs A/B tests and changes its UI without notice.

  • 03

    Automation that moves too fast or too uniformly gets flagged.

What was built
  1. 01

    A Manifest V3 extension: right-click any image or video on any site to queue it, then publish as a properly created pin with destination URL, title, description, and hashtags from reusable profiles.

  2. 02

    The pin-builder flow was reverse-engineered from recorded HAR traffic and documented in an engineering spec (selectors, flows, failure modes).

  3. 03

    A Humanizer module simulates realistic typing delays, word pauses, and natural mouse movement.

  4. 04

    Publish Guardian confirms success from 4 independent DOM signals before closing a tab; MutationObserver-based waits replace fixed timeouts.

Engineering decisions

Fallback selector chains + remote config

Every field has a prioritized selector list; if Pinterest's A/B tests change the DOM, the next selector is tried automatically. Selectors are also synced from a remote JSON config every 6 hours, so UI changes don't require re-publishing the extension.

Batch queue with locks

Web Locks API guards the publish queue against concurrent triggers, and batch mode publishes up to 10 items sequentially instead of racing them.

Result
  • ✓

    Full build from reverse engineering to shipped extension, with engineering spec and case study committed alongside the code.

  • ✓

    The recorded HAR analysis files are included in the repo as evidence of the method (verified to contain no credentials or session data).