README

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.

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.

On Resend's side

1. Set up a receiving domain for your app's name — Resend receives mail for ANY address at a verified domain, so one domain serves every account: give each its own local part. Use a SUBDOMAIN if the root domain already handles mail. On the Domains page, copy the MX record value shown for the domain (it differs by region) into your DNS, then confirm it. Resend's MX record must be the LOWEST priority value on that domain, or mail does not reach Resend. (resend.com)
2. Create a Full access API key — Sending access "can only send emails", and the email_received trigger READS every message (email_get) and its attachments, so this connector needs Full access. The key's value cannot be viewed again after it is created, so store it straight away. (resend.com)
3. Point a webhook at your app's name — On the Webhooks page, Add Webhook: the endpoint is your host's webhook URL for this connector, and the event is email.received. Copy the webhook's signing secret exactly as shown, whsec_ prefix included; every delivery is refused until it is set. (resend.com)
4. Send a test message to an account's address — Send one email to an address on the receiving domain that belongs to an account, and check it arrives routed to that account. (resend.com)

Every step in full — who does it, what to paste, which credentials it yields, and how you know it worked — is in SETUP.md.

Credentials

A Resend connection holds 2 values.

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

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

attachment_get — Get attachment

Turn one attachment of a received email into a signed download URL.

GET /emails/receiving/{emailId}/attachments/{attachmentId} · reads only — safe to replay

attachment_list — List attachments

List a received email's attachments, each with a signed download URL.

GET /emails/receiving/{emailId}/attachments · reads only — safe to replay

email_get — Get received email

Read a received email in full: its bodies, its headers and the list of its attachments.

GET /emails/receiving/{emailId} · reads only — safe to replay

email_send — Send email

Send an email through Resend.

POST /emails · idempotent — safe to replay

Triggers

email_received — Email received

Start when an email arrives at one of your Resend receiving addresses, with the email read in full.

Delivered by webhook, and the signature is verified before anything runs. The delivery only names what arrived, so the run's first step reads it: email_get with emailId from data.email_id, published under email. A failed read fails the run.

You have to set this up with the provider first:

Point a receiving domain's MX record at Resend, then in the Resend dashboard (Webhooks → Add webhook) point an endpoint at the route your host mounts for this trigger and subscribe it to email.received. Put the endpoint's signing secret -- shown as whsec_… -- on the connection as webhookSecret, exactly as shown.

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.