How does it work?

1. Decide which Jitterbit Harmony pattern you need. Use Jitterbit Studio’s FTP connector when Jitterbit should read files from or write files to SFTP To Go. Use Jitterbit API Manager when SFTP To Go should call a custom API that triggers a Harmony operation. Use Jitterbit EDI when the workflow involves trading partners, EDI transactions, or FTP/SFTP document exchange. Use SFTP To Go File Automations when files should be copied, moved, deleted, encrypted, decrypted, delayed, or routed inside SFTP To Go before or after Jitterbit processing.
2. In SFTP To Go, create or select the credential Jitterbit Harmony should use. Use a dedicated credential for Jitterbit, bind it to the correct home directory, and give it only the directory permissions required for the workflow.
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, with alternative SFTP ports available where needed.
4. Choose the authentication method Jitterbit should use to connect to SFTP To Go. For password authentication, use the SFTP To Go username and password in the Jitterbit FTP connection. For SSH key authentication, configure the Jitterbit private key according to your Jitterbit agent setup and add the matching public key to the relevant SFTP To Go credential.
5. In Jitterbit Studio, create an FTP connection for SFTP To Go. Configure the SFTP To Go host, port, username, authentication method, runtime environment, and folder path according to the connector and agent setup you are using.
6. If Jitterbit should ingest files from SFTP To Go, add an FTP Read activity to the relevant Studio operation and point it to the SFTP To Go folder where inbound files will be available. Use the expected file name or file pattern so the operation processes only the files that belong to the workflow.
7. If Jitterbit should deliver output files to SFTP To Go, add an FTP Write activity to the relevant Studio operation and point it to the correct SFTP To Go output folder. Use an output filename pattern that downstream users, systems, or automations can recognize.
8. If files need preparation before Jitterbit 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 Jitterbit read from the prepared folder.
9. 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.
10. If SFTP To Go should trigger Jitterbit after a file event or File Automation, create and deploy the Jitterbit Studio operation first. The operation should accept the incoming request payload, branch on the event data where needed, retrieve the file through SFTP if file content is required, and return an appropriate response.
11. In Jitterbit API Manager, expose the deployed Studio operation as a custom API. Configure the service URL, method, security profile, environment, operation to trigger, and response behavior according to your Jitterbit API Manager setup.
12. In SFTP To Go, create a webhook notification or File Automation webhook action that calls the Jitterbit API Manager custom API URL. For webhook notifications, choose the endpoint type Webhook, paste the Jitterbit API 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.
13. Use SFTP To Go webhook filters to keep Jitterbit 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.
14. In Jitterbit, inspect the incoming request 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.
15. Branch the Jitterbit operation based on the incoming event type. For example, route file.created events to ingestion and transformation steps, file.downloaded events to audit or reporting actions, and file.deleted events to status updates or review tasks.
16. If Jitterbit needs the file content after receiving a webhook, use the SFTP path from the payload to retrieve the file through the configured FTP 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 Jitterbit FTP activity or script logic.
17. If your workflow uses Jitterbit EDI, configure the partner communication settings according to the trading-partner requirements. Use SFTP To Go as the managed SFTP server when Jitterbit EDI should send documents to or receive documents from a controlled SFTP folder, while Jitterbit EDI handles trading partners, EDI transactions, document processing, acknowledgments, archive behavior, and partner communication settings.
18. When configuring Jitterbit EDI FTP/SFTP communications, set the remote download folder, remote upload folder, file naming, automation frequency, retrieval mask, duplicate transaction check, and delete-after-download behavior according to the partner workflow. Avoid delete-after-download unless your retention and audit process allows the source file to be removed after Jitterbit retrieves it.
19. If Jitterbit 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 Jitterbit 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 Jitterbit operations 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, Jitterbit API Manager security profiles, and signature validation for SFTP To Go File Automation webhook requests where your Jitterbit 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 Jitterbit reads it from the expected FTP Read activity, API-triggered operation, or EDI communication setting.
24. Test the outbound flow by confirming that Jitterbit 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 Jitterbit, check operation logs, API Manager logs, EDI transactions, connector activity, retries, and error messages. 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 Jitterbit Harmony for application integration, API-triggered operations, mapping, transformation, partner workflows, 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, Jitterbit Studio FTP connector, Jitterbit FTP connection setup, Jitterbit API Manager custom APIs, publishing Jitterbit operations as APIs, Jitterbit EDI workflows, and Jitterbit EDI FTP/SFTP communications.