Remote systems
Use an agent-based connection for a server or endpoint included in your deployment.
FileMotion Agent
Extend the workflow to your endpoints.
Connect remote systems to your FileMotion deployment with the right endpoint component.
FileMotion Agent
Bring remote endpoints into the workflow.
The Agent is FileMotion’s endpoint component. Pair it with FileMotion Server when your deployment calls for an agent connection.
- Place the endpoint component on the system you need to connect
- Define the paths and access for the workflow
- Configure and run the transfer from the Server
Endpoint component
A local connection.
A central workflow.
Think of Server as the coordination point and Agent as the endpoint component. Select the connection model according to the system you need to reach.
REMOTE ENDPOINTSSERVER COORDINATION
Where Agents fit
Extend your reach without changing the goal.
Configured paths
Work with the paths and permissions selected for that endpoint, rather than assuming unrestricted access.
Central job control
Keep transfer-job configuration and execution coordinated from FileMotion Server.
Connection choices
Does every system need an Agent?
No. The appropriate connection depends on what the destination exposes and what your environment allows.
Agent connection
Use the FileMotion endpoint component where that deployment model meets your requirements.
Existing connection
Use a supported SFTP server or network share when an existing service provides the access your workflow needs.
Choose the right Agent setup.
Tell us your operating systems, locations, paths, and transfer direction. We’ll discuss the components you need.