CONNECT APP
Build with WordPress.com
Productivity
- OAuth
MCP
Give your agent WordPress.com tools
Every WordPress.com action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's WordPress.com account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "wordpress_com",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Create New Post:
const result = await mcp.callTool({
name: "wordpress_com-create-post",
arguments: {
site: "Site ID or Domain",
title: "Post Title",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "wordpress_com",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Create New Post:
result = await session.call_tool("wordpress_com-create-post", {
"site": "Site ID or Domain",
"title": "Post Title",
})API PROXY
Call the WordPress.com API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the WordPress.com API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://public-api.wordpress.com/rest/v1.1/me",
})
// Any allowed WordPress.com endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://public-api.wordpress.com/rest/v1.1/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9wdWJsaWMtYXBpLndvcmRwcmVzcy5jb20vcmVzdC92MS4xL21l?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run WordPress.com actions from your backend
Connect a user's WordPress.com account once, then run Create New Post on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "wordpress_com-create-post",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
wordpress_com: { authProvisionId: "apn_xxxxxxx" },
site: "Site ID or Domain",
title: "Post Title",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="wordpress_com-create-post",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"wordpress_com": {"authProvisionId": "apn_xxxxxxx"},
"site": "Site ID or Domain",
"title": "Post Title",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "wordpress_com-create-post",
"configured_props": {
"wordpress_com": { "authProvisionId": "apn_xxxxxxx" },
"site": "Site ID or Domain",
"title": "Post Title"
}
}'TOOLS
WordPress.com actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Create New Post
actionCreates a new post on a WordPress.com site. See the documentationWritev0.0.4 -
Delete Post
actionDeletes a post. See the documentationWritev0.0.3 -
List Site ID or Domain Options
actionRetrieves available options for the Site ID or Domain field.Read-onlyv0.0.1 -
Upload Media
actionUploads a media file from a URL to the specified WordPress.com site. See the documentationWritev0.0.4
EVENTS
WordPress.com triggers
Event sources your backend can deploy for users and receive through a webhook.
-
New Comment
triggerEmit new event for each new comment added since the last run. If no new comments, emit nothing.v0.0.2 -
New Follower
triggerEmit new event for each new follower that subscribes to the site.v0.0.2 -
New Post
triggerEmit new event for each new post published since the last run. If no new posts, emit nothing.v0.0.2
MULTI-APP
Use WordPress.com with other popular apps
Most products don't stop at one integration. Pair WordPress.com with the other apps your users rely on, and ship use cases that span both.
- App slug
- wordpress_com
- Authentication
- OAuth
- Categories
- Productivity
- Actions
- 4
- Triggers
- 3
- API proxy
- Available
OAuth scopes
These are the scopes Pipedream's managed WordPress.com OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.
- global