Basic
Overview
Section titled “Overview”A connector of type Basic stores a user name and password, the password encrypted. It is the right place for every password a workflow needs: the mailbox for SMTP, access to an internal REST API, an FTP server or a network share (SMB). How to create a connector is described under None.
Structure
Section titled “Structure”| Field | Meaning | Placeholder |
|---|---|---|
| Username | user name | {{connector.<Name>.Username}} |
| Password | password (stored encrypted) | {{connector.<Name>.Password}} |
| Base URL | address of the service | {{connector.<Name>.BaseUrl}} |
Test signs in for real when the base URL is a server address (smtp://, imap://, ftp://, ftps://, sftp://, e.g. sftp://sftp.partner.com:22); for any other address it sends a request with Authorization: Basic … to the base URL.
Example
Section titled “Example”Mail server for SMTP. Connector Mailserver, auth type Basic, user name invoice@example.com, the mailbox password:
{ "Type": "SMTP", "Name": "Send", "Parameters": { "SmtpServer": "smtp.example.com", "SmtpUser": "{{connector.Mailserver.Username}}", "SmtpPassword": "{{connector.Mailserver.Password}}", "From": "{{connector.Mailserver.Username}}", "To": "customer@example.com", "Subject": "Your invoice", "Body": "Hello,\n\nplease find your invoice attached.", "Attachments": "{{FilePath}}" }}Internal REST API with Basic sign-in. Connector Internal from the Internal REST API template:
{ "Type": "HttpRequest", "Name": "Orders", "Parameters": { "Url": "/orders", "Connector": "Internal" }}SFTP server for FTP. Connector Partner, base URL sftp://sftp.partner.com, user name and password of the account. The FTP action takes protocol, host and port from the base URL:
{ "Type": "FTP", "Name": "Upload", "Parameters": { "Server": "{{connector.Partner.BaseUrl}}", "User": "{{connector.Partner.Username}}", "Password": "{{connector.Partner.Password}}", "Operation": "Upload", "Source": "{{FilePath}}", "Destination": "/inbox" }}