WordPress

What it is

An agent connected to WordPress looks after your website’s content the way a teammate does. It drafts and edits posts and pages, uploads images, keeps categories and tags tidy, and answers and moderates comments.

In WordPress, the agent works as the user who approves the connection. What it may do is that user’s role, and its posts carry that user’s name. A user of its own, with the agent’s name, is the cleanest choice: Editor to look after everyone’s posts and pages, Author for its own posts only.

Before you start

• Your site’s address. The site needs a secure address (https) and WordPress 5.6 or later.
• A WordPress user for the agent with the right role. Sign in to your site as that user in the browser you connect from, so WordPress asks the right user to approve.
• WordPress’s application passwords switched on. They are on by default; some security plugins switch them off.

Connecting WordPress

1. Open the agent, go to the Tools tab and choose WordPress.
2. Enter your site’s address and click Continue to WordPress. WordPress opens its own approval page (sign in first if it asks).
3. Check that the page names the agent (“AgentTeams for …”) and click Yes, I approve of this connection. WordPress hands AgentTeams an application password for that user, and you’re back in the wizard.

If your site doesn’t show the approval page, choose “My site doesn’t show the approval page” in the wizard. Then, signed in to WordPress as the agent’s user, open Users, Profile, add one under Application Passwords, and paste it with the username. WordPress shows it only once.

What the agent can do

• Posts and pages. Find and read them, published, scheduled or in draft; write new ones as drafts (or send them to an editor for review); edit titles, text, excerpts, categories, tags and featured images; publish or schedule them; and move them to the trash.
• Media. Look through the media library and upload images and files: one it made, or a photo someone sent it. It writes alt text for images so they work for everyone.
• Categories and tags. Read them and add new ones.
• Comments. Read comments, answer them, and approve, hold, mark as spam or remove them.
• Everything else the site offers apps, like its settings or a plugin’s own parts, as far as the user’s role allows.

The agent writes in plain formatting that WordPress stores as a classic block; the editor turns it into blocks with one click. When it edits an existing post, it keeps the post’s blocks as they are.

What the connection allows

An application password lets the agent do in WordPress what its user’s role allows, nothing more. We keep it encrypted, and the one WordPress hands back is swapped for a fresh one at once, so only AgentTeams holds the one in use. You see it in WordPress under Users, Profile, Application Passwords, named after the agent.

What it reacts to

WordPress doesn’t tell apps when something happens on a site, so there are no WordPress reactions. For regular work, give the agent a schedule on the Tasks page: a weekly post, a look at new comments every morning, a check of last month’s drafts. See Tasks & schedules.

Staying in control

New posts and pages are always drafts. Publishing, editing what’s already live, answering or approving a comment, and every other change go through a review step first, and your company’s rules decide which need a person to approve them. Publishing and anything else the public sees are reviewed every time, never waved through because similar ones were approved before. Approval gates explains how.

What we receive, and what we keep

• We only read your site when the agent works on it. WordPress sends us nothing on its own.
• What the agent reads and writes while working stays with that agent in your own AgentTeams workspace, the same way its chats and emails do.
• Nothing from your site is used to train any model. For the full picture, see our privacy policy.

Disconnecting

There are two places, and doing both is the clean way round:

1. In AgentTeams. Open the agent, go to the Tools tab, open the WordPress card and click Disconnect. The agent stops working on your site at once.
2. In WordPress. Open Users, Profile of the agent’s user, and revoke its password under Application Passwords (it is named after the agent). That ends the access on the site itself.

Disconnecting leaves everything the agent already wrote on your site in place.

If something is off

• The site doesn’t show the approval page. Application passwords may be switched off (often by a security plugin), the site isn’t on a secure address, or WordPress is older than 5.6. Switch them on, or paste an application password made by hand.
• WordPress approved it, but the connection still fails. Some hosting setups drop the sign-in on its way to WordPress. Ask your host to let it through (they may know it as passing on the Authorization header), or paste an application password instead to check.
• It can’t publish or edit someone else’s post. Its user’s role doesn’t allow it: an Author publishes only its own posts. Give the user the Editor role.
• Its posts carry someone else’s name. It was connected while signed in as that person. Disconnect, then connect again signed in as the agent’s own user.

Related

• AI agents for WordPress: what teams use it for
• WooCommerce: the store on your WordPress site
• Tasks & schedules: regular work on a schedule
• Approval gates: who approves what