How to Use Globalscape EFT 8.3.4 Triggers and Actions to Build a Fully Automated Secure File Workflow
Managing secure file transfers manually is time-consuming and prone to errors. Global E-Director helps businesses simplify this process with Globalscape EFT 8.3.4, using its powerful event-driven Triggers and Actions to build a fully automated, secure file workflow that runs reliably around the clock with minimal human intervention.
This guide explains the core concepts and walks you through the steps to configure a production-ready automated workflow.
What Are Triggers and Actions in Globalscape EFT 8.3.4?
At the heart of Globalscape EFT 8.3.4 is an event-driven automation framework. In simple terms:
Triggers are conditions or events that EFT monitors such as a file upload completing, a scheduled timer firing or a user logging in.
Actions are the tasks EFT executes in response to a trigger such as moving a file, sending an email notification, running a script, or encrypting data.
Together, Globalscape EFT 8.3.4 Triggers and Actions form a flexible automation layer that eliminates manual intervention from routine file-handling tasks.
Why Build an Automated Secure File Workflow?
Before diving into configuration, it helps to understand the business case. An automated secure file workflow built on Globalscape EFT 8.3.4 delivers:
Consistency: every file is processed the same way, every time.
Speed: files are moved, transformed, or distributed the moment they arrive.
Auditability: EFT logs every trigger event and action outcome, supporting compliance requirements.
Reduced risk: removing manual steps reduces the chance of human error or missed transfers.
Step 1: Plan Your Workflow Before Touching the Interface
Effective automation starts with a clear plan. Before opening the Globalscape EFT 8.3.4administration interface, map out the following:
What event starts the workflow? (A file upload? A schedule? A user action?)
What conditions must be met? (Specific folder? File type? File size threshold?)
What should happen next? (Move, copy, rename, encrypt, notify, archive?)
What happens to failure? (Alert an administrator? Retry? Log an error?)
Documenting this flow on paper or in a diagram saves significant troubleshooting time later.
Step 2: Access the Event Rules Manager
In Globalscape EFT 8.3.4, Triggers and Actions are managed through the Event Rules system. To get there:
Open the EFT Administration Interface.
Select the Server or the specific Site you are configuring.
Navigate to the Event Rules tab in the right-hand panel.
Click Add Rule to create a new automated rule.
Each Event Rule in Globalscape EFT 8.3.4 contains one trigger and one or more actions chained in sequence.
Step 3: Configure Your Trigger
The trigger defines what event starts the automated secure file workflow. Globalscape EFT 8.3.4 offers a broad range of trigger types:
Trigger Type | Typical Use Case |
File Upload Complete | Process a file immediately after a client uploads it |
Scheduled Timer | Run a batch transfer or cleanup task at a set time |
User Login | Trigger a welcome action or folder permission check |
File Download Complete | Archive or delete a file once it has been retrieved |
Folder Monitor | Watch a local or network folder for new file activity |
To configure a trigger, select the relevant event type from the drop-down list and apply any filters such as limiting the trigger to a specific folder path or a particular file extension.
Step 4: Add and Chain Your Actions
Once the trigger is set, you define what Globalscape EFT 8.3.4 does in response. Actions are added sequentially, and EFT executes them in order. Common actions for building an automated secure file workflow include:
Move File: relocate the uploaded file to a processing or archive folder.
Copy File: send a copy to a secondary destination for redundancy.
Rename File: apply a timestamp or unique identifier to prevent naming conflicts.
Run Command or Script: invoke a custom script for validation, transformation, or integration with another system.
Send Email Notification: alert an internal team or external partner that a file has arrived.
PGP Encrypt or Decrypt: apply or remove encryption to meet security requirements.
Write to Log: record a custom message in the EFT audit log for traceability.
To chain actions, simply click Add Action within the same Event Rule and select the next task. Globalscape EFT 8.3.4 executes them in the listed order, allowing you to build multi-step pipelines from a single trigger event.
Step 5: Apply Conditions to Refine Workflow Logic
Not every file that arrives should be treated identically. Globalscape EFT 8.3.4 Triggers and Actions support conditional logic within rules. You can add conditions that check:
File name patterns (wildcards or specific strings)
File size (minimum or maximum thresholds)
The authenticated user or group associated with the event
Time of day or day of the week
The result of a previous action (success or failure)
Using conditions allows a single Event Rule to handle branching logic for example, routing files differently depending on the uploading user's group membership.
Step 6: Configure Error Handling
A production-grade automated secure file workflow must account for failure. In Globalscape EFT 8.3.4, each action can be given an on-failure behaviour :
Continue: proceed to the next action regardless of the failure.
Stop: halt the workflow and log the error.
Run an alternative action: for example, send an alert email if the Move File action fails.
Adding an email notification or a log-write action tied to failure conditions ensures that problems are visible and traceable rather than silently dropped.
Step 7: Test Before Going Live
Before enabling the rule in a production environment, test it thoroughly:
Create a test folder structure that mirrors your production environment.
Use a test user account to upload sample files and trigger the event.
Review the EFT Audit Log and Event Log to confirm every action executed as expected.
Deliberately trigger failure conditions to verify error handling behaves correctly.
Adjust filters, conditions, or action order based on what you observe.
Testing in Globalscape EFT 8.3.4 is non-destructive when performed in an isolated test site, so there is no risk to live data during this phase.
Step 8: Enable, Monitor, and Refine
Once testing is complete, enable the Event Rule by toggling it active in the Event Rules manager. From this point, the automated secure file workflow runs without manual intervention.
Ongoing monitoring is straightforward in Globalscape EFT 8.3.4:
Review the Audit Log regularly to spot unexpected patterns or recurring errors.
Use the Report module to generate summaries of file activity over time.
Revisit and update Event Rules whenever business requirements change.
Putting It All Together
Globalscape EFT 8.3.4 Triggers and Actions provide administrators with the tools needed to replace manual, error-prone file handling with a reliable, auditable, and scalable automated secure file workflow. Global E-Director supports this approach by helping businesses streamline secure file transfer processes through effective automation.
The process is straightforward: plan your workflow, configure a trigger, chain the required actions, apply conditions, handle errors, test thoroughly, and monitor performance in production.
Start with one well-defined workflow and expand from there. As you see how consistently Globalscape EFT 8.3.4 executes event rules, you can identify more manual processes that are ready for automation.
Ready to build your first automated workflow? Open the Event Rules Manager in Globalscape EFT 8.3.4 and follow the steps above your first rule could be live within the hour.
