resend

Name: resend
Availability: InStock
Author: Curvenote

Route email tasks to Resend sub-skills for sending, inbound processing, and audience management.

161|10|Updated Sep 24, 2021

Search Tags:#automation #routing #email #webhook #resend #inbound

Ready to run

npx skills add https://github.com/curvenote/curvenote --skill resend-curvenote

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resend
Source: https://github.com/curvenote/curvenote/tree/main/.agents/skills/resend
Command: npx skills add https://github.com/curvenote/curvenote --skill resend-curvenote

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes routing logic to the Resend sub-skills for email sending, inbound processing, and audience management, simplifying integration for developers building automated email workflows.

Core Features & Use Cases

Sub-skill routing: Direct tasks to Send-email, Resend-inbound, or Moltbot as needed.
Unified onboarding: Quick-start references for API keys, domains, and webhooks.
Use Case: Build modular email pipelines where outbound and inbound workflows are cleanly separated and routed to specialized sub-skills.

Quick Start

Use the resend skill to route a request to the appropriate sub-skill like 'send-email' for transactional emails, or 'resend-inbound' for inbound processing.

Frequently Asked Questions about resend

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

FAQPage Schema

How do I automate email workflows with inbound webhooks and transactional sending?▼

Automating email workflows involves routing tasks to specialized sub-skills for transactional sending and inbound webhook processing. This approach separates outbound and inbound pipelines to simplify integration and secure modular email flows.

What is the best way to route inbound email processing separately from outbound transactional emails?▼

Routing inbound email processing separately requires a central routing logic that directs tasks to dedicated sub-skills. This Skill routes inbound webhooks and transactional sending to distinct modules, ensuring automated email workflows remain cleanly separated and modular.

Do I need API keys and domain configuration to set up automated email routing?▼

Yes, setting up automated email routing requires API keys and domain configuration. This Skill specifies dependencies on these prerequisites alongside webhook setup to empower secure, modular workflows for both outbound sending and inbound audience management.

Can I use this routing approach for agent inbox scenarios and audience management?▼

Yes, this routing approach applies to agent inbox scenarios and audience management. The Skill routes requests to sub-skills like Moltbot for audience tasks, handling transactional sending, inbound webhooks, and agent inbox integration within modular email pipelines.

How do I start sending transactional emails after configuring webhooks and domains?▼

To start sending transactional emails, use this Skill to route a request to the send-email sub-skill. It provides unified onboarding references for API keys, domains, and webhooks, enabling quick integration for automated outbound email workflows.

Why separate email routing logic instead of handling sending and inbound processing together?▼

Separating email routing logic prevents coupling between outbound and inbound workflows, simplifying integration for developers. This Skill centralizes routing to specialized sub-skills, ensuring transactional sending and inbound webhooks are processed cleanly within modular pipelines.