# Sekalum workflow idea – shown with n8n as example

**URL:** https://discourse.nodered.org/t/sekalum-workflow-idea-shown-with-n8n-as-example/101727
**Category:** Share Your Projects
**Tags:** function-node
**Created:** [3 September 2026 17:18 UTC](https://discourse.nodered.org/t/sekalum-workflow-idea-shown-with-n8n-as-example/101727 "2026-09-03T17:18:22Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![luiscyphre](https://avatars.discourse-cdn.com/v4/letter/l/c57346/32.png) [@luiscyphre](https://discourse.nodered.org/u/luiscyphre)
#### Post date: [3 September 2026 17:18 UTC](https://discourse.nodered.org/t/sekalum-workflow-idea-shown-with-n8n-as-example/101727/1 "2026-09-03T17:18:22Z")

</div>

Hi all,

I posted a few things about Sekalum here before, so just a short project update.

I made a small video to explain the basic workflow idea.

The demo uses n8n because there is already a native Sekalum node there. But the important part is not n8n itself.

The idea is:

**Discover available credentials → Resolve what is needed → use it for the next service**

For Node-RED this video is mainly an example of the concept. There is no dedicated Node-RED node at the moment.

I thought it may still be useful to show what I mean when I talk about Sekalum and runtime credential access.

Video:

> [https://youtu.be/FWSN5JfJ8dg](https://youtu.be/FWSN5JfJ8dg)

If someone sees a useful Node-RED use case for this, feel free to share it.