Feature Requests

We have certain automations that require fields to be are not empty. Out of sheer convenience, people do an inline trigger of automation in the grid view by changing the status value. This causes issues as the automation does not fire because the required value wasn't provided. Would help to have a prompt to complete all required values or indicate it on the field name in the grid layout itself, if it is a required field. This will ensure automations aren't fired without required values being provided.

I feel this feature might be useful when there is a need for an AI workflow agent to read through a particular transcript, create a checklist of tasks to be done as a follow-up. This if created using the checklist field itself, makes it easy to assign tasks to different people as well.

Expanded Microsoft Teams Integration for Approvals & Notifications Business Need: Many approval workflows require reviewers to examine supporting documentation before approving or rejecting a request. Currently, Teams notifications do not provide direct access to attachments associated with the triggering record, creating additional steps for approvers and slowing decision-making. This challenge is especially significant for users who primarily work from mobile devices (also businesses that are IP fenced and unable to use the SmartSuite Mobile App) or do not always have immediate access to a company issued laptop. Without access to supporting documents directly from the Teams notification, approvers must navigate back to SmartSuite, making the process less efficient and reducing adoption automations for Teams-abased notification approvals/rejections. Requested Enhancements Attachment Support in Teams Notifications Add support for including record attachments in Microsoft Teams notifications through one or more of the following options: A configurable File and Image field within the Message Configuration section that can dynamically pull attachments from the Triggering Record or a Find Records action. Support for attachment links within the Message Content field, allowing users to open documents directly from Teams. Optional View Only permissions for shared files to prevent downloads when required by governance, compliance, or security policies. Enhanced Approval Actions Improve the approval experience by allowing additional response options beyond a simple Approve/Reject action: Rejection Reasons: Require or optionally prompt users to select a rejection reason before the Reject button is enabled. Single-select or multi-select options would both be acceptable. Examples: Missing supporting documentation Incorrect information Requires additional review Policy exception identified Other Request More Information: Provide a "More Information" action that allows the reviewer to specify what information is needed before a decision can be made. This would help streamline communication and accelerate the review process without requiring separate follow-up emails or messages. Expected Benefits Faster approval and review cycles. Improved mobile user experience. Reduced need to navigate back into SmartSuite. Increased adoption of Teams-based workflows and automations. More efficient approval, rejection, and information-gathering processes. Better auditability through structured rejection reasons and feedback. Improved user productivity and decision-making. As demonstrated in Artem's Teams integration tutorial ( https://www.youtube.com/watch?v=38LwpEY92ec ), adding attachment support within automated Teams notifications would significantly enhance the usability and effectiveness of approval workflows. This enhancement would transform Teams notifications from simple informational messages into actionable approval experiences, making it a highly impactful and valuable feature for organizations that rely on workflow automation and distributed approval processes. In short: This would be a critical feature that enables users to review, approve, reject, or request additional information directly from Teams while maintaining access to the supporting documentation necessary to make informed decisions. Increasing adoption of this integration feature while keeping SmartSuite as the system of record and source of truth by enabling users to take critical decision actions from Microsoft Teams.

We create tasks before work is to be started. These tasks are created via automations, but we cannot set the Start Date as it is not available.

Summary When using the “Link to open record” variable in an automation that includes a Merge Records action, the generated link in downstream steps (e.g., Send Email) points to the original triggering record—even if that record is deleted during the merge. This results in a broken link and creates an unusable output for end users. Current Behavior The automation trigger generates the “Link to open record” variable based on the initiating record. The Merge Records action retains the oldest record and deletes the duplicate (triggering) record. The Send Email step still uses the original variable, which now references a deleted record. As a result, the email contains a link that resolves to a non-existent record. Impact Produces broken links in automation-generated emails. Reduces user confidence in automated notifications. Limits the practical usability of automations involving deduplication. Forces users to manually locate the surviving record, reducing efficiency. Expected / Desired Behavior One of the following improvements would resolve the issue: The “Link to open record” variable dynamically updates to reference the surviving (merged) record. A new system variable becomes available, such as: “Link to merged/surviving record” “Final record after merge” The automation provides a post-merge record reference that can be reliably used in downstream steps. Proposed Enhancement Enhance automation variable handling so that workflows involving record merges can reliably reference the final record state after all actions are completed. Business Value Ensures accurate and actionable notifications Improves end-user experience and trust in automations Supports data quality workflows (e.g., deduplication) without breaking downstream actions Reduces need for manual intervention or workaround logic Use Case Example A deduplication automation merges duplicate records and sends a notification email. The recipient expects a working link to review the updated record, but instead receives a dead link because the original record was deleted during the merge.

Currently the Find Records action only has the "if no records are found" path option, and there's no inverse "if records ARE found, stop" option.

Please create a official SKILL.md file with knowledge about SmartSuite formulas. So we can upload skills in Claude, for example, and create formulas super easily.

We would like SmartSuite to provide a secure server-side Script Engine that allows administrators to create, manage, schedule, and run JavaScript scripts in isolated environments, so teams can automate custom business logic, data transformations, and external system interactions without deploying custom backend services.

We would like SmartSuite to support on-call scheduling with rotations, primary and secondary coverage, escalation paths, and notification routing, so incidents can be assigned and escalated automatically to the right responders at the right time.

Please consider adding an integration with CraftMyPDF for automated PDF document generation. CraftMyPDF allows users to generate PDF documents from templates and dynamic data. With a SmartSuite integration, users could automatically create invoices, contracts, certificates, proposals, reports, and other documents directly from SmartSuite records. This integration could allow users to: Generate PDFs when records are created or updated Map SmartSuite fields into document templates Save generated PDFs back to records automatically Automate document workflows without manual copy and paste This would be valuable for teams using SmartSuite to manage structured data and needing a simple way to generate professional PDF documents at scale.