Connectors
Resend
Connect Resend for modern API delivery while keeping GenieOS as the template and workflow layer.
Use the Resend connector when your team wants a lightweight ESP API with GenieOS handling templates, validation, approvals, and audit history.
Before you start
- Create a Resend API key.
- Verify the sending domain in Resend.
- Confirm the
fromaddress you will use for workspace sends.
Setup
sequenceDiagram
participant Admin as Workspace admin
participant MG as GenieOS
participant Resend as Resend
participant Recipient as Recipient
Admin->>Resend: Create API key and verify domain
Admin->>MG: Install Resend connector
MG->>Resend: Send test email
Resend->>Recipient: Deliver email
Resend->>MG: Webhook events- Open Settings -> Connectors and choose Resend.
- Paste the API key.
- Set default sender details.
- Add the GenieOS webhook URL in Resend.
- Send a connector test.
Capabilities
| Capability | Support |
|---|---|
| Transactional sends | Yes |
| Broadcast sends | Yes |
| Attachments | Resend limits apply |
| Inline images | Resend limits apply |
| Webhooks | Delivery, bounce, complaint, open, click events where enabled |
| Suppressions | Provider events can create GenieOS suppressions |
Webhooks and suppressions
Resend webhook events are normalized into GenieOS timelines. Bounces, complaints, and unsubscribe-style events should be treated as suppression signals where Resend emits them for your account configuration.
Troubleshooting
- Authentication errors usually mean the API key was revoked or copied incorrectly.
- Sender errors usually mean the domain is not verified in Resend.
- Missing events usually mean the webhook endpoint was not created or the event type was not enabled.
Resend is a good default when you want a simple API provider and do not need a heavy lifecycle marketing platform.