Solution Documentation & Demo Guide

OmniMFT Ops Copilot

AI Agent for Managed File Transfer Operations — Axway SecureTransport × Boomi

Version 1.4 · November 2026 · Agent package v11.0 · Web portal v1.0 · MFT Operations, Security Auditors and Integration Engineers

Executive summary

OmniMFT Ops Copilot is an AI agent that helps MFT operations teams track file transfers, diagnose failures, guard certificate expiry, reprocess files, onboard new SFTP partners and notify the team by e-mail — all through conversation.

The agent is available in three places: in Boomi Agentstudio (cloud, for business users), in the OmniMFT web portal on localhost (a lightweight operator console that talks to the same Boomi bridge) and as a local agent in Claude Code (for engineers). All three use the same OmniMFT logic and have been tested against SecureTransport 5.5 in the lab.

Partner uploads are routed to Boomi, to an SFTP inbox, or to both. Every route, the resubmit flow and the e-mail notifications were verified end to end — without opening any inbound port into the on-premise network.

12agent tools in Agentstudio
3delivery routes per partner
2notification channels (e-mail, WhatsApp)
0inbound ports opened

Background

Managed File Transfer (MFT) is the backbone of B2B data exchange: invoices, payment files, orders and reports move between the company and its partners every day through Axway SecureTransport. Each partner needs an account, transfer sites, subscriptions and often downstream processing in an integration platform such as Boomi.

Operating this landscape is still largely manual. Answering a simple question like “did the bank file arrive and where did it go?” means logging into the ST admin console, filtering transfer logs and correlating them with integration logs. Certificates expire silently, partner onboarding takes many screens and careful configuration, and failures are often discovered only when a business user complains.

At the same time, security constraints are strict: ST sits on a private network behind VPN, corporate laptops run Zscaler, and no inbound connection into the on-premise network is allowed. Any automation must respect these boundaries.

Pain points

Slow answers

Status questions require specialist access to the ST console and manual log correlation across ST and Boomi.

Late failure detection

Failed pushes and rejected files are often noticed only when the business side escalates.

Silent expiry

Expired certificates and keys break partner connections without warning.

Manual onboarding

New partners need an account, sites, subscriptions and routes configured by hand — slow and error-prone.

Strict security

Private network, VPN and Zscaler rule out tunnels and inbound access for cloud tools.

Scattered audit trail

Evidence of who changed what, and which files reached which system, is spread across several consoles.

Business value

OmniMFT turns MFT operations from console work into governed, conversational automation. Values are qualitative; no baseline measurements were taken yet.

Faster operations

Status, diagnosis and certificate checks are answered in seconds through conversation instead of console navigation.

→ Shorter time-to-answer for every transfer question

Lower mean time to recovery

Failures arrive with cause, HTTP status and recommended fix; resubmit is one approved step.

→ Incidents resolved in one conversation

Faster partner go-live

Partner onboarding (account, sites, subscription, routes) is a single approved request with dry-run and rollback.

→ Same-day onboarding, consistent configuration

Reduced operational risk

Proactive certificate and key expiry alerts prevent avoidable partner outages.

→ Fewer outages caused by expired credentials

Governance & compliance

Human approval for every change and message, allow-listed actions, and an audit trail in Boomi.

→ Controlled automation that auditors can verify

Proactive communication

The team is informed by e-mail or WhatsApp with concise, factual summaries at the moment it matters.

→ Stakeholders informed before they have to ask

Security by design

Outbound-only architecture: no tunnels, no inbound ports, credentials stay on-premise.

→ Cloud AI adopted without weakening the perimeter

Reusable foundation

The same OmniMFT logic serves Agentstudio and Claude Code, and new routes or channels plug in as profiles and tools.

→ Low cost to extend to new use cases

Use case highlights

Six use cases cover the daily MFT operations lifecycle — each one is live and demonstrable today.

1. Transfer tracking & failure diagnosis

Persona: MFT operator, service desk  ·  Trigger: A partner or business user asks whether a file arrived, or a transfer fails.

BeforeLog into the ST console, filter logs, inspect protocol details, then check Boomi execution logs separately.
With OmniMFTAsk the agent; it reports sender → receiver, status, size, time, the ST error, the remote HTTP status and a fix, correlated with Boomi.

Business value: Answers in seconds; no specialist console access needed for routine questions.

2. Certificate & key expiry guard

Persona: Security auditor, MFT administrator  ·  Trigger: Periodic review, audit request, or a partner connection failing with TLS/SSH errors.

BeforeExport certificate lists and check expiry dates by hand, often after something already broke.
With OmniMFTThe agent lists CRITICAL (expired) and WARNING (≤30 days) items with remediation commands and can alert the team.

Business value: Outages from expired credentials are prevented instead of repaired.

3. Partner onboarding & setup check

Persona: Integration engineer, partner manager  ·  Trigger: A new trading partner must start exchanging files, or an existing partner stops receiving files.

BeforeCreate account, sites, subscription and routes across many ST screens; find missing or deleted pieces by hand.
With OmniMFTOne request onboards the partner (dry-run, approval, rollback); one question checks any or all partners for gaps.

Business value: Faster, consistent go-live and quick detection of broken partner setups.

4. Reprocess a failed transfer

Persona: MFT operator  ·  Trigger: A delivery failed because of a downstream or configuration issue that has since been fixed.

BeforeFind the right transfer record (outbound vs. original upload) and resubmit it in the console.
With OmniMFTThe agent finds the failure, explains it, resubmits the correct record after approval and reports the result.

Business value: Recovery in one conversation, without knowing ST record internals.

5. Team notifications (e-mail & WhatsApp)

Persona: Operations lead, on-call engineer  ·  Trigger: A critical finding, an onboarding result or a reprocessing outcome needs to be shared.

BeforeCopy information into an e-mail or chat by hand, often late or incomplete.
With OmniMFTThe agent drafts a factual summary and sends it by e-mail, WhatsApp or both after approval.

Business value: Stakeholders informed immediately and consistently.

6. Automatic processing of inbound files in Boomi

Persona: Integration engineer, business process owner  ·  Trigger: A partner uploads a file to SecureTransport.

BeforeFiles wait in ST folders or are forwarded by bespoke scripts without validation.
With OmniMFTST pushes the file to Boomi automatically; Boomi validates it, rejects empty files, audits it and returns a receipt.

Business value: Reliable, auditable hand-off from MFT to integration with failures visible in ST.

Four core capabilities

Tracking & diagnosis

Answers transfer questions in natural language: sender → receiver, protocol, status, size, time. Failed transfers come with the ST error, the remote HTTP status and a root-cause diagnosis.

Certificate & key guard

Audits SSL/TLS certificates, SSH keys and PGP keys in ST. Expired items are CRITICAL, items expiring within 30 days WARNING — with remediation commands and an optional e-mail alert.

Reprocess & notify

Correlates ST transfers with Boomi executions, resubmits failed transfers (re-running the original upload when needed) and e-mails the outcome to the team after approval.

Partner lifecycle

Creates SFTP partners routed to Boomi, an SFTP inbox or both (dry-run, approval, rollback) and checks existing partners for missing or misconfigured parts.

Solution architecture

File flow: Partner → SecureTransport → Boomi

Partner SFTP → SecureTransport (on-prem, VPN) → Boomi Cloud 1. Partner upload SFTP port 8022 to the/inbound folder 2. SecureTransport 5.5 Basic Applicationsubscription auto-push 3. Generic-HTTP(S) site HTTPS PUT to the Boomilistener 4. Boomi listener OmniMFT API – ST InboundFile 5. Subprocess Unwrap multipart →validate → audit → JSONreceiptOn-premise (lab, via FortiClient VPN)Boomi Cloud (Test atom)
Figure 1 — File flow from the SFTP partner to processing in Boomi

Agentstudio ↔ on-premise: outbound-only bridge

ON-PREMISE (lab + laptop) BOOMI CLOUD Axway SecureTransport 5.5 192.168.0.21 · Admin API 8444 · SFTP 8022Stays private OmniMFT bridge worker bridge_worker.py (laptop/host)Snapshots every ±60 s · queue polling ±5 sAllow-listed actions · credentials in .envAdmin REST API via VPN Disk V2 store work/omnimft snapshots/ · requests/ · results/no DELETE Bridge listeners (WSS) upsertOmnimftDoc · getOmnimftDoccreateOmnimftRequestqueryOmnimftRequests Agentstudio: OmniMFT Ops Copilot read snapshots · queue actions · get resultspublish snapshots & results (outbound HTTPS)fetch queued actions (outbound HTTPS)Internet · ZscalerInbound ports to on-prem: NONE
Figure 2 — Agentstudio reaches SecureTransport through the outbound-only bridge

Why outbound-only? The corporate laptop runs Zscaler (TLS inspection, blocks tunnelling apps) and ST is reachable only via FortiClient VPN. The outbound-only pattern complies with security policy without special exceptions.

Delivery routes

RouteObjects created in STResult
boomiAccount + Generic-HTTP(S) site + Basic Application subscriptionFiles are processed by the Boomi listener (validation, audit, receipt).
sshAccount + SSH site to a registered profile (e.g. inbox_lab) + Basic subscriptionFiles are delivered to an SFTP inbox, e.g. 192.168.0.21:/usecase/inbox.
bothAccount + both sites + Advanced Routing subscription + SIMPLE / TEMPLATE / COMPOSITE routesOne Send To Partner step fans every file out to Boomi AND the SFTP inbox.

Notifications: e-mail & WhatsApp

Cloud-only

Runs entirely in Boomi Cloud (no bridge or VPN needed): e-mail through the existing 'Boomi Training (Mail)' connection (Amazon SES), WhatsApp through the Meta WhatsApp Cloud API.

Severity-tagged

Subject is prefixed [OmniMFT][INFO|WARNING|CRITICAL]; the message is sent as a URL-encoded parameter so line breaks and quotes are safe.

E-mail & WhatsApp

Channel per request: email, whatsapp or both. Recipients are dynamic (any e-mail domain, any WhatsApp number, ';'-separated); empty uses the defaults.

Approved & audited

Every message needs human approval (in Agentstudio or in the web portal) and is logged in Boomi (OMNIMFT_NOTIFY).

Local agent (Claude Code)

For engineers, the same logic is available as a local MCP server in Claude Code that reaches SecureTransport directly over the VPN.

OmniMFT web portal (localhost)

A lightweight operator console that replaces the Agentstudio chat window on the operator's machine. It runs at http://localhost:8080, talks to the same Boomi bridge endpoints as Agentstudio, and needs no cloud deployment.

Chat Copilot

Chat bubbles, the six conversation starters and quick follow-up chips. Partner names can be typed naturally (“check PT Nusantara Cargo” → PT_Nusantara_Cargo).

Approval cards

Resubmit, onboarding execution and every notification show an Approve / Reject card first; notification drafts are editable before sending.

Context-aware notifications

Every activity remembers its outcome; “send this to …” drafts the subject, severity and message from the last result. Recipients are read from the prompt.

Bridge health

Sidebar widget with SecureTransport connectivity, snapshot age, bridge worker status (read from the host) and Boomi API status, refreshed every 30 s.

One pattern for every activity

1

Run

Ask for an activity: failed transfers, certificates, partner check, partner transfers, onboarding, resubmit or bridge health.

2

Remember

The portal keeps a factual summary of the outcome (never passwords or secrets).

3

Notify

“…and e-mail it to …” or “send this to …” drafts the notification from that summary.

4

Approve

Review or edit the draft, then Approve & send; Boomi returns the status per channel.

Example prompts

PromptWhat the portal does
check PT Nusantara CargoRead-only partner setup check for PT_Nusantara_Cargo
transfer gagal dari akun RTGSLive SecureTransport search: failed transfers of account RTGS (7 days)
Check all partners and email the result to <address>Fresh partner check, then a WARNING e-mail draft listing the gaps and fixes
kirim hasil tadi ke <address>E-mail draft built from the last result in this session
kirim email ke <address> pesan: <text>E-mail with exactly the typed message

Modes

ModeBehaviourOpen
SimulationBuilt-in sample data; every flow can be tried offline and nothing is sent or changed.http://localhost:8080/?mode=simulation
LiveCalls the Boomi bridge listeners through the local proxy: real snapshots, queued actions and real notifications.http://localhost:8080/?mode=live

Architecture & guards

How to start: Start: python3 -I portal/portal_server.py (from the project folder), then open http://localhost:8080/?mode=live. Live mode needs the bridge and VPN for ST data; e-mail works without them.

Conversation starters

Six ready-made prompts in Agentstudio and in the web portal. Each one demonstrates a key use case end to end and doubles as a demo script.

1

“Which file transfers failed in the last 7 days, and why?”

Purpose: Shows instant operational visibility: the agent turns raw ST transfer logs into a plain-language failure report.

What the agent does: Reads the transfer snapshot, explains each failure (ST error, HTTP status, diagnosis, fix) and correlates Boomi-bound files with Boomi executions.

2

“Check certificates and keys that are expired or expire in the next 30 days.”

Purpose: Shows proactive security: certificate and key expiry is caught before it breaks partner connections.

What the agent does: Reads the certificate snapshot and lists CRITICAL (expired) then WARNING items with remediation commands for the operator.

3

“Check all partners and tell me which ones are incomplete.”

Purpose: Shows configuration assurance: deleted, misconfigured or half-built partners are found before files go missing.

What the agent does: Runs a read-only check of every OmniMFT partner (account, sites and targets, subscription, routes) and lists the ones that are not complete, with the fix for each.

4

“Onboard a new SFTP partner PT_Nusantara_Cargo and route its files to both Boomi and the SFTP inbox.”

Purpose: Shows automation of a change that normally takes an administrator many manual steps — with human control.

What the agent does: Builds a dry-run plan (removing leftover routes if the name was used before; account, two sites, Advanced Routing subscription and routes), waits for approval, executes with rollback and returns the SFTP connection details.

5

“Find the most recent failed transfer, resubmit it, and notify the ops team.”

Purpose: Shows end-to-end incident handling: diagnose, reprocess and report in one conversation.

What the agent does: Finds the latest failure and explains it, resubmits after approval (re-running the original upload when needed), then notifies the team after a second approval.

6

“Send a CRITICAL alert about expired certificates by email and WhatsApp.”

Purpose: Shows multi-channel communication: the agent informs people where they are, not just in the inbox.

What the agent does: Gathers the certificate facts, drafts subject, severity, recipients and a short message, asks for approval and sends it by e-mail and WhatsApp through Boomi, reporting the status per channel.

Starter 4 creates a real account (use a new name for repeat demos). For starter 5 prepare a fixable failure first; starter 6 sends WhatsApp once Meta approves the template.

Components

Boomi components

Platform folder: Training-Sandbox-WSL/OmniMFT-STInboundListener

ComponentTypePurpose
OmniMFT API - ST Inbound FileProcess (WSS listener)Receives files from ST: POST/PUT /ws/simple/executeStInboundFile
[SUB] OmniMFT - Receive ST FileProcess (subprocess)Unwraps multipart, rejects empty files, audits, returns JSON receipt
OmniMFT API - Send NotificationProcess (WSS listener)Validates channel, recipients and severity; sends e-mail and/or WhatsApp; returns per-channel status
OmniMFT Mail Send NotificationOperation (Mail)Inline text e-mail on the shared connection 'Boomi Training (Mail)'
OmniMFT WhatsApp Cloud API + Send TemplateConnection + operation (REST)WhatsApp template messages via graph.facebook.com; token injected from an environment extension
OmniMFT Bridge API - Upsert DocProcess (WSS listener)Bridge worker writes snapshots/results
OmniMFT Bridge API - Get DocProcess (WSS listener)Agentstudio reads snapshots/results (NOT_FOUND if missing)
OmniMFT Bridge API - Create RequestProcess (WSS listener)Agentstudio queues an action, returns a requestId
OmniMFT Bridge API - Query RequestsProcess (WSS listener)Bridge worker lists the queue
OmniMFT Disk Store + Upsert/Get/ListConnection + operations (Disk V2)Document store under work/omnimft on the cloud atom (no DELETE)
OmniMFT Ops CopilotAgentstudio agent6 tasks, 12 tools, guardrails; package v11.0 on Agent Garden Production

Agentstudio agent tools

ToolKindPurpose
get_bridge_healthReadBridge health, ST connectivity, snapshot age
get_transfer_snapshotReadTransfers of the last 24 h + failed transfers of 7 days
get_certificate_snapshotReadExpired & expiring certificates/keys (30 days)
get_boomi_inbound_snapshotReadBoomi listener executions of the last 24 h
request_live_transfer_searchAction (queued)Live transfer search with filters
request_snapshot_refreshAction (queued)Ask for snapshots to be refreshed now
request_resubmit_transferAction (approval)Resubmit a transfer in ST
request_partner_onboarding_planAction (queued)Onboarding plan for route boomi / ssh / both (dry-run)
request_partner_onboarding_executeAction (approval)Execute onboarding as planned
request_partner_checkAction (queued)Read-only partner health check (one or all partners)
send_notificationAction (approval)Notify by e-mail, WhatsApp or both (dynamic recipients)
get_request_resultReadFetch an action's result by requestId

On-premise code

FilePurpose
server.pyOmniMFT logic + MCP server for the local agent in Claude Code
omnimft/st_client.pySecureTransport Admin REST API v2.0 client (stateless, no session cookies)
omnimft/boomi_client.pyBoomi Platform API client (executions & execution history)
bridge_worker.pyOutbound-only bridge for Agentstudio (snapshots + action queue, restart-safe)
start-bridge.shStart / stop / status of the bridge worker
config/route_profiles.jsonRegistered SSH delivery targets (no secrets; passwords come from .env)
demo_resubmit.pyPrepares a fixable failure for the resubmit demo (prepare / fix / status / cleanup)
agent/agentgarden_build.pyCreates/updates tools and the agent in Agentstudio, and deploys
portal/index.htmlOmniMFT web portal: single-file chat UI with starters, approval cards and bridge health (simulation or live)
portal/portal_server.pyLocal server + proxy on 127.0.0.1:8080 that adds the Boomi credentials and allow-lists three bridge endpoints

Security & compliance

No inbound ports

No tunnel or open port; every connection goes outbound over HTTPS to *.boomi.com, compliant with Zscaler.

Credentials stay on-prem

ST, Boomi and SSH-target credentials live in .env (mode 600). New partner passwords are stored in secrets/ and never displayed.

Human approval

Resubmit, onboarding execution and every message require approval in Agentstudio or the web portal; onboarding always starts with a dry-run.

Allow-listed actions

The bridge only runs allowed actions; Boomi endpoints and SSH targets are fixed on-prem and cannot be changed from chat.

Agent guardrails

Refuses credential requests, destructive operations and private key content; tool results are treated as data.

Audit trail

Requests, inbound files and e-mails are logged in Boomi execution logs (OMNIMFT_REQUEST, ST_INBOUND, OMNIMFT_NOTIFY).

Test results

ScenarioResultStatus
Route boomi: CSV, 4 KB binary, empty fileProcessed / exact 4096 bytes / empty file rejected with diagnosisPassed
Route ssh (live)File delivered to 192.168.0.21:/usecase/inboxPassed
Route both (live)File delivered to the SFTP inbox AND received by BoomiPassed
Onboarding rollback & duplicate guardObjects removed on failure; existing account refusedPassed
Resubmit after fixing the site404 failure diagnosed; resubmit re-ran the upload; Boomi received the filePassed
E-mail notificationSENT to default and external (Gmail) recipients; invalid formats rejectedPassed
WhatsApp channelRequest reaches Meta; delivery starts once the message template is approvedPending
Bridge: queue → execute → resultProcessed by the bridge in about 8 secondsPassed
Partner setup checkComplete, incomplete (wrong Boomi path), deleted and orphaned partners detected correctlyPassed
Re-onboarding a deleted partnerLeftover routes listed in the plan and removed before re-creationPassed
Agentstudio deploymentPackage v11.0 ACTIVE on Agent Garden Production, 6 startersPassed
Web portal: live bridge via the local proxyHealth snapshot read; read-only partner check queued, executed by the bridge and returnedPassed
Web portal: e-mail to an external recipientRecipient taken from the prompt; Boomi returned SENT for an external Gmail addressPassed
Web portal: proxy guardsCalls without the portal header, other endpoints, kind=requests and foreign Host headers are refusedPassed
Web portal: conversation flows (simulation)6 starters, partner names in free text, and notify-about-the-last-result for every activityPassed

Technical challenges solved

FindingCauseSolution
ST native HTTP site rejected by Boomi (403)The native HTTP site speaks the ST-to-ST protocol (POST / first).Use the Generic-HTTP(S) plugin with the PUT method.
File name not transmittedST expressions are empty in the Generic-HTTP plugin; the file is sent as multipart.The Boomi subprocess unwraps the multipart and reads the name from Content-Disposition.
Agentstudio 'Invalid JSON request body'Agentstudio validates JSON bodies; free-text e-mail content is not JSON.Send the message as a URL-encoded query parameter with a static {} body.
Failed auto-push not resubmittableIn Basic Application only the original upload record is resubmittable.Resubmit the upload with the same coreId, which re-runs the push.
Mail step returns no documentBoomi Mail Send emits zero documents, so later steps are skipped.Branch: send on path 1, audit + acknowledgement on path 2.
Tunnels blockedZscaler blocks tunnelling apps.Outbound-only bridge architecture via Boomi.
Leftover routes after manual deletionDeleting an account in ST Admin keeps its account-less SIMPLE/TEMPLATE routes.The partner check reports them; re-onboarding the same name removes them after approval.
No free connector licenceThe account had used every Standard connector slot.Share one mail connection component instead of a duplicate, freeing a slot for WhatsApp.
Browser cannot call Boomi listenersBoomi Web Services listeners answer the CORS preflight with 403.A local proxy (portal_server.py) serves the portal and forwards three allow-listed endpoints with the Boomi credentials from .env.
WhatsApp template categoryMeta re-categorised the first template as MARKETING.A second, transactional template (UTILITY) is the default; the name is switchable via an environment extension.

Demo guide

Runbook

  1. Connect FortiClient VPN (ST 192.168.0.21 must be reachable).
  2. Start the bridge: ./start-bridge.sh, then check ./start-bridge.sh --status (must be RUNNING).
  3. Open Boomi Agentstudio → OmniMFT Ops Copilot → pick a conversation starter. Alternative: python3 -I portal/portal_server.py, then open http://localhost:8080/?mode=live.
  4. Approve actions and e-mails when the agent asks for confirmation.
  5. When finished: ./start-bridge.sh --stop.

Resubmit demo

  1. Prepare a fixable failure: .venv/bin/python demo_resubmit.py prepare (partner demo_resubmit, wrong Boomi path, file uploaded).
  2. Ask the agent: “Find the most recent failed transfer and tell me why it failed.” — it reports HTTP 404 on the endpoint path.
  3. Fix the site as the operator: .venv/bin/python demo_resubmit.py fix.
  4. Ask: “The site is fixed. Resubmit that transfer and email the ops team the result.” — approve both steps.
  5. Verify with demo_resubmit.py status; clean up with demo_resubmit.py cleanup.

Limitations & next steps

Limitations

  • Snapshots lag by about 1–2 minutes; for up-to-the-second data use refresh or a live search.
  • Queued actions take about 10–30 seconds including the agent polling for the result.
  • The bridge host and VPN must be up for ST data and actions; e-mail works without them.
  • SSH target host keys are not pinned (same as the existing RTGS site); notification recipients can be any domain or number, so approvals matter.
  • WhatsApp delivery depends on Meta approving the message template; template text is a single paragraph (no line breaks).
  • Queue/result files in Boomi are not deleted automatically (no-DELETE design); cleanup can be scheduled.
  • The web portal maps prompts to OmniMFT operations with rule-based intent routing (English and Indonesian), not a language model; free-form questions outside the supported operations get a help message.
  • The web portal remembers the last result only until the page is reloaded; it runs on the operator's own machine (127.0.0.1) and is not a shared multi-user service.

Next steps

  1. Move the bridge worker from the laptop to a lab server/VM so it runs 24/7.
  2. Replace the default ST admin account with a dedicated, least-privilege API account and rotate shared passwords.
  3. Pin SSH host keys on SSH delivery sites and register further SSH target profiles as needed.
  4. Add per-partner downstream routing in Boomi after the audit step.
  5. Renew the expired certificate and the one expiring within 14 days.