Content & Documents · Integration
WordPress.com
Add WordPress.com to your product for your customers, and give your AI agents governed access to it.
This connector is WordPress.com, the hosted service Automattic runs, rather than a self hosted WordPress install somebody maintains on their own server. The distinction decides how the connection is made: a WordPress.com site is reached through Automattic's own authorisation flow and addressed by site id, so a customer approves it in a browser and there is no server address to configure, whereas a self hosted install would want its own credentials at its own domain. What the integration works with is what a site is made of: posts and pages with their revisions, media in the library, categories and tags, comments waiting on moderation, and users with the roles the site owner set. Plan tier is worth checking early, because what a site is permitted to do through the API is not identical on every plan. fastn keeps each site's authorisation per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer authorise their own WordPress.com site so your product publishes under their identity rather than a shared account.
Draft, schedule and publish posts and pages from inside your product, with categories and tags mapped to what that site already uses.
Upload images and files into the site's media library and attach them to the post that needs them.
Read and moderate comments so a community conversation is handled where your users already work.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent drafts a post and leaves it in draft until a person says otherwise.
An agent publishes an approved post to the site it was authorised for, and the site id is recorded.
An agent reports which comments are pending moderation and summarises what they say.
Example prompt
What is scheduled to publish on this WordPress.com site this week, and is anything still in draft?
Set up WordPress.com in 4 steps
- 01Enable the WordPress.com connector in your fastn dashboard.
- 02Have each customer authorise their own site, and record the site id the connection resolves to.
- 03Map that site's categories, tags and author roles, then decide what your product may publish rather than draft.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the WordPress.com integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a WordPress.com integration without building it. Your customers connect their own WordPress.com account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a WordPress.com update is not your on-call problem.
- One integration serves your product and your agents. The same governed WordPress.com connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Webflow
ContentfulWorks well with
SquarespaceOften used alongside
Tools the same teams tend to run next to WordPress.com, across other categories.
Shopify
Stripe
Jira
AsanaWordPress.com integration FAQ
How do I add a WordPress.com integration to my product?
Enable the WordPress.com connector in your fastn dashboard, then let each customer authenticate their own WordPress.com account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no WordPress.com client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own WordPress.com account?
Yes. Every connection is scoped to the individual customer, so each authorises their own WordPress.com account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this WordPress.com integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent drafts a post and leaves it in draft until a person says otherwise.
Who maintains the WordPress.com integration?
fastn does. When WordPress.com changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the WordPress.com integration run under?
Each customer's own WordPress.com grant. Where WordPress.com holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in WordPress.com automatically?
Where WordPress.com supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the WordPress.com integration?
A common starting point: let each customer authorise their own WordPress.com site so your product publishes under their identity rather than a shared account. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the WordPress.com integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding WordPress.com does not change your per-connector cost. You can start free with 3 connected accounts.
Add WordPress.com to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.