Pinterest Automation with n8n, Make and Zapier: A DIY Guide

You can automate Pinterest with n8n, Make or Zapier by connecting the tool to Pinterest's official API and letting it create Pins from a source you control, such as your blog's RSS feed or a spreadsheet of Pins you have approved. Make and Zapier have ready-made Pinterest apps; n8n has no dedicated Pinterest node, so you call the Pinterest API with its HTTP Request node and your own Pinterest developer app. This guide compares the three, explains Pinterest's API access rules, walks through a working n8n workflow with an approval step, and is honest about what a DIY setup cannot do safely. Everything below was checked on each platform's own documentation and on developers.pinterest.com on October 29, 2026.

n8n vs Make vs Zapier for Pinterest (checked October 29, 2026)

Each platform has its own plans and usage limits, so check its pricing page against the number of Pins you plan to publish. If your only goal is getting WordPress posts onto Pinterest, our WordPress to Pinterest guide covers simpler routes.

Pinterest API access: what you need before you build

Make and Zapier connect through their own Pinterest connection: you sign in to Pinterest and approve access. With n8n you bring your own Pinterest app, so Pinterest's developer rules apply to you directly. These come from Pinterest's access tiers, rate limits and authentication docs.

• A developer app. You create it under My apps on developers.pinterest.com. Pinterest says that if your app is approved for API use, it receives Trial access.
• Trial access is a sandbox. Pinterest says "all Pins and Boards created with Trial access are only visible to their creator as Sandbox entities." Trial apps get 1,000 requests a day per app, and 300 a day for creating, editing or deleting Pins and boards.
• Standard access makes Pins public. To upgrade, click Upgrade on your app card in My apps, confirm your use case and privacy policy link, and upload a video of your app completing an action with the Pinterest API, including the OAuth flow. Pinterest says that even if you are the only intended user, it still requires that video. Reviews happen regularly and the decision comes by email; Pinterest publishes no turnaround time, and developers on its community forum have reported waits of several weeks.
• Standard limits. 100 requests per second per user per app overall, and 100 requests per minute per user per app for creating Pins and boards. Pinterest says all rate limits can change without notice.
• Use a business account. Pinterest's authentication docs warn that apps registered on or after September 14, 2026 may get an HTTP 403 PINNER_DATA_ACCESS_DENIED error when requesting a board or Pin for non-business users without Pinterest's authorization. Our business account guide shows the free switch.
• Tokens expire. Pinterest's example token response shows an access token valid for 2,592,000 seconds (30 days) and a refresh token for 31,536,000 seconds (one year). Apps created on or after September 25, 2025 use continuous refresh tokens automatically.
• Keep credentials private. Pinterest's Developer Guidelines say not to use someone else's API credentials and not to let anyone else use yours.

The rule most DIY workflows break

Under "What not to do," Pinterest's Developer Guidelines list "offering features that enable end users to automatically initiate actions without specifically considering each action," with this example: "if your app allows end users to schedule Pin publishing, the end user must choose each Pin to be published." A workflow that turns every new RSS item straight into a public Pin, with no human step, is exactly that pattern. Pinterest's Community Guidelines also prohibit automation that Pinterest has not explicitly approved. That is why the workflow below has an approval column, and why we cover the wider question in is Pinterest automation safe?

Step by step: an n8n Pinterest workflow with an approval step

The design: one workflow writes draft Pins into a Google Sheet, you review them and mark the ones you want, and a second workflow publishes one approved Pin per run. The sheet is your approval queue and your log. Node and field names below are from n8n's documentation on October 29, 2026.

Step 1: Set up the sheet

Create a Google Sheet with one row per Pin and these columns:

Step 2: Create your Pinterest app and the n8n credential

1. In n8n, create a new credential of the generic type OAuth2 API. n8n's docs say to use the OAuth Redirect URL it shows as the redirect URI for the service you connect. Copy it.
2. On developers.pinterest.com, open My apps, create your app, add that URL as the redirect URI, and note the App ID and app secret.
3. Back in n8n, fill in: Grant Type Authorization Code; Authorization URL https://www.pinterest.com/oauth/; Access Token URL https://api.pinterest.com/v5/oauth/token; Client ID your App ID; Client Secret your app secret; Scope boards:read,boards:write,pins:read,pins:write (the scopes Pinterest lists for creating a Pin; it accepts commas or spaces).
4. Set Authentication to Header. Pinterest's token endpoint expects HTTP Basic authentication with your client ID and secret, and n8n's Header option sends the credentials as a basic auth header.
5. Click connect and approve access in the Pinterest window that opens.

Step 3: Find your board IDs

Add an HTTP Request node with Method GET and URL https://api.pinterest.com/v5/boards. Under Authentication choose the generic credential type, then OAuth2 API, then the credential from Step 2. Run the node once. Each board in the result has an id; copy the IDs of the boards you want into your sheet. Board choice is a manual decision in a DIY setup, so keep a short list of which topics go to which board.

Step 4: Workflow A drafts Pins from your RSS feed

1. RSS Feed Trigger. n8n's docs say it starts a workflow when a new item is published to an RSS feed, by polling the feed. Enter your Feed URL (for WordPress, usually your site address plus /feed/) and set Poll Times to Every Day.
2. Optional AI step. If you add an AI node to draft the title and description, tell it the 100 and 800 character limits and ask for the words people search, not clever headlines. You will edit the result anyway.
3. Google Sheets, Append Row. Map the feed item's title and link into your columns (after a test run, n8n shows the feed fields in the node's input panel), set status to draft and give each row a row_id.

Step 5: Review in the sheet

This is the step that keeps the workflow inside Pinterest's rule. For each draft, add a vertical image URL, pick the board ID, tighten the title and description, and change status to approved only for Pins you would happily publish by hand. Rows you skip stay as drafts.

Step 6: Workflow B publishes one approved Pin per run

1. Schedule Trigger. Set Trigger Interval to Hours, for example every 4 hours. n8n uses the workflow's time zone if you set one, otherwise the instance time zone (America/New_York by default on self-hosted instances).
2. Google Sheets, Get Row(s), with a filter on the status column for approved. n8n returns only the first matching row by default, so each run publishes one Pin. That is your pacing.
3. HTTP Request: Method POST, URL https://api.pinterest.com/v5/pins, the same OAuth2 credential, Send Body on, Body Content Type JSON, Specify Body Using JSON. Switch the JSON field to an expression and build the body in one line, so quotation marks in your titles cannot break the JSON:
   {{ JSON.stringify({ board_id: String($json.board_id), title: $json.title, description: $json.description, link: $json.link, alt_text: $json.alt_text, media_source: { source_type: 'image_url', url: $json.image_url } }) }}
4. Google Sheets, Update Row, matching on row_id: set status to posted and pin_id to the id returned by Pinterest.
5. Plan for failure. If the Pinterest call fails, the row stays approved and the next run tries it again. Add a branch that marks failed rows error so one bad image URL cannot block the queue, and check the sheet weekly.

Fields in that body, from Pinterest's Create Pin reference:

Step 7: Test, then publish the workflows

While your app is on Trial access, test freely: Pinterest says Pins and boards created with Trial access are sandbox entities only you can see. Once Standard access is approved, publish both workflows. n8n's docs note that a workflow must be published for the Schedule Trigger to run; saving is not enough.

The same flow in Make and Zapier

Make. Build one scenario that runs on a schedule: a Google Sheets module that finds one row marked approved, then Pinterest Create a Pin, then a Google Sheets module that marks the row posted. Make's Pinterest app has List Boards for finding board IDs and Make an API Call for any endpoint its modules do not cover. Make's scheduling decides your pacing, so run it every few hours, not every minute.

Zapier. Zapier's Pinterest app has one action, Create Pin, which takes a board, an image URL, and optionally a link, title and description. Pair it with a Google Sheets trigger and a filter that only continues when status is approved. A Zap runs when its trigger fires, so if you approve twenty rows at once, you need a delay or queue step to space them out. Zapier's Create Pin does not list an alt text field.

Both connections post to your real Pinterest account, so the approval rule applies exactly as it does in n8n.

GitHub bots, ChatGPT and free Pinterest automation

• "Pinterest automation" scripts on GitHub. Many drive a browser that logs in to Pinterest and clicks for you, instead of using the API. Pinterest's Community Guidelines prohibit automation it has not explicitly approved, and its Developer Guidelines prohibit scraping or data extraction unless Pinterest expressly permits it. Only use code that calls the official API through your own app. If an account was already restricted, read what to do after a Pinterest suspension.
• Automating Pinterest with ChatGPT. An AI step is a good way to draft titles and descriptions, as long as a person reviews them. Pinterest's Create Pin API also has an optional ai_disclosures field (values such as AI_MODIFIED) for declaring AI-made content; our guide to the AI modified label explains what the label does. For quick drafts without building anything, the free Pin description generator gives AI suggestions you can paste into your sheet.
• Free automation. Self-hosting n8n avoids a subscription, but you pay for the server and in your own time, and you still need Pinterest's Standard access to publish.

What DIY automation can't do safely (unless you build it)

A working Create Pin call is the easy 20%. The parts that protect your account are what take time:

• Approval. Pinterest's guidelines expect a person to choose each scheduled Pin. Without a review step, every feed glitch becomes a public Pin.
• Pacing. Pinterest publishes no safe daily number, and its spam rules target repetitive, high-volume posting. A trigger that fires on a backlog of 200 old posts can publish them in one burst. Our guide to how many Pins per day to post gives a range by account age.
• Duplicate detection. RSS triggers can fire again when you edit a post, and nothing in a basic flow stops the same URL being pinned week after week. Pinterest's help says repeatedly saving the same Pins may get you flagged as spam and temporarily blocked from creating Pins. Fresh designs matter; see what counts as a fresh Pin.
• Board choice. The workflow posts to whatever board ID is in the row. Matching each post to the right board needs a mapping table or a judgment call every time.
• Pin images. RSS items rarely include a vertical image. Someone has to design a 2:3 Pin for every row, or the flow posts cropped blog images.
• Link hygiene. Pinterest blocks some shorteners and redirects. Test links with the free Pinterest link checker, and if one is flagged, follow this fix.
• Errors, tokens and API changes. Expired tokens, rate limits and rule changes (like the September 2026 change for new apps and non-business users) fail quietly until someone checks.

Rather not build and maintain those parts yourself? PinBoostr does them for you, and you approve each Pin before it publishes. It reads your website, writes keyword-led titles and descriptions, designs vertical Pins and picks a matching board from yours. Approved Pins publish through the official Pinterest API, paced with per-link, per-board and per-keyword caps and a gap of 14 days by default before the same page is pinned again. See the Pinterest scheduler.

DIY vs PinBoostr: an honest comparison

When DIY is the better choice

• You already run n8n or Make for other work and enjoy building flows.
• You publish a handful of Pins a week from an unusual source (a product database, a spreadsheet of quotes, a custom CMS).
• You want Pinterest as one step in a bigger flow, such as creating a Pin when a product goes live and posting the same news elsewhere.

When a dedicated tool is the better choice

• You want a steady flow of fresh Pins from a blog or store without designing each one.
• You would rather not wait on Pinterest's API review or maintain tokens and error handling.
• You care most about pacing and duplicate protection, which is where DIY setups usually break. Our list of the best Pinterest automation tools compares the options, and the complete guide to automating Pinterest covers the basics.

Try the approve-first version

If you like the idea of the workflow above but not the upkeep, PinBoostr gives you the same approval queue without the build. It prepares Pins from your posts and product pages with AI-written titles, descriptions and designs, you approve each Pin, and it publishes through the official Pinterest API at a paced rate. Start free for a month with no card; Starter is $19.99 a month for one Pinterest account and one website (pricing). To see how the Pins are made, try the AI Pin generator.

FAQ