Skip to content

Webhooks

A webhook tells your own systems the moment a post goes out. Each time a post publishes, Sharek sends its details to an address you choose: an n8n workflow, a script on your server, anything that accepts an HTTP request.

Not on every plan. The Webhooks tab in Settings appears only when your plan includes webhooks. See pricing.

When a post publishes on a channel the webhook covers, Sharek sends one POST request to the webhook’s URL, with Content-Type: application/json. The body is a JSON array that holds the post that just went out:

[
{
"id": "post-id",
"content": "<p>Our new release is out</p>",
"publishDate": "2026-09-01T10:00:00.000Z",
"releaseURL": "https://x.com/your-handle/status/1234567890",
"state": "PUBLISHED",
"integration": {
"id": "channel-id",
"name": "Sharek on X",
"providerIdentifier": "x",
"picture": "https://example.com/avatar.png",
"type": "social"
}
}
]
Field Description
id The post’s id in Sharek, the one the public API uses.
content The post text as Sharek stores it. Text written in the composer arrives as HTML, such as <p>…</p>.
publishDate When the post was set to go out, in UTC.
releaseURL The link to the live post on the platform.
state PUBLISHED.
integration The channel it published on: its id, its name on the platform (a name you set with Rename channel does not appear here), providerIdentifier for the platform, such as x or linkedin-page, its picture, and type, which is social.

A few things to plan for:

  • One request per channel. A post to three channels is three posts in Sharek, so each one sends its own request as it publishes.
  • Threads arrive once. For a post with replies, Sharek waits until the whole thread is out, then sends the first post only.
  • Only posts that publish. A post that fails sends nothing.
  • Best effort. Sharek sends each request once. It ignores your server’s answer and never retries, so a delivery missed while your server was down stays missed. A failed delivery never affects the post.
  • No signature. The request carries no secret or signature, so anyone who has the URL can send your server a request that looks the same. Keep the URL private and hard to guess.
  1. In Sharek, open Settings, then the Webhooks tab. Settings covers the other tabs.
  2. Click Add a webhook. The Add webhook window opens.
  3. Give it a Name you will recognize, and paste your endpoint’s address into URL. It must be a public HTTPS address: http:// addresses, localhost and private network addresses are refused.
  4. Keep All integrations to hear about every channel, or choose Specific integrations and pick the channels. Here, integrations means your channels.
  5. Click Send Test to check the address, as described below, then click Save.

Save and Send Test stay greyed out until Name is filled in, URL holds a valid address and, with Specific integrations, at least one channel is picked.

After Save, check that the webhook shows in the list with the address you gave. If it does not, Sharek refused the address: it is not a public HTTPS address Sharek can reach.

Send Test sends a fixed sample to the address in URL, so you can try an address before you save it. The sample is an array of two made-up posts, one on Instagram and one on Facebook, in the shape above. A real delivery carries one post: yours.

Sharek shows Webhook send as soon as you click, whether or not your server got the request, so check on your side that it arrived. If nothing arrives, the address was refused by the same rule as Save, or your server does not accept a POST there.

The tab lists your webhooks with their Name and URL.

  • Edit opens the window again as Update webhook, with every field as you left it. Change what you need and click Save.
  • Delete asks first. Confirm with Yes, delete it! and the webhook stops receiving posts at once.

How many webhooks you can add depends on your plan. The tab’s heading shows how many you have next to how many your plan allows. At the limit, Save on a new webhook opens You’ve reached your webhook limit instead. Deleting a webhook frees its place. See pricing.

  • n8n: start a workflow with n8n’s Webhook trigger node and set its HTTP Method to POST. To try it, paste its Test URL into URL, select Listen for test event in n8n, then click Send Test; n8n takes the test request only while it listens. Once you publish the workflow, edit the webhook and paste its Production URL instead. The n8n instance must be reachable over public HTTPS. To act on Sharek from the same workflow, add the Sharek node.
  • Your own server: any HTTPS endpoint that accepts a JSON POST will do. Read the array, and use the post’s id with the public API to act on it, for example to read its analytics.