Auto-publish new WordPress posts to Pinterest with PinBridge

This workflow automatically turns WordPress posts into Pinterest publish jobs using PinBridge as the publishing layer. It is designed for bloggers, publishers, affiliate sites, and content teams that already publish to WordPress and want a repeatable way to distribute that content to Pinterest without manually copying titles, descriptions, links, and images every time a post goes live. The workflow starts by querying PinBridge for existing Pins, aggregates their titles, then fetches published WordPress posts from the WordPress REST API. From there, it filters out posts that do not have featured media and skips posts whose titles already exist in PinBridge, which gives the workflow a simple duplicate-protection layer. For posts that pass that filter, the workflow builds a publish-ready payload, validates the required fields, downloads the featured image, uploads that image through PinBridge, submits the Pinterest publish job, and returns a structured success or invalid result. The goal is not just to publish. The goal is to publish in a way that is operationally clean, easy to review, and safer to run repeatedly. --- What problem this workflow solves A common WordPress-to-Pinterest workflow usually looks like this: - a post is published in WordPress - the title already exists - the link already exists - the featured image already exists - but Pinterest publishing still happens manually That manual step creates several problems: - publishing is inconsistent - some posts are missed completely - metadata gets copied differently every time - duplicate publishing becomes easy when you rerun the process - scaling beyond a handful of posts becomes annoying This workflow solves that by turning WordPress into the content source and PinBridge into the publishing layer, with n8n sitting in the middle as the orchestrator. When you run the workflow, it does the following: 1. Lists existing Pins from PinBridge 2. Aggregates their titles into a reference list 3. Fetches published posts from WordPress 4. Skips posts that do not have featured media 5. Skips posts whose titles already exist in PinBridge 6. Builds a Pinterest-ready payload from the post 7. Validates that the required fields are present 8. Downloads the featured image 9. Uploads the image to PinBridge 10. Submits the Pin publish job through PinBridge 11. Returns a success or invalid result That gives you a practical operational loop with a built-in first layer of duplicate protection. --- Why PinBridge is used here This workflow is intentionally built around PinBridge instead of direct Pinterest API plumbing. PinBridge is the publishing layer in the middle. In this workflow: - WordPress is the content source - n8n is the orchestration layer - PinBridge is the publishing layer that receives the image asset and submits the Pinterest publish job That separation keeps the workflow focused on the things n8n should be doing: - reading content from the CMS - filtering and validating data - checking whether a post appears to have already been published - downloading media - passing a clean payload into the publishing layer - handling the returned job submission result instead of forcing the workflow to become a full Pinterest delivery implementation. --- What this workflow does differently from the simpler version This updated version adds an important protection step before WordPress posts are processed: Existing Pin title check The workflow starts with the List pins node, which loads existing Pins from PinBridge. Then the Published Titles aggregate node collects those titles into a single list. Later, inside Skip Posts Without Featured Media, the workflow checks two things at once: - the WordPress post has featured media - the cleaned WordPress post title is not already present in the aggregated PinBridge title list That means this workflow is no longer just “publish latest posts.” It is now closer to: publish posts that have images and do not already appear to be published to Pinterest