Skip to content
Integrations

Connect Publishly to the tools you already use.

Build posting into your own product, use a visual workflow, or let an approved assistant help. Every route ends with the same clear result: live, retrying, or needs your attention.

Quick answer

Publishly integrates through four surfaces: a public REST API with keys you can limit and revoke, a built-in MCP server for AI assistants, verified delivery alerts, and n8n and Make packages. The n8n and Make packages currently install from this codebase; no public marketplace listing is claimed yet.

REST API

Add posting to your product

Create and schedule posts, upload media, connect accounts, and read the result of every delivery.

API docs

MCP

Let an approved assistant help

The built-in MCP server lets a compatible AI assistant schedule posts and check results with only the permissions you approve.

Set up MCP

Webhooks

Send results to your own software

Your software gets an immediate, verified alert when a post advances, goes live, or fails — including the reason and retry decision.

Webhook reference

n8n

Build visual workflows in n8n

Publish, schedule, check account health, and start a workflow when a verified delivery alert arrives.

n8n node

Make

Build scenarios in Make

Use ready-made actions for posting, scheduling, receipts, and account health, plus a trigger for verified alerts.

Make app

Copy-paste proof

Ask for the receipt. Get the result.

After creating a post, replace POST_ID below with the ID returned by Publishly. The response shows each delivery step and the final live link when the platform confirms it.

curl — get a delivery receipt
curl https://your-publishly-host/public/v1/posts/POST_ID/receipts \
  -H 'Authorization: YOUR_API_KEY'

# response (trimmed to the delivery fields)
{
  "postId": "POST_ID",
  "latestStage": "confirmed_live",
  "receipts": [{
    "provider": "linkedin",
    "stage": "confirmed_live",
    "attempt": 1,
    "providerUrl": "https://www.linkedin.com/feed/update/urn:li:share:742…",
    "confirmationMethod": "linkedin_post_read"
  }]
}

See the complete create-and-check example

Everything on this page maps to working code in this repository. The API reference remains the source of truth for exact request fields and event names.