Feature Requests

Could we please add the ability for an "IF Error, Then..." path of an automation? Currently, if a node in the automation fails, in some automations, this turns off the automation completely. Rather, I'd like for the automation to take an error path that updates a status of the record it's working with to "Needs Review" (or some status choice), notifies our team as it already does, but NOT turn off the automation.

Need to add an ability to support icons that are used in SmartSuite fields to be rendered in Generate PDF automation action. As an example I might have icons in the Status / Single Select fields that I want to be present in the PDF that I generate with automations

id like to have a buttom that alolows for testing the automoation. Currently i have to eitehr wait for the schedule time or make a change in record etc to ensure irt runs proeprly.

I would like to have "Changes" added to the conditions options for Date field types like most other fields have. Right now, Date field types do not allow me to do something like this reference image which is an Address field type.

For many, a work management platform can be a way to eliminate email internally. To embrace that, it'd be helpful to split up the "Send Email" Action. Currently, this action requires you to both "Send an Email" and "Send a Notification". Suggestion: Make only one of the two types of alerts required (so you could send an email, send an notification, OR send both) Make "Send a Notification" as a separate standalone Action

Would be awesome to trigger automation by pushing a button (the ones in smartsuite...)

A more in-depth question about this function.. In theory, would it be possible in the future for automations triggered via a webhook to also return a response? Specifically, I’m planning to use an automation to generate a PDF with the document designer in SmartSuite and return either the PDF itself or a URL to the PDF. This way, it would be possible to generate and retrieve a PDF on demand through a webhook. If the response can be configured with a 303 and a location header containing the URL of the generated PDF, we could have certain customers access an on demand generated document. This would be very valuable for us and our operations. So, to summarize my question: Will it be possible to return a response from automations triggered by webhooks?

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 have recently rebuilt all of our Document Designer templates under one solution, mainly due to the need for most documents to pull data from several solutions and the large number of formulas needed in each table to accomplish this. Now, I have one "Document Creator" table chock full of formulas to pull data in for the Document designer, eliminating the need for redundant formulas across other solutions and tables. This is working really well and has kept my other tables a lot "lighter", as well as making it easy to duplicate and modify existing doc templates to create new ones. The last hurdle to overcome is having a way to dynamically select a PDF template within an automation by using a single select value. My preference would be to add a "Fields from Trigger" in the Create PDF action aimed at a single select field with values matching the doc template names. Next best would be conditional logic where I could if/then select the template. As it is, I use a Yes/No field named after each document and separate automations, but as I have about thirty doc templates to create in total this will get cumbersome very quickly. I tried skipping automations and just opening the doc designer, selecting the record, and exporting, but then I had to manually rename each document, so automations are the way to go to prevent PDF naming errors.

I want to create multiple records from a list of linked records or multiple select items in the parent record. Example: The parent contract record has a linked record field to "pay periods" that is automatically populated with which pay periods are included in the contract. For each pay period, there needs to be a new record created for the pay schedule (the amount paid per period and the pay date). So when the automation triggers, the "Create records" action would parse that there needs to be a new record for each pay period linked in the given field (i.e. if the person is paid in January and February, there would be a linked record field that contains 2025-P1 and 2025-P2, and then a pay schedule record would be created for each of those). There are multiple other use cases I can think of, but the core function I am looking for is to iterate an automation action over each item in a list from a previous action or trigger.