Tread Connection in n8n Agents

Updated October 9, 2026

n8n can run an AI agent on a schedule and let it call tools. Tread Connection is the JobTread tool. This page sets up one workflow that does two jobs for a contractor. Every Monday morning it posts who owes you money and for how long. Every weekday afternoon it posts which active jobs have no daily log from today or yesterday. Both are read only. Nothing is written to JobTread.

What you need
Set it up
Which tools it uses
Limits and cost
Changing it
Troubleshooting

What you need

A Tread Connection membership with JobTread connected (see Connect your JobTread account).
An n8n instance that has the AI Agent and MCP Client Tool nodes. n8n Cloud does, and so does a current self-hosted n8n.
An Anthropic API key (or swap the chat model node for another model), and a Slack workspace. Telegram, email or any other n8n output node works in place of Slack.
For the Monday receivables nudge, the owner's Tread Connection key. Receivables across all jobs is an owner-level tool. A key for a seat on your team will not list it, and the agent says so and stops.

Set it up

Download the template: tc-ar-nudge-and-log-gaps.json.
In n8n, create a new workflow, open the menu and choose Import from file.
Get your key at treadconnection.ai/my/access. In n8n, add a Bearer Auth credential and paste the key as the token. Select it on the Tread Connection MCP node. The template ships with a placeholder, never a key.
Add your Anthropic credential on the Anthropic Chat Model node, and your Slack credential and channel on Post to Slack.
Run each branch once by hand with Execute step on its trigger, read the Slack message, and check it against JobTread.
Publish the workflow. The schedules use Central time. Change the cron expressions on the two trigger nodes for your own hours.

The MCP node points at https://treadconnection.ai/mcp over streamable HTTP and sends your key as a Bearer token. If you would rather not store a key in n8n, use the node's OAuth2 option instead. Tread Connection supports OAuth sign-in for MCP clients, described in Other MCP clients.

Which tools it uses

Tool	Used for	Who can call it
`org_ar_aging`	Open customer invoices across all jobs, grouped by days past due, with a collection order.	Owner (admin) keys only
`my_jobs`	The list of active jobs.	Any Member key
`my_dailylogs`	The newest daily logs, to see which jobs have none.	Any Member key
`job_overview`	Available if you extend the prompt to drill into one job.	Any Member key

The node is set to expose only these four tools, so the agent cannot reach anything else, even though every Tread Connection tool a key can see would otherwise be listed. All four are read only. The daily log check only covers what your JobTread role can see.

Limits and cost

Every request to the MCP endpoint counts against your hourly limit, and that includes the setup calls n8n makes before the agent does any work. Member allows 100 an hour. One run of either branch uses roughly 4 to 6 of them. Two scheduled runs a day will never come close.
If you add more schedules or let the agent loop, you can run through the limit and your own assistants will be told to wait. The template caps the agent at 6 steps and tells it to call each tool once.
Your n8n instance pays for the model. n8n counts one scheduled run as one execution.
Each tool call reads from JobTread with your connected key, so a run also uses a little of your JobTread API budget.

Changing it

The two prompts live in the Task nodes. Edit them like any other text.
To send to Telegram, email or Teams, replace the last node. The agent's answer is in output.
Keep the line telling the agent to use only numbers the tools returned. It is what keeps the receivables message from guessing.

Troubleshooting

The agent says the key is not an owner key. org_ar_aging is missing from the key's tool list. Use the account owner's key for the Monday branch.
"No JobTread account connected." Connect JobTread first. See Connect your JobTread account.
A rate limit message. You used the hour's calls. Wait for the reset time it shows. Check that nothing else is looping on the same key.
The MCP node shows no tools. Check the URL is exactly https://treadconnection.ai/mcp, the transport is streamable HTTP, and the credential is a Bearer token holding your key.
n8n Agents are in preview. Node names and settings may shift between n8n versions. If an import complains, add the nodes by hand using the table above.

Docs · Privacy Policy · Terms of Service · treadconnection.ai