Connecting your WordPress site
Link a WordPress site to a Nodest workspace and what to do when it won't connect.
Connecting a site links it to one Nodest workspace. From then on, its events can start automations and Nodest can act on it.
There are two ways in, and they end at the same place.
From the plugin
Once the plugin is installed and activated, open it in your WordPress admin and connect it to your workspace. This is the simplest route — you're already signed in to WordPress, so there are no credentials to copy.
From Nodest
Add a WordPress connection in your workspace and supply three things:
| Field | What it is |
|---|---|
| Site URL | The full address of your site, including https:// |
| Username | The WordPress account Nodest should act as |
| Application password | A revocable password generated in WordPress, not the account's login password |
If the plugin isn't on the site yet, Nodest installs and activates it as part of this step.
Creating an application password
Application passwords are a WordPress feature made for exactly this: giving an external service access without handing over a login.
- In WordPress, go to Users → Profile for the account you want Nodest to use
- Scroll to Application Passwords
- Enter a name — "Nodest" — and click Add New Application Password
- Copy the generated password immediately; WordPress only shows it once
Paste it into Nodest exactly as shown, spaces included.
Two things to know: your site must be served over HTTPS, since WordPress disables application passwords on insecure connections, and the password can be revoked on its own later without touching the account.
Which account should I use?
Use an account with enough permission for what your automations do — and remember Nodest acts as that account.
An administrator is needed if you want Nodest to install the plugin for you. Beyond that, the account needs rights to whatever your automations touch: reading orders, creating posts, and so on.
Prefer an account that isn't tied to one person. If you connect as an individual employee and their account is later removed, every automation using that connection stops.
What happens when you connect
Nodest verifies the connection immediately, using the details you supplied. If the site can't be reached or the credentials are rejected, the connection isn't saved — you find out straight away rather than when an automation fails later.
Once it succeeds, the site's events become available, and so do the plugins installed on it.
One site per workspace
A workspace holds a single WordPress connection, so a workspace maps to one site.
Running several sites means a workspace each — which is usually what you want anyway, since it keeps each site's automations, connections and run history separate. An agency gets one workspace per client, with no chance of a workflow reaching the wrong site.
If you need a single automation to span sites, that's a sub-automation call into another workspace, available on plans that include cross-site automation.
