AgentHub keeps the operating record
AgentHub keeps a client's request, workflow context, owner, approval record, implementation note, verification result, scope reconciliation, and client brief attached to the same change.
Code-backed automations can include repository, deployment, pull request, commit, and test references. The durable artifact is recorded without copying source code or AI chat transcripts into AgentHub.
Its purpose is to reduce manual reconstruction across Slack, email, tickets, documents, and automation platforms.
People control every consequential decision
AI output and captured messages remain drafts until a workspace member confirms them. A person decides whether to file a request, record approval, mark implementation complete, pass verification, decide whether the result matches the recorded scope, publish a brief, and send it.
- Slack messages are not automatically filed as change requests.
- A suggested verification plan does not run tests or mark them complete.
- Publishing a brief does not email it.
- Scheduled briefs create private drafts and do not publish or send themselves.
Connected tools are optional and read-only or inbound
You can use AgentHub manually without connecting another platform. Connected tools reduce duplicate entry or bring selected signals into the record.
- n8n and Make: import workflow inventory, assign workflows to clients, and capture safe structural versions when supported.
- Slack: inspect only selected client channels for likely workflow requests that a person must review.
- Zapier: receive scoped manager alerts. Inventory import is separate.
- HubSpot: import read-only company, contact, and deal context for a client.
- GitHub: no account connection yet. Operators file repository and change evidence links manually.
AgentHub is not a workflow control plane
AgentHub does not run, pause, edit, deploy, or roll back connected automations. It records what should change, what was authorized, what a person changed in the source platform, and how the result was verified.
It is also not an uptime monitor, electronic-signature product, ROI measurement system, or replacement for n8n, Make, Zapier, Slack, HubSpot, or your ticketing system.
Missing evidence stays visible
A fingerprint can prove that recorded structure changed, but it cannot always explain the change. AgentHub labels partial comparisons, missing baselines, stale connections, and insufficient verification instead of converting them into certainty.
A complete change requires a passed verification result and a human-filed scope reconciliation outcome. Human judgment remains responsible for whether the evidence supports the result and whether the implementation matches the recorded scope.
Keep secrets out of records
Connected-service tokens are encrypted and kept server-side. Workspace records may contain private client information, including workflow and node names, so access remains workspace-scoped.
Repository URLs, deployment URLs, and artifact names may be private client information. Do not paste source code, AI chat transcripts, passwords, API keys, private keys, credentials, signed access links, or execution payloads into requests, evidence, or notes. Review the privacy notice for the current data-handling details.
Verify it worked
- Your team can explain that AgentHub records and coordinates client automation changes but does not execute them.
- Optional connections are used to reduce friction, not treated as prerequisites for the operating record.
- Approval, verification, publishing, and delivery each remain explicit human actions.
- Scope reconciliation records a human judgment and never presents an AgentHub inference as fact.
Common issues
Can AgentHub make the requested workflow change?
No. Make the change in the source platform, then record the implementation and verification in AgentHub.
Does AgentHub monitor every workflow for failures?
No. Supported connections can import inventory or selected alerts, but AgentHub does not provide a universal uptime guarantee.
Is an AgentHub approval an electronic signature?
No. A secure link can record the name and response supplied by the client, or an operator can record a decision that happened elsewhere. Neither is an electronic signature or authenticated identity proof.
Do I need to connect n8n, Make, Slack, Zapier, or HubSpot?
No. Connected tools are optional. Start with a real client, workflow, request, verified change, and published brief.
Does AgentHub connect to GitHub or my coding assistant?
Not in this release. Add the client workflow manually, choose where it runs, and file durable repository, pull request, commit, test, or deployment links. AgentHub does not ingest source code or AI conversations.
Can Ask AgentHub explain how to use the product?
Yes. Setup questions use the current Help Center and link to the full guide. Questions about your clients and work use only the records in your workspace and show the evidence used.