Skip to main content

WordPress.com

A site hosted on WordPress.com: agents draft, publish and manage posts, pages and media for the site you choose.

Connect it with: Sign in (OAuth). WordPress.com's own documentation: https://developer.wordpress.com/docs/oauth2/.

What agents can do​

Connect WordPress.com so the agents working your tasks can reach it. With it connected, they can:

  • Draft, edit, schedule and publish posts and pages on the site you choose when connecting.
  • Upload images and files to the site's media library.
  • Manage categories, tags and comments.
  • Read the site's content and stats to answer questions or plan new content.

Before you start​

  • A WordPress.com account that is an administrator or editor of the site agents should work on.
  • For a self-hosted WordPress site (not on WordPress.com), use the WordPress integration instead.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with WordPress.com​

This is the quickest way in: you sign in to WordPress.com and approve what Jaah asks for. You never copy a key.

  1. In Jaah, open Secrets and select New.
  2. Search for WordPress.com and select its card.
  3. Give the secret a name you will recognize, such as the account or workspace it reaches, and choose who can use it (see Who can use it).
  4. Select Connect WordPress.com. WordPress.com's sign-in window opens.
  5. Sign in to WordPress.com if asked, check the access listed, and approve it.
  6. You land back in Jaah on the new secret, which reads Connected once its test passes.

If the button reads Jaah app not configured, this Jaah has no app registered at WordPress.com yet. Use your own OAuth app until it does (see Use your own OAuth app).

Scopes Jaah requests​

Jaah asks WordPress.com for these scopes, and no others. A scope marked optional is a checkbox on the Connect screen: untick it and agents simply cannot do that part.

Jaah names no scopes on the sign-in request: the vendor grants the access set on Jaah's app itself, and lists it on its approval screen.

Connect with an API key​

WordPress.com has no API key option in Jaah: connect with the sign-in above.

Use your own OAuth app​

Register your own OAuth app at WordPress.com when your company requires apps it controls, or before this Jaah has an app registered there.

  1. Create an OAuth app in WordPress.com's developer console, https://developer.wordpress.com/apps/new/ (WordPress.com's documentation).
  2. Set its redirect URI to https://app.jaah.ai/api/credentials/connect/callback (on your own Jaah, its console address followed by /api/credentials/connect/callback).
  3. Give it the scopes in Scopes Jaah requests.
  4. Copy its client ID and client secret.
  5. In Jaah, start a new WordPress.com secret, select Use your own OAuth app, paste both values and select Connect WordPress.com.

The client secret is stored with the connection, encrypted, like any other secret value.

Test the connection​

Select Test on the secret. Jaah calls WordPress.com's API once (GET https://public-api.wordpress.com/rest/v1.1/me) with the stored values, and shows who it answered as, or which value WordPress.com refused and the status it answered. Jaah also tests automatically when you save or reconnect.

The last result and its time stay on the secret's page, so you can see whether it still works without testing again.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.

Tell the agent in your task description which secret to use, for example “use the WordPress.com secret org/wordpress-com”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Reconnect: when WordPress.com ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at WordPress.com's side too, revoke Jaah in WordPress.com's settings.

Limitations​

  • One connection reaches one site: WordPress.com asks you to pick the site while you approve. Connect again (as another secret) for each further site.
  • Agents can do what your WordPress.com role on that site allows; WordPress.com does not let Jaah ask for narrower access.
  • WordPress.com issues no refresh token: when the grant ends (you revoke it, or change your password), select Reconnect.
  • Agents can do only what the connected WordPress.com account and its granted scopes allow.

Troubleshooting​

Test says WordPress.com rejected the access token and asks you to reconnect

The grant was revoked, or your password or two-step settings changed. Select Reconnect on the secret and approve Jaah again for the site.

The site I want is not offered while I approve

WordPress.com lists only sites where your account is an administrator or editor. Ask the site owner to raise your role under Users on the site's dashboard, then connect again.

An agent gets 403 for a different site

Each connection covers only the site you picked when approving. Connect again, choose that site, and tell the agent to use the new secret.

Still stuck? Select Test and read the result: it names the value WordPress.com refused and the status it answered.

FAQ​

How do I revoke Jaah's access in WordPress.com?

Open wordpress.com/me/security/connected-applications and disconnect Jaah. The secret then shows Needs reconnect after its next test.

My site runs on WordPress but not on WordPress.com. Which integration do I use?

The WordPress integration, which connects any self-hosted site with an application password.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one WordPress.com account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.