Pulling Posts from Content Porter
Write and approve pages and blog posts in Content Porter, then pull them directly into your WebHaste site with one click. The page, images, menu link and list entry are all set up for you.

What is Content Porter?
Content Porter generates content (blog posts and website pages) and publishes it to websites and social channels. For a WebHaste site, it doesn't push files to your server. It builds each approved post and holds it as Ready to pull. WebHaste then pulls ready posts into your site folder when you ask it to. That keeps you in control: nothing changes in your site until you click the button, and nothing goes live until you Publish.
This works in WebHaste itself, so there's nothing to install and no command line, which means it works on a Chromebook.
1. Set up the destination in Content Porter
In Content Porter, open your project and add a destination of type Static site export. The settings tell Content Porter how your site is organized:
- Site URL — your live site, such as
https://example.com. Used to build each post's live link. - Folder for posts — where blog posts go, such as
blog. - Page template — a file in your site's
.webhaste/templatesfolder, such astemplate-blog.html. Leave it blank to use your site's default template. - Add to menu — a menu from your Menus (for example
blog) that each post is added to. Leave it blank for no menu link. - Add to list — a List (for example
blog-posts) that gets each post's date, title and link. The list has to exist in your site already; if it doesn't, the pull skips it and tells you.
Once the destination is saved, click Make pull token. The token starts with cpx_ and is shown only once, so copy it. If you lose it, make a new one; that stops the old one from working.
2. Add the token to WebHaste
- Open your site in WebHaste, then click ⚙️ Site Admin and ⚙️ Site Settings.
- Under Content Porter, paste the token.
- Click Save. WebHaste checks the token and shows Connected to … in the status bar. If something is wrong (a bad token, or a destination that's switched off in Content Porter), the status bar shows the reason.
The token is stored on this device only, per site. It is never written into your site folder, so it can't end up in a git repository or on your published site. To turn the feature off, clear the token and save. You'll need to enter the token again on each computer or browser profile where you use WebHaste.
3. Pull posts into your site
When you've approved a post in Content Porter and published it to your destination, it shows as Ready to pull. In WebHaste:
- Click ⚙️ Site Admin, then 📥 Pull from Content Porter. This item only appears once a token is set, and a badge shows how many posts are ready (checked when you open the site).
- WebHaste brings in every ready post, oldest first, and then shows a results list.
For each post, WebHaste:
- saves its images into
assets/. An identical image already there is reused, and a different image with the same name is saved asname-2.jpgand so on, so nothing is ever overwritten; - writes the page into your post folder (for example
blog/my-post.html); - adds its title, description and template to the page's Page Properties, keeping anything you've set there, like header code or draft status;
- adds a link to the menu and an entry to the list, if you set those up. A post that's already there is updated, not duplicated.
Then Content Porter marks the post Published and shows its live link. If a post can't be brought in, the results list says why, and it stays Ready to pull so you can try again after fixing the problem. The other posts are still pulled.
4. Check, then publish
Pulling puts the posts into your site, but it doesn't publish. Open the new pages, check them over, make any edits you like, and then click 🚀 Publish as usual. See Publishing.
Updating a post
If you publish the same post to the destination again from Content Porter, it keeps the same address. The next pull replaces that page with the new version and updates its menu and list entries. Any edits you made to the page in WebHaste in the meantime are replaced, so make further changes in Content Porter, or pull first and then edit.
Troubleshooting
- The Pull item isn't in the Site Admin menu. No token is saved for this site on this device. Add it in Site Settings.
- "Nothing ready to pull." No post is waiting. Check that you've approved the post and published it to the Static site export destination in Content Porter.
- An error about the token. The token is wrong or has been replaced. Make a new one in Content Porter and save it in Site Settings.
- An error saying the destination is switched off. Turn it back on in Content Porter.
- Too many requests. Content Porter limits how often it can be asked. Wait a minute and try again.
- The post isn't in the blog index or menu. The destination's menu or list name has to match one in your site. Check Menus and Lists; the results list notes a list it couldn't find.
Using Claude Code or the command line instead
If you'd rather work outside WebHaste, or you're using an AI agent on your site's files, Content Porter also offers a small Node script that does the same pull from the site folder. See Content Porter's own help for that. Sites that use the WebHaste extension don't need it.
Topics