postqueen has an n8n community node

n8n-nodes-postqueen is published on npm, at 0.2.17 as of this release. It is a community node: you install it into your own n8n, and postqueen shows up in the node picker alongside everything else you have wired together.

What shipped

n8n is already sitting in the middle of a lot of stacks. It watches an RSS feed, a form submission, a database row or a webhook, and then it does something. This node is the something. A workflow hands a post to postqueen, picks the channels and sets the time, and the interesting parts of your pipeline (the approval step, the translation, the image generation, the thing your team argued about for a week) stay exactly where you built them.

The advantage over calling the REST API from an HTTP Request node is mostly credentials and shape. The node stores your API key as an n8n credential, and the fields are laid out as fields instead of as JSON you assemble by hand in an expression editor.

How to install it

On a self-hosted n8n you install community nodes from the settings panel, or with npm if you manage the container's packages yourself.

# install the community node into a self-hosted n8n
npm i n8n-nodes-postqueen
 
# the n8n UI does the same job:
# Settings, Community nodes, Install, then enter the package name

Then add a postqueen credential with an API key from your account, cloud or self-hosted, and drop the node into a workflow.

One honest note about the version, written when this shipped: 0.2.17 was pre 1.0, deliberately rather than decoratively, because fields could still move between releases. That caveat has expired. The node reached 1.0 since, and the current release is 1.0.2. Pinning the version in a workflow you depend on is still good practice, but the field names are stable now.

Source, issues and requests for the next set of operations go to https://github.com/GkhanKINAY/postqueen-app