Feature Requests

Very simply, if there's any kind of change to a table, run an automation. Use case: notify me if (1) new records are created, (2) when records are updated, or (3) when records are deleted. Right now I have to create 2 different automations for (1) and (2) and (3) is not supported.

I need to be able to capture the IP address of a user who triggered an automation through a button click. Use case: I want to be able to filter and track tickets based on whether certain users read them, and I want to be able to maintain a log of various times a user (throughout the lifetime of a ticket), confirmed that they read it. This will be used for auditing purposes so I need to log their IP address as well.

We have about 5 solution managers on a solution and every time an automation errors, or I have to do automation testing, it notifies all of the solution managers. Could you please add a feature to choose who gets what notifications among solution managers?

Secrets, like API keys, can be used in multiple automations and webhook automation actions. If a secret expires or is changed, it becomes a huge hassle to update everywhere and oversights can occur! It would be lovely if there was a central key-value store to manage these from. We should then be able to reference a secret by key from our difference webhook actions, but only need to update it from our central secrets vault when required.

I want to be able to make calls to the same webhook from different automations, without having to recreate the webhook call every time, by just adjusting input parameters and storing results (if any) in output parameters that can then be utilised in subsequent actions.

Would be very useful and powerful to have a trigger to export the database to Google Sheets with automation, for many companies the backup or use with other internal systems depends on Sheets/Excel.

I would like to alert users if the form they submits creates a merge records action - as the automated record creation I have written can create duplicate entries in title field (despite it being set to only allow unique entries!) I am cleaning this up with a "merge records" automation to keep the old record and remove the new - but I can't alert users to this.

SmartSuite’s Gmail integration is so close to unlocking huge automation potential. But one key piece is missing: control over when emails are sent. Right now, we can trigger automations based on dates (e.g. “X days before project date”), but emails always send at midnight—which isn’t practical or professional. WHY THIS MATTERS In many service-based and event-driven businesses, timing matters. Getting an email at 1:00am looks sloppy. Getting it at 8:00am looks polished. SUGGESTED SOLUTIONS OPTION 1 - Add a dynamic “Time Now” field A time field that updates automatically (say every 15 minutes) would let us set triggers like: “If date is in the next 1 day AND time is after 8:00am → send email.” OPTION 2 - Let us set global send windows Just like we set working hours, let us define when SmartSuite is allowed to send emails—e.g. only between 8:00am and 6:00pm. Simple, clean, and flexible. OPTION 3 - Delay Step with Time Window Allow a “Wait Until Time” step inside automations. For example: Wait until 8:00am before sending the email. This would give precise control, without needing external schedulers or hacks. OPTION 4 - Add a "Send Window" Setting to Email Actions Let us set a time window directly in the email step, like: Only send this email between 8:00am–6:00pm. (Or an exact time) If the automation runs outside that window, it could delay the email until the next valid send time. WHY CURRENT WORKAROUNDS ARE NOT GOOD ENOUGH Technically, I could use the “At a scheduled time daily” trigger to run a “Find Records” step that only sends the email if certain criteria are met and fails otherwise. But when you have dozens of different email workflows, that means running every single one, every day, just to check if a condition is true. That quickly becomes messy, inefficient, and hard to manage at scale. REAL-WORLD EXAMPLES A home services company wants to email the assigned technician at 8:00am on job day. Not at midnight. A wedding photographer wants to send a thank you email the MORNING after wedding day. A medical office wants to email patients two days before an appointment, but only during business hours. A school wants to send reminders to parents the morning of a field trip—not in the middle of the night.

I want to a way to view all fields and its related Automation that it is being used for. This will allow me to make changes and updates to a field without worrying an Automation might break. Especially if my Solutions are more complex.

Currently the looping action is always the last action in the automation but I need to be able to add an action after a looping action has finished to update the status of the triggered record. Use case is for onboarding of personnel. When the Status of person is changed to 'Initiate Onboarding' I want the looping action to generate all the required onboarding tasks from a template tasks table I have and once finished then update the status of the person to 'Onboarding' which is then used for notifications and other processes.