Current focus
Fewer steps in everyday client work
Our focus now is making it easier to capture client information, find what matters and prepare an update.
Public roadmap
See what we’re working on, what we’re exploring and what you can use today.
We’ll announce availability in Updates.
See what shipped, with datesCurrent focus
Our focus now is making it easier to capture client information, find what matters and prepare an update.
Next
Next is what follows the current focus.
Ideas we’re investigating. None of these is a promise.
Exploring agents that take on a recurring job for each client, such as preparing a brief before a weekly call. You review the result and decide what to share.
Good to know: Hosted agent execution is not committed. Infrastructure depends on repeated demand, paid pilot commitments and a scoped reliability and security design.Keep the state a workflow was in before an implementation so a rollback decision has evidence behind it.
Good to know: Under consideration; no delivery date is committed. Evidence only. AgentHub would not perform a rollback.Let a client see approved records and briefs without exposing the agency's full operating workspace.
Keep workflow inventory and client context current without widening what those connections can read or write.
Evaluate controlled actions from Slack after selected-channel intake proves useful and false-positive behavior is understood.
Let an agency mark which client workflows contain AI steps so review and verification can account for them.
Evaluate Salesforce as a source of client, owner, and business context after live usage identifies the actual demand.
Evaluate a scoped GitHub App that can attach selected pull request, commit, CI, and deployment metadata after manual evidence use proves the recurring need.
Good to know: No broad personal token, source-code ingestion, automatic verification, merge, or deployment control.Turn a prepared package into a public offer with an example result, requirements, support details and your chosen price.
Good to know: The marketplace is not open yet. Private workflows and AI skills can already be saved in the free library.Evaluate a listing, inspect its requirements and included support, and access a digital purchase. Marketplace participation will not require a client workspace.
Good to know: Not open yet.Participating consultants can review a buyer's short brief and propose scope and price. Accepted work can enter a client workspace with buyer consent. Service payments take place outside AgentHub.
Good to know: Not open yet. Creators choose which requests to accept and agree scope and price separately.Describe the service clients hire you for so a client can ask for a proposal. An agreed engagement becomes client work on the record.
Good to know: Not open yet. You can write and save your service page privately now.Available in the product. See Updates for what changed.
A redesigned Home, one page for each client, simpler onboarding, client updates in your voice and Settings on one screen.
Nothing is published or sent automatically.Turn on “Add items from my notes” for a schedule, and on the due date AgentHub suggests items from your notes. Review them, untick anything you don’t want, then prepare the draft.
Off until you turn it on. Nothing is published or sent automatically.Home lists the promises in your notes, who owes each one and when. Click Draft follow-up and AgentHub prepares text for you to review and send.
Only you see your promises. You send any follow-up yourself.Ask for an update in a client conversation, choose the items from your notes, and they appear in the draft as your report. Works for clients without workflows too.
Nothing is published or sent automatically. Your source conversations stay private.Turn it on for an n8n account, and answers about a client can explain how its assigned workflows are set up.
Off until an owner, admin or operator turns it on. Code is never read or kept, and turning it off deletes the summaries.In a client conversation, AgentHub can use what you told it in your other conversations with that client, and says where each item came from.
Only your own conversations with that client, never a teammate’s or another client’s.Ask for a Word document or an Excel workbook, revise it by typing, restore an earlier version, and share one version by private link.
AgentHub does not check that figures or wording are right for your client. Sharing sends nothing.Ask on Home, keep the conversation, and choose which parts to share into a job. Answers about your clients link to the records they used.
Advice is a suggestion, not evidence. The assistant does not run, change or check your automations.Invite people by email as a viewer, operator or admin.
Plans are priced by clients, not people.A brief reads as a letter in your name and colors: the summary in your voice, then the changes enclosed with who approved each one and how it was checked. The client opens it from a link with no account.
Written from the record. The consultant reviews every word before publishing; nothing is sent automatically.The library opens with workflows and AI skills from public repositories, each with its author and license, drawn as the item itself. Copy one into your library and start the next client from it.
Catalog items are copied as published, with their license. They cannot be sold on.Paste a client's email or Slack message. The title, who asked and when are read from it; you confirm the client, the workflow and where it runs, and the record exists.
Save workflows and AI skills with supporting files in your library. Review and export your package without a paid workspace subscription.
Include recorded approval attribution in new brief drafts, distinguish client-link responses from outside approvals recorded by the team, and show missing approval explicitly.
Private approval emails and response notes stay out of briefs. Existing frozen briefs are unchanged.Refresh the workspace and sign-in design, preserve first-change form details after a failed save, and clarify the handoff from completed work to a client brief.
Give each client a secure, reusable link for submitting change requests without creating an AgentHub account.
Submissions arrive as drafts for the consultant to review and confirm. They never approve scope, start work, or change the workflow automatically. The link can be shared through email, Slack, WhatsApp, or another messaging tool without building separate channel integrations.Forward a client email to your workspace address and it lands on Drafts to review with the sender, the date and the ask filled in. Same review-first path as Slack and the client link.
Freeze the exact requested scope in a secure 14-day link so a client can approve it or request changes once without an AgentHub account.
AgentHub creates but does not send the link. The record shows when the approval page was first opened successfully, not who opened it. Approval stops at Approved and never starts work. The record is not an electronic signature or authenticated identity proof.Require the operator to record whether the verified implementation matches the approved scope before a passed change can close.
The operator records a match, cites revised approval, or closes with a visible unresolved scope difference. AgentHub does not infer the result.Start with the request, select an existing client and workflow or create only the missing records inline, and open one formal Requested change in a single transaction.
Existing owners are preserved. No connector is required, and nothing is sent, approved, implemented, verified, or published automatically.Choose where a client workflow actually runs, optionally link its repository and deployment, and attach reviewed pull request, commit, test, and deployment references to the client change.
References are private by default and never replace human verification.Prepare private client brief drafts on an agency-controlled schedule, then let the consultant review, publish, and explicitly email the frozen link.
Nothing is published or emailed automatically.After a forward-only baseline is recorded, compare supported workflow versions and show safe structural differences on the linked change record.
Detection is not approval and does not change a live workflow.Turn the recorded request and available safe structural difference into a focused, editable verification plan on the change record.
The consultant still records the verification outcome.Manage clients, live workflows, ownership, requests, incidents, commitments, and evidence in one workspace.
Carry a client request through every accountable step on one record instead of across tools and memory.
Produce a client-facing brief from the recorded work and share a fixed copy of it.
Watch only the Slack channels an agency explicitly selects and place likely requests in a review inbox before any record is created.
Human confirmation remains required.Follow current guides for the first client change, setup, connected tools, approvals, verification, and briefs, or ask product and workspace questions from the same surface.
Help answers link to current guides. Workspace answers cite stored records. Unsupported or unrelated questions are not guessed.Connect n8n or Make once, then assign only selected workflows or scenarios to clients. Zapier alert intake stays client-scoped, while HubSpot supplies client context.
Unassigned n8n and Make resources are not imported.Workspace API keys, narrow client, workflow, and change-request endpoints, and published documentation of the supported boundary.
Get started
Keep using the tools that already run the workflow.
14 days free. Up to 3 clients. No card.
Questions first? Talk to us.