Exchange data with Transports
Use Transports to receive files or messages from external systems and to send Flow output. Start with Transport concepts to understand direction, queueing, retries and service-account boundaries.
Choose a Transport
- For FTP, SFTP or network folders, use file and network Transports.
- For web endpoints, use HTTP Transports.
- For Microsoft Message Queuing or IBM MQ, use message-queue Transports.
- For mailbox collection or email delivery, use email Transports.
The available type is not a compatibility promise. Confirm the authentication, protocol, server and client-library requirements for the deployed Velox version and target system.
Implementation path
- Create an inactive Transport in Designer and configure a non-production endpoint.
- Test connectivity with sanitised content and the intended runtime identity.
- Configure local File Connections and post-receipt handling where required.
- Add an outbound Transport to a tested Flow, or add an inbound Transport to a monitored Flow.
- Follow Test and operate Transports to verify queue and delivery outcomes separately from Flow completion.
Operate safely
Treat credentials, certificates, payloads and communication traces as sensitive. Before retrying, check both Flow execution and Transport Logs so an earlier queued item is not delivered twice.
Review shared authentication, TLS, timeout and retry settings. Use file and Transport troubleshooting when a test or queued item fails.