Internal tools

STYD can power internal tools for your team through its API, which is included in every plan. These are often the most practical place to start.

Example internal tools

An internal dashboard with a question box that returns answers from your data.
An internal assistant for operations, sales, support or finance.
A workflow that asks a database or Odoo question and writes the result somewhere.
An email-assist workflow where STYD searches connected data and helps prepare a response.

These are generic patterns to build with the API. Adapt them to your own tools and data.

What you can use today

  • The API, with answers as structured data, plain text or an email-style reply. See API getting started.
  • Claude, for people who prefer to ask in an AI app. See Use STYD from Claude.
  • Make, with the STYD app. It is installed from an invitation link, because it is not in Make's public list yet. See Make.
  • n8n, with the HTTP Request node. A STYD node is not published yet. See n8n.
There are no built-in connectors for Slack, Teams or email. To put STYD inside one of those, build it on the API or see the catalogue of custom builds.

Build them safely

Respect workspace permissions: the tool sees what its workspace and key allow.
Keep API keys server-side and out of shared logs.
Plan for usage controls. Internal tools still use the workspace's prompts.
Validate important answers, and review what sensitive data the tool can reach.