Before you start
- Permission to connect the external account and use its selected client records in AgentHub.
- An AgentHub client record before connecting Slack, Zapier, or HubSpot. n8n and Make can be connected before clients exist.
- The provider credentials or authorization described in the relevant step below. Never paste those credentials into a request, note, or client brief.
Choose the connection that removes duplicate work
Open Integrations. Your tools shows each connected account with its status and anything left to do; Add a tool lists the rest. Connections are optional. Add a client workflow manually when that is faster, and connect a provider only when its inventory, requests, alerts, or context will save repeated entry.
- n8n and Make: bring selected workflow or scenario inventory into client records. With setup reading on, answers can also explain how an assigned n8n workflow is set up.
- Slack: turn likely requests from selected client channels into drafts for human review.
- Zapier: route scoped Zapier Manager error and status alerts into one client record.
- HubSpot: add read-only company, contact, and deal context to one client.
Connect n8n and assign selected workflows
Choose Connect n8n. Enter the Public n8n URL and n8n API key, then choose Connect n8n. The URL must use public HTTPS on port 443; local and private addresses are blocked.
After verification, AgentHub opens Assign n8n workflows. Select only the workflows you support, choose an existing client or enter a new client name (owners and admins only), then use the assignment button showing the number selected. Unselected workflows are not imported.
Each time AgentHub lists your workflows (when you connect, open Assign n8n workflows, assign or refresh), n8n sends every workflow the API key can see, whole, including workflows you never assign, their settings and any code. AgentHub uses only each workflow's id, name, status and last change time, and the names and types of its steps, which steps are turned off and how they connect, and drops the rest. To limit which workflows n8n sends, create the key as an n8n user who can see only the projects you want AgentHub to see.
On Integrations, an n8n account with workflows not yet imported shows Assign workflows; once none are left it shows View workflows, which opens the same page. Use Refresh n8n to update workflows already assigned in AgentHub and surface newly available workflows.
So answers can explain how a workflow is set up, tick Also read how workflows are set up when you connect, or choose Turn on setup reading on Assign n8n workflows (owners, admins and operators). AgentHub then reads each assigned workflow when you turn it on, assign it or choose Refresh n8n, and keeps summaries: what starts it, the checks it makes, the fields it writes and the steps it runs. Earlier summaries stay as its history. n8n sends the whole workflow for a moment; AgentHub never reads, keeps or analyzes code, and withholds values in sensitive fields such as keys, emails and phone numbers. A sensitive value in a plainly named field can still be kept.
In a conversation about that client, answers can then explain the workflow and cite n8n setup, which opens the workflow's Setup tab. It is the configuration, not proof that the workflow ran or works. Under Setup reading, Turn off deletes what was kept and stops answers using it; answers already given stay. Disconnecting the n8n account deletes it too, including in a read-only workspace.
Connect Make and assign selected scenarios
In Make, create an API token with the scenarios:read scope. Copy it before leaving the token page. Make hides it afterward.
Choose Connect Make in AgentHub. Enter the Make zone shown in your signed-in URL, the numeric Team ID from the teamId value, and the Make API token.
After verification, AgentHub opens Assign Make scenarios. Select the scenarios you support, assign them to an existing or new client, and leave unrelated scenarios unselected. Return through Assign scenarios or View scenarios on Integrations, or use Refresh Make when the inventory changes.
Connect Slack and select client channels
A workspace owner or admin chooses Connect Slack on the Slack card on Home, or Authorize Slack on the Slack page under Integrations. Step 1 says what AgentHub does in Slack, what it reads and what happens if Slack is disconnected. Tick the confirmation and choose Continue to Slack, then allow AgentHub in Slack. AgentHub records who confirmed, when and the text they saw. An install started from Slack’s side comes back to this page first. Not now hides the Home card in that browser, for you and that workspace.
Step 3 links your own Slack account: choose Link my Slack account, send AgentHub any message in Slack and follow the link it sends, then choose Continue. You’re set offers Open AgentHub in Slack and, optionally, a client channel to watch: choose the channel and the client, tick the confirmation and choose Watch channel, or Skip for now.
To watch more channels later, invite the AgentHub Slack app to each client channel (type /invite @AgentHub in it), then reload the Slack page. For the exact channel, choose the AgentHub client, confirm your organization is authorized to process its new messages, and choose Monitor channel. After you add a client, one line on its page suggests the Slack step that fits, such as Watch their channel.
New likely workflow requests appear under Requests as drafts to review. Review, edit, and confirm a draft before it becomes a change request. Use Pause monitoring when AgentHub should stop checking that channel.
Slack is open to workspaces in the free Slack pilot, by invitation, for now. Outside the pilot, an owner or admin can choose Ask to join the Slack pilot on Home (unless hidden with Not now) or on the Slack page, or Ask to join on a new client’s page. It sends AgentHub your request and shows Request received. We’ll reply by email. Anyone can also write to info@agenthub.ai.
Create a scoped Zapier alert endpoint
On Integrations, choose Set up alerts on Zapier. On Receive Zapier alerts, select the client whose alerts AgentHub should receive, and choose Create alert endpoint. Copy the webhook URL immediately; it is shown only after creation or rotation.
In Zapier, use Zapier Manager → New Zap Error or Zap Turned Off as the trigger. Scope each trigger to the exact client folder or individual Zaps. Do not leave the Account, Folder, or Zap fields account-wide.
Add Webhooks by Zapier → POST and send JSON fields zap_name, event_type (zap_error or zap_turned_off), and optional zap_id, error_message, and occurred_at.
Connect HubSpot and confirm the client company
Choose Connect HubSpot, select the AgentHub client, and choose Continue to HubSpot. Review and authorize the read-only permissions HubSpot displays.
After authorization, choose the exact company under Choose the HubSpot company, then choose Confirm company and import. AgentHub imports only that company and its associated contacts and deals.
On Integrations, open Account details on HubSpot to see when each account was last imported and use Import again when the selected context needs to be refreshed. Before the first import, the account shows Import now.
Link GitHub and AI build evidence without a connection
GitHub, Claude Code, Codex, Cursor, and Copilot are not connected accounts in this release. Choose where the automation actually runs as the workflow's Runtime platform.
On the client workflow, add the repository or deployment link when one exists. On an in-progress change, use Implementation evidence → Add evidence for the pull request, commit, test, or deployment that documents the work.
Record the build tool when useful, but keep source code and AI conversations in their original systems.
Verify it worked
- The provider appears on Integrations under Your tools, and its account shows Connected. Anything left to do shows on its own line with the next action.
- Assigned n8n workflows or Make scenarios appear under the correct client and Client workflows; unselected inventory remains outside AgentHub.
- With n8n setup reading on, an assigned workflow's Setup tab shows its steps and when they were read.
- A selected Slack channel shows Active and the correct client under Filed under.
- Zapier shows Connected; a correctly scoped test alert creates or updates the expected client incident.
- HubSpot shows imported client context, and Account details on Integrations shows when it was last imported, with Import again.
- Repository and implementation links appear on the intended workflow or change without exposing source code or credentials.
Common issues
n8n does not show an API key option
n8n Cloud trials do not provide API keys. Use a paid Cloud plan or a self-hosted instance with the public API enabled.
AgentHub rejects my n8n URL
Use the public HTTPS base URL on port 443. Localhost, private network addresses, credential-bearing URLs, and non-HTTPS endpoints are blocked.
Make refuses the token or team
Confirm the Make zone, the numeric teamId from the signed-in URL, and a token with scenarios:read. Create a new token if the original value was not copied before Make hid it.
An answer says it has not read how an n8n workflow is set up
Setup reading must be on for that n8n account, and the workflow read since. Choose Refresh n8n on Assign n8n workflows. Answers also say when a workflow was read more than 7 days ago, its last refresh failed, or n8n no longer returns it.
An answer will not say what a whole n8n workflow does
It says that only when every step, and every workflow it runs, was read in full. Code steps, unsupported steps and what an HTTP request sends are not read. The workflow's Setup tab marks those steps Partly read or Not read.
n8n or Make connected, but no client workflows appeared
Connecting verifies the account but imports nothing by itself. Open Assign workflows or Assign scenarios, select the resources, and assign them to an existing or new client.
Slack shows no available channels
Invite the AgentHub Slack app to the exact client channel, then reload the page. AgentHub cannot select a channel it has not joined.
Slack is connected, but no drafts appear
Confirm the channel is active and mapped to the correct client. Only new messages classified as likely workflow requests appear under Requests as drafts to review.
A Slack channel shows Paused and has no Resume monitoring
AgentHub was removed from that Slack workspace, so it stopped monitoring the channel and deleted its Slack name. After Slack is connected again, choose the client on that channel, tick the confirmation, and choose Save channel.
“Slack can’t be used in this workspace right now.”
The workspace has Slack connected but cannot use it now: the free Slack pilot ended, there are more managed clients than the plan allows, the workspace is read-only, or it is not invited. The line under the heading says which. AgentHub isn’t reading Slack or answering there, and saved work stays. An owner or admin can still choose Disconnect Slack, and a linked account can still be unlinked with Unlink.
How do I disconnect Slack?
An owner or admin chooses Disconnect Slack on the Slack page. AgentHub says what stops and what stays; choose Disconnect Slack again, or Keep Slack connected. Saved work stays. Once Slack confirms, the page says Slack is disconnected and offers Connect again.
Slack says it is already connected to another AgentHub workspace
One Slack workspace connects to one AgentHub workspace at a time. An owner or admin of the other AgentHub workspace chooses Disconnect Slack there first; then connect it here.
Slack shows Disconnect not finished
Slack did not confirm that AgentHub was removed. AgentHub has already stopped reading the workspace's messages. An owner or admin chooses Retry disconnect on the Slack page. Until it finishes, no AgentHub workspace can connect that Slack workspace.
I no longer want AgentHub to hold a tool’s key
On Integrations, open the tool’s Account details and choose Disconnect beside the account (n8n, Make, HubSpot or Zapier; owners, admins and operators). The confirm page says what stops and what stays. AgentHub deletes its copy of the key at once; to be sure the key can never be used, also delete it in the tool, as the page says. Slack has its own Disconnect Slack on its page.
A Slack message says Not sorted
The workspace reached its limit for sorting Slack messages with AI. The message is still captured, unsorted, with its reason. Review it manually; sorting resumes as earlier use ages out.
A Zapier alert is missing or filed under the wrong client
Confirm the Zap uses the webhook URL created for that client, the trigger is scoped to the exact folder or Zaps, and event_type is zap_error or zap_turned_off. Rotate the URL if it may have been exposed.
An account shows Needs attention
Use the action on that account's line. HubSpot: Try the import again. n8n or Make: Review and refresh opens that account's list, where Refresh tries again. Choose Reconnect only when the credentials changed or were removed.
The HubSpot company is missing
Confirm the authorized HubSpot account contains the company and that your permissions allow it to be read. Reconnect HubSpot if the company list cannot be loaded.
Can I connect Salesforce?
Not in this release. Salesforce is listed under Not available yet. Add the automation manually, choose Salesforce Flow as its runtime platform, and use AgentHub for its requests, approvals, changes, verification, and client briefs.
GitHub or my coding assistant did not appear under Integrations
That is expected in this release. Add the workflow manually, link the repository or deployment, and attach durable implementation evidence to the change.