Feature Requests

Automations' Advanced Logic building blocks, Conditional Logic and Repeating Actions (Looping), can now be nested inside each other, up to two levels deep. That unlocks multi-level workflows: a branch inside a branch, a loop inside a branch, a branch inside a loop, and a loop inside a loop. Process a set of records, loop over each one, and within each loop branch on a per-record condition, all inside a single automation. Available on all plans.

The Webhook Received automation trigger picks up per-field Required controls and a distinct Rejected run-history status. All fields in the webhook structure are non-required by default; toggle Required on the fields that truly matter, and requests that arrive without one of those fields return HTTP 400 to the caller (naming the offending field) plus a Rejected run in history, separate from Failed and Error. Non-required fields no longer break the whole run when missing. Incoming webhook payloads are now captured in Run History as an expandable tree (parsed and raw) for every run, including rejected ones. Available on all plans.

Add ability to create automations using MS Outlook as a trigger and/or as an action. I want to be able to link my Outlook account to SmartSuite, so the system could perform actions in response to incoming emails (create and update records, mainly). Vice versa, SmartSuite should be able to send emails on behalf the linked Outlook account based upon defined conditions.

would like to run automations at specific times but only if additional criteria are met.

I'm trying to create automations that repeat until conditions are right. For instance, it would be nice to build an automation that can create every Tuesday in the month of August or create "x" amount of records based off a number in a field, or create every day in the month of July and link it to other records matching certain conditions. One thing I am trying to do is create a basic scheduling app that I can schedule clients or teachers for the next 10 weeks (or whatever) and bill them based off of the number of scheduled meetings.

As an admin, that has built a number of automations that rely on values (for single select type fields and statuses) it would be good to confirm or update the automation rules that rely on the renamed values. If that does not happen, automations could not act as expected and need a full re-testing

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.

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.

The goal of this feature is to add an if/else statement in order to do différents actions, depending previous actions like a search. For example, if a find return a record, I will update it, if it does not find a record, I will create a new one.

I would like to increase the file size limit for Automation from the current 3MB to 20MB. This enhancement would allow me to work with larger files more efficiently, improving my workflow and productivity.