Skip to main content

Resend

Resend for fancy-flow — as four imported, versioned packages, one per runtime. Not vendored source: a copy cannot be upgraded, and third-party APIs change.

Runtime Package Install
Authoring surface (every host) @particle-academy/resend-ui npm install @particle-academy/resend-ui
Node @particle-academy/resend-js npm install @particle-academy/resend-js
PHP 8.4+ particle-academy/resend-php composer require particle-academy/resend-php
Python 3.11+ fancy-resend pip install fancy-resend

The ui package is the editor surface and is React on every host — a PHP or Python project installs it and its own runtime package, and never the js one.

What it costs you

One dependency: @particle-academy/fancy-connector-core (or particle-academy/fancy-connector-core on Composer), which the js and php packages pull in themselves. The Python package has zero runtime dependencies.

No Resend SDK. Plain HTTP, deliberately: a vendor SDK is third-party code subject to the kit's full approval bar, and one per provider is hundreds of dependencies nobody is tracking.

Setting it up

Everything below is generated from provider/manifest.json, so it cannot disagree with what the packages do.

Credentials

A Resend connection holds 1 value.

Every value here is account scope: one per connected account, not one per installation.

Field Scope Secret Where it comes from
API key per connected account secret re_... from the Resend dashboard. There is only one estate, so this key sends real email.

The estate

Resend has no test estate, and somebody checked. Everything this connector does is real. Use the faker to build against it.

Resend has NO test estate, and somebody checked. Its simulator RECIPIENTS -- delivered@resend.dev, bounced@resend.dev, complained@resend.dev, suppressed@resend.dev -- are not one: the send is real, it is billed, and it counts against the quota. Modelling them as a sandbox would put a live send behind a control labelled "test", so mode does not offer sandbox at all and fake is the primary development mode rather than the fallback.

What it can do

Actions

email_send — Send email

Send an email through Resend.

POST /emails · idempotent — safe to replay

Input Required What it is
from yes Must be an address on a domain you have verified with Resend. An unverified sender is refused at send time, not at setup.
to yes One address, a comma-separated list, or an expression. Resend's simulator addresses (delivered@resend.dev, bounced@resend.dev) are LIVE sends that are billed and counted — they are not a sandbox.
subject no Subject
html no HTML body
text no Plain-text body
replyTo no Reply-To
headers no Sent as the email's own headers. The usual use is a threading or reference id.

Run it before you have credentials

Every operation ships a faker, whether or not Resend has a sandbox. Set a node's mode to fake and it returns the shape Resend actually publishes — the same field names, deterministically — so you can wire the downstream nodes before touching an account, a key, or a network.

This repository is generated

provider/ is the source. Everything under packages/ is emitted from it and must not be hand-edited — CI regenerates and diffs on every push, and the next protocol sync destroys anything it finds. See AGENTS.md.

Two namespaces, which do not match on purpose

The repo is github.com/Fancy-Friends/resend; the packages publish under particle-academy. Nothing derives one from the other — the names come from weaver's friends.json and nowhere else.

Licence

MIT.

Metadata

Release files for fancy-resend 0.3.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fancy-resend 0.3.2
File Size Uploaded
fancy_resend-0.3.2.tar.gz 17.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for fancy-resend 0.3.2
File Interpreter ABI Platform
fancy_resend-0.3.2-py3-none-any.whl Python 3 none any Details

Total release size: 35.1 kB

Release files / fancy_resend-0.3.2.tar.gz

Download URL fancy_resend-0.3.2.tar.gz
Size 17.6 kB
Tags Source
SHA-256 checksum
How to use checksums
7e60f7a4b34b32893a7d00c3dc7691eed3a60f5cadfb76f4af444d0e86132234
BLAKE2b-256 checksum
How to use checksums
07af132b6a1b2c0076a5c25b6a3aa06ecc55e0a89486ee01520981412128400b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.15

Release files / fancy_resend-0.3.2-py3-none-any.whl

Download URL fancy_resend-0.3.2-py3-none-any.whl
Size 17.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5faf9fbe91a4fbb448b2e17e1c5f67a822a36a92a7cdeb9873ee62a7b3293e07
BLAKE2b-256 checksum
How to use checksums
79b8528ea3fc0e2a3a5fdd04060f487653981fe813d3c38a3260837e8059554a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.15

Release history Release notifications | RSS feed

0.4.0

2 release files

0.3.4

2 release files

0.3.3

2 release files

This release

0.3.2 This release

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page