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 Connected tools. 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.
- 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, then use the assignment button showing the number selected. Unselected workflows remain outside AgentHub.
Return to Connected tools and use Assign workflows when you need to assign more. Use Refresh n8n to update workflows already assigned in AgentHub and surface newly available workflows.
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 use Refresh Make when the inventory changes.
Connect Slack and select client channels
A workspace owner or admin chooses Authorize Slack and completes Slack authorization for the agency workspace.
Invite the AgentHub Slack app to each client channel you want available, then reload the Slack connection page. For the exact channel, choose the AgentHub client, confirm your organization is authorized to process its new messages, and choose Monitor channel.
New likely workflow requests appear as drafts in Request inbox. Review, edit, and confirm a draft before it becomes a change request. Use Pause monitoring when AgentHub should stop checking that channel.
Create a scoped Zapier alert endpoint
Choose 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.
Return to Connected tools and use Sync when the selected HubSpot context needs to be refreshed.
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 under Connected accounts with status Connected.
- Assigned n8n workflows or Make scenarios appear under the correct client and Client workflows; unselected inventory remains outside AgentHub.
- A selected Slack channel shows active and the correct client under Filed under.
- Zapier shows Alert intake active; a correctly scoped test alert creates or updates the expected client incident.
- HubSpot shows imported client context and the connection row offers Sync.
- 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.
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 in Request inbox.
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.
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 as a future connection. 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 Connected tools
That is expected in this release. Add the workflow manually, link the repository or deployment, and attach durable implementation evidence to the change.