Read your Hashnode publication and docs, then publish changes as approved steps.
Connect Hashnode and Luumen can read your publication the way you would: posts, series, single articles by slug, user profiles, and documentation projects. Changes — a comment, a reply, a new content block, a custom domain on a docs project — are previewed first and held for your approval by default. Authentication uses an API key.
67 tools: 17 read, 50 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Hashnode run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — hashnode accept publication invite, hashnode add comment, hashnode add content block, hashnode add custom mdx component, and more — is shown as a plan and requires approval by default, including the 10 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Hashnode — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.