company logo

Help center

Go to Hello Hotel
BlogPricingAboutRoadmap
All collectionsIntegrationsConnecting Your Email

Connecting Your Email

Connect Gmail, SMTP, or Resend to send automated emails from your hotel's address instead of a noreply address.

Connect your own Gmail, SMTP, or Resend account so automated emails go out from your hotel's address — guests see your domain in their inbox, not a noreply address.

Before You Start

Pick the connection type that matches your setup:

  • Gmail — easiest. Sign in once with Google OAuth and you're done. Works for both Gmail and Google Workspace accounts.

  • SMTP — works with any email provider that supports SMTP (custom domain, Microsoft 365, Zoho, Fastmail, etc.). Requires server credentials.

  • Resend — for teams already using Resend. Requires a Resend API key.

You can connect multiple email accounts to one organization (e.g., one for reservations, one for marketing).

Connecting Gmail

  1. Go to Settings → Integrations → Email

  2. Click Connect Gmail

  3. Sign in with your Google account and authorize Hello Hotel

  4. You're done. The connection appears with a green health indicator.

Gmail and Google Workspace are both supported. If your organization uses Google Workspace with restrictive third-party app settings, an admin may need to allow Hello Hotel before users can connect.

Connecting via SMTP

  1. Go to Settings → Integrations → Email

  2. Click Add SMTP Connection

  3. Fill in your SMTP server details:

    • Display Name — how this connection shows up in your workflow builder (e.g., "Reservations Email")

    • Email Address — the email address that will appear in the From line

    • SMTP Host — your provider's SMTP server (e.g., smtp.gmail.com, smtp.office365.com)

    • Port — usually 587 with STARTTLS, or 465 with implicit TLS

    • Security — toggle STARTTLS on for port 587

    • Username — usually your full email address

    • Password — your SMTP password or app-specific password

  4. Click Test & Save Connection

Hello Hotel sends a test connection to verify your credentials before saving.

Using Gmail or Google Workspace via SMTP? Google blocks regular account passwords for SMTP. You must generate an App Password (requires 2-Step Verification) and paste the 16-character code into the Password field. Use smtp.gmail.com with port 587, toggle STARTTLS on, and your full email address as the username.

Using a Google Group Address

Want emails to come from a group address like [email protected] that's actually a Google Group? Groups don't have their own passwords, so they can't connect directly — but you can send as the group through a regular Google Workspace account:

  1. Pick a real user account to send through, like whoever manages reservations. This account does the actual sending, but guests will only ever see the group address.

  2. In that user's Gmail, go to Settings → See all settings → Accounts → Send mail as and add the group address. Google emails a verification code to the group — any group member can grab it.

  3. Set up the SMTP connection as described above, with one twist: the Email Address field is the group address, while the Username and App Password belong to the real user account.

Don't skip the "Send mail as" step. If the group address isn't a verified alias on the sending account, Google silently replaces the From address with the user's own — and your guests will see the wrong sender.

When a guest replies, the reply goes to the group and is delivered to its members like any other group email.

Connecting Resend

  1. Go to Settings → Integrations → Email

  2. Click Add Resend Connection

  3. Paste your Resend API key

  4. Click Save

Testing Your Connection

Each email connection has a Send Test Email button on its card. Use it to send a real test email to any address — useful before wiring the connection into a workflow.

Tips

  • Verify SPF and DKIM on your domain. Whatever email provider you use, make sure your domain is properly authenticated to avoid deliverability issues. Your email provider's documentation has the records you need to add.

  • One connection per use case. If you send transactional confirmations and marketing campaigns from different addresses, set up separate connections so each workflow uses the right sender.

  • Rate limit is 100 emails per hour per organization. This protects your sender reputation. If you need more, reach out.

  • Connection health is monitored automatically. If a connection breaks (token revoked, password changed, API key invalidated), the connection is disabled and you'll see a red indicator on the card.

Did this answer your question?
😞
😐
😁