SocialClaw
OAuth integration

Publish WordPress posts and pages through SocialClaw.

SocialClaw keeps WordPress site connection, remote media upload, publish settings, validation, and post inspection in one hosted workspace shared by the dashboard, API, CLI, and agent workflows.

Media WordPress supports up to twenty remote media assets per post or page. SocialClaw uploads remote media into WordPress and embeds it into the published content.
Publishing SocialClaw publishes WordPress posts or pages through one explicit WordPress provider. WordPress taxonomy, category, tag, and richer block-editor controls are still thin.

What this integration supports

The main details for this connection.

Account type WordPress.com or Jetpack-connected site Connect the WordPress.com or Jetpack-connected site through the hosted SocialClaw OAuth flow, then reuse the site target from the same workspace.
Auth model OAuth The hosted SocialClaw OAuth flow stores the connection in the workspace.
Scheduling Validate, draft, apply, inspect SocialClaw publishes WordPress posts or pages through one explicit WordPress provider. Reconciliation currently supports WordPress post lookup.
Analytics Snapshots and health Analytics snapshots are available, but WordPress provider-native analytics fetchers are not implemented yet.

Connection, media, and delivery

How accounts connect, what media works, and how publishing behaves.

Connection model OAuth Connect the WordPress.com or Jetpack-connected site through the hosted SocialClaw OAuth flow, then reuse the site target from the same workspace.
Media and delivery WordPress supports up to twenty remote media assets per post or page. SocialClaw uploads remote media into WordPress and embeds it into the published content.

Settings and discovery

Useful settings and discovery notes for this provider.

Current settings surface

  • postStatus
  • postType
  • slug

Discovery notes

  • Use capabilities and settings inspection to confirm the publish target and post settings before applying a schedule.

CLI and HTTP examples

Example commands and requests for this integration.

CLI flow Workspace API key + provider connect
socialclaw login
socialclaw accounts connect --provider wordpress --open
socialclaw accounts capabilities --provider wordpress --json
socialclaw validate -f schedule.json --json
HTTP API flow Hosted SocialClaw endpoints
curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"provider":"wordpress"}' \
  "https://getsocialclaw.com/v1/connections/start"

curl -sS \
  -H "Authorization: Bearer $SC_API_KEY" \
  "https://getsocialclaw.com/v1/accounts"

Current limitations

A few practical limits to keep in mind.

  • WordPress taxonomy, category, tag, and richer block-editor controls are still thin.
  • WordPress media URLs must resolve to supported image or video types.
  • Publish interactions currently support only post steps.

Related routes

Related use cases and workflows.

Frequently asked questions

How does SocialClaw connect WordPress?

Connect the WordPress.com or Jetpack-connected site through the hosted SocialClaw OAuth flow, then reuse the site target from the same workspace. The connection is stored in the workspace so scripts, agents, and the dashboard reuse the same account state.

What can I publish to WordPress with SocialClaw?

SocialClaw publishes WordPress posts or pages through one explicit WordPress provider. WordPress supports up to twenty remote media assets per post or page. SocialClaw uploads remote media into WordPress and embeds it into the published content.

What should I check before scheduling WordPress posts?

Inspect publish settings such as postStatus, postType, slug. WordPress taxonomy, category, tag, and richer block-editor controls are still thin.

Use WordPress through one hosted SocialClaw workspace

Connect the account once, validate before apply, and keep post plus run inspection in the same workspace used by the dashboard, API, and CLI.