SMTP

The SMTP tool in viaSocket allows you to send emails directly from your workflows using your own SMTP server. This feature is useful for transactional emails such as confirmations, alerts, or notifications, without requiring a third-party service.

When to Use the SMTP Tool

Use this tool when:

• You want to send custom emails based on workflow actions.

• You are using a private or company-owned SMTP server.

• You need full control over the email delivery process.

How to Add an SMTP Connection

To configure your SMTP settings, fill in the required details as shown in the SMTP form within viaSocket.

Host (Required)

Enter the address of your SMTP server.
Example: smtp.yourdomain.com or smtp.gmail.com

Email/Username (Required)

Provide the username or email address associated with your SMTP account.
Example: [email protected]

Password (Required)

Enter the password or app-specific password used for authentication with your SMTP server.

• Ensure this password matches your SMTP login credentials.

• Some providers may require you to generate an app password.

Port (Optional)

Select the appropriate port from the dropdown.
Available options:

• 587 – Used for SMTP with TLS (recommended)

• 465 – Used for SMTP with SSL

• 2525 – Often used as an alternative to 587 (supported by some providers)

• 110 – Generally used for POP3, not SMTP; avoid unless specified

• 80 – Used for HTTP, not email; select only if your provider explicitly instructs it

If you are unsure, 587 is usually the safest choice.

Use TLS? (Optional)

Specify whether to enable TLS encryption.

• Choose Yes if your SMTP server requires a secure connection (most do).

• Choose No if your server supports unencrypted access (not recommended).

Once these fields are completed, click Add Connection. This securely saves your SMTP settings, and you can use this connection inside any viaSocket workflow.

Best Practices

• Use app-specific passwords for services like Gmail or Outlook.

• Always use encrypted ports (587 or 465) for secure communication.

• Avoid using generic ports like 80 or 110 unless directed by your SMTP provider.

• Test the connection with a sample email before deploying your workflow.