Skip to content

Automate Sharek with n8n

n8n connects Sharek to everything else you run. A new row in a sheet becomes a scheduled post; an RSS item becomes a draft your team reviews. No code, and no polling script to keep alive.

Sharek publishes its own n8n community node, so on self-hosted n8n this is a handful of clicks rather than a set of HTTP Request nodes you maintain yourself.

Both routes use your Sharek API key. Not on every plan. The Developers tab, where the key lives, appears only when your plan includes the public API. See pricing.

  1. In n8n, open Settings, then Community nodes, and select Install. If no community node is installed yet, the button reads Install a community node.

  2. Enter the package name:

    n8n-nodes-sharek
  3. Tick I understand the risks of installing unverified code from a public source, then select Install. A node called Sharek then appears in the node panel.

n8n Cloud cannot install the Sharek node yet, but its built-in HTTP Request node can call the public API directly, with the same API key.

  1. Add an HTTP Request node. Under Authentication, choose Generic Credential Type, then Header Auth as the Generic Auth Type, and create a new credential.

  2. In the credential, set Name to Authorization and Value to your Sharek API key, from the API Key card described in authentication. Paste the key on its own, with no Bearer in front of it.

  3. Set Method to GET and URL to the address below, then run the node. The node sends this request, and {"connected": true} means the key works:

    GET https://dash.sharek.app/api/public/v1/is-connected
    Authorization: your-api-key
  4. Point the node at the operation you need, at its address under /public/v1. For an operation with a body, such as creating a post, turn on Send Body, set Specify Body to Using JSON, and paste the body from that page.

  1. Add a Sharek node to a workflow and create a new Sharek API credential.

  2. In API Key, paste your Sharek API key. Get it from Settings, then Developers, then the API Key card in Sharek, as described in authentication. Paste the key on its own, with no Bearer in front of it.

  3. Leave Host as it is. It already points at the right place:

    https://dash.sharek.app/api
  4. Save. n8n tests the credential as it saves, by calling GET https://dash.sharek.app/api/public/v1/is-connected. A green test means the key works.

Seven operations:

Operation What it does
Get Channels Lists your connected channels with their ids
Create Post Drafts, schedules or publishes a post to one or more channels
Get Posts Lists posts in a date range, optionally for one brand (the Customer field takes the brand’s id)
Delete Post Deletes a post by id
Upload File Puts media in your library and returns its reference
Generate Video Generates a video
Video Function Fetches values a video generator needs first

Each one calls one public API operation: Get Channels is list channels, Create Post is create a post, Get Posts is list posts, Delete Post is delete a post, Upload File is upload a file, Generate Video is generate a video and Video Function is video provider functions. Those pages are the detail behind each one.

The node also works as a tool for n8n’s AI Agent node. Connect it as one of the agent’s tools and the agent runs these operations itself, for example scheduling a post it has just written.

The shortest useful workflow is two nodes.

  1. Add a Sharek node and set the operation to Get Channels. Run it. You get your channels back with their ids, which confirms the credential works and gives you the id for the next step.

  2. Add a second Sharek node set to Create Post. Set Type to Schedule, put a future ISO 8601 date in Date, then add one entry under Posts: the channel id from step 1, and your content.

  3. Run the workflow, then open the calendar in Sharek. The post is sitting there.

The rest of Create Post:

  • Short Link is off by default. Turn it on to replace the links in your content with Sharek short links, so clicks are counted.
  • Tags sits on Create Post itself, so one set of tags covers the whole request. Group sits inside each entry under Posts; leave it empty for a new post. A value there names an existing post’s group, and that post is replaced: the old one is deleted, as over the API. Sharek gives every new post a group of its own.
  • Each entry under a post’s Settings has a Key, a Value Type and a value. Value Type is String unless you change it to Number, Boolean or JSON; pick the one the setting expects, and JSON for an object or a list.

Once that works, replace the manual trigger with whatever should really start it: a schedule, a webhook, a new row, a new RSS item.

Media has to be in Sharek before a post can use it, so put an Upload File step in front of the post.

Upload File reads binary data from the incoming item rather than a path, and the Binary Property field names which one to read, usually data. So the step before it has to produce binary: an HTTP Request node downloading the image, a Read/Write Files from Disk node, or whatever your trigger already provides.

Take the id and path the upload returns into the post’s Images entry, as its ID and Path. The path must end in .png, .jpg, .jpeg, .gif, .webp or .mp4, or Create Post is refused, as over the API. A path on your own machine never works, because Sharek publishes only media it can fetch.

  • The credential test fails. Check the key first. If you changed Host, it should end at /api with no /public/v1 and no trailing slash.
  • 401 on every operation. The response’s msg says why: a wrong or rotated key, a key pasted with Bearer, or an organization with no active subscription. Authentication lists each one. Check the key against the API Key card.
  • Upload File errors about binary data. The incoming item has none, or the Binary Property name does not match what the previous node produced.
  • Create Post is rejected. A platform setting is missing for that channel. Each channel’s settings page is linked from the channels Sharek offers.
  • Posts go out at the wrong time, or at once. Date is read as UTC when it has no offset, and a date already past publishes straight away. If a post never publishes, check that Type is not Draft.