Informatica

How does it work?

1. Choose the right pattern: use an Informatica SFTP connection for file reads and writes, a file listener for supported folder monitoring, B2B Gateway for EDI or trading-partner flows, or Application Integration when SFTP To Go should call an Informatica REST endpoint.
2. In SFTP To Go, create a dedicated credential for Informatica. Bind it to the correct home directory and allow only the folder permissions the workflow needs.
3. Copy the SFTP To Go host, username, authentication details, and port from the SFTP connection setup. SFTP To Go uses SFTP port 22 by default.
4. In Informatica, create the SFTP connection required by your service. Configure the host, port, username, password or private key, runtime environment, and SFTP To Go folder path.
5. Use the Informatica SFTP connection as a source for inbound files or as a target for output files. Keep file names and folder paths predictable for the workflow.
6. Where supported, create an Informatica file listener for the SFTP To Go folder. Use narrow file patterns, listener events, schedules, and stability checks so only the right files are processed.
7. If files need preparation before Informatica reads them, handle that inside SFTP To Go. For example, use File created → PGP decrypt → Move, then let Informatica read from the prepared folder.
8. Use SFTP To Go File Automations for storage-side steps such as copy, move, delete, PGP encrypt, PGP decrypt, create file or folder, delay, notifications, or webhook requests.
9. For B2B Gateway flows, let Informatica handle trading-partner configuration, routing, transformation, validation, and EDI or EDIFACT processing. Use SFTP To Go as the managed SFTP exchange point.
10. To trigger Informatica from SFTP To Go, expose an Informatica REST endpoint where supported, then call it with an SFTP To Go webhook notification or File Automation webhook action.
11. Keep triggers narrow with SFTP To Go filters such as path, actor type, actor ID, and file or folder matching rules. For file-only workflows, exclude folder events.
12. In Informatica, inspect the incoming payload and branch by event type. For example, route file.created to ingestion, file.downloaded to audit actions, and file.deleted to status updates or review tasks.
13. If Informatica needs file content after a webhook, retrieve the file through the configured SFTP connection using the path in the payload. Decode Data.Path first if the payload uses URL encoding.
14. If Informatica writes an output file back to SFTP To Go, use File Automations on the output folder for follow-up handling such as encrypt, copy, move, notify, or trigger another webhook.
15. Use the SFTP To Go REST API only 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.
16. Make the integration safe and testable. Use dedicated credentials, narrow permissions, key authentication where preferred, IP allow lists where appropriate, HTTPS endpoints, retry-safe IDs, and signature validation where supported.
17. Test inbound, outbound, webhook, and automation paths. Review Informatica runs, listeners, B2B Gateway activity, retries, and errors alongside SFTP To Go file activity, credential access, automation history, webhook deliveries, and audit logs.
18. In production, keep responsibilities clear: Informatica handles data integration, mapping, transformation, B2B routing, and EDI processing; SFTP To Go handles managed SFTP access, secure storage, file automations, webhooks, API 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.