Webhooks

​

When to use webhooks vs other integrations

​

Events

​

Where to find it

• Create form at the top — name, events, and URL.
• Webhooks table below — every webhook you’ve created, with its status, events, created date, and actions to edit or delete.

​

Step 1 — Stand up an endpoint

• A route in your own app (Express, FastAPI, Rails, Laravel — anything that speaks HTTP).
• A serverless function (Cloudflare Workers, AWS Lambda + API Gateway, Vercel Functions).
• A no-code receiver like webhook.site for testing — generate a unique URL, paste it in, fire a test event, and inspect the body.

​

Step 2 — Fill in the create form

1. Webhook Name — a label you’ll recognize later (e.g. CRM enrichment, Internal dashboard). It’s only shown inside Carousify.
2. Events — click the dropdown and tick any combination of Post Scheduled, Post Published, and Post Publish Failed.
3. Webhook URL — paste the HTTPS endpoint from Step 1.

On non-Enterprise plans, Create Webhook opens an upgrade modal instead of saving. Reach out to Support if you’d like to talk through pricing.

​

Step 3 — Trigger a test event

1. Open New Post and draft anything — even one line of text.
2. Schedule it for a minute or two from now.
3. Within seconds you’ll see a Post Scheduled request hit your endpoint. When the scheduled time arrives, you’ll see Post Published (or Post Publish Failed if LinkedIn rejected it).

​

Request shape

{
  "event": "post.published",
  "timestamp": 1715072400000,
  "data": {
    "id": "65f8b2a14d9c3e0011223344",
    "workspaceId": "65a1f0c8d9b34e0099887766",
    "userId": "6593a4b8e1f234001a2b3c4d",
    "accountType": "profile",
    "accountId": "ACoAAB12Cd3EfGh4IjKlMn5OpQrStUvWxYz6789",
    "content": "We just shipped link tracking for every published post...",
    "title": "",
    "media": [
      "https://cdn.carousify.com/uploads/abc.png"
    ],
    "status": "published",
    "postUrn": "urn:li:share:7196543210987654321",
    "utmCampaign": "",
    "postingTime": "2026-05-07T10:30:00.000Z",
    "createdAt": "2026-05-07T09:55:12.000Z",
    "updatedAt": "2026-05-07T10:30:04.000Z"
  }
}

​

Field reference

​

Responding to a delivery

• Reply with 2xx quickly. Acknowledge the webhook first, then queue any heavy work (CRM lookups, AI calls, database writes) to run asynchronously. Holding the request open while you do that work makes deliveries slow and risks timeouts.
• Make handlers idempotent. Use data.id plus event as a dedupe key — if the same (id, event) pair shows up twice, treat the second as a no-op. Retries on transient failures are normal across any webhook system.
• Don’t trust the source IP. Pin authenticity to a shared secret in the URL instead — e.g. https://yourapp.com/hooks/carousify?token=... — and reject requests where the token doesn’t match.

​

Managing existing webhooks

​

Troubleshooting

• No requests arriving at my endpoint. Confirm the URL in Carousify ends in https://, the endpoint is publicly reachable (curl it from a laptop, not localhost), and the webhook status is Active. Schedule or publish a post to fire a fresh event.
• Endpoint returns 200 but I don’t see the data. You’re likely reading the wrong field. Carousify always wraps the post under data — log the full body before parsing.
• Endpoint times out, then receives duplicate deliveries. Expected — those are retries. Make your handler idempotent (see above) and shorten its response time by deferring work to a queue.
• “Create Webhook” opens an upgrade modal. Webhooks aren’t included on your current plan. Use the Slack or Zapier integrations in the meantime — both cover the same events.
• Receiving events for posts I don’t expect. Webhooks are workspace-scoped. If you’re managing multiple clients via separate workspaces, each one needs its own webhook configured.

​

What’s next