Choose SMTP, Provider API or Connected Inbox
Compare SMTP, provider API and connected-inbox options before connecting business email to Wemblo.
Overview
Search Aliases: SMTP or API, connect mailbox, email sending method, Wemblo inbox type
SMTP
Best for: Standard email sending through a business mailbox or email service.
Usually requires: Host, port, username, password or app password, encryption.
Strength: Widely supported.
Important limitation: Does not automatically provide inbound conversation synchronization.
PROVIDER API
Best for: Supported email-delivery services with API features and event webhooks.
Usually requires: Provider account, verified sender/domain, API key or OAuth, event configuration.
Strength: Better provider-specific status and scale where supported.
Important limitation: Provider-specific setup and billing.
CONNECTED INBOX
Best for: Supported inbound and outbound mailbox workflows.
Usually requires: OAuth or mailbox authorization, folder access and Reply-To configuration.
Strength: Can connect replies and threads with customer history.
Important limitation: Availability and behavior depend on the provider and current Wemblo release.
DECISION CHECKLIST
- Do you need only outbound sending, or inbound replies as well?
- Does the provider support OAuth or API connection in Wemblo?
- Does the organization prohibit app passwords?
- What send volume and deliverability controls are required?
- Which provider events are needed for status and reporting?
- Who owns credential rotation and domain authentication?
BEST PRACTICE
Use OAuth or a restricted provider API where supported. Use an app password only when the provider supports it, the account has the required security configuration and a safer connection option is unavailable.
Last reviewed: