weegloo-send-email

Configure SMTP email accounts and send transactional email from Weegloo Spaces.

1|2|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-send-email-weeglooapi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weegloo-send-email
Source: https://github.com/weeglooapi/weegloo-mcp-plugin/tree/main/plugins/weegloo/skills/weegloo-send-email
Command: npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-send-email-weeglooapi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up product email (notifications, receipts, verification codes, digests) on Weegloo requires choosing an SMTP vendor, registering an EmailAccount with correct credentials, and wiring a Script's EmailSend — with vendor-specific pitfalls that silently fail. This Skill guides the full flow, defaulting to Gmail SMTP when no vendor is named. ## Core Features & Use Cases - Vendor selection with a Google default: When the user names no SMTP service, it uses Gmail (smtp.gmail.com:587/StartTls) and asks only for a Google App Password and its account address; it also covers Naver, Resend, and Brevo presets with per-vendor username/password/fromAddress rules. - EmailAccount creation guidance: Explains that creating an account sends a real test message before persisting, that endpoint/username/password are immutable (rotation means recreate), and that Update is REST-only, not an MCP tool. - Permission and plan constraints: Details the SETTING_EMAIL_ACCOUNT permission, token-type restrictions (no SpaceAccessToken), and plan limits on custom SMTP hosts. - Use Case: A user building a booking product needs order confirmation emails; the Skill walks them through creating a Gmail App Password, registering the EmailAccount, and pointing a Script's EmailSend at it. ## Quick Start Set up email sending for my Weegloo space so my app can send order confirmation emails.

Frequently Asked Questions about weegloo-send-email

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send email from a Weegloo Space?

Create an EmailAccount (the SMTP sender registered in the Space via the CMA API), then use a Script's EmailSend statement to send messages through it. The account must exist first, and EmailSend never carries a from-address — the sender identity lives on the account.

Which SMTP service should I use if I haven't picked one?

Use Google Gmail SMTP (smtp.gmail.com, port 587, StartTls), which is the default and works on every plan. You only need to provide a Google App Password from myaccount.google.com/apppasswords and the Google address it belongs to.

What credentials do Resend and Brevo need for SMTP?

Resend's username is the literal string "resend" with an API key as the password, and any address at a verified domain as fromAddress. Brevo uses its @smtp-brevo.com login as username and its SMTP key (not the API key) as password.

Why did my EmailAccount creation fail with an error?

Creation sends a real test message before storing anything, so a refusal means wrong settings (commonly a mistyped App Password) or vendor-side prerequisites not met, such as an unverified Resend domain. The server's failure reason is returned, and no resource is left behind.

Can I update an EmailAccount's password or endpoint after creation?

No. The endpoint, username, and password are immutable, and password is never readable. To rotate credentials or change servers, create a new account, repoint your Script's EmailSend to the new id, then delete the old account.

Can a SpaceAccessToken manage email accounts?

No. Managing EmailAccounts requires the SETTING_EMAIL_ACCOUNT permission and is only reachable from a console login session or Personal Access Token. SpaceAccessToken, DeliveryAccessToken, and ServiceUser tokens cannot manage email accounts at all.