Send email from your app

1. In the project, open Settings and choose Email under the project. The Delivery section shows what happens to the app's email: Sending (it reaches your team and your verified inboxes), Sending · to anyone (it reaches anyone, from your own domain), or Capture ("Every email is captured and stored - nothing reaches a real inbox").

2. Send from the app's backend. A new Cloud app already sends three emails: a welcome email when someone registers, a password reset link, and each contact form message to you. For another email, ask the agent, or call @playcode/sdk, which reads the app's PLAYCODE_SECRET_KEY:

   import { Playcode } from '@playcode/sdk'
   
   const pc = new Playcode()
   const { status } = await pc.email.send({
     to: 'anna@example.com',
     subject: 'Your receipt',
     html: '<p>Thank you for your order.</p>',
   })
   

3. Test it on yourself: leave out to, and the email goes to the project owner's account address, which needs no verification. The call answers status: "sending". The agent can read the email back and follow its links.

4. To reach another inbox of yours, like a sales address, type it under Notifications and choose Send verification. Playcode emails it a link, and the address shows Verified once the link is opened.

5. To email your customers, verify your own domain. See Send from your own domain.

Later, the agent sees whether the receiving server accepted the email (Delivered), refused it (Bounced), or the person marked it as spam (Complained).

Each case and its fix is on An email did not arrive.

The app has no email credential, which happens in projects created before Playcode Email. Ask the agent to switch on email for the app.

The email has no to, and Playcode has no owner address for the app yet. Pass to, or ask the agent to check the app's email setup.

Send several emails instead. See What your app may send for the limits.

Add an html or a text body to the email.

The app reached a sending limit. The retry-after header says how many seconds to wait. If the app sends the same email again and again, fix that first: a loop pauses sending.

Replies go to the email's replyTo address, or else to the address in its from line. In a new Cloud app, that from address is noreply@example.com, which nobody reads. Set replyTo on every email that expects an answer.

Playcode delivers email without attachments. Put the file behind a link in the email.

The app never sent it. Ask the agent: it lists the app's emails with their status and reason, and finds where the app's code stopped.

• Playcode Email only sends. It hosts no inbox and cannot receive replies.
• Transactional email only: no newsletters or marketing. See What your app may send.
• The number of recipients per email and of emails per minute and per day is limited. See Sending limits.
• At zero credits, email past the included amount is stored, not delivered. Included email and email to the workspace's members still go out.
• A static site cannot send email: it has no server to keep the secret key.