CONNECT APP
Build with WordPressOrg
Social Media
- API key
MCP
Give your agent WordPressOrg tools
Every WordPressOrg 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 WordPressOrg 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_org",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Create Post:
const result = await mcp.callTool({
name: "wordpress_org-create-post",
arguments: {
title: "Title",
content: "Content",
},
})# 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_org",
}
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 Post:
result = await session.call_tool("wordpress_org-create-post", {
"title": "Title",
"content": "Content",
})API PROXY
Call the WordPressOrg API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the WordPressOrg 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://api.example.com/v1/me",
})
// Any allowed WordPressOrg 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://api.example.com/v1/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZXhhbXBsZS5jb20vdjEvbWU?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run WordPressOrg actions from your backend
Connect a user's WordPressOrg account once, then run Create 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_org-create-post",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
wordpress_org: { authProvisionId: "apn_xxxxxxx" },
title: "Title",
content: "Content",
},
})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_org-create-post",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"wordpress_org": {"authProvisionId": "apn_xxxxxxx"},
"title": "Title",
"content": "Content",
},
)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_org-create-post",
"configured_props": {
"wordpress_org": { "authProvisionId": "apn_xxxxxxx" },
"title": "Title",
"content": "Content"
}
}'TOOLS
WordPressOrg actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Create Post
actionCreate a new WordPress post using the REST API directly. See the documentationWritev0.0.6 -
Create User
actionCreates a user. See the documentationWritev0.0.6 -
Get User
actionRetrieves information for a user. See the documentationRead-onlyv0.0.4 -
List Author Options
actionRetrieves available options for the Author field.Read-onlyv0.0.1 -
List Categories Options
actionRetrieves available options for the Categories field.Read-onlyv0.0.1 -
List Featured Media Options
actionRetrieves available options for the Featured Media field.Read-onlyv0.0.1 -
List Post Options
actionRetrieves available options for the Post field.Read-onlyv0.0.1 -
List Status Options
actionRetrieves available options for the Status field.Read-onlyv0.0.1 -
List Tags Options
actionRetrieves available options for the Tags field.Read-onlyv0.0.1 -
List User Options
actionRetrieves available options for the User field.Read-onlyv0.0.1 -
Search Posts
actionSearches for specific posts. See the documentationRead-onlyv0.0.5 -
Update Post
actionUpdates a post specified by its ID. See the documentationWritev0.0.5 -
Update User
actionUpdates the information of a user. See the documentationWritev0.0.4 -
Upload Media
actionUpload a media item to your WordPress media library. Returns a media ID to be used in creating or updating posts.See the documentationWritev0.0.6
EVENTS
WordPressOrg triggers
Event sources your backend can deploy for users and receive through a webhook.
No WordPressOrg triggers are available yet.
MULTI-APP
Use WordPressOrg with other popular apps
Most products don't stop at one integration. Pair WordPressOrg with the other apps your users rely on, and ship use cases that span both.
- App slug
- wordpress_org
- Authentication
- API key
- Categories
- Social Media
- Actions
- 14
- Triggers
- 0
- API proxy
- Available