npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-sofia-post

v0.1.3

Published

Sofia for n8n: publish, schedule and follow your social media posts from any workflow.

Readme

n8n-nodes-sofia-post

Publish, schedule and follow your social media posts with Sofia from any n8n workflow.

Installation · Credentials · Operations · Example · Compatibility · Resources

Installation

Follow the installation guide in the n8n community nodes documentation, with the package name n8n-nodes-sofia-post.

Credentials

The Sofia API credential takes a personal key:

  1. In Sofia, open Settings › API › Personal access and create a key. It starts with sofia_pk_live_.
  2. In n8n, create a Sofia API credential and paste the key in Personal Key. Leave API URL as is.

One key acts for you on every Workspace you belong to, so one credential reaches all your establishments. If Sofia refuses the key (it was revoked or deleted), create a new one and paste it in the same credential.

Operations

Sofia

  • Post › Create: publish now, schedule, or save a draft on one or several connected accounts. One post goes to each chosen account, with the same text. Media are public URLs separated by commas; .mp4, .mov, .webm and .m4v are sent as videos, anything else as images. Schedule At is read in the workflow's time zone.
  • Post › Get: read a post and the state of each network. An unknown post returns no item.

The output of a post carries its id, status, platforms, the first permalink, every network's refusal on one line in errors, and the detail of each network in targets.

Sofia Trigger

  • Post Published: a post went live on at least one network.
  • Post Failed: a network refused a post, even if others published it.

The trigger polls Sofia. It starts with the posts that appear after the workflow is activated: posts published before are not replayed. Fetch Test Event shows the latest post so you can map its fields. Choose an establishment to watch only that one.

Example

A workflow that schedules a post on Instagram and Facebook, then reads its state.

1. Create the post

Add a Sofia node, choose Post › Create, and fill it in:

| Field | Value | | ------------------------------- | ------------------------------------------------------------ | | Establishment Name or ID | Bistrot Lumiere | | Account Names or IDs | Instagram — @bistrot_lumiere, Facebook — Bistrot Lumiere | | Text | Fresh pasta is back on the menu this Friday. | | Additional Fields › Media URLs | https://example.com/pasta.jpg | | Additional Fields › Schedule At | 2026-11-13T11:30:00 |

Establishment and Accounts are dropdowns filled from Sofia; Accounts lists the networks connected to the chosen establishment. Leave Schedule At empty to publish now, or turn Draft on to save the post without publishing it.

The node returns one item:

{
  "id": "pst_01HZX4T9M2",
  "status": "scheduled",
  "establishmentId": "est_01HZX4R7K8",
  "createdAt": "2026-11-10T09:12:44.000Z",
  "scheduledAt": "2026-11-13T10:30:00.000Z",
  "platforms": "instagram, facebook",
  "targets": [
    { "platform": "instagram", "accountId": "acc_01HZX4S1A1", "state": "scheduled" },
    { "platform": "facebook", "accountId": "acc_01HZX4S1B2", "state": "scheduled" }
  ]
}

scheduledAt is the instant Sofia will publish at: here 11:30 in a workflow whose time zone is Europe/Paris.

2. Read the post

Add a second Sofia node, choose Post › Get, and set Post ID to {{ $json.id }}. Once the post is out, the item carries the link and what each network answered:

{
  "id": "pst_01HZX4T9M2",
  "status": "partial",
  "establishmentId": "est_01HZX4R7K8",
  "createdAt": "2026-11-10T09:12:44.000Z",
  "scheduledAt": "2026-11-13T10:30:00.000Z",
  "platforms": "instagram, facebook",
  "permalink": "https://www.instagram.com/p/DCxyz123/",
  "errors": "facebook: the page is no longer connected",
  "targets": [
    {
      "platform": "instagram",
      "accountId": "acc_01HZX4S1A1",
      "state": "published",
      "publishedAt": "2026-11-13T10:30:05.000Z",
      "permalink": "https://www.instagram.com/p/DCxyz123/"
    },
    {
      "platform": "facebook",
      "accountId": "acc_01HZX4S1B2",
      "state": "failed",
      "error": "the page is no longer connected"
    }
  ]
}

partial means the post went live on one network and was refused by another; a post that every network accepted is published.

3. React to a result

Start another workflow with a Sofia Trigger node on Post Failed, and connect it to a Slack or email node with a message such as {{ $json.platforms }}: {{ $json.errors }}. The trigger emits the same item as Post › Get, once per post.

Compatibility

Built and tested against n8n-workflow 2.x, with n8n nodes API version 1.

Resources

This package is built from the Sofia monorepo and published from this repository by GitHub Actions, with an npm provenance statement.