Third-party actions in workflows

Connect your tech stack to Atomicwork to automate as many manual tasks as possible. Need to automatically trigger new user creation in Azure AD when someone submits an onboarding request? Want to create a Teams channel for high-priority requests from C-suite execs with all stakeholders involved? Automate routing and communication workflows through Atomicwork. Workflows can also be configured so that actions executed by one workflow can trigger other workflows, enabling more complex automation sequences.

Third-party actions:

• Slack actions

• Teams actions

• Azure AD actions

• Okta actions

• Checkr actions

Notes

• You can reference specific people in actions (for example: Andy Jones) or you can reference a placeholder (E.g: Assigned agent or requester) or you can reference the output of an action (we call this a data pill).

Slack actions

• Send a Slack DM. Specify the recipient and the message (complete with dynamic placeholders). You can send a Slack DM to multiple people, but Atomicwork will not send it to a group; it will be sent as messages to each person individually.