Feature Requests

I have a detailed report on this. Please note the attachment.

It would be great to be able to configure MCP server parameters at the level of each individual Solution. An admin could then choose which fields the MCP should be allowed to work with and which it should ignore, and could also provide descriptions explaining the meaning of individual fields as well as the purpose of the Solution itself and how it should be used. These settings would live in both the Solution settings and the field settings. At the same time, it would be great if the cloud MCP server were also available to cloud-based AI agents, without the need to run them on local devices.

Please add explicit trigger controls for AI Field Agents so users can choose exactly which field changes cause an automatically running Field Agent to execute. I originally understood the Run Automatically setting to mean the agent runs whenever any part of the record is updated. SmartSuite's current documentation clarifies that automatic runs actually occur when fields referenced in the AI Field Agent prompt change . That is useful behavior, but it creates a different limitation: fields used as AI context and fields used as execution triggers are currently the same thing. For example, an AI Field Agent might reference both: * Transcription — the source content that should cause the summary to regenerate * Helpful Instructions for the AI — additional context the AI should use Both fields need to be available to the prompt, but a user may want only Transcription to trigger an automatic run. There is currently no explicit setting to distinguish “use this field as context” from “run the agent when this field changes.” Ideally, AI Field Agent settings would include a Run when these fields change option that allows one or more trigger fields to be selected independently of the fields referenced in the prompt. It would also be useful to support trigger conditions such as: * Changes to any new value * Changes to a specific value * Becomes populated * Is cleared This would make AI Field Agent behavior more explicit and predictable, avoid unnecessary AI runs, and support more precise automated workflows. There is also a UX issue related to this. The current tooltip for Run Automatically says: “Allow AI to run automatically when a record is updated” That wording implies a record-level trigger, while the documentation says automatic runs are based on changes to referenced fields. At minimum, the tooltip should be updated to accurately describe the current behavior, for example: “Allow AI to run automatically when a field referenced in the prompt is updated.” Explicit trigger-field configuration would be preferable because it would allow prompt context and execution logic to be controlled independently.

The AI Field Agent feature is fantastic, but for now, we can only add an OpenAI key. It would be very helpful if we could also add API keys for other AI platforms (like Gemini, Azure and Anthropic). This is important for companies that already have a paid plan with a provider, as they need to know that their data will not be used for AI training or shared.

For using Smart Suite tables in local AI platforms to enhance company agent data sources. AI agents can work very well with more addtional context. Support a Pipe Delimited AI export (pipes make it easier to no confuse system with commas). Rows 1-5 in the export are for AI context. 1-Field Name 2-Field Unique ID 3-Field Help text (AI context for purpose) 4-Field Type (AI context for data types and structure) 5-Linked to Field Unique ID (if linked fields add this so AI can understand cross references) Data follows in all the rows. Would be option in export "AI Export Format" Would be great to have Pipe as option for both imortant and export for comma heavy data.

SmartSuite currently supports LLM completions but doesn't support invoking agents as far as I can tell; specifically Azure AI Foundry agents. This is a meaningful gap for enterprise customers who have already invested in building agents within Azure.

Need to disable some LLMs from being selected within the AI automations

Possibility to have Gemini as an option in AI control center for AI field agents

I wanted to share a product enhancement idea that could significantly accelerate solution building in SmartSuite, especially while your team continues developing AI-powered solution creation. The Concept: Schema-First Solution Building What if SmartSuite allowed users to define solutions through structured text/code (similar to YAML or JSON), which could then be imported to automatically generate the complete SmartSuite solution? Real-World Parallel: Home Assistant The Home Assistant ecosystem provides an excellent model for this approach. Users can define automations in two ways: Visual UI Builder - Point-and-click interface (like SmartSuite's current approach) YAML Code - Structured text that gets imported and rendered as the visual interface Here's a simple Home Assistant automation example: ```yaml automation: - alias: "Evening Lights" trigger: - platform: sun event: sunset offset: "-01:00:00" condition: - condition: time after: "16:00:00" before: "23:00:00" action: - service: light.turn_on target: entity_id: group.living _room Many users find it faster to write/copy/modify YAML code than to click through multiple UI screens, especially for similar automations or complex logic. How This Could Work in SmartSuite **For Solution Building:** ```yaml smartsuite_solution: name: "Project Management System" tables: - name: "Projects" fields: - name: "Project Name" type: "text" required: true - name: "Status" type: "single_select" options: ["Planning", "Active", "Complete"] - name: "Tasks" type: "linked_record" link_to: "Tasks" - name: "Tasks" fields: - name: "Task Name" type: "text" - name: "Assignee" type: "member" - name: "Project" type: "linked_record" link_to: "Projects" For Automations: ```yaml smartsuite_automation: name: "Task Assignment Notification" trigger: field_change: "Tasks.Assignee" action: send_email: to: "{{ trigger.field.new _value}}" subject: "New task assigned: {{Tasks.Task Name}}" ``` Key Benefits Speed - Experienced users can build solutions much faster through code Reusability - Easy to copy, modify, and share solution templates Version Control - Text-based schemas work well with Git and other versioning systems Documentation - Schema serves as living documentation of the solution structure AI Integration - AI could generate, validate, or suggest improvements to schemas Bulk Operations - Easy to make widespread changes across multiple tables/fields Implementation Approach Phase 1: Schema Import Define a SmartSuite schema format (YAML or JSON) Build an import function that creates solutions from schema files Support core elements: tables, fields, relationships, basic automations Phase 2: Bi-directional Sync Allow exporting existing solutions as schema files Enable round-trip editing (schema → UI → schema) Phase 3: AI Enhancement AI-powered schema generation from natural language descriptions Schema validation and optimization suggestions Template library with AI-categorized schema examples Why This Makes Sense Now While you're developing comprehensive AI solution building, this feature could: Provide immediate value to power users Serve as a foundation for AI-generated solutions Create a structured format that AI can work with more effectively Appeal to technical users who prefer code-based workflows The Home Assistant community loves having both options available - many start with the UI to understand the structure, then switch to YAML for speed and flexibility. Would love to discuss this further if it aligns with your roadmap.

Please give us a way to turn off the spacebar shortcut for AI in SmartDoc fields. The Document Designer does not recognize bulleted/numbered formatted SmartDoc lists, so in order to generate PDFs with numbered lists I have to manually enter list numbers in the Smartdoc field. Easy enough, except using the spacebar to indent items and defeat auto-numbering opens the AI menu. I spend way too much time entering a dummy character at the beginning of a line, entering the spaces and numbering I want, and deleting the dummy character to get the Document Designer output I need. The / menu is perfectly fine for the rare times I want to use AI and I would not miss the spacebar shortcut at all.