Event types
There are many event types that you may listen for when defining triggers. Below you will find a list of event types and their corresponding descriptions. You will find the same information in the context sensitive help available in MFT Server Manager when creating a trigger.
Name | Description |
---|---|
Account Created |
Fired when an account is created. |
Account Deleted |
Fired when an account is deleted. |
Account Disabled |
Fired when an account is disabled. |
Account Updated |
Fired when an account is updated. |
Administrator Login |
Fired when an administrator tries to login. |
Administrator Created |
Fired when an administrator is created. |
Administrator Updated |
Fired when an administrator is updated. |
Administrator Deleted |
Fired when an administrator is deleted. |
Amazon Sqs Message Consumed |
Fired when Amazon SQS message is consumed. |
AS2 Receipt Received |
Fired when an AS2 receipt is received. |
AS2 Receipt Sent |
Fired when an AS2 receipt is sent. |
Connection Rejected |
Fired when incoming connection is rejected for some reason. |
Current Time |
Fired every minute while the domain is running. |
Data Connection Error |
Fired when data connection is failed for some reason. |
Database Log Failure |
Fired when log database failure occurs. |
Directory Change |
Fired when client attempts to change current working directory. |
Directory Create |
Fired when client attempts to create a directory. |
Directory Delete |
Fired when client attempts to delete a directory. |
Directory Monitor Created |
Fired when a directory monitor is created. |
Fired when a directory monitor is deleted. |
|
Directory Monitor Failure |
Fired when a directory monitor fails (e.g. the target directory is invalid or no longer accessible, or the user who is attempting to write a file to the target directory lacks permission, etc.). |
Directory Monitor File |
Fired when a file is added, changed, deleted or aged, depending on the trigger condition specified. See Directory Monitor File conditions supported. |
Directory Monitor File Added |
Fired when a file is added to a monitored directory. |
Directory Monitor File Aged |
Fired when a file in a monitored directory is aged. |
Directory Monitor File Changed |
Fired when a file in a monitored directory is changed. |
Directory Monitor File Deleted |
Fired when a file in a monitored directory is deleted. |
Directory Monitor Idle |
Fired when a directory monitor has not been active within the specified time frame. |
Directory Monitor Updated |
Fired when a directory monitor is updated. |
Directory Monitor Quota Exceeded |
Fired when the quota for a directory monitor has been exceeded. |
Dlp Rule Matched |
Fired when a DLP rule is matched. |
Domain Started |
Fired when attempting to start a domain. |
Domain Stopped |
Fired when attempting to stop a domain. |
Drop Zone Created |
Fired when a Drop Zone is created. |
Drop Zone Deleted |
Fired when a Drop Zone is deleted. |
Drop Zone Updated |
Fired when a Drop Zone is updated. |
Email File Retrieved |
Fired when a file that was emailed using ad-hoc email transfer is retrieved by recipient. |
Email File Sent |
Fired when a file is emailed using ad-hoc email transfer. |
Event Publish Failed |
Fired if event is failed to publish to the remote trigger service. |
External File Download |
Fired when an action in response to a trigger downloads a file and stores locally. |
External File Upload |
Fired when an action in response to a trigger sends a local file to remote user or file transfer service. This event is NOT fired when using File Transfer Script action. |
Failover Synchronization |
Fired when failover synchronization is performed. |
File Copy |
Fired when local file is copied. |
File Delete |
Fired when attempting to delete a file. |
File Download |
Fired when attempting to download a file. |
File Download Aborted |
Fired when FTP/S client aborts file transfer by sending ABOR command. Many clients do not send ABOR command but instead simply close the connection. In this event no event is fired. |
File Download Started |
Fired when server receives request from client to download a file. |
File Download Quota Exceeded |
Fired when file download quota has been exceeded. |
File Move |
Fired when local file is moved. |
File Rename |
Fired when attempting to rename a file. |
File Synchronization |
Fired when file is synchronized. |
File Upload |
Fired when attempting to upload a file. |
File Upload Aborted |
Fired when FTP/S client aborts file transfer by sending ABOR command. Many clients do not send ABOR command but instead simply close the connection. In this event no event is fired. |
File Upload Started |
Fired when server receives request from client to upload a file. |
File Upload Quota Exceeded |
Fired when file upload quota has been exceeded. |
File Transfer Quota Exceeded |
Fired when file transfer quota has been exceeded. |
Group Created |
Fired when a group is created. |
Group Updated |
Fired when a group is updated. |
Group Deleted |
Fired when a group is deleted. |
Icap Antivirus Violation |
Fired if ICAP Antivirus Scan action fails. |
IP Access Rules Updated |
Fired when IP Access rules are updated. |
IP Blocked |
Fired when a client IP address is blocked and added to IP Access list. |
IP Flagged |
Fired when a client IP address is flagged as blocked. |
Log Extension Failure |
Fired when log extension failure occurs. |
Log Rotated |
Fired when log file is rotated. |
Log Updated |
Fired when log file is updated. |
Log Search Completed |
Fired when a report has completed processing. |
Oftp Receipt Received |
Fired when an OFTP receipt is received. |
Oftp Receipt Sent |
Fired when an OFTP receipt is sent. |
Report Completed |
Fired when a report has completed processing. |
Reverse Proxy Created |
Fired when a network storage is created. |
Reverse Proxy Deleted |
Fired when a network storage is deleted. |
Reverse Proxy Updated |
Fired when a network storage is updated. |
Service Start |
Fired when a service is started for a domain. |
Service Stop |
Fired when a service is stopped for a domain. |
Tag Changed |
Fired when keyword tags for a document have changed. |
Trading Partner Command Executed |
Fired when trading partner command is executed. |
Trading Partner Synchronization |
Fired when a Trading Partner Synchronization action is executed. |
Trigger Error |
Fired when an action within a trigger fails execution. |
User Connect |
Fired when a user connects to service. |
User Disconnect |
Fired when a user disconnects from service. |
User Login |
Fired when user attempts authentication with service. See User Login Failure Codes below. |
User Logout |
Fired when user logs out of session with service. |
User Password Changed |
Fired when user changes password. |
User Password Reset Requested |
Fired when user password reset is requested. |
User Registered |
Fired when user self-registration process complete. |
Web Hook |
Fired on demand only when a user selects the Trigger > Run option in the UI, or runs the equivalent call using the REST API, or executes the js-runtrigger command line utility. |
Conditions supported include: File_Added, File_Changed, File_Deleted, and File_Aged. Example: If you want the trigger to fire on a file add or a file change, the trigger condition would be as follows: EventType = "File_Added" OR EventType = "File_Changed"
The User Login event generates failure codes if the login is not successful. Below is the list of failure codes that can be used in the Trigger Condition (Expression) or an action.
-
INTERNAL_ERROR
-
ACCESS_DENIED
-
INVALID_CREDENTIALS
-
USER_CONFIRMATION_FAILED
-
SSO_AUTHENTICATION_DISABLED
-
PUBLIC_KEY_AUTHENTICATION_REQUIRED
-
ACCOUNT_NOT_FOUND
-
ACCOUNT_DISABLED
-
ACCOUNT_EXPIRED
-
ACCOUNT_ROOT_PATH_NOT_FOUND
-
PASSWORD_RESET_REQUIRED
-
SECURE_CONNECTION_REQUIRED
-
PROTOCOL_NOT_ALLOWED
-
TOO_MANY_USER_CONNECTIONS
Example usage in the Trigger Conditions > Expression
field:
Success = FALSE AND FailureReason = "INVALID_CREDENTIALS"
See also