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. Open Main contact or More details when the contact, status, website, industry, work you support, or internal notes help your team understand the account. An owner or admin's new client starts as Onboarding unless they choose another status.

Onboarding, Active and Paused clients each use a managed slot on your plan. Only an owner or admin adds such a client, activates a prospect, or offboards a managed client. An operator's new client is saved as a Prospect, and an owner or admin activates it before work can start. Operators edit and work on managed clients as usual, including moving one between Onboarding, Active and Paused. On a new request, an import or a reuse form, only an owner or admin sees Add a new client.

The assistant uses the website (as text; it does not visit it), industry, work you support and the main contact’s name and title in that client’s conversations, files and request drafts. Internal notes and the contact’s email stay out of it. The main contact is preselected as the reader of client updates. If the save is refused, everything you typed stays, and a field that needs fixing opens with the cursor on it.

Add a client

Choose how to add client workflows

For the fastest start, add one workflow manually. On the client, open More client actions (the … button beside the client name) and choose Add a workflow, or open Workflows and choose Add a workflow.

Manual: best for one or two visual or code-backed workflows.
CSV import: open More client actions and choose Import workflows from 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.

Open Where the workflow lives to add the workflow URL, for a direct link back to n8n, Make, Zapier, or another runtime, and 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. Add What it does in a sentence when it helps. Open Add operating context when business impact, trigger, output, schedule, systems, or tags will help later decisions and client updates.

Add a client workflow

Assign the three ownership roles

Open the workflow and choose Name the owners, or open its Details and find Owners. 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 on the client's Workflows view and under Workflows.
The workflow shows Owners named on the client's Workflows view when all three roles are assigned.

Common issues

I cannot choose Active, or Add a new client is missing

New managed clients need an owner or admin. Add the client (it is saved as a Prospect) and ask an owner or admin to activate it. If a save is refused, what you typed stays on the page.

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.

Using a coding assistant such as Claude Code, Codex, Cursor, or Copilot?

You do not need to connect it. Choose where the automation actually runs as the Runtime platform. Then link its repository and deployment when they exist. No GitHub connection required: AgentHub stores links, not source code or AI conversations.

I do not know every owner yet

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