Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Tymeslot/tymeslot/llms.txt

Use this file to discover all available pages before exploring further.

Email delivery is a hard requirement for any production Tymeslot instance. The platform sends outbound mail for booking confirmations (with ICS calendar attachments), booking reminders, cancellation and reschedule notifications, password reset links, and contact-form submissions. Without a working email adapter, users cannot recover their accounts and invited guests never receive their booking details.

​
Why email is required

Every key user-facing workflow depends on outbound email:
  • Booking confirmations — sent to both the host and the guest immediately after a booking is created, with an .ics attachment guests can import into any calendar app.
  • Reminders — automated emails sent before a scheduled meeting.
  • Cancellation and reschedule links — the only way guests can modify or cancel a booking is through a signed link delivered by email.
  • Password resets — standard account recovery flow.
  • Contact-form submissions — forwarded to EMAIL_CONTACT_RECIPIENT.
The default EMAIL_ADAPTER=test silently discards every outgoing message — no error is shown, no mail is queued, nothing is delivered. This is intentional for development and test environments, but it means password resets, booking confirmations, and all other transactional email will vanish without a trace on a misconfigured production instance. Always set EMAIL_ADAPTER to smtp or postmark before going live.

​
Sender identity variables

Regardless of which adapter you use, set these variables to control how your emails appear to recipients:
VariableDefaultDescription
EMAIL_FROM_NAMETymeslotSender display name shown in email clients
EMAIL_FROM_ADDRESShello@tymeslot.appSender address — use an address on your own domain
EMAIL_SUPPORT_ADDRESS(same as EMAIL_FROM_ADDRESS)Support address shown in email footers
EMAIL_CONTACT_RECIPIENT(same as EMAIL_FROM_ADDRESS)Recipient for contact-form submissions

​
Adapter configuration

SMTP is the right choice for most self-hosted deployments. It works with any mail provider that supports STARTTLS on port 587 — including Gmail (with an App Password), SendGrid, Mailgun, Brevo, Amazon SES, and your own mail server.Set these variables in your .env:
EMAIL_ADAPTER=smtp
EMAIL_FROM_NAME="Your Company"
EMAIL_FROM_ADDRESS=noreply@yourdomain.com
SMTP_HOST=smtp.example.com
SMTP_PORT=587
SMTP_USERNAME=your-smtp-username
SMTP_PASSWORD=your-smtp-password

​
Provider examples

EMAIL_ADAPTER=smtp
EMAIL_FROM_NAME="Your Company"
EMAIL_FROM_ADDRESS=you@gmail.com
SMTP_HOST=smtp.gmail.com
SMTP_PORT=587
SMTP_USERNAME=you@gmail.com
# Use a Google App Password, not your account password.
# Generate at: myaccount.google.com/apppasswords
SMTP_PASSWORD=your-16-char-app-password
SMTP_PORT defaults to 587 (STARTTLS), which is the standard value for almost all providers. Only change it if your provider explicitly requires a different port.

​
Testing your email configuration

The quickest way to verify that email delivery is working is to use the Forgot Password flow:
1

Open the login page

Navigate to your Tymeslot instance and click Forgot password? on the login screen.
2

Enter your email address

Submit the form with the email address of a registered account.
3

Check your inbox

A password reset email should arrive within a few seconds. If it does not arrive, check docker logs tymeslot for delivery errors.
If you see EMAIL_ADAPTER not set or test adapter messages in the logs, verify that your .env changes have been picked up by restarting the container: docker restart tymeslot.

Build docs developers (and LLMs) love

Get started for freeTalk to us