Your AI Connector Docs

WordPress

Who is this for? Businesses that run a WordPress site and want an automation to write posts on it or create accounts on it. If you don’t use WordPress, you can skip this page.

Use a different website platform? Anything with an API can still be connected: see Connecting a Tool We Do Not List.

WordPress is the software a very large share of the web runs on. Connecting it to Your AI Connector gives your automations ready-made steps for the two things people usually want from a site: putting content on it, and giving someone an account on it. A conversation that ends in “yes, send me the guide” can create the WordPress user. A weekly summary can land as a draft post waiting for your review.

Nothing is installed on your WordPress site. You connect your own site with your own login details, and we call WordPress’s built-in REST API the same way your own dashboard does.

Availability: Automations is available on every account. It’s already in your sidebar, and there’s nothing to enable or request.

What You Need

  • A WordPress site on version 5.6 or newer, reachable over https.
  • Pretty permalinks switched on (Settings → Permalinks, anything other than “Plain”). This is what makes the /wp-json/ address work, and it is the single most common reason a connection is refused.
  • An application password for the WordPress user the automation should act as. In WordPress, go to Users → Profile, scroll to Application Passwords, give it a name like “Automations” and click Add New. WordPress shows the password once, in blocks separated by spaces. Copy it with the spaces.

An application password is not your normal login password. Your real password stays out of this, and deleting the application password later revokes exactly this connection and nothing else.

Whatever the user you pick is allowed to do in WordPress is the limit of what the automation can do. A user who cannot publish posts will not be able to publish them from an automation either.

Connecting WordPress

You connect from inside an automation, the first time you use a WordPress step.

  1. Open Automations in the sidebar (under the AI Studio group) and open or create an automation.
  2. Add a step and search for WordPress in the step picker.
  3. Pick the WordPress action you want. The step asks you to connect first.
  4. Fill in the three fields:
    • Site URL is the address of your WordPress site, starting with https://, for example https://yoursite.com.
    • WordPress username is the username that user signs in with, not their email address.
    • Application password is the password you created above, pasted with its spaces.
  5. Click connect.

We check the details against your site before saving anything, by reading the profile of the user you gave us. A wrong address, a wrong username, a wrong password, or a site where /wp-json/ doesn’t resolve is refused right there with the reason on screen, so you never get a connection that looks fine and fails the first time the automation runs.

Your application password is stored encrypted and never shown back to you. Lost it? Create a new one in WordPress and connect again.

The Actions

Each action is a step you drop on the automation canvas. Every field accepts data from earlier steps with the usual insert-data buttons, so a title can be built from a contact’s name and content can come from an AI step.

Create post

Publishes a new post, or saves it as a draft.

  • Title is the post title. Required.
  • Content is the body of the post. Required. It accepts HTML.
  • Status decides what happens to it: publish, future, draft, pending or private. Leave it empty and the post is saved as a draft, on purpose: an automation that publishes to your public site on its first test run is a worse surprise than one that doesn’t.
  • Excerpt is the short summary WordPress shows in lists. Optional.

Update post

Changes a post that already exists.

  • Post ID is the post to change. Required. You’ll find it in the address bar when editing a post in WordPress, or take it from a Create post step earlier in the same automation.
  • New title, New content and New status are all optional, and only the fields you fill in change. Leaving the title empty does not blank the live post’s title.

Get post

Fetches one post so later steps can use it: title, content, status and its public link.

  • Post ID is the post to read. Required.

Create user

Creates a WordPress account.

  • Username is the name they will sign in with. Required.
  • Email is their email address. Required. This is usually the contact’s email from the trigger.
  • Password is optional, and best left empty. A random password is set, and they choose their own with Lost your password? on your login page. Anything you type here is saved with the automation, so a password you type is visible to anyone who can open it. The field is masked.
  • First name and Last name are optional.
  • Role is picked from a list: Subscriber, Contributor, Author, Editor, or Customer (the WooCommerce role). Optional; left on your site’s default role, WordPress gives them the default role set under Settings → General. Administrator is not on the list on purpose: an automation started by a chat or a form should never be able to create an admin on your site.

Find user by email

Looks a user up by email address, and returns their id so a later step can use it.

  • Email is the address to search for. Required.

An Example Automation

Give a customer a site account the moment they ask for one.

  1. Trigger: a tag is added to a contact, say wants access, by your AI agent or by a team member.
  2. Find user by email, with the contact’s email. This tells you whether they already have an account.
  3. A Condition step on whether anything came back.
  4. On the “nothing found” branch, Create user with their email, a username and the role Subscriber, leaving the password empty.
  5. A Send message step that tells them on WhatsApp their account is ready, with the username and a link to your login page, where Lost your password? lets them set their own password.

A second one, for content: an automation on a schedule that asks an AI step to write up this week’s most asked question, then a Create post step that saves it as a draft. You open WordPress on Monday to a post that only needs reading and publishing.

Good to Know

  • Outputs travel forward. Everything an action returns is available to later steps as variables, so the id from Find user by email is what you hand to the next step, and the link from Create post is what you send in a message.
  • Draft is the safe default. Create post saves as a draft unless you set a status yourself.
  • Some hosts strip the Authorization header before WordPress sees it, which makes any application password look wrong. If your details are definitely right and the connection is still refused, that is what to ask your host about.
  • There is no trigger that watches WordPress. Nothing polls your site for new posts or new users. To have WordPress start an automation, use a Webhook trigger in the automation and point a WordPress webhook plugin at the address it gives you.
  • Anything not on the list above is still possible with the HTTP request step, which can call any address on your site’s API directly.

Next Steps