Happy New Year!
We’ve been hard at work improving Flowsana, and we’re excited to share a ton of new features and enhancements we’ve added that will make your workflows even more powerful and versatile! This includes one of the most highly requested feature updates: The ability to customize the Sender name and/or Reply-To email address in the Send Email rule action.
Customization of Sender name and/or Reply-To email address in the Send Email Rule Action
Customizing Sender Name
By default, the email will show that it came from “Asana”. However, you have the ability to set a different sender name, and the email will instead show that it came from your customized name. Please note that it is NOT possible to change the actual email address that the email comes from; for deliverability purposes, it must come from a “flowsana.net” domain. See below for the two flowsana.net email options it will come from, based on what you choose as the Reply-To email.
Reply-To Email
By default, the email will come from the email address “no-reply@flowsana.net” and cannot be replied to; if the user attempts to reply, their email will bounce. However, you have the ability to set a custom “reply-to” email address, meaning that if the user replies, it will be sent to your custom reply-to email address. If you customize a reply-to email address, the email comes from “asana@flowsana.net”.
So to reiterate, you can now customize the sender name and reply-to email address, but the email will always come from a flowsana.net email address.
– If you don’t set a reply-to email, the email will come from no-reply@flowsana.net
– If you do set a reply-to email, the email will come from asana@flowsana.net
Variable Substitution Updates
- For rule triggers/conditions/actions, we added new variables for {any} and for {none} or {empty}.
{any}
You can use {any} to match any value for a field. Some examples of where this can be used:
– triggering a rule when any tag is added to a task
– triggering a rule when a task in moved to any other section
– including a condition such that a rule only fires if the task is attached to any project
{none} or {empty}
You can use {none} or {empty} to match the lack of any values set for a field. The two are
identical; use whichever one sounds more appropriate. Some examples of where these can be used:
– triggering a rule when a task has no tags attached to it
– including a condition such that a rule only fires if the task is not attached to any projects
- For rule actions, we added a new type of variable, {triggeringTask.xxx} to allow you to reference values in the task that triggered the rule action.
{triggeringTask.}
For any of the {task.} variable phrases, you can specify {triggeringTask.} instead. This is specifically for use in two scenarios:
– When creating a rule where the action applies to the parent of the subtask triggering the rule, and you want to pull the value from the triggering subtask.
– In the Create task… and Create subtasks… rule actions, so that you can populate information in the new tasks or subtasks from the task that triggered the creation.
- Previously you could only put variables in any field except a numeric field, but we added the ability to use numeric fields, so now all custom fields support variables.
Other Rule Workflow Enhancements
- For rule triggers, we added a new Is changed option for dropdown list and text custom fields and for task name and description, so you can fire a rule when the value in any of the above items changes from one value to some other value.
- Similar to above, we added a new Assignee is changed trigger option so you can fire a rule when a task’s assignee is changed to a different assignee.
- Added a new Convert subtask to a task rule action. As part of this action, you can specify the section that the task gets put into after it’s converted.
- In the rule trigger “If the task is assigned to a value in a custom field”, you can now use a People custom field.
We’ve been hard at work behind the scenes to develop these enhancements based on your valuable feedback, and we can’t wait for you to try them out!
We’ve been hard at work behind the scenes to develop these enhancements based on your valuable feedback, and we can’t wait for you to try them out!
Happy workflow building!