Actions

Actions is the live, searchable list of every tool method your operators can call. Built-in tools, MCP tools, and integration-provided tools all land in the same flat surface — one row per verb, grouped by provider.

The sidebar item lives under TEAM with three siblings: Operators (who), Skills (named recipes), Actions (verbs), Conversations (where it all happens).

Why a flat list

Tool catalogs grow fast. A real guild has 50-200 actions across 10-20 providers. A categorical UI (sub-menus, accordions per provider) makes you hunt. A flat, searchable list lets you find what you need in two keystrokes.

Three filters keep it manageable:

• Type — Built-in / Curated / Marketplace
• Active — only show actions wired to at least one operator
• Search — matches provider name, action name, description

What's on each row

A row is one action (a single tool method an LLM can call):

[icon] Send Reaction
       sendReactionTool
       React to the user's message with an emoji…
       [No operators linked] [Manage →]

Manage opens a sheet where you wire the action to operators or scope it to specific roles. Operators only see actions they've been granted.

Built-in vs Curated vs Marketplace

• Built-in — ships with Guilde. Browser, Canvas, Knowledge, Work Items, Web Research, Vault, Team Management, Design Kits, Self Capabilities, Agent Network, Routine Scheduler, Company Workflow, Content Creation, Guild Management. These are always available.
• Curated — first-party HTTP integrations Guilde maintains (Stripe, HubSpot, Linear, …).
• Marketplace — MCP servers and community packages. Install from Integrations and they appear here.

Wiring an action to an operator

Click an action row → Manage → pick the operators that should be able to call it. You can also wire by role (every operator with the SDR role gets these actions automatically) — see Members for role definitions.

Operators only run actions they're explicitly granted. The default for a new operator is the minimal essential bundle (the always-on universal set); everything else is opt-in.

What's next

• Integrations — installer for new actions
• Skills — named recipes that compose actions
• MCP servers — long-tail action sources