Appearance
WordPress
undefined
| Detail | Value |
|---|---|
| Category | CMS |
| Base URL | https://{your-site}/wp-json/wp/v2 |
| Authentication | Bearer Token |
| Endpoints | 7 |
| Connector key | wordpress |
Using WordPress in a workflow
- Go to Connections and click New Connection.
- Pick WordPress from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | List Posts |
GET | Create Post |
GET | List Pages |
GET | Upload Media |
GET | List Categories |
GET | List Users |
GET | List Comments |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
List Posts
| Detail | Value |
|---|---|
| Operation ID | list_posts_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your WordPress connection from the Connection dropdown.
- In the Operation dropdown, select
list_posts_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream WordPress API reference.
GET
Create Post
| Detail | Value |
|---|---|
| Operation ID | create_post_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your WordPress connection from the Connection dropdown.
- In the Operation dropdown, select
create_post_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream WordPress API reference.
GET
List Pages
| Detail | Value |
|---|---|
| Operation ID | list_pages_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your WordPress connection from the Connection dropdown.
- In the Operation dropdown, select
list_pages_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream WordPress API reference.
GET
Upload Media
| Detail | Value |
|---|---|
| Operation ID | upload_media_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your WordPress connection from the Connection dropdown.
- In the Operation dropdown, select
upload_media_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream WordPress API reference.
GET
List Categories
| Detail | Value |
|---|---|
| Operation ID | list_categories_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your WordPress connection from the Connection dropdown.
- In the Operation dropdown, select
list_categories_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream WordPress API reference.
GET
List Users
| Detail | Value |
|---|---|
| Operation ID | list_users_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your WordPress connection from the Connection dropdown.
- In the Operation dropdown, select
list_users_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream WordPress API reference.
GET
List Comments
| Detail | Value |
|---|---|
| Operation ID | list_comments_6 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your WordPress connection from the Connection dropdown.
- In the Operation dropdown, select
list_comments_6. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream WordPress API reference.