This SFTP connector setup guide shows you how to connect your Lingk infrastructure with your SFTP (Secure File Transfer Protocol) server, and allows data integration between SFTP and many other systems.PrerequisitesTo set up the SFTP connector, you need an SFTP account with read/write permissions.The SFTP connector supports the following authentication methodsUsername and PasswordSSH KeyMultifactor authenticationCompatibilityThe SFTP connector supports all versions of the Secure File Transfer ProtocolSFTP connector setup instructionsSTEP 1 - Set up an environmentHere you can create a new environment (recommended), or use the existing default environment.Learn how to set up an environment from our Environment Management GuideSTEP 2 - Add SFTP connectorFirst, you need access to an SFTP host to add the SFTP connector.You can also choose a different path from the root path (or just use the root path - /).Finally, there is an option to only connect with specific file patterns (or just use the default wildcard for all files - *.*). If you wanted to retrieve only CSV files, for example, you could use *.csv as a file pattern.Helpful tip: You can also use the file pattern option to dynamically retrieve files based on changing patterns, e.g. the latest file based on a date pattern. You can take a look at this sample recipe to understand how it works.Authentication can be done using one of three options:Username + PasswordThe most basic way to authenticate the SFTP connector with your SFTP server is to use a username-password combination.SSHSFTP connector also provides public key authentication. This method allows users to log in to your SFTP service without entering a password authentication and is often employed for file transfer automation.To use SSH, you need to generate an RSA secure keypair, save the private key in the SFTP server, and enter the public key in the SSH key field in your SFTP connector setup.Read more about connecting to SFTP with an SSH keyMultiFactor AuthenticationYou can also set up MFA with your SFTP server, if it supports MFA.You also need to have an SSH key set up for MFA to work (exactly like the SSH authentication) method.STEP 3 - Save the connectionYou can optionally test the connection, and click Save.OptionalMake these credentials available via API: Makes the connection available as a REST API for external integration.