add a documentation page for the n8n community node

[seebi]

Adds the missing documentation page for the n8n community node that shipped with Corporate Memory 26.2, and carries two changes that came out of writing it.

⚠️ Repository policy change: a page has three titles, and they need not match

This is the part that needs a second opinion, because it reverses a rule the repository has been enforcing.

.claude/docs-guidelines/repo-conventions.md stated:

The page title (# Heading) and the .pages nav title must correspond.

That is wrong. A page carries its name in three places, and each serves a different purpose:

Place	Purpose
the entry in the directory's .pages file	the label in the navigation menu
title: in the Markdown front matter	the site page title and the entry on the tags page
the # Heading at the top of the Markdown	the visible title rendered on the page

They legitimately diverge in both directions. A menu label competes for horizontal space and is read inside its section, so it is often shorter than the heading. The front matter title is often longer than the heading, because the tags page lists pages flat, stripped of the hierarchy that would otherwise say what a page belongs to — which is exactly why every cmemc page sets title: "cmemc: Installation" against a heading of Installation.

The consequence for anyone editing: do not "fix" such a divergence as if it were drift, and in particular do not rewrite a deliberately chosen .pages entry just because the heading says something else.

The new page is itself an instance of this:

.pages	n8n Integration — reads well next to Continuous Integration and Scheduling Workflows
title:	n8n: Corporate Memory Community Node — self-describing in a flat tag listing
# Heading	n8n Community Node

The corrected rule is recorded in both repo-conventions.md and CLAUDE.md.

The page

docs/automate/n8n-node/index.md — introduction, use cases, prerequisites, working mode.

• Use cases: event-driven workflow execution, publishing graph content to downstream systems, Knowledge Graph lookup inside a larger automation.
• Working mode: one credential, one node, three resources and their five actions, as a table using the action labels shown in the n8n node panel.
• Technical detail stays external. Installation, credential fields and per-action parameters live in the repository README, which the page links to.
• No version number appears on the page, so it does not age when the next npm release ships. The release note remains the version-stamped record.
• The credential prerequisite points at a dedicated Keycloak client scoped to what the automation needs, rather than at the broadly privileged cmem-service-account that the Power BI and Redash pages reuse. Worth a look — it is a deliberate departure from the existing precedent.

The screenshot is the one already published in the 26.2 release note.

Also in this commit: a fifth card on the Automate landing page, the integrations entry repointed at the page, the 26.2 release note pointed at the page instead of at npm, and an Integration tag mapping in mkdocs.yml.

Integrations entries rewritten in the imperative

The entries in data/integrations.yml addressed the reader directly ("You can send and receive messages", "your Knowledge Graphs", "files you created") and spoke for eccenca in the first person ("by using our Power-BI-Connector"), against style guide 3.2. Nine entries are rewritten.

Three unrelated defects in the same texts are fixed along the way: "and captures its output" (Kubernetes), "to user and groups" and "in you Mattermost" (Mattermost).

The template comment at the top of the file keeps its "you" — it addresses the author of an entry, not a reader of the page.

Notes for the reviewer

• task check passes on every commit.
• Two claims on the page could not be verified against a running instance and rest on the README and on the node's Verified badge: that the node installs on n8n Cloud as well as self-hosted, and the wording of the five action labels beyond what the screenshot shows.
• While mapping the Integration tag I found there is no md-tag--* CSS anywhere in the repo, so the value in extra.tags acts as a slug and no icon asset is needed. repo-conventions.md claims an unmapped tag "renders without an icon", which appears to overstate what this build does — left alone, not verified end to end.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DoyrnqQWXJBjPFqX1kj5cP

[github-actions]

Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
1 files   ±0   0 ❌ ±0 

Results for commit 286eb74. ± Comparison against base commit 7fa06a0.

♻️ This comment has been updated with latest results.

[rpietzsch]

LGTM