Journey actions can be tasks, scheduled emails, scheduled Slack messages, or actions like adding the employee to a channel, Okta actions like adding an employee to a group, and so on. Here's a list of all the actions you can perform in a journey:
Create a webhook
Azure AD actions
Google Workspace actions
Okta actions
Checkr actions
Slack actions
Teams actions
Some actions you can perform in a journey:
Assign a task
For example, an onboarding journey could have tasks like “Provide ID card and biometric access” for an office manager, “Ship a laptop” for the IT manager, and so on. You can create tasks and assign them to your teammates, along with due dates.
Personalization: You can personalize task titles and descriptions with dynamic placeholders like ##{{employee.full_name}} or ##{{employee.hrbp.full_name}} to build connections.
Assignees: Tasks can be assigned to the journey assignee, the assignee’s manager, the assignee’s HRBP, or specific teammates.
Visibility: You have the option of marking tasks that are not directly relevant to an employee as invisible to the employee assigned to the journey. This means that this task will be visible in the configuration view but not in the live view.
Due dates: Tasks can be due on the day an employee is assigned a journey or relative to that day. For example, tasks can be due two days after a journey is assigned to an employee.
Send an email
Add an action that automatically sends an email on your behalf. For example, an onboarding journey could have scheduled welcome emails, emails asking the new hire to sign their contract, company policy emails, etc.
Personalization: You can personalize the sender's name (From name) that will appear in the recipient’s inbox, subject, and email body.
Who should send the email? You can choose to have the email sent automatically or sent by a specific person manually. If you choose the second option, it’ll be assigned as a task to that employee.
When should the email be sent? You can choose to send the email as soon as the employee moves to the stage or pick a day relative to the stage movement date field.
Title: You can give the action a title that makes the purpose of the email clear to all of your collaborators.
Visibility: Emails are not actions that are visible to the journey assignee.
Create a webhook
Webhooks are a way for apps to communicate with each other. For example, you can create a webhook in BambooHR to notify Atomicwork when a candidate accepts an offer so you can trigger a preboarding journey.
Send a form
Use forms to gather data from your employees in journeys. For example, an onboarding journey could include a T-shirt size form. The form’s response can be sent to vendors so that they ship the right size to the new hire.
Go to Settings > Workspace > Forms
Click on Create a form.
Enter the form’s name and description. This will be displayed to anyone who has been assigned this form, so please make your name and description clear and succinct. You can modify the name and description later as well.
Enter a section name. This is not mandatory, but we’d recommend it. Form questions can be grouped into sections so that it’s easy for employees to go through long forms.
Enter the question name and choose a response type. You can edit the question name even after you save the form, but you can’t edit the response type. You can also add a hint if the question needs an explanation.
Choose whether you want to make this question mandatory.
Once you’re done adding questions and sections to the form, you can customize the form’s appearance by clicking on the Customize tab in the middle of the navigation bar.
The Customize tab allows you to customize the button text at the end of the form, the success message that appears when you click on the button, and the background color of the form.
Once you’ve created a form, you can preview it by sending yourself a test via Slack or Email to determine how employees assigned to a journey will see it.
Hit Save to save all your progress and see this form in the list of forms while setting up a journey.
Send a form
You can send a form to an employee as a part of a journey.
Go to Settings > Journey templates > Journeys. Click Add an action and Send a form.
Choose the form you’d like to send and the employee who you want to send the form to. For example, in an onboarding journey, you might want to send one form to an employee for their personal info and another form to a manager to capture their IT requirements for the new hire.
Choose how you’d like to send the form - Slack or email. If you choose email, you can also customize the sender's name. If you choose Slack, Atom will DM the form link to them.
Choose the date by which the employee needs to fill out the form.
Enter the action’s name. This name will be visible to collaborators and journey creators in the configuration view but not the live view for employees assigned to this journey.
View form responses
You can view all the responses a form has received from its configuration page.
Go to Settings > Workspace name > Forms
Click on the Form > Responses tab to view a list of all the responses. You can export the responses as a CSV file.
Create a service request
In onboarding and offboarding journeys, IT might want to create a service request to keep track of all of their deliverables.
Click on Create a service request > Choose the service > Fill out the service form.
Specify when the action should be executed
Enter the action’s name. This name will be visible to collaborators and journey creators in the configuration view but not the live view for employees assigned to this journey.
When a journey is assigned to an employee and a service request is created, you can view the service request in the workspace. If a journey prompted service request creation, the linked journey is visible in the service request. You can also view the service request ID in the journey.