The connection section tells an automation where data comes from or where it should be sent.
In the current engine, the supported connection types are:
| Type | Typical use | Supported for |
|---|---|---|
| ftp | Standard FTP file transfer | Import and export |
| sftp | SSH-based file transfer | Import and export |
| ftps | FTPS file transfer | Import |
| http | REST APIs and web endpoints | Import and export |
| Email inbox import or email delivery | Import and export | |
| sds3 | SureDone-managed S3 storage | Import and export |
| sdsftp | SureDone-managed SFTP storage | Import and export |
Common Connection Fields
- type - required connection type
- address - host, URL, or recipient address depending on the connector
- username and password - used for FTP, SFTP, and some HTTP login flows
- path - remote folder or path for file-based connectors
- headers and payload - used mostly with HTTP APIs
- port - optional port override when the default is not correct
FTP, SFTP, and FTPS
These are the standard choices for file-based integrations.
HTTP
Use http for APIs, JSON/XML endpoints, webhook-style requests, OAuth-based integrations, and multi-step trigger workflows.
Use email when you need to fetch attachments from an inbox or send exports by email. For exports, the connection typically includes recipient address information and may include options such as sending the file as an attachment.
SureDone S3
sds3 uses SureDone-managed S3 storage.
SureDone SFTP
sdsftp is used for SureDone-managed internal SFTP storage rather than a third-party server.
Choosing the Right Connection Type
- Use FTP/SFTP/FTPS when a vendor gives you files on a server
- Use HTTP when the vendor gives you an API
- Use Email when files arrive by inbox or need to be delivered by email
- Use sds3 or sdsftp when the workflow is built around SureDone-managed storage