AgentHub Help
Get a real client change through AgentHub.
Start with the complete path, then use the focused guides when you need one part of the workflow.
Complete your first client automation change
This guide takes an AI consultant or automation agency from an empty workspace to one verified client change and a published client brief.
Follow the quick startTask guides
Find the job you need to finish
Each page covers one task, how to confirm it worked, and the common ways it gets stuck.
Getting started
Add a client, workflow, and owners
This guide shows you how to create the minimum operating context AgentHub needs before you record a client request.
Read guideConnected tools
Connect your tools and assign client workflows
This guide shows you how to connect n8n, Make, Slack, Zapier, or HubSpot, bring only the records you need into AgentHub, and confirm each connection is working.
Read guideRequests and changes
Capture and review a client change request
This guide shows you how to turn a secure client-link submission, email, call, ticket, or selected Slack message into a formal change request without losing the original context.
Read guideRequests and changes
Record approval and verify a client change
This guide shows you how to move a request through authorization, implementation, and production verification without claiming more evidence than you have.
Read guideClient proof
Create, publish, schedule, and send a client brief
This guide shows you how to turn the operating record into a client-facing update while keeping draft generation, publishing, and delivery under human control.
Read guidePlan and access
Choose a plan and manage client capacity
This guide explains Free, Consultant, Agency, managed-client limits, and what happens to client records when a plan changes.
Read guideReference
What AgentHub does and does not do
AgentHub is the operating record for client automation changes. This reference explains the product boundary so your team and clients know which decisions remain human.
Read guideThe app and the guide do not match?
Tell us what you were trying to do. That is either a documentation gap or product friction we need to remove.