New: Composio-powered Actions connect your Pickaxe tools to any workflow

Releases & Features
1

We just shipped a big Actions update: Pickaxe can now talk directly to third-party apps through Composio connectors, and you can decide whether those calls run with your studio credentials or every end user’s own login.

:play_button: Video walkthrough:

Where to find it

Open any agent in the Builder, head to the Actions tab, and tap the Composio MCPs filter in the Actions Library to browse the new connectors.

696×630 39.4 KB

What’s new

  • Composio connectors in Actions – wire up Google Drive, HubSpot, Notion, DocuSign, Slack, and dozens more directly from the Actions tab inside every agent build.
  • Flexible auth – choose between workspace-owned credentials (best for internal automations) or prompt your end users to authenticate so Actions can run inside their SaaS accounts with scoped permissions.
  • Trigger logic + guardrails – give each Action a clear run condition (specific phrases, structured criteria, or every user request) and limit each agent to the 3–5 Actions that actually move the workflow forward.
  • MCP + automation stacks – the same connectors are available through our MCP integration, so you can pass control to Zapier, Make, or n8n whenever you want branching automations beyond a single API call.
  • Real-world example – the HubSpot lead-qualifier demo in the video walks through connecting via Composio, authorizing as an end user, and letting the Action create/score a lead inside HubSpot with zero manual handoff.

Scoped credentials example

When you add a connector like DocuSign you can decide whose credentials run it and limit the exact scopes/tools that Action can touch.

638×680 50.7 KB

Why it matters

  • Turn every Pickaxe into a true co-worker: research in chat, then push structured updates into the tools your team already lives in.
  • Sell higher-ticket portals: bundle specialized automations (e.g., “When my customer asks for a proposal, auto-generate the doc and file it in Google Drive”) as paid add-ons.
  • Stay in control: view connector status, scopes, and run logs right from the builder so you can prove what ran, when, and on whose behalf.

Give it a spin: open any agent, hop into the Actions tab, add a connector, and set a trigger. Ready to try it yourself? Jump into the Builder here!

If you run into edge cases (scopes, auth windows, etc.) drop a note below—we’re listening.

1 Like