How an agent reaches your apps, your flows, and your systems
Tools are how an agent reaches the rest of your company, and it uses them two ways.To find out. It searches Slack, Linear, Drive, or any of 760+ apps at the moment it needs the answer, rather than working from whatever you pasted into the instructions.To act. It raises the invoice, drafts the document, updates the record.Attach none and it can only talk.
Piece tool
A single action from one of your connected apps.
Flow tool
One of your own flows, handed over as a tool.
MCP server
An external server, for systems that aren’t pieces.
You attach individual actions, not whole apps. An agent given Send message can post to Slack and nothing else.Each input on that action is one of three modes, so you pin what has to be exact and leave the rest to the agent.
Let agent decide
It writes the value.
Set value myself
You pin it.
Leave empty
Nothing is sent.
Pin the Slack channel, let the agent write the message.
The most underused one. When part of a job has to happen the same way every time, build that part as a flow and hand it over.The agent chooses the moment. The flow guarantees the steps.
Paste the URL and pick how it authenticates: none, an access token, an API key, or custom headers. Streamable HTTP, SSE, and plain HTTP all work.Activepieces lists the server’s tools as soon as you add it, so you know it works before an agent depends on it.
When an agent keeps getting something wrong, ask what it was missing. Usually it needed somewhere to look something up, not a longer prompt.
