Application example Bindings

Use Send Email in a real application path

The send_email binding lets Workers send outbound email through Cloudflare Email Routing.

This example keeps outbound email explicit: one binding, one recipient rule, one worker path that sends one message.

It is enough to teach the binding accurately without dragging inbound processing or full provider workflows into the very first page.

Config focus: Explicit destination rules
Runtime shape: Call from a worker route
Best use: Transactional or support notifications

Start by wiring the binding clearly in config

Minimal Send Email config

import { defineConfig } from 'devflare/config'

export default defineConfig({

name: 'send-email-example',

files: {

fetch: 'src/fetch.ts'

bindings: {

sendEmail: {

SUPPORT_EMAIL: {

destinationAddress: 'support@example.com'

}

})

Build the application flow around the binding

Treat this as the app-level Send Email path: the route, event handler, or service module receives a real request and uses the binding to do useful work.

Keep product limits, remote ownership, and fallback behavior visible in the code around the binding instead of hiding everything behind a vague utility too early.

Keep the first outbound example narrow so the binding contract stays obvious.
If you also handle inbound email elsewhere in the app, document that on the email-event pages rather than merging the two stories here.

Send one email from the worker

import { env } from 'devflare/runtime'

export async function fetch(): Promise<Response> {

await env.SUPPORT_EMAIL.send({

from: 'noreply@example.com',

to: 'support@example.com',

subject: 'New support request',

text: 'A customer asked for help.'

})

return new Response('sent')

}

Keep production boundaries visible

Config focus: Explicit destination rules.
Runtime shape: Call from a worker route.
Best use: Transactional or support notifications.

One message is enough to teach the binding

You do not need a full notification system on the first page. One send call already proves the important contract.

Testing Send Email

Send Email is stronger locally than many platform-service bindings because outbound email can be exercised in the default harness, while inbound email has its own related helper surface.

Rate Limiting

Add the Rate Limiting config, call from worker code, and start with the local test path Devflare supports.