How to register custom tools and integrate Pipedream into the tool system when building a Flow

Hi Rowboatlabs team 👋

I’m working with your project and I’d like to add my own custom tools so that they can be recognized and used automatically when building a Flow.

Here are my main questions:

1. Registering custom tools
How can I make my own custom tools (for example, modules built as MCP-style tools) discoverable by the system so that they appear automatically in the tool list when creating a Flow?

Should they be placed in a specific directory (like packages/tools) or registered through something like a manifest file?

Is there a required structure for exporting functions or defining metadata so the Flow builder can recognize them?

2. Integrating Pipedream
Is it possible to make Flow search and list Pipedream actions (or similar services like Zapier) as available tools during flow creation?

If yes, what’s the setup or integration process for that?

Is there any roadmap or plugin mechanism planned for adding external tool sources like this?

My goal is to allow the Flow builder to dynamically use both internal and external tools (like MCP-based tools and Pipedream) without manually editing the core codebase.

Thanks for your amazing work 🙏
I’d be happy to open a small PR or test branch if it helps explore this integration.

The issue names no files, tests, or entry points. Start by mapping the Flow builder's existing tool-registration path and checking how internal tools are discovered; then investigate whether an extension point exists for MCP-style tools or external action providers. Done means documenting or implementing a defined registration and integration path for custom tools and Pipedream actions.

Written by the indexing model from the issue text.