Guides

1Brain

Connect your 1Brain in the hub, then let Claude look up your procedures, see 1Brain on your business map, and let your automations and AI agents read and write your policies, procedures and training. Everything the 1Brain node in n8n can do, and when to use it.

1Brain, from Business Blueprint, is where your business keeps its systems: policies, procedures (SOPs), training courses, quizzes and acknowledgements. Awesomate connects it to Claude, to your business map and to your automations: Claude can answer "what are the procedures for this role?" with a link to each page, your map shows which 1Brain Departments sit in each of its departments, a workflow can turn a form into a draft procedure, and an AI agent can answer your team's questions from your own procedures. 1Brain stays the home of every procedure: Awesomate reads it live and keeps no copy.

#Is it on your account?

1Brain is reaching accounts one by one. If it is on yours, you will see 1Brain in the hub under Settings, Integrations. If it is not, Claude says so in one line and does not offer it.

Where things stand today. 1Brain's connection for Claude and automations runs on 1Brain's development server (dev.1brain.io). The everyday 1brain.io (and staging.1brain.io) do not offer it yet, so for now a connection reaches the development server, not the 1Brain your team signs in to each day. The 1Brain node is in the automations of accounts on the newest Awesomate n8n, and reaches every account with the next update.

#Connect 1Brain

Connect my 1Brain to my automations.

1. In the hub, open Settings, Integrations and find 1Brain.
2. Click Connect 1Brain. You sign in on 1Brain's own page and tick the 1Brain accounts to allow. Awesomate never sees your 1Brain password.
3. Back in the hub you see who you are signed in as, the 1Brain accounts you allowed, and the credential "1Brain - ", now in your automations for the 1Brain node. The hub keeps it current; nobody copies a token.

Some things to know:

• Each person connects their own 1Brain. The owner and team members with full access can each connect. A connection sees exactly what that person can see in 1Brain, and nothing more. The card also shows who else on your account has connected.
• Connecting switches on Let Claude Code work with your automations (in Settings, Privacy): that is what lets the hub put the credential in your automations.
• To allow another 1Brain account, click Connect again and tick it.
• Disconnect forgets your sign-in and removes your credential, so any automation using it stops reading 1Brain. 1Brain has no way for us to withdraw its permission ourselves, so the hub links each 1Brain account's own settings page where you remove it.
• "Your automations don't have the 1Brain node yet" means your connection worked but your automations are on an older n8n. The credential is added as soon as the node arrives.

#The ways to use 1Brain

To add 1Brain's own connector to Claude Code, run claude mcp add --transport http onebrain https://dev.1brain.io/mcp, then /mcp in Claude Code to sign in. In Claude.ai, add it under Settings, Connectors as a custom connector.

#What you can ask Claude

What are the procedures for the front desk role?

How do we handle a refund? Show me the procedure.

Add our onboarding folder to the front desk role.

Write up how we close the shop at night as a draft procedure in Operations.

Claude looks these up with awesomate_onebrain, through your own 1Brain login, so it sees exactly what you can see in 1Brain. Answers end with a link to every page used. A procedure Claude writes always goes into 1Brain as a draft for you to review and publish there.

Build me an agent that answers my team's questions from our procedures in 1Brain.

When someone fills in our "new process" form, turn it into a draft SOP in the Operations department.

Every Monday, email me the 1Brain pages still sitting as drafts.

Our old 1Brain workflows stopped working. Can you fix them?

Claude checks that 1Brain is on your account and that the node is in your automations, finds your credential with awesomate_n8n_inspect, then writes, tests and switches on the workflow through your own n8n's MCP server, the usual way (see Automations). The awesomate-onebrain and awesomate-n8n skills hold the details (Skills).

#1Brain on your business map

Once 1Brain is connected, your business map (Business map in the hub) shows it:

• Your business is a 1Brain category. Pick the category that is this business (Your procedures in 1Brain, then Pick the 1Brain category). Claude can list your categories and suggest the link too.
• 1Brain Departments sit in your map's departments. Each 1Brain Department (Marketing, Sales, Finance and the rest) goes in one department of your map, and optionally one of its sub-departments. Each starts where its name suggests; change any of them under 1Brain Departments. Inside Awesomate they are always called 1Brain Departments, so they are never mixed up with your map's own departments.
• Each department lists its systems, live from 1Brain, each linked to its page in 1Brain.
• Each role lists its 1Brain systems: the pages and folders someone in that role must know. Add from 1Brain finds them; they are also tagged job:<role> in 1Brain so your team sees it there. If 1Brain does not let you tag a page (you cannot edit it), it is still on the role, with a warning sign that says why. If 1Brain stops partway (too many requests in a minute), what was added stays added and the rest stays ticked to add again. The list is knowledge only: it gives nobody access to anything.
• Search 1Brain from the top of the map.

Claude reads the same from awesomate_onebrain: every role with its 1Brain systems (roles), and the 1Brain Departments in one of your map's departments with their pages (department_systems). When you ask, it takes a page or folder off a role (unlink_role); the job:<role> tag stays on it in 1Brain, which has no way to remove a tag.

Everyone sees 1Brain through their own login: someone who has not connected 1Brain sees a Connect 1Brain link instead. Only the owner changes the category and the 1Brain Departments directly; anyone else's change, and Claude's, is a suggestion the owner accepts from Tasks.

#Onboarding: a 1Brain course for each role

When onboarding is on for your account, Business map, Onboarding builds a 1Brain course for each role from that role's 1Brain systems, and a starter course for everyone joining from one 1Brain Department or folder. An Owner who is a 1Brain owner or admin builds them, and picks whose 1Brain checks training each morning. Start someone's onboarding with the starter course and the roles they are about to hold: each course becomes a Task for them, and their own page shows how far they have got. When they have passed every quiz and acknowledged every page, the person they will report to gets a Task asking whether to hand the role over. Finishing a course changes nobody's access by itself.

Build the 1Brain course for the front desk role.

Start Kai's onboarding with the starter course and the front desk role, finished by the end of the month.

Claude does this with awesomate_onebrain (onboarding, build_course, start_onboarding with roles), on the key of an Owner. Nothing is changed in 1Brain when someone starts: share each course with them in 1Brain.

Check everyone's training now. Kai's plan says it can't find him in 1Brain: his 1Brain login is kai@example.com.au.

Claude can also make your own 1Brain the one that checks training (set_reader, when you're a 1Brain owner or admin), check everyone's progress now instead of waiting for the morning (check_onboarding), match a plan to the person's 1Brain login when the hub couldn't (link_member), and show your own plans (my_onboarding). With your yes, it stops a plan (close_plan) or moves one onto a role's newer course (move_plan, where their progress is read again from the new course).

#How Claude and your automations treat 1Brain

• Drafts first. Anything written to 1Brain goes in as a draft. Publishing is a separate step you ask for. (1Brain on its own publishes by default; the node does not.)
• Your words, never invented ones. 1Brain does not write content. A procedure is written from your notes, documents or answers; a missing step is left as a question for you, not filled with a guess.
• Many pages at once are confirmed. Before writing or publishing more than one page, Claude says how many, where, and whether as drafts, and waits for your yes.
• Every answer links its sources. An answer built from 1Brain ends with links to the pages it used. When nothing matches, the answer says so.
• The 1Brain account is always named. If you belong to more than one, each step says which one it works in.
• Your permissions, not more. Automations and agents see and change only what the connected person can in 1Brain. An agent answering for a supervisor never sees more than that supervisor.
• 60 requests a minute per person, shared by every workflow and agent on that person's connection. The node waits and tries again when it hits the limit.

#What the 1Brain node can do

The node is 1Brain in n8n: CUSTOM.oneBrain, and CUSTOM.oneBrainTool when it is a tool on an AI Agent. New nodes are version 2.

Credentials. Authentication Access Token (the default) uses the oneBrainApi credential the hub makes for each person who connects. Authentication OAuth2 (oneBrainOAuth2Api) has n8n sign in to 1Brain itself, for n8n instances Awesomate does not manage. The base address is https://dev.1brain.io until 1Brain's everyday site offers the connection.

Search options: Limit to Department, Limit to Folder, and Include Content (adds each result's page text, one extra request per result). Each result has its title, type, status and link (url).

The dropdowns load live from your 1Brain: accounts, categories, departments (shown as "Category / Department", because category names can repeat), folders (searchable), and the list of tools for Tool, Call.

Writing SOPs. If a category has no business description yet (what the business does, who its customers are, where it works), the SOP steps stop and ask for one. SOP Save also asks which template to follow: 1Brain's, or your own.

When something goes wrong, the node says so plainly:

#Your old 1Brain workflows

If you used 1Brain in automations before, those workflows open with the new node as version 1: Page, Search, with your account and search words kept and the page text added to each result, as before. Two things change:

• Reconnect. Choose your "1Brain - " credential. Old credentials cannot reach 1Brain's new connection.
• Tags are gone from search. 1Brain's search can no longer filter by tag, so an old step with tags set stops with a clear message instead of searching your whole account. Remove the tags, or use Limit to Department or Limit to Folder.

Claude can do both for you, testing a copy before your live workflow changes.

#What it can't do yet

• Read or remove tags. Tags can be added to pages, but 1Brain does not yet return them, search cannot filter by them, and they cannot be removed through the connection. So the hub keeps each role's list of systems itself, and taking a system off a hat leaves its tag in 1Brain until someone removes it there.
• Delete or move pages, folders, departments or categories. Do that in 1Brain.
• Act as the business. Every connection is a person, so an automation acts as whoever's credential it uses.
• Courses, quizzes, acknowledgements or publishing from the Awesomate MCP. Use 1Brain's own connector, or a workflow with the 1Brain node.