n8n + Korfix: Three Workflows That Work Out of the Box

n8n has everything to connect services: triggers, branching, schedules, hundreds of nodes. What it doesn't have is a place for your data to live. Most workflows either move data in transit or hit Google Sheets as a "database" that isn't really a database.

Korfix fills exactly that gap. It's storage with typed catalogs, a REST API, and MCP — the data layer n8n lacks. Here are three workflows that show the combination in action. Each is self-contained: paste your token and it runs.

Korfix as data layer for n8n

There are two ways to connect to Korfix from n8n.

HTTP Request node. Korfix has a REST API: /api/db/{catalog} with an Authorization: Bearer <token> header. Any HTTP Request node reads and writes records directly. The token is in your Korfix panel → /db/api → create a token with the permissions you need.

MCP node. If the workflow includes an AI agent, Korfix connects as an MCP server — the agent reads and writes catalogs itself using db_read / db_insert tools. Your personal MCP address is in your account settings.

In the examples below, direct operations use HTTP Request — the most explicit path. MCP node setup is covered at the end.

The token defines what the workflow can do with your data. For a workflow that only writes to the Applications catalog, give the token access to exactly that catalog and exactly write permission. Minimum rights — fewer consequences if the token leaks.

---

Workflow #1. Telegram bot → record in Applications catalog

A client messages the bot — the application shows up in Korfix. No form, no spreadsheet, no manual transfer.

Nodes in order:

1. Telegram Trigger — fires on incoming message to the bot.
2. Set — maps the message to fields: name (message text), contact (sender username), source = telegram.
3. HTTP Request — creates a record:

POST https://vibe.korfix.info/api/db/applications
Header: Authorization: Bearer {{ $env.KORFIX_TOKEN }}
Body (form-data):
  name     = {{ $json.name }}
  contact  = {{ $json.contact }}
  source   = telegram
  submit   = 1

1. Telegram — replies to the client: "Request received, we'll be in touch."

The Applications catalog (applications) is a catalog with typed fields. Create it once: name — text, contact — text, source — select, status — select. Every application lands there structured, not as a chat string.

---

Workflow #2. New record → Telegram notification

The reverse direction. Someone added a record to the catalog — you find out immediately, with details.

Nodes in order:

1. Schedule Trigger — every 5 minutes (or a afterSave webhook if the catalog supports it — then instant).
2. HTTP Request — fetches recent records:

GET https://vibe.korfix.info/api/db/applications?filter[status]=new&order_by=date&order=DESC
Header: Authorization: Bearer {{ $env.KORFIX_TOKEN }}

1. IF / Filter — cuts out already-processed ones (compare against the last seen id).
2. Telegram — sends to your chat: "New application: {{ $json.name }}, contact {{ $json.contact }}".

This shows why field types matter. The status field is a select with a fixed value set, and status=new always means exactly one thing. In a table where status is free text, that filter will eventually miss something.

---

Workflow #3. Daily report at 9:00

Every morning — a catalog summary in Telegram. How many applications since yesterday, how many in progress, how many closed.

Nodes in order:

1. Schedule Trigger — cron 0 9 * * *.
2. HTTP Request — pulls the full catalog:

GET https://vibe.korfix.info/api/db/applications?limit=999
Header: Authorization: Bearer {{ $env.KORFIX_TOKEN }}

1. Code — counts by status: new, in progress, closed; sums whatever is needed.
2. Telegram — sends the formatted report text.

The same pattern scales: a sales report, a task report, any catalog. Only the catalog name in the URL and the counting logic in the Code node change.

---

How to set up the MCP node in n8n

If your workflow has an AI agent (AI Agent node), Korfix connects to it as a data source via MCP — and the agent decides itself what to read and write.

1. In your Korfix account open settings → MCP, copy your personal MCP address.
2. In n8n add an MCP Client node (or connect the MCP server to the AI Agent node as a tool).
3. Set type to SSE and paste the copied address.
4. Done — the agent sees tools for working with catalogs.

Now workflow #1 can be rewritten without manual field mapping: the AI Agent receives the message text and places it into the Applications catalog itself, figuring out what's the name, what's the contact, what's the gist. n8n stays the orchestrator; data understanding goes to Korfix.

---

The bottom line

n8n is good at connecting services, but bad at storing data. Korfix gives n8n a proper data layer: typed catalogs, REST API, MCP. A Telegram bot writes applications to a catalog, catalog changes arrive as notifications, the morning report builds itself.

The three workflows above aren't demo for demo's sake. Swap in your catalog and your token — and they work.

---

Copy and run. Registration at vibe.korfix.info is free and requires no credit card. Create a catalog, generate a token in /db/api, import the workflow — your first automation on top of your own data will take less than an hour.

Back to blog