How does it work?

1. Decide which Informatica pattern you need. Use an Informatica SFTP connection when Informatica should read files from or write files to SFTP To Go. Use an Informatica file listener where your Informatica service supports monitoring a folder for file arrival, update, or delete events. Use Informatica B2B Gateway when the workflow involves trading partners, B2B document exchange, EDI, or EDIFACT. Use Informatica Application Integration when SFTP To Go should call an Informatica REST endpoint after a file event or File Automation.
2. In SFTP To Go, create or select the credential Informatica should use. Use a dedicated credential for Informatica, bind it to the correct home directory, and give it only the directory permissions required for the integration.
3. Copy the SFTP To Go host, username, authentication details, and port by following the SFTP To Go documentation for SFTP connections. SFTP To Go uses SFTP port 22 by default, so set the Informatica connection port explicitly instead of relying on any generic FTP default.
4. Choose the authentication method Informatica should use to connect to SFTP To Go. For password authentication, use the SFTP To Go username and password in the Informatica connection. For key authentication, configure the private key in Informatica and add the matching public key to the relevant SFTP To Go credential.
5. In Informatica, create the SFTP connection type that matches the Informatica service you are using. Configure the host, port, username, password or private key, runtime environment, and folder path for the SFTP To Go directory that Informatica should access.
6. If Informatica should ingest files from SFTP To Go, configure the SFTP connection as the source for the relevant file ingestion, mapping, B2B Gateway, or data integration flow. Point the source to the SFTP To Go folder where inbound files will be available.
7. If Informatica should deliver output files to SFTP To Go, configure the SFTP connection as the target. Point the target to the correct SFTP To Go output folder and use a filename pattern that downstream users, systems, or automations can recognize.
8. If Informatica should run when files arrive, create a file listener for the relevant SFTP To Go folder where supported by your Informatica service and connector type. Configure the folder path, file pattern, listener events, schedule window, recursion, stability check, and any post-action settings according to your workflow.
9. Use file patterns carefully in Informatica. Limit the listener, source, or task to the file names and extensions that belong to the workflow, such as .csv, .xml, .json, .txt, .edi, .x12, or another agreed naming convention. This prevents temporary, archive, or unrelated files from being processed.
10. If files need preparation before Informatica reads them, keep that preparation inside SFTP To Go. For example, use SFTP To Go File Automations for File created → PGP decrypt → Move, or File created → Copy → Send webhook request, then let Informatica read from the prepared folder.
11. When using SFTP To Go File Automations, use a trigger such as File created, File downloaded, File deleted, or a schedule. Add a Type is File filter where the workflow should ignore folder events. Then add file actions such as copy, move, delete, PGP encrypt, PGP decrypt, create file or folder, delay, Slack notification, Microsoft Teams notification, email notification, or webhook request.
12. If your Informatica flow uses B2B Gateway, configure the partner flow according to the message type and trading-partner requirements. Use SFTP To Go as the managed SFTP exchange point for files that Informatica sends or receives through the configured SFTP connection, while Informatica handles partner configuration, B2B routing, transformation, validation, and EDI or EDIFACT processing.
13. If SFTP To Go should trigger an Informatica Application Integration process, expose the Informatica process as a REST service endpoint where supported by your Informatica setup. Use a process input structure that can accept the SFTP To Go webhook or File Automation payload.
14. In SFTP To Go, create a webhook notification or File Automation webhook action that calls the Informatica REST service URL. For webhook notifications, choose the endpoint type Webhook, paste the Informatica endpoint URL, select the relevant topics, and add filters where needed. For File Automations, add a webhook request action after the required file actions have completed.
15. Use SFTP To Go webhook filters to keep Informatica triggers narrow. Common filters include path, actor type, actor ID, and file or folder matching rules. For file-only workflows, use a path pattern or a Type is File automation filter so folders do not trigger file-processing logic.
16. In Informatica, inspect the incoming REST payload when using SFTP To Go webhooks or File Automation webhook actions. For webhook notifications, useful fields include Topic, Data.Path, Data.Size, Actor, and Metadata. For File Automation webhook actions, the payload also includes automation, execution, action, attempt, and idempotency metadata.
17. Branch the Informatica process or downstream flow based on the incoming event type. For example, route file.created events to ingestion and transformation, file.downloaded events to audit or reporting actions, and file.deleted events to status updates or review tasks.
18. If Informatica needs the file content after receiving a webhook, use the SFTP path from the payload to retrieve the file through the configured SFTP connection. If the payload comes from older SFTP To Go webhook notifications where Data.Path is URL encoded, decode the path before using it in the SFTP source configuration.
19. If Informatica creates an output file that requires storage-side handling, use SFTP To Go File Automations on the output folder. For example, use File created → PGP encrypt → Copy → Send webhook request, or File created → Move → Send email notification.
20. If Informatica or another orchestration layer needs to manage SFTP To Go configuration, use the SFTP To Go REST API for supported management tasks such as credentials, webhooks, share links, audit logs, and audit log exports. Use SFTP, FTPS, HTTPS, or S3 for file content rather than the management API.
21. Make the integration safe to retry. SFTP To Go webhook and automation delivery can be retried, and Informatica jobs or processes may also retry depending on their configuration. Use event IDs, delivery IDs, execution IDs, or X-Idempotency-Key values where available to avoid duplicate records, duplicate partner messages, repeated tickets, or repeated downstream actions.
22. Secure the integration. Use dedicated SFTP To Go credentials, narrow directory permissions, public key authentication where preferred, IP allow lists where appropriate, HTTPS endpoints for webhook calls, and signature validation for SFTP To Go File Automation webhook requests if your Informatica endpoint or fronting service validates signed requests.
23. Test the inbound flow by uploading a sample file to the SFTP To Go inbound folder and confirming that Informatica reads it from the expected source, file listener, task, partner flow, or process.
24. Test the outbound flow by confirming that Informatica writes the expected output file to the correct SFTP To Go folder and that any SFTP To Go File Automation, webhook, notification, or follow-up process runs as expected.
25. Review both systems after the test. In Informatica, check task runs, file listeners, process instances, B2B Gateway activity, error messages, retries, and monitor logs. In SFTP To Go, check file activity, credential access, automation execution history, webhook deliveries, and audit logs.
26. When the flow is ready for production, keep the responsibilities clear. Use Informatica for data integration, application integration, mapping, transformation, partner flows, B2B routing, and EDI processing. Use SFTP To Go for managed SFTP access, directory controls, secure storage, storage-side file automations, webhooks, API-driven management, and audit visibility.

You can find further insight into managed SFTP connection setup, SFTP file automations, SFTP webhook notifications, SFTP management APIs, Informatica Advanced SFTP V2 connector, Informatica Advanced SFTP V2 connection properties, Informatica file listeners, and Informatica REST endpoints and data conversion.