SocialClaw
GitHub Dashboard
Embedded SaaS

Embed a hosted social publishing layer without rebuilding account connection and delivery state.

SocialClaw fits embedded SaaS products that want one workspace identity, one connection hub, hosted media URLs, validate-before-apply behavior, and inspectable publishing state behind a hosted API.

Start free View pricing
Best for Embedded SaaS Use SocialClaw as the hosted social publishing layer inside another SaaS product while customer account connections stay in one workspace.
Includes Dashboard, CLI, and API The current product is strongest for one workspace identity and API-key execution, not for multi-seat approvals, agency switching, or advanced team-permission flows.

Why this workflow fits SocialClaw

One workspace, one connection hub, and one publishing layer.

Workspace model One workspace identity Customers sign into the dashboard with Google, resolve a workspace, and create workspace API keys that the product can use for hosted calls.
Connection hub Customer account connections stay in SocialClaw OAuth and manual connection state live inside SocialClaw so the embedded product does not have to reimplement provider auth and token storage.
Hosted media Public media handoff Media can be uploaded into the workspace and reused through hosted public URLs when providers require URL-based delivery.
Publish flow Validate, apply, inspect The hosted API exposes validate, apply, post inspection, run inspection, analytics snapshots, and workspace health for product and support flows.
Operator visibility Jobs and connection health Support teams can inspect connection health, job queues, usage, and publish state without inventing a second status surface.

How the workflow runs

Connect accounts, upload media, validate posts, then publish.

Step 1

Let the customer create a workspace key

The customer signs into the dashboard with Google, resolves the SocialClaw workspace, and creates or copies a workspace API key.

Step 2

Connect customer accounts once

Account connection happens through SocialClaw so the embedded product can reuse stored publish targets rather than storing provider auth itself.

Step 3

Upload media or reuse hosted URLs

If the workflow needs public image or video URLs, upload them through SocialClaw first so the publish payload can reuse the workspace-hosted asset.

Step 4

Validate before creating work

Use the hosted validate endpoint or CLI validation to catch provider-specific limits before the product commits a schedule.

Step 5

Apply schedules or draft campaigns

Create scheduled work or staged draft runs from the same workspace, depending on whether human review happens before publish.

Step 6

Inspect runs, jobs, and health for support

Read run status, post details, connection health, jobs, and usage when the embedded product or support team needs operational visibility.

CLI and HTTP examples

Example commands and requests for this setup.

CLI flow Embedded SaaS example 
socialclaw login --api-key <workspace-key> --base-url https://getsocialclaw.com
socialclaw accounts list --json
socialclaw accounts capabilities --json
socialclaw validate -f embedded-schedule.json --json
socialclaw apply -f embedded-schedule.json --idempotency-key tenant_launch_1 --json
socialclaw runs inspect --run-id <run-id> --json
HTTP API flow Hosted SocialClaw endpoints 
curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"provider":"linkedin_page"}' \
  "https://getsocialclaw.com/v1/connections/start"

curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -F "file=@./launch.png" \
  "https://getsocialclaw.com/v1/assets/upload"

curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d @schedule.json \
  "https://getsocialclaw.com/v1/posts/validate"

curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d @schedule.json \
  "https://getsocialclaw.com/v1/posts/apply"

curl -sS \
  -H "Authorization: Bearer $SC_API_KEY" \
  "https://getsocialclaw.com/v1/runs/<run-id>"

Relevant provider coverage

Integrations that usually fit this setup best.

LinkedIn Page LinkedIn page or organization

SocialClaw keeps LinkedIn page connection, native media upload, validation, and post inspection under the same workspace used by your dashboard, CLI, and API.

OAuth LinkedIn pages support one video or up to twenty images per post.
Open integration
Instagram Business Page-linked professional or business account

SocialClaw keeps account connection, hosted media URLs, schedule validation, and Instagram Business publish execution in the same workspace used by your dashboard, API, CLI, or agent workflow.

OAuth Instagram Business requires one image or one video per post and does not support text-only posts in the current flow.
Open integration
Facebook Pages Facebook Page

SocialClaw keeps Facebook Page connection, media handoff, schedule validation, and publish execution in one hosted workspace instead of splitting them across separate tools.

OAuth Facebook Pages support feed posts plus one effective image or video per post.
Open integration
WordPress WordPress.com or Jetpack-connected site

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.

OAuth WordPress supports up to twenty remote media assets per post or page.
Open integration

Related workflows

More routes that fit the same setup.

Audience workflow
LinkedIn page scheduler for embedded SaaS Use SocialClaw as a LinkedIn page scheduler for embedded SaaS products with workspace account storage, native media upload, and inspectable publish state.
Publishing API
Instagram Business publishing API Use the SocialClaw workspace API and CLI to connect Instagram Business, validate schedules, upload media when needed, and inspect publish state.
Publishing API
Facebook Pages publishing API Use the SocialClaw workspace API and CLI to connect Facebook Pages, validate schedules, upload media when needed, and inspect publish state.

Operator notes and limits

A few practical limits to keep in mind.

  • The current product is strongest for one workspace identity and API-key execution, not for multi-seat approvals, agency switching, or advanced team-permission flows.
  • Provider-specific media and settings rules still apply to every embedded schedule.
  • An active trial or paid plan is required for API execution.

Frequently asked questions

Can an embedded SaaS keep customer social connections in SocialClaw?

Yes. SocialClaw is intended to hold the workspace identity and connected account state so the SaaS can call the hosted API instead of rebuilding connection storage.

Does SocialClaw host media URLs for embedded flows?

Yes. The workspace can upload media and reuse the returned publicUrl when the provider requires a public asset URL at publish time.

What operator surfaces exist for support teams?

Support teams can inspect run status, post details, analytics snapshots, workspace health, connection health, jobs, and usage through the hosted product surfaces.

Start with the Embedded SaaS workflow

Create the workspace, connect accounts once, and keep validation plus delivery state inside the same hosted product.

Start free View pricing