Resend for Meta Muse
Community draft proposes: Send email through Resend and check delivery status. Every send is confirmed with you first.
Pinned source description: Send email through the Resend API and check delivery status. Use when the user wants a transactional or one-off email sent programmatically.
Community-authored Draft; OpenTools has not independently installed or live-tested this skill. A stored key is not proof of send permission. Verify the domain in Resend, then require explicit review of from, to, subject, and body before any send; use a real message ID to check results only after sending.
View original source ↗How to set it up
Paste a promptDraft — these instructions come from the linked source and have not been independently live-tested by OpenTools.
Source maturity: 🧪 Draft: written from Resend's public API docs; not yet live-tested end-to-end.
Before you start
- Resend API key (per-user, resend.com/api-keys)
Steps
- Review the pinned connectors/resend/SKILL.md and its listed files (SKILL.md, bin/resend.py). This community draft has not been live-tested end to end.
- Before setup: A stored key is not proof of send permission. Verify the domain in Resend, then require explicit review of from, to, subject, and body before any send; use a real message ID to check results only after sending.
- Only if the Muse runtime supports pinned repository installs and the source-declared credential and host flow, try `bin/resend.py get --id <a real id>`. Report the actual response and verify one safe read before any writes.
Prompt to paste into Muse
Inspect this community skill: https://raw.githubusercontent.com/bluman1/muse-connectors/6e31fd44a71f9f28377a1460e64cd7483c3cce22/connectors/resend/SKILL.md Read its Files manifest. If this Muse account supports custom skill installation and secure credentials, install exactly those files; otherwise report that the setup is unavailable. Collect credentials through Muse's secure credential flow; never ask me for raw keys in chat. Run the skill's status check and report the actual result.
Account access: Resend API key via the secure credential flow (`credentials.request_api_access`); create one at resend.com/api-keys
Allowed hosts: api.resend.com
Source status check: Source-proposed status check (not live-tested by OpenTools): `bin/resend.py get --id <a real id>`
A successful source status check may verify only configuration or credentials; it is not proof of a working end-to-end integration.
Services it connects with
These are the services the connector uses. The publisher is identified separately.
Resend