Email

by val-town2d3ec654b6a7No licenseListed Oct 8, 2026Updated Oct 8, 2026

Use when a val sends email, receives email, or is triggered by an incoming email. Covers email-type vals (the Email handler shape, attachment limits, the assigned val email address) and sending mail via std/email.

AI-generated overview

Guides building Val Town vals that receive incoming email and send mail via std/email.

What it does
Explains the email-type val handler shape, including the inbound Email object fields and the 30MB per-message limit. Shows how to read the val's assigned address from the API response rather than constructing it. Covers sending mail with the std/email send function and replying to an incoming message. Describes verifying changes by running the handler with a sample payload and checking logs.
When to use it
Use when a val needs to be triggered by incoming email, send email, or reply to a received message. Also useful when checking attachment limits or the val's assigned email address.
Requirements
Runs on Val Town; uses the std/email module imported from esm.town and the platform's file and log APIs. No scripts ship with the skill.

Email

Val Town supports both directions: vals can be triggered by incoming mail (email-type vals) and can send mail via std/email.

Receiving email — email-type vals

Email vals (fileType: "email") run when a message is delivered to the val's assigned address.

ts
// Learn more: https://docs.val.town/vals/email/// Email type: {//   from: string,//   to: string[],//   subject?: string,//   text?: string,//   html?: string,//   attachments: File[],//   headers: Record<string, string>// }export default async function (e: Email) {  console.log(e.from, e.subject, e.text);}

The file must have an export — export default for the handler.

Maximum 30MB per message, including attachments. Larger messages will be rejected.

Reading the assigned address

When you list files or create an email-type file, the response includes links.email — the address that triggers this val. Always read this from the API response. Never construct an email address yourself — the format is owned by the platform and may change.

Sending email — std/email

For outgoing mail, import from std/email:

ts
import { email } from "https://esm.town/v/std/email";
await email({  to: "[email protected]",  subject: "Hello",  text: "Message body",});

std/email exports email as the send function itself — call it directly (email({ ... })); there is no email.send method. It accepts the shape you'd expect: to, subject, text, html, plus from, cc, bcc, replyTo, attachments, and headers. If no to field is specified, it defaults to sending mail to the val owner's address.

Replying to an incoming message

Combine the two — read the inbound from in an email-type handler, then call email to reply:

ts
import { email } from "https://esm.town/v/std/email";
export default async function (e: Email) {  await email({    to: e.from,    subject: `Re: ${e.subject ?? ""}`,    text: "Got it, thanks!",  });}

Verifying changes

After editing an email-type val, use run_file with a sample Email payload to invoke the handler manually instead of waiting for a real incoming message. For send-only vals, run the script the same way and check get_logs for delivery errors.

Source and attribution

Source:val-town/pluginsinplugin/skills/emailat commit2d3ec65

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal