Schedule Photos to Post Automatically with Postbot

Schedule Photos to Post Automatically with Postbot

Schedule photos to appear on your site automatically, with Postbot.

We’re big fans of photography here at WordPress.com, and we know that a lot of you are, too. Sometimes we’ll take a bunch of photos and want to post them, one at a time, spread over several days. Doing this manually is time-consuming and, let’s be honest, a little boring.

To help this situation we created Postbot, a photo scheduling app that allows you to quickly upload and schedule multiple photos.

postbot-blog

Postbot will create a post for each photo and schedule it to appear at a certain time over a given number of days. This is the ideal way to share a lot of photos without having to manually create and schedule each one.

Postbot is a stand-alone application that works with your WordPress.com blog, and your Jetpack-powered WordPress.org blog. You can use it from your desktop or mobile browser.

How to use Postbot

To use Postbot, go to postbot.co and click on the Connect with WordPress.com button. If you’re not logged in to WordPress.com, you’ll be asked to log in. If you are logged in, you’ll be asked to grant access to Postbot.

wpcc-button

Then drag and drop a bunch of photos onto the page. If you’re on a mobile device you can click on the upload button to open your photos.

postbot dragdrop

You can edit photo details while they upload — there’s no need to wait.

When everything is ready just pick a schedule — a start date and the number of days between each photo — and we’ll do the rest. If you want to exclude the weekends then that’s fine too.

postbot schedule

It’s worth re-iterating that Postbot works on both WordPress.com and WordPress.org blogs. For WordPress.org you’ll need the Jetpack plugin installed and the JSON API module enabled.

For the technically minded, Postbot was created using the WordPress.com API. All of the code is available on Github and is released under a GPL license. We’ll be writing a follow-up post explaining some of the details on the WordPress.com developer blog.


Posted by WordPress Guru