HackMD
for LuumenAI
Read team notes for context, and draft new ones as approved steps
Connect HackMD and your runbooks, incident notes, and team docs become context the agent can read directly. Ask what a procedure says, find the folder a postmortem belongs in, or check what is sitting in trash. When the agent writes a note, moves one to trash, or restores one, it shows you the change first and waits for approval.
The HackMD toolbox
8 tools: 5 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet AccountReturn the HackMD profile for the connected token and the teams visible to it.
- ReadGet NoteGet a note by ID, including its Markdown content.
- ReadList FoldersList all folders in the personal workspace, or in one team workspace when team_path is supplied.
- ReadList NotesList all notes in the personal workspace, or in one team workspace when team_path is supplied.
- ReadList TrashList soft-deleted notes in the personal workspace.
- WriteCreate NoteCreate a Markdown note in the personal workspace or a specified team workspace. Approval by default
- WriteMove Note to TrashSoft-delete a note by moving it to trash in the personal workspace or an explicitly selected team workspace. Approval by default
- WriteRestore NotesRestore one or more personal notes from HackMD trash. Approval by default
One prompt, start to finish
What a governed HackMD run looks like inside Luumen.
Questions
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 — create note, move note to trash, restore notes — is shown as a plan and requires approval by default, including the 1 action 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 HackMD — 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.
Often connected alongside
All integrations
ConfluenceSOPs and runbooks that become skills the whole team can run.
NotionRunbooks in Notion, followed and turned into skills.
SharePointRead SharePoint sites for context, then change files and permissions on approval.
Google DriveSearch Drive for the file you need, then write the change back as an approved stepPut HackMD to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.