This is not going to be a big blog post. However, my smaller projects often get overlooked. A while ago, I published two n8n nodes as community nodes. One provides nodes for the PKM tool Capacities. The other tool allows n8n to communicate with the social media platform Bluesky.
I have given both projects another update (after quite some time).
Capacities (n8n-nodes-capacities)
Unfortunately, the Capacities API is still somewhat limited. I am trying to cover the existing API completely. One small search feature was still missing. Search queries can now filter by "structures". This is important if, for example, you want to search only for web links or only for pages.
Previously, you had to filter the results yourself in n8n.
You can also specify multiple structures.
n8n Bluesky Node (n8n-nodes-bluesky)
A feature that some users have wanted for a long time (GitHub Issue #9) is the ability to post images directly.
Previously, you could only add images to a post indirectly by loading them using "Fetch Open Graph Tags".
With the new update, you can now put image binary data directly into the Bluesky node.
Metadata can also be passed along, as you can see in the screenshot.
At first glance, this looks very simple. However, an image file must not be larger than about 950 KB. This means that images that are too large would cause an error. I chose an approach where the "sharp" library in the node resizes the image on the fly. I had already implemented this logic for the "Fetch Open Graph Tags" feature and was able to reuse it.
Also, when working with Bluesky through the API, you have to proceed in two stages. First, upload the image. Then create the post with the media ID of the uploaded image.
n98-magerun2
There is always something to do with n98-magerun2. There are no major features or developments here. However, there is always some maintenance to take care of. This month, for example, the GPG key used to sign the Phar files had expired and needed to be renewed. I have now created a reminder (and a short guide for myself) so that in two years, random GitHub Actions do not fail again with strange messages.
Another outstanding task was updating the "GitHub Superlinter" we use to version 8. I had to adjust some configuration for this.
And that is it for my little status update for October 2025. Let's see what November has in store.
As a small spoiler... I might publish something related to Adobe App Builder.