PostsBridge

Synchronize backend data with WordPress post collections over HTTP APIs, enabling remote and automated web content management.

With Posts Bridge you can move your workspace from the WordPress admin to collaboration tools, or get your backend data automatically synchronized with your website, and use Gutenberg, WordPress’ powerful page builder, as the frontend editor of your business tools.

Don’t bother your team with context switching and manual web content synchronizations. Posts Bridge lets you automate data flow to WordPress from any API-powered system—without writing a single line of code.

Work where your data is, and use Posts Bridge to seamlessly transform it to web content without effort.

What is a bridge?

Think of a bridge as a mapping that links your backend data with a post type collection from your WordPress web page. Each item on your backend database will be converted to a post, and each field on your backend records can be mapped to a post field, post meta or taxonomy terms.

Once you link a post type to an endpoint from your backend API, you get a Remote CPT. Remote CPTs are a special type of posts that can fetch data over HTTP requests on render time and stay synchronized with your backend state.

With bridges you can connect your WordPress posts to any kind of backend, it doesn’t matter if it is a CRM, an ERP, a booking system or an online spreadsheet, the only requirement is an HTTP API.
If it has an API it can be bridged!

Synchronization

Posts Bridge treats post collections as indexes that represents your backend data. Either by manually triggering bulk synchronizations, by scheduling automatic background jobs, or dynamically loading data on renders, Posts Bridge fully integrates your backend data into the WordPress CMS system.

Posts Bridge offers two strategies for content synchronization:

Add-ons

Posts Bridge comes with free add-ons. Each add-on add to the plugin new bridges to work with specific APIs.

Need a custom integration?

Connect to any custom API using standard HTTP methods and authentication using the abstract REST API add-on. Perfect for integrating with proprietary or less common systems.

Fields mappers

Field mappers are relations between fields in your backend data and post fields in WordPress. Posts Bridge use them to translate your backend API responses into post attributes like the title, content or excerpt, or into custom fields.

Tax mappers

In addition, with field mappers you can map fields from your backend responses to taxonomies in WordPress and manage your post tags and categories from outside WordPress. And not only tags and categories, Posts Bridge also supports custom taxonomies.

Json fingers

In both, fields and tax mappers, you can use json fingers as foreign names.

A json finger is a hierarchical pointer to data structures like children[0].name.rendered. For example, if your backend sends payloads like this:

{
  "name": "Bob",
  "company": "Example Coop",
  "address": {
    "street": "Carrer de Balmes, 250",
	"city": "Barcelona"
  }
}

Then you can use two mappers to rename the street and city fields from your backend response with address.street and address.city fingers as the foreign name.

With this setup, your backend payload will enter the bridge as a hierarchical data structure and will be mapped to the target post fields or taxonomy terms.

Remote fields

Posts Bridge comes with a custom WordPress block: Remote Fields ✈️. This block allows you to use remote field placeholder marks in the content of your posts. On render time, Posts Bridge will request those field values to the backend and replace them dynamically.

A remote field placeholder mark looks like {{fieldName}}, with the name of the field between curly brackets. Place them there where you want your backend fields to be shown and Posts Bridge will do the rest.

Backends

A backend can be your open software ERP, or maybe the collaboration platform your team works with. There is where the journey comes to end, where your data should be. To allow Posts Bridge to get to your backend, it needs a URL, an array of HTP headers, and, if required, an HTTP authentication credential.

Authentication

Posts Bridge supports standard HTTP authentication methods out of the box. API keys, Basic Auth, Digest Auth, OAuth, Bearer Tokens, RPC credentials and custom headers. Store your credentials once, select one authentication schema and Forms Bridge will take care of the hard work for you.

Screenshots

Settings page screenshot — Settings page

Backend settings screenshot with two registered backends, ntfy and Odoo — Settings page

Support us 💙

Posts Bridge is open source software. This means it’s free and open. We don’t charge with any fee the use of this piece of software, feel free to use it and to share with your friends.

Behind Posts Bridge plugin is Còdec, a web development cooperative studio based on Barcelona. We work with WordPress and the CoopPress stack, our own toolset and methodology inspired and oriented to the cooperative market of Catalonia. If you want to know more or want to work with us, get in touch!

Donate

If you only wants to support the project and make it a little bit more sustainable, you can donate to Forms Bridge via Buy Me a Coffee ☕.

Screenshots

Support us 💙

Donate

About

Privacy