Burnpedia Pin Scheduler for Pinterest

Writing the post is the work. Remembering to pin it, three days later, is the part that quietly stops happening.

This plugin schedules Pinterest Pins for you, automatically, from the posts you already publish. Burnpedia Pin Scheduler connects your WordPress site to your Burnpedia account; when a post goes live, it builds a Pin from that post’s image, title and link and hands it to Burnpedia to publish on a schedule — to the board you picked, at a sensible time, without you opening Pinterest.

What it does

• Creates a Pin automatically when a post is published — or only for the posts you tick.
• Uses the featured image, or the first image in the post if there is no featured image.
• Sends the Pin to one fixed board, a board per category, or a board named after your site. A board that does not exist yet is created for you.
• Writes the Pin title and description from templates with {title}, {excerpt}, {site} and {categories} tags — editable per post.
• Adds campaign tags to the link (utm_source=pinterest…) so Pinterest traffic is visible in your analytics. Links that are already tagged are left alone.
• Schedules with a delay, so your caches and CDN are warm before Pinterest fetches the image.
• Retries by itself when something goes wrong, and waits for the reset when you have used up the day’s allowance.
• Shows what happened, per post, in an Activity log — including the posts it skipped and why.

Works on the free plan

Nothing here is locked, time-limited, or waiting for an upgrade. A free Burnpedia account publishes up to 3 Pins a day, and the plugin’s every feature works on it. Paid plans raise the daily allowance and add AI-written Pin copy and AI images; the plugin behaves identically either way. See burnpedia.app/pricing.

You keep your Pinterest password

The plugin never sees your Pinterest credentials. You connect Pinterest once inside Burnpedia, on Pinterest’s own login screen, over the official Pinterest API.

Open source

The plugin is GPL. Its source, and the API it talks to, are documented at burnpedia.app/developers.

External services

This plugin is a client for Burnpedia, a Pinterest scheduling service run by Burnpedia at https://burnpedia.app. The plugin cannot work without it: WordPress has no way to publish to Pinterest on its own, and Burnpedia is what holds the Pinterest connection.

Nothing is sent anywhere until you save a Burnpedia API key. With no key saved, the plugin makes no outbound request of any kind.

Once a key is saved, the plugin contacts https://burnpedia.app/api/v1 in these situations:

1. When you open the plugin’s settings screen or press “Check connection” — a GET /api/v1/me request that returns your Burnpedia plan, the Pinterest accounts connected to it, and how much of today’s Pin allowance you have used. Sent: your API key.
2. When you press “Load my boards” — a GET /api/v1/boards request. Sent: your API key.
3. When a post is published (with automatic pinning on), or you press “Pin this post now” — a POST /api/v1/pins request. Sent: your API key, the Pin title, the Pin description, the post’s public permalink, the URL of the post’s image, the board name or id, and the time the Pin should be published.
4. Only if you switch on “When a post has no image, let Burnpedia generate one with AI” — a POST /api/v1/images request, made for a post that has no featured image and no image in its content. Sent: your API key and the post title, which is used as the description of the picture to draw. This setting is off unless you turn it on, it spends AI points on your Burnpedia account, and nothing is charged when a generation fails. Every generation is written to the plugin’s Activity log.
5. When you open the “Pins from this site” tab — a GET /api/v1/pins request. Sent: your API key and this site’s address, so that Burnpedia returns only the Pins that link to this website rather than every Pin on your account.
6. When you open the “Pins from this site” tab, or the posts list in WordPress — a GET /api/v1/analytics/site request. Sent: your API key and this site’s address. It returns the impressions, saves and clicks Burnpedia has already recorded for your Pins; it does not ask Pinterest anything, so it cannot use up your Pinterest rate limit.

Every request also carries a header naming the plugin and its version (for example wordpress/1.0.0), the same way a browser identifies itself, so that support and compatibility questions can be answered.

No visitor data, no analytics, no usage statistics and no content beyond the fields listed above are transmitted. The plugin has no telemetry of its own: it never reports your traffic, your other plugins, or anything about your visitors. Your site’s address is sent only as part of a Pin’s own link, and when looking up this site’s Pins as described above.

Your use of the service is covered by Burnpedia’s terms and privacy policy:

• Terms of service: https://burnpedia.app/terms
• Privacy policy: https://burnpedia.app/privacy

Pinterest itself is contacted by Burnpedia’s servers, not by your site. Note that Pinterest downloads your image from your own site, so the image URL has to be publicly reachable — the settings screen warns you when it looks like it is not.

1. Install and activate the plugin.
2. Create a free account at burnpedia.app and connect your Pinterest account there (this happens on Pinterest’s own login screen).
3. In Burnpedia, open Dashboard → API and create an API key. It is shown once — copy it.
4. In WordPress, go to Burnpedia → Connection, paste the key and save.
5. Open the Automation tab, turn on “Create a Pin automatically when a post is published”, choose your board, and save.

Publish a post to try it. The Activity tab shows what happened.

1. 

   The settings screen: connection status, plan, and today's Pin allowance.

2. 

   Automation settings — when to pin, which posts, which board.

3. 

   The Pinterest box in the post editor, with per-post title, description and board.

4. 

   The Activity log: what was pinned, what was skipped, and why.

1.0.13

• New: the “Pin older posts” tab now tells you how many published posts have no
  Pin – on the tab itself, so you can see it without opening it – and roughly how
  many days it would take to work through them.
• Each post in the list says whether it is ready, or why it is not: no image
  Pinterest can use, in a category you excluded, or switched off by hand. You can
  no longer tick a post that would immediately be skipped.
• Long archives now page, and there is a tick-all for the page you are on.
• This works on every plan, including the free one. A bigger plan clears the
  backlog faster; nothing here is locked.
• New: when your Pins are stuck because WordPress is not running its scheduler,
  there is now a “Run it now” button next to the warning. It sends the waiting
  Pins straight away, so you are not stuck until your host answers.
• The button only appears when something is actually overdue, sends up to five
  Pins per press, and can be pressed once a minute. It is a nudge, not a fix –
  the cron line under it is still what stops the problem coming back.

1.0.12

• New: if you are publishing far more Pins per day than is safe for a Pinterest
  account, the plugin’s settings screen now says so, with the number you actually
  published and what we recommend. Pinterest has suspended accounts for high-volume
  publishing, and a suspension cannot be undone by reconnecting.
• You can close the notice. It comes back after a few days if the pace continues,
  and straight away if it gets faster.

1.0.11

• Fixed: the “Pinterest account” setting only ever offered one choice. If you have
  several Pinterest accounts connected to Burnpedia, all of them are now listed by
  username, and the one you picked is remembered.
• If the account this site was set to publish to is disconnected on Burnpedia, the
  setting now says so instead of quietly falling back to your default account.
• Internal: the Burnpedia API transport is now a single shared file, so both
  Burnpedia plugins handle errors, rate limits and daily-limit resets identically.
• Upgrade links now say which plugin they came from.

1.0.10

• The “Pins from this site” tab now shows what your Pins actually did: impressions, saves, and clicks through to your site – for the whole site, and per Pin.
• The posts list shows the same numbers next to each post, so you can see which posts Pinterest is actually sending people to without leaving WordPress.
• Pinterest reports about two days behind, and the screen says so rather than showing the missing days as zero.
• A Pin published this week reads “No numbers yet” instead of “0 impressions” – they are different things.
• Per-post numbers are on the paid plans; the site total is on every plan, including free.
• None of it costs you anything on Pinterest’s side: the numbers come from Burnpedia’s own copy, so opening these screens can never slow down or rate-limit your account.

1.0.9

• New tab: Pins from this site. Everything Burnpedia holds for this website – what went out, when, to which board, and what is still queued – with a link straight to the live Pin.
• It reads from Burnpedia rather than from the plugin’s own log, so it shows Pins that published after the log was written, Pins you made in the Burnpedia composer for this site, and the real Pinterest link once a Pin is live.
• Only this site’s Pins are listed, even if your Burnpedia account also schedules for other websites.
• New, and off until you turn it on: when a post has no image, Burnpedia can generate one with AI. Until now a post with no featured image and no image in its content produced no Pin at all – it was skipped and logged. Automation tab, under Image.
• It spends AI points from your Burnpedia account, one generation per image-less post, and every one is written to the Activity log so you can see what was used. Nothing is charged when a generation fails.
• You get a photographic background with no text on it. Posts that already have an image are never touched.
• Per post, too: a post with no image shows the choice right in the editor sidebar, so you can spend on one post without turning it on everywhere – or skip one on a site where it is on.
• If the AI provider has a bad moment the Pin is retried on the usual schedule instead of being skipped for good.
• Clearer messages when Burnpedia says you are out of AI points, or when AI is switched off for your login by an account owner.

1.0.8

• New: a “WordPress scheduler” panel on the Connection tab. Publishing a post does not send a Pin immediately – it hands the job to WordPress’s own scheduler – and on some hosts that scheduler never runs. Until now the plugin said nothing and the Pins simply sat there.
• If Pins are waiting, it says how many and how long the oldest has been overdue, and gives you the exact cron line to hand your host.
• If your host already runs WordPress’s scheduler from a real cron job, it says so and stays quiet. Having DISABLE_WP_CRON set is not treated as a problem on its own.
• The warning appears on the plugin’s other tabs only when something is actually wrong.

1.0.7

• New “Pin older posts” tab: pick posts you published before installing the plugin and queue them in one go. They are spread across the same best-time slots the Burnpedia scheduler uses (9am, 1pm, 5pm, 8pm) and sent one at a time – selecting 200 posts creates Pins at exactly the same rate as selecting 2, only for longer.
• Nothing about it is locked to a plan. Every plan can queue the same posts; your plan decides how quickly the queue drains, and when the daily allowance runs out the queue waits for the reset instead of failing.
• You can stop a run at any time; posts already sent keep their Pins.

1.0.6

• Your plan card now shows the same wording Burnpedia itself uses — “1 of 3 Pins used today on the Starter plan” — instead of a number the plugin had to phrase on its own. It stays correct through a plan change or a trial without waiting for a plugin update.
• When today’s allowance is actually used up, the plan card links to the plans page. It appears only when the allowance is spent and only when there is a higher plan to move to; nothing in this plugin is locked.
• “Daily pin limit reached” now tells you where to go if you want more Pins today.
• Fixed: the plugin reported its version as 1.0.4 in 1.0.5, which could serve stale admin CSS/JS from cache after an update.

1.0.5

• Tested with WordPress 7.1. Removes the “has not been tested with your current version of WordPress” warning on the plugin screen.
• No functional change.

1.0.4

• New: a “Coming next” table on the Activity tab. It shows Pins that are queued, waiting for tomorrow’s allowance, or retrying after a problem — with when each one is due. Previously only finished attempts appeared, so a Pin on its way looked like nothing happening.
• An overdue Pin now says so, and says why: WordPress has not run its scheduler.
• Success rows show the destination board and link straight to the Pin.
• A post skipped for having no image now offers a button to go and add one.

1.0.3

• New: “Send a test Pin” on the Connection tab. It runs the real publishing path without sending anything and reports every step — which post it would use, the image URL it resolved, the board, the exact title and description, whether your site is reachable from the internet, and whether WordPress is running its scheduler. A second button then sends it for real.
• The check uses the same code that publishes, so it cannot pass while publishing fails.
• A test Pin is a real Pin: it appears on your Pinterest account and uses one of the day’s Pins. The button says so before you press it.

1.0.2

• New: a first-run checklist on the Connection tab — API key, Pinterest account, board, automatic pinning, first Pin — so you can see at a glance which step is still missing.
• New: a dismissible notice on the plugin’s own screens when automatic pinning is off and posts have been published since you connected. Previously nothing said the switch was off, and posts went out with no Pin and no explanation.
• The “Getting started” steps now show a distinct “checking…” state while your account is being looked up, instead of showing a red cross for something we have not asked about yet.
• Larger touch targets and 16px form text on touch devices, so wp-admin no longer zooms when you tap a field on a phone.

1.0.1

• Stricter capability checks on the plugin’s own admin REST routes.
• “Pin this post now” now requires the publish capability for the post type, not only edit access to the post.
• A post that is not published and publicly viewable can no longer be pinned by hand.
• Reading the connection status and listing boards now require the manage_options capability.

1.0.0

• First release.