How to Automatically Create Pinterest Pins from WordPress Posts (Make.com Tutorial)

What you'll build: WordPress (new post) → PinImage Studio API (designed pin PNG) → Pinterest (published pin). Total setup time: about 15 minutes.

What you need:

1. WordPress site (self-hosted)
2. free Make.com account
3. PinImage Studio Pro account with an API key (get one here)
4. Pinterest business account connected to Make

Step 1 — Connect WordPress to Make (the right way)

Make's WordPress modules do not use WordPress Application Passwords. They need the "Make Connector" plugin:

In your WordPress admin, go to Plugins → Add New and install Make Connector. Activate it, open its settings, and copy the generated API key. In Make, add a WordPress module and create a connection using your site URL and that key.

Step 2 — Choose your trigger

For live automation, use WordPress → Watch Posts. One important detail: Watch Posts only fires for posts published after you set it up. It will not process your back catalog, and it will not fire when you edit an old post.

For testing, don't use Watch Posts. Use WordPress → Get a Post (with a specific post ID) or List Posts instead — otherwise you'll sit waiting for a trigger that only fires on brand-new posts.

Step 3 — Generate the pin with PinImage Studio

Add an HTTP → Make a request module after the WordPress module:

URL: https://pinimagestudio.com/api/public/v1/pins Method: POST — this matters; a GET request will not create anything. Headers: add one header — Name: Authorization, Value: Bearer pk_live_YOUR_KEY (the word Bearer, a space, then your real key). Body type: Raw → JSON (application/json) Parse response: Yes

Request content (map WordPress fields into it):

json{ "template": "classic", "title": "{{title from your WordPress module}}", "image_url": "{{featured image URL from your WordPress module}}", "brand_color": "#7C3AED" }

Set brand_color to your blog's brand hex color, and pick any of the 15 templates (classic, bold-quote, magazine, minimal, polaroid, and more — full list in the API reference).

The image URL rule that trips everyone up

image_url must be a direct link to an image file — a URL that ends in the actual image, like your post's featured image URL. It cannot be a page URL: a link to an Unsplash or Pexels photo page is a web page, not an image, and the render will fail. Your WordPress featured image URL (from the media library) is exactly the right kind of link. JPEG or PNG works best.

Step 4 — Post to Pinterest

Add Pinterest → Create a Pin:

Board: pick your target board Image URL: map the url field from the HTTP module's response — this is your freshly designed 1000×1500 pin Title: map the post title Description: map the post excerpt Destination link: map the post URL, so the pin drives traffic back to your blog

Step 5 — Test it

Run the scenario once using Get a Post with a real post ID. You should see:

The HTTP module return status 200 with a JSON body containing id, url, and usage The pin appear on your Pinterest board within a few seconds The same pin in your PinImage Studio My Pins dashboard

If the HTTP module errors, check the three usual suspects: method is POST, the Bearer prefix is present in the Authorization header, and image_url is a direct image link.

Once the test passes, switch the trigger to Watch Posts, turn scheduling on, and you're done — every new post now becomes a designed pin automatically.

Going further

Multiple pins per post: duplicate the HTTP module with different template values — Pinterest rewards fresh creatives for the same URL. Zapier / n8n: the same API call works in any automation tool that can send an HTTP POST. Quotas: Pro includes 500 pins/month, Agency 1,500 — the usage field in every response shows where you stand.

Questions? The full endpoint documentation lives in the API reference.