Add a client, workflow, and owners

Before you start

The client's name.
The name and platform of at least one live workflow you support.
The people responsible for the business outcome, technical implementation, and ongoing support, when known.

Create the client record

Open Clients and choose Add client. Only the client name is required. Add the website, industry, work you support, and primary contact when they help your team understand the account.

Internal notes stay inside the workspace. The primary contact can later be selected as the recipient of a client brief.

Add a client

Choose how to add client workflows

For the fastest start, add one workflow manually. From the client record, use the action menu and choose Add client workflow, or open Client workflows → Add client workflow.

Manual: best for one or two visual or code-backed workflows.
CSV import: open the client action menu and choose Import CSV for an existing inventory.
n8n or Make: connect the shared account first, sync its inventory, then assign individual workflows or scenarios to clients.

Important: A connection is not required to use AgentHub. Shared n8n and Make accounts can be connected before clients exist because consultants often run client and internal work in the same account.

Create the workflow record

Select the client, enter the workflow name, and choose the Runtime platform where the automation runs. Use Custom code / AI agent only when custom code or an agent is itself the running automation.

Add the workflow URL if you want a direct link back to n8n, Make, Zapier, or another runtime. Under Repository and deployment, add the source repository or deployment when they exist. These references are optional and do not grant AgentHub access.

Claude Code, Codex, Cursor, Copilot, and similar products are build tools, not runtime platforms. If Codex helped change an n8n workflow, choose n8n as the runtime and link the repository separately.

Only the client, workflow name, and runtime platform are required. Open Add operating context when purpose, business impact, trigger, output, schedule, systems, or tags will help later decisions and client briefs.

Add a client workflow

Assign the three ownership roles

Open the workflow record and assign Business owner, Technical owner, and Support owner. Use the person who currently owns the decision, not the person you expect to own it later.

If an owner is unknown, leave the gap visible. Do not invent an owner to complete the checklist.

Verify it worked

The client appears under Clients.
The workflow appears under both the client record and Client workflows.
The workflow ownership badge shows Owned when all three roles are assigned.

Common issues

AgentHub will not let me add a workflow

Create the client record first. Every client workflow must belong to a client, even when the automation account is shared.

A client contact is missing from the owner list

Add the contact to the client profile, then return to the workflow record. You can also assign a workspace member or external person.

I connected n8n or Make before adding clients

That is supported. Sync the account, then assign imported workflows to the correct clients as those client records are created.

I built or changed the automation with Claude Code, Codex, Cursor, or Copilot

Choose where the automation actually runs as the Runtime platform. Then link its repository and deployment when they exist. Do not copy source code or the AI conversation into AgentHub.

I do not know every owner yet

Leave the role unassigned. AgentHub should show the gap until the responsibility is real.