Post to WordPress From an Automation
DM Champ connects to your own WordPress site so automations can write posts on it and create accounts on it. You paste your site address, your WordPress username and an application password. Nothing is installed on your site. Five ready-made steps cover posts and users, and drafts are the default.
How it worksConnecting WordPress Step by Step
What the setup actually looks like, from the connection screen to the first booking or record the AI handles in WordPress.
- 01Create an application password in WordPress
In WordPress go to Users, then Profile, scroll to Application Passwords, name it Automations and click Add New. WordPress shows it once, in blocks separated by spaces. Copy it with the spaces. Your normal login password is never used.
- 02Add a WordPress step to an automation
Open Automations in the sidebar under AI Studio, add a step and search for WordPress. Pick the action you want and the step asks you to connect first.
- 03Paste your site address and credentials
Site URL is your site starting with https, WordPress username is the name that user signs in with rather than their email, and Application password is the one you just created.
- 04Let the credential check run
We read that user's profile back from your site before anything saves. A wrong address, a wrong username, a wrong password or a site where the API address does not resolve is refused on screen with the reason.
- 05Build the rest of the workflow
Every field takes data from earlier steps, so a post title can come from a contact's name and its body from an AI step. What an action returns is available to later steps as variables.
Every screen and field is covered in the setup guide: WordPress documentation.
The stepsFive Actions For Posts And Users
Each action is a step you drop on the automation canvas, with plain fields and the usual insert-data buttons. Create post saves as a draft when you leave the status empty, on purpose: an automation that publishes to your public site on its first test run is a worse surprise than one that does not.
- Create post: title, content, status of publish, future, draft, pending or private, and an optional excerpt
- Update post: only the fields you fill in change, so an empty title never blanks the live post
- Get post: title, content, status and the public link, for later steps to use
- Create user: username, email, password, optional first and last name, and an optional role such as subscriber, author or editor
- Find user by email: returns the user's id so a later step can act on it
Before you connectWhat Your Site Needs To Have
WordPress 5.6 or newer, reachable over https, with pretty permalinks switched on under Settings, then Permalinks, anything other than Plain. That last one is what makes the API address resolve and it is the single most common reason a connection is refused. You also need an application password for the WordPress user the automation should act as, and whatever that user is allowed to do in WordPress is the limit of what the automation can do: a user who cannot publish posts will not publish them from an automation either. Deleting the application password later revokes exactly this connection and nothing else.
Two workflows to copyWhat People Actually Build With It
The first one gives a customer a site account the moment they ask for it, without anyone opening WordPress. The second turns your own inbox into content.
- A tag such as wants access is added to a contact by your AI agent, Find user by email checks whether they already have an account, a Condition branches, and Create user makes one with the subscriber role
- A Send message step then tells them on WhatsApp that their account is ready, with the username
- On a schedule, an AI step writes up the week's most asked question and Create post saves it as a draft, so Monday starts with a post that only needs reading and publishing
Worth knowingThe Limits, Stated Up Front
None of these stop the workflows above, but they change how you wire the automation, so they are worth reading first. The important one is the direction of travel: these steps write to WordPress, they do not watch it.
- There is no polling trigger, so nothing watches your site for new posts or new users
- To have WordPress start an automation, point a WordPress webhook plugin at the address the automation's Webhook trigger gives you
- Some hosts strip the Authorization header before WordPress sees it, which makes a correct application password look wrong
- Your application password is stored encrypted and never shown back to you, so a lost one is replaced by creating a new one in WordPress
- Anything not among the five actions is still possible with the HTTP request step, which can call any address on your site's API
Frequently Asked.
Meet the Closer. Then Decide.
The same AI agent that closes $40K deals in DMs is one click away. No signup, no demo call - open the chat, push back, see if you can break it.
