Skip to main content
Toolkits & Tools is the project-wide catalog of abilities your agents can use: send Slack messages, read Gmail, run your own scripts, and more. Open Toolkits & Tools. The page is scoped to the project — the same catalog is shared by every end user. Connecting an account or running a tool still uses the End user in the top bar.

​
Toolkit vs tool

Built-in catalog tools are available to the whole project. Tools and toolkits you create are marked Project and stay in this project.

​
Project vs end user

Creating or editing tools and toolkits is only available when the End user switcher is on the project default user (or you are a platform admin). Switch to Default user in the top bar if the UI blocks create/edit.

​
Browse and filter

  1. Search with Search toolkits or tools…
  2. Filter ownership: All or Project tools & toolkits (only what you created in this project)
  3. Filter type: All | Actions | Triggers
  4. Expand a toolkit and use tabs Triggers | Actions
Useful header links: Empty states: No toolkits or tools found. For project-only filter with nothing yet: No project tools or toolkits yet. with CTA Create toolkit.

​
Create a custom toolkit or tool

When create is allowed (default user selected): On a Create Tool form you typically set:
  • Slug, Name, Description
  • Toolkit ownership
  • Type: Action, Poll, or Webhook
  • Input/Output Parameters
  • Optional Custom script (JavaScript or Python)
  • No Authentication Required when the tool does not need a connected account
Per-row actions on project-owned tools (when allowed): Run, Create trigger, edit, Enable / Disable, delete.
Deleting a tool cannot be undone. Flowra removes it from all places where it is currently used (including agents that pinned it).

​
Auth and connections

  1. Toolkits declare how login works (OAuth, API key, no auth, …). Project auth configs live with shared project setup — see Projects and API keys.
  2. Each end user connects under Connection.
  3. Run or Create trigger asks for a Connected account — Select or connect account.
  4. On an agent, pin tools with Select Tools; bind accounts under Your accounts for testing when the editor asks.
If OAuth fails, check the End user switcher first — connections are per end user.

​
Attach tools to an agent

In Workflows & Agents, open an agent and go to Tools:
  1. Click Select Tools
  2. Use tabs Toolkits | MCP
  3. For toolkits, choose Normal (pin exact tools) or Meta (broader discovery) when offered
  4. Keep the set small — the product may warn when too many tools are pinned (hard limit is high; quality drops earlier)
MCP tools come from MCP in the dashboard, not from this catalog alone.

​
Tips

  • Prefer a small pinned set; use Meta when the agent should discover tools instead of you listing every slug.
  • Disabled or Deprecated tools cannot Run.
  • Switch End user before testing Slack/Gmail-style tools so you use the right connection.
  • After cloning a Marketplace template, reconnect accounts — templates do not bring OAuth tokens.
  • Custom create/edit needs Default user; testing OAuth often needs a named end user.