Skip to content
FidelicRoster →

WordPress integration · OAuth + REST

Connect AI agents to your WordPress site

AI agents that read your WordPress posts and pages, draft new records, and post the result to Slack — SEO content briefs, editorial calendars, and content hygiene.

How a Fidelic agent reaches WordPress.

The connection

What's wired

Fidelic agents connect to WordPress through OAuth + the WordPress REST API. Your agent reads the posts, pages, and categories the site admin explicitly grants.

When the agent reads, it stays inside the site you've shared. Nothing leaves your WordPress site unless the agent posts a brief to Slack or creates a draft post or page you authorized.

→ WordPress official API docs

Set it up

How to connect

Before you start

  • A WordPress site (self-hosted or WordPress.com Business+).
  • Site admin role.
  • A Slack workspace where the agent will live and post.
  • A decision on which WordPress sites the agent should reach.
  • About five minutes for the OAuth flow.

The steps

  1. Sign in to Fidelic and pick the agent. From the Roster, pick the SEO agent.
  2. Authorize WordPress. Click Connect WordPress. The OAuth dialog opens; sign in with your site admin account. The app appears in your site's authorized apps.
  3. Pick the sites the agent should reach. Pick the sites and post types the agent will read or write to.
  4. Confirm and finish. The agent runs a test read. When it passes, your Slack channel shows a Connected to WordPress message.
  5. Try the first agent action. Ask for a content brief in Slack.

The edges

Connection limits

Where the connection draws the line:

  • · The agent only reads sites and post types the admin explicitly shares.
  • · WordPress plugins extend the REST API; non-default endpoints require explicit scope grants.
  • · Multisite networks require per-site authorization.

The path

Where the data goes

The connection runs inside your sandboxed Anthropic project. One project key per Fidelic customer; Fidelic infrastructure does not see your platform data.

Anything the agent reads stays inside your environment. The only data that leaves is what the agent posts to Slack or writes back to a destination you authorized — and you can revoke either at any time from the platform's connections panel.

→ Read the full security architecture

Where to next