Events & Actions are actions that are taken when an event occurs. In other words, a specific action is taken when a user triggers a condition based on its properties. These conditions include: User is Enabled, User is Disabled, User is Added, From Source, or For All Users.
There are various action types. The following require no configuration and can be setup within the Events & Actions tab of a destination:
- Assign Property and Value: a user is assigned a assigned a value for the specific property
- Move to OU: a user is moved to the specified organizational unit, formatted specifically for the destination type
The remaining actions require additional setup and configuration:
Execute PowerShell Script: run a PowerShell file of your own design. This action will load all .ps1 files from "C:\ClassLink OneSync\Scripts". Once loaded, you can then enter parameters into the event and action. These parameters can accept mappings and text transformations.
Email: message the designated email address. The email address, the email body, and the email subject can all be templated. That is, they will accept mappings and text transformations. Before you can use this action, you must enter email credentials in the Events & Actions tab of the destination.
These credentials include: an Email to Send From, Password, Port, and Host. Once you have entered your credentials, you can send a test email to confirm that the action will function correctly. Your email client will often set a secure port for you. Otherwise, you must choose a port yourself. The host is the server name of your email client. For example, for Office 365 email accounts, the port number is 587 and the host is "smtp.office365.com".
Note for Gmail users: In order to send emails via an SMTP relay, you must edit your account permission settings to allow lower security clients to access your account. This requires that you login using an administrator account and two steps. The first involves routing outbound mail using the SMTP relay service. The second involves pointing your on-premise outbound server to Google. For more detailed steps to route outgoing non-Gmail messages through Google and more information, click here.