CAAL Tool Registry & Tool API are live! 🚀

[cmac86]

CAAL Tool Registry & Tool API - Share Your Tools

v1.5.0 introduced the CAAL Tool Registry - a community-driven platform for sharing voice-optimized tools. Think of it as an app store for CAAL capabilities. Browse, install, and share tools directly from the CAAL frontend.

What's New

Browse & Install Tools

Open the Tools panel (wrench icon) to browse community tools by category. Click Install, fill in your variables and credentials, and the tool is live - CAAL discovers it instantly.

Share Your Tools

Built a useful workflow? Click Share on any custom workflow in your Installed Tools tab. CAAL sanitizes the workflow locally in your browser - strips API keys, parameterizes your URLs, nullifies credentials - then walks you through submitting it to the registry. Your secrets never leave your network.

An automated reviewer checks your submission and posts feedback on the PR. If everything looks good, it gets merged and is available to every CAAL user.

CAAL Tool API

We've formalized how tools are built, shared, and installed into the CAAL Tool API. This covers:

• Tool Spec - How to structure workflows for voice (webhook descriptions, response format, tool suites)
• Registry - How tools are packaged and distributed
• Submission Pipeline - How tools get reviewed and published
• Install Flow - How tools get imported into your n8n instance

Tool Builder Prompt

If you're building tools with Claude Code, Gemini CLI, OpenCode, or any AI coding tool, check out the CAAL Tool Builder Seed. It's pre-loaded with all the conventions so your AI assistant builds tools that work with CAAL out of the box.

Tools in the Registry

We're just getting started. Here's what's available now:

Tool	Category	Description
Weather Australia	Utilities	Forecast and current conditions for any Australian city (community - @AbdulShahzeb)
Weather Canada	Utilities	Forecast and current conditions for any Canadian city
Google Tasks	Productivity	Get, add, complete, and delete tasks
Google Calendar	Productivity	View, create, and delete calendar events
Google Contacts	Productivity	Search contacts by name
TrueNAS	Homelab	System status and app control
Radarr	Media	Search and add movies
Sonarr	Media	Search and add TV shows
ESPN NHL/NFL/NBA/MLS/F1/EPL	Sports	Scores, schedules, and standings
Notion	Productivity	Create and manage tasks

How to Contribute

Share from CAAL

1. Build and test your workflow in n8n
2. Open Tools panel > Installed tab
3. Click Share on your workflow
4. Review the security dialog
5. Fill in the submission form
6. Done - automated review runs within minutes

Option for buildings tools: Use the Tool Builder Seed
Point your AI coding tool at the builder seed and describe what you want. It'll generate a workflow following all the conventions. Then you can share that tool to the registry!

What Tools Do We Need?

Anything you find useful! Some ideas:

• Smart Home - Specific device control, automations, sensor readings
• Media - Jellyfin, Plex, Overseerr, Lidarr
• Homelab - Proxmox, Docker, Pi-hole, Unraid, Portainer
• Productivity - Todoist, Obsidian, Slack, email
• Social - Discord, Telegram, X/Twitter, Reddit
• Utilities - Weather for other regions, currency conversion, package tracking
• Developer - GitHub, GitLab, CI/CD status

If you don't know how to build a tool but have an idea, request it.

Video Coming This Week

I have a video dropping this week that walks through the full architecture - the registry, submission flow, and how tool calling works end to end.

Looking forward to seeing what you all build.

[AKA-Twizzler]

I know you said that this is really early development/edge case of this stage of the Tool api, but im a bit confused by certain things.

How do i create n8n workflows now compared to how we used to create them inside of n8n?
Apologies if i missed instructions somewhere, im a bit confused by how you have this setup now.

When i was using opencode before, i was using a wrapper for Claude Code to redirect to opencode so it would create the files, i did update my setup to match what you have now but i might have to go back to my original update (i have a backup).

[cmac86]

Hey @AKA-Twizzler,

Good questions and apologies for the confusion. My brain may be moving faster than my explaining. I need to keep people along for the journey better.

The video releasing this Friday will explain how this works and will be easier to understand than reading a long post or a wiki. Let me try though:

Nothing changed about how you create workflows - the Tool API and Tool Registry are additions, not a replacement. The Tool API defines how tools should be structured (ideally) and the Tool Registry houses the tools that are shared to the community.

Building tools (same as before):

• Build directly in the n8n editor, OR
• Generate workflow JSON with any AI coding tool (Claude Code, OpenCode, Gemini CLI, etc.)
• Use the create workflow, workflow and ask CAAL to build your tool. Just point it at the updated builder seed:

The https://github.com/CoreWorxLab/caal-tools/blob/main/prompts/caal-tool-builder-seed.md is just a prompt you can feed to your AI tool so it knows CAAL conventions. You don't have to use it - it just helps avoid common mistakes and should spit out tools that follow the Tool API conventions.

The workflow that CAAL calls to build other workflows is a convenience thing but if you’re already using a coding agent like OpenCode, Claude Code or Gemini CLI. You can build workflows directly with that coding agent. Then upload and have the agent test them with curl commands. (I think I should do a video on how I’m doing this.)

What's new:

• Registry - browse and install tools other people built
• Share - submit your tools to the registry from the CAAL frontend
• CAALBot - automated PR review for submissions

Your OpenCode setup should still work exactly the same. Build the workflow however you want, test it in n8n, then optionally share it to the registry if you want others to use it.

What specifically is tripping you up? Happy to clarify.

cmac