WEB EVENTS & WORKFLOW INTEGRATION
Connect the work before and after
a file transfer, in one flow.
Connect INNORIX EX transfer events to your existing web application, database, external APIs and security systems. Manage transfer and business processing results separately, and avoid resending completed files even when a follow-up task fails.
- 01File TransferCompleted
- 02DB RegistrationCompleted
- 03Security CheckCompleted
- 04Business SystemCompleted
Transfer & Workflow Status100% Complete
BEFORE TRANSFER
Before you receive a file, check what it needs first.
Connect what must happen before a file is received, such as checking user permissions, issuing a job number and deciding the upload target and storage path, to your existing web application.
Only files that meet the preconditions start transferring, so your business rules hold.
Pre-transfer Validation
- User Authorization
- Allowed
- Business ID
- Auto-generated
- Storage Target
- Verified
- Upload Permission
- GRANTED
AFTER TRANSFER
When the file arrives, run the next task automatically.
Use upload completion as the starting point for follow-up work such as registering file information in the database, calling external business system APIs and notifying users.
Deliver file transfer and business processing as one user experience, while managing each step's result separately.
Event Execution Log
EVENT,FILE_UPLOAD_COMPLETED
- File ReceivedUpload completed successfullyDone
- Database APIFile metadata registered200
- Business APIWorkflow triggered200
- User NotificationCompletion notification sentDone
EXTERNAL INTEGRATIONS
Connect your existing business tools and security systems.
Connect file transfer events to external platforms such as Slack and Datadog, and feed the results of your enterprise security solutions into business processing.
Check permissions and security policies before a transfer, and run what is needed afterwards, such as malware scanning and DRM. Which products can be integrated and when they run depends on the APIs and security solutions actually supported.
External Integrations
- SlackNotifications
- DatadogMonitoring
- Malware ScanSecurity Check
- DRMPolicy Control
INDEPENDENT EXECUTION
If a follow-up task fails, there is no need to resend the file.
Manage file transfer and follow-up processing results independently.
If the file was received but DB registration or an external API call failed, keep the completed file and rerun only the failed task.
Recover from errors while avoiding duplicate transfers and unnecessary work.
Recovery Process
- File Transfer
- COMPLETED
- DB Registration
- COMPLETED
- Business API
- FAILED
- Selective Retry
- 200 OK
- Final Workflow
- COMPLETED
EXECUTION RESULTS
Tell transfer success apart from business completion.
A file arriving safely does not mean all the work is done.
Check transfer results and follow-up processing results separately, and set things up so you can see which step failed.
Final completion can be judged not only by file receipt but by the business conditions you need.
Execution Summary
- Security Check
- Passed
- DB Registration
- Success
- External API
- Retry Successful
FREQUENTLY ASKED QUESTIONS
Questions about
web events & business integration
Can I get approval from an existing business system before a file is uploaded?
You can integrate existing authentication/authorization APIs and business rules to configure file transfers to start only when the preconditions are met.
Can a file be registered in the database automatically when its upload completes?
You can connect file transfer completion events to DB registration processes in existing applications.
Can I connect multiple external APIs?
You can configure multiple external APIs and follow-up tasks according to business needs. The execution sequence and failure-handling policies are determined by the integration design.
Can security checks run before and after a file transfer?
You can configure pre-transfer policy checks and post-transfer inspections through APIs or integration points provided by existing security solutions.
Can events be sent to Slack or Datadog?
You can design notification or monitoring integrations using supported event delivery methods and external platform APIs.
If an external API call fails, do I need to upload the file again?
If file transfers and business processes are managed independently, you can configure only the failed business task to be re-executed.
Can file transfer success and final business success be judged separately?
You can distinguish file reception results from follow-up processing results and design the system to determine the final status based on whether the required business steps have been completed.
Can I check business processing results and error history?
You can link transfer events with external processing results to check execution status and error details. The specific recording scope depends on the integration method.
Connect file transfer to your existing business processes.
Use INNORIX EX events and APIs to automate everything from file receipt to security checks, DB registration and external system integration.