Tools
Under App Blueprint → Tools, GenieForge stores the secure actions your app can run: create a record, call an API, calculate something, or trigger a side effect. You describe what must happen for each role; GenieForge decides how tools fit that outcome.Where it lives
App Blueprint → Tools. Tools are part of the shared blueprint and are available in every project of that app. Data they read or write is still project-scoped.How to verify
- Open the tool under App Blueprint → Tools.
- Confirm allowed roles, Requires approval, and Always runs as a background job when that matters for the workflow.
- If it imports a library, Libraries lists that library and the helper names the tool uses.
- Preview as the intended role and run the action from the screen or flow that should use it.
- If it works as owner but fails as a customer role, check Access and the tool’s roles, then retry Preview as.
- For background or API-driven runs, confirm success in Executions.
Limits and notes
- Auto-generated model tools (one per database table) always ask for approval on delete. Custom tools use the optional Requires approval setting.
- Some custom tools are marked Always runs as a background job. Calling one returns a task id immediately. Watch progress under Executions. Those tools cannot power public intake or a page data source.
- Parameter formats such as email, phone, URL, date, datetime, and UUID are checked before the tool runs. Matching form fields get the same checks in the browser.
- Do not paste API keys into chat. Store them under App Settings → Connections → Environment Variables and let Build use those names.
- Code tools can carry a deterministic test suite. Open the tool page, then the Tests tab, to see the suite source, last run, and run history. Prefer putting shared coverage on a library. See Tests.
- A page or tool can analyze an uploaded photo (project file) with a chat model you choose. That is separate from generating an image. See App files vs project files.