Smart rules

Be able to extract and transform attachement content data to use in dynamic variables in workflows. For example: extract attachment info > use in API request to create order request in TMS

It would be very helpful if there was a condition in rules that allowed you to trigger a rule based on what Front user performed the originating trigger/action. For example, we have an SLA set up but we have a tag that will exclude a message from ...

Allow someone to multiply a dynamic variable by a number or other dynamic variable.

While custom fields are currently enabled on the Inbox level, having these fields enabled a step further on the Channel level – the actual email customers use for example – would allow you to dynamically insert phone numbers, names, and other impo...

Have a new [Is out-of-office] Teammate property to use in Dynamic Variables, in addition to [Is available] which returns false whether the status is Busy or Out-of-office.

Example use case: In building some rules/macros, I want to access the current timestamp. For example, I want to create a tag prefixed with the current date; "[2025-03-25] {generated-tag-name}". At present, you can fetch a timestamp from attributes...

Rule data sets are currently manually maintained or limited to 500 rows for a CSV import. API access to manage this would give an avenue to maintain this in a non manual way and reduces chances of errors occurring

Introduce duration fields in rules to power time-sensitive workflows. For example: Add a "SLA target" custom field on the account to support a customer-specific SLA targets Have a "contract renewal date" custom field and use dynamic variable to fi...

I have a use case where I match text patterns in a message body (like ORDER-{digits}) and want to convert all matches to markdown links ( `[ORDER-123](https://example.com/orders/ORDER-123)` ) Right now this is not supported - as there's no way to ...

I think it would be beneficial for rule sets to support dropdown menu custom fields