Skip to main content

Workflow Emails

Written by Efrat Barak Zadok

Shapes' automated emails allows you to automatically send custom emails based on employee fields to internal stakeholders, on behalf of anyone in your organization.

Creating a workflow email

Follow the steps here to create a workflow template and run it on an employee.

In either the template or an assigned workflow, click "Add Task" and then "Send Email".

The Email contains 3 components:

1. Due date

2. To

3. Email content

Due dates

All due dates are based on the anchor date, and can be set to occur before, after, or on the anchor date.

For automated emails specifically, the email is actually sent on the task's assignment date — the date calculated from the workflow's anchor (for example, an employee's Start Date). You can confirm this for any email task by hovering over it: the tooltip will read "This task will be sent on its assignment date."

Note that the Due Date shown in the column may not always match the assignment date. If you need to confirm exactly when an email will go out, check the assignment date via the tooltip rather than relying on the Due Date column alone.

To (Recipient)

"To" allows you to pick any employee in the platform to send the email externally to them. Automatically, Shapes will send an email to the employee.

You can choose whether workflow emails are sent to an employee's work email or personal email. This is especially helpful for pre-onboarding workflows, where welcome emails and instructions often need to be sent to an employee's personal email before their work account is active.

Email content

The email content can be completely customizable. Shapes allows you to include files and variables. Variables allow you to automatically pull data of the employee into the email.

Inserting a variable

Type {{ in the email editor to open a list of the fields you can use, right at the cursor. Keep typing to narrow the list, then press Enter or click a field to insert it. You can also insert variables from the {} menu.

Typing a full field name, such as {{First Name}}, turns it into the variable automatically. To keep a literal {{, press Esc and the text stays as typed.

Emailing people outside your organization

In Workflows 2.0, a Send email step can go to any email address, not just people in Shapes.

  1. In the step's To field, type the full email address into the search box, for example a team inbox, a vendor or IT.

  2. Click Add "<address>".

  3. Add more addresses or people the same way, up to 10 email addresses per email alongside any people you pick from Shapes.

  4. Write the Subject and Message, then click Save and publish the workflow.

You'll see This email isn't valid. Enter a valid email address, Already on the list or Up to 10 email addresses per email when relevant. Every recipient gets their own copy, so nobody sees who else received it.

What outside addresses see (Field access)

The Field access banner appears under the message as soon as the message or subject includes an employee field, or you attach a file field. Click Manage, choose an option and click Save for this email.

  • Follow each recipient's permissions (default): each employee sees only the fields they can view. Typed addresses see public fields only: first and last name, work email, phone, job title, manager, team, department, office and start date. Other fields, such as Personal Email or salary, show {Missing Info}. Files from employee file fields aren't sent to typed addresses or employees without a Shapes account (the builder marks them Employees only and warns External addresses don't get employee documents.).

  • Bypass permissions: everyone the step goes to, including typed addresses and employees without a Shapes account, sees every field in the subject and message and gets every file from the step's file fields.

Files you upload to the step from your computer go to everyone.

  • You can turn on Bypass permissions only if you can view every field the step uses. If a step uses a field you can't view, you can't change its recipients or Field access until you remove that field, and saving or publishing a bypassing step fails with This workflow uses a field you don't have access to. Only someone who can view it can save or publish it.

  • The setting is per step. Runs already in progress keep the setting they started with.

  • Table fields (for example a Bonuses amount) show the value from the employee's most recently added row.

  • Need more than 10 outside addresses? Add a second Send email step.

Bypass permissions shows every field in the step, including sensitive ones, to everyone it goes to. Use it only when everyone on the step should see that information.

And thats it! You've now created custom emails based on employee fields to internal stakeholders.

Did this answer your question?