Using journeys, HR, IT, and other teams can maintain a checklist of tasks, communication, and automated actions around key employee moments like onboarding, offboarding, promotions, learning, or compliance in one place.
When configuring a journey like onboarding, offboarding, or compliance, you can set up Slack actions to automatically perform these operations instead of having to note them down on your to-do list and perform them yourself every time. For example, you could set up an onboarding journey to notify the payroll team to add the new hire, the manager to assign them a buddy, and so on.
Slack journey actions
When you connect Slack and Atomicwork, you can set up four types of automated actions in a journey:
Send a Slack DM
Post to a Slack channel
Create a Slack channel
Add a user to a Slack channel
Note: To add Slack actions to a journey, you must connect Slack to Atomicwork
Send a Slack DM
To set up an automated action that sends a Slack DM, you need to specify the recipients, the message, when it should be sent, and whether it needs to be triggered by someone. For example, in an onboarding journey, you might want to notify the manager the day before a new hire joins of this event. You can add a Slack DM action with the manager as the recipient and a note.
Recipients. You can send Slack DMs to multiple recipients in one shot. The messages will be sent as DMs to each recipient by Atom.
Message. You can send personalized messages using placeholders to make the message more specific and relevant. These placeholders can be both employee fields and form responses. You can also mention Slack users in a message by typing “@” to pull up a list.
Who should perform the action? You have the option of choosing whether this action should be assigned as a task to someone to execute or whether Atomicwork can automatically send it. Tip: Use the former option for messages that must be reviewed before they’re sent out. For example, if you want a manager to review a Slack DM before it’s automatically sent to the new hire, assign it as a task to the manager.
When should this action be performed? Your two options are the day the employee moves to the stage or a day relative to the day an employee moves to this stage. Choose wisely.
Name the Slack action in a way that makes its purpose clear to all journey collaborators. This action will be visible to collaborators but hidden from employees assigned to this journey. This means that the Slack action will be visible in the journey configuration view that collaborators and creators can access but not the live view that employees have access to.
Post to a Slack channel
Set up automagical actions to post to a Slack channel on your behalf by specifying the channel, when it should be sent, and the message. For example, you could use this Slack action in an offboarding journey to notify service teams of an employee’s last date and what needs to be done before their exit.
Channel name. Atom can only post to public channels. If you want it to post to a private channel, you need to add Atom to the channel first. To pull up a channel, start typing in the name of a channel, and Atomicwork will find it for you.
Message. You can send personalized messages using placeholders to make the message more specific and relevant. These placeholders can be both employee fields and form responses. You can also mention Slack users in a message by typing “@” to pull up a list.
Who should perform the action? You have the option of choosing whether this action should be assigned as a task to someone to execute or whether Atomicwork can automatically send it. Tip: Use the former option for messages dependent on other actions in the journey. For example, if you want to post a success message to a Slack channel, it’s a good practice to assign this action as a task so that the task assignee can confirm the success and execute it.
When should this action be executed? Your two options are the day the employee moves to the stage or a day relative to the day an employee moves to this stage.
Name the Slack action in a way that makes its purpose clear to your teammates and journey collaborators. This action, like all other automated actions, will be visible to collaborators but hidden from employees assigned to this journey. This means that the Slack action will be visible in the journey configuration view that collaborators and creators can access but not the live view that employees have access to.
Create a Slack channel
To create a Slack channel, you need to specify the channel type, the new channel’s name, its topic, its description, and who should be added to this channel. For example, you could use this action in an onboarding journey to create a new Slack channel with the IT manager, the new hire’s manager, their HRBP, etc. for stakeholder coordination.
Channel type. Slack allows for public and private channels. If you need to change the setting from public to private and vice versa later, you can.
Channel name. Give the channel a name that makes it easy for people to keep track of. Specificity is the need of the hour for Slack channel names. Use placeholders to create customized channel names. The placeholders can be both employee fields and form responses.
Who should we add? You can add up to 1,000 people to a channel at once. Source.
Channel topic. Topics are to let people new to a channel know what’s being discussed at the moment. This is not a mandatory field for this action, so you can skip it if you’d like.
Channel description. Descriptions are to let people know the purpose of a channel. This is not a mandatory field for this action. This is not a mandatory field for this action, so you can skip it if you’d like. Learn more about these Slack features.
When should this action be executed? You can choose for this action to be executed when the employee moves to the stage or a day relative to the day an employee moves to this stage.
Name the Slack action in a way that makes its purpose clear to your teammates and journey collaborators. This action, like all other automated actions, will be visible to collaborators but hidden from employees assigned to this journey. This means that the Slack action will be visible in the journey configuration view that collaborators and creators can access but not the live view that employees have access to.
Add a user to a Slack channel
To add a user to a Slack channel, you need to specify who we should add and the channel name they need to be a part of. For example, you could use this action in an onboarding journey to add a new hire to all the Slack channels they need to be a part of.
Who should we add? You can add up to 1,000 people to a channel at once. Source.
Channel name. Atom can add users to public channels, but you can add users to private Slack channels through Atomicwork only if Atom is already a part of the channel.