---
title: "Resend Connector | Tajo"
description: "Implementation notes for building and operating the Resend connector in Tajo."
url: https://tajo.io/docs/connectors/resend/
markdown: https://tajo.io/docs/connectors/resend.md
lang: en-US
author: "Set Noa"
author_url: https://tajo.io/set-noa/
robots: noindex
---

# Resend Connector

[Set Noa](https://tajo.io/set-noa/)

Connector status: In progress Being built. Not verified yet.

| Source field | Destination field | Sample value |
| --- | --- | --- |
| `record.id` | `source_id` | `record_1042` |
| `record.updated_at` | `updated_at` | `2026-10-18T08:00:00Z` |
| `record.value` | `value` | `sample_value` |

Connector implementation

## Build the Resend integration

Developer email platform for transactional email, broadcasts and contacts

Migrate from

*Resend connector flow from source system to Tajo mapping and Brevo activation.*

## Implementation Overview

**Build target**

Implement a Resend connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.

**Current status**

Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.

**Primary surface**

github.com/resend/resend-openapi/blob/main/resend.yaml

| Property | Value |
| --- | --- |
| Integration surface | OpenAPI |
| Status | In progress |
| Category | Migrate from |
| Setup complexity | medium |
| Vendor documentation | [resend.com/docs/api-reference/introduction](https://resend.com/docs/api-reference/introduction) |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | [github.com/resend/resend-openapi/blob/main/resend.yaml](https://github.com/resend/resend-openapi/blob/main/resend.yaml) |
| MCP server | Not recorded |
| Last researched | 2026-10-30 |

Official OpenAPI 3.1 document (version 1.5.1). Bearer API key (Full access for reads). Cursor paging on the last id with has\_more; no change filter on any list. Resend also publishes an MCP server (resend-mcp, one tool per operation); this connector does not use it.

## Authentication

- Use [github.com/resend/resend-openapi/blob/main/resend.yaml](https://github.com/resend/resend-openapi/blob/main/resend.yaml) to generate or validate typed API clients and request models.
- Keep [resend.com/docs/api-reference/introduction](https://resend.com/docs/api-reference/introduction) linked from the connector runbook so operators can confirm vendor behavior during incidents.
- Store credentials per Tajo workspace and keep tenant-specific secrets out of connector configuration files.
- Add a credential smoke test that verifies read access to a harmless resource before running backfills or enabling webhooks.

## Data To Sync

Start with these inferred data domains, then confirm exact vendor resources and permissions from the source documentation:

- Contact and identity records
- Campaign, messaging, or audience state

The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.

## Sync Shape

| Resource | Direction | Conflict handling |
| --- | --- | --- |
| `contacts` | bidirectional | source\_wins, loop guard none |
| `suppressions` | inbound | n/a |
| `emails` | inbound | n/a |
| `segments` | inbound | n/a |
| `topics` | inbound | n/a |
| `domains` | inbound | n/a |

Resend is the record of the contact and its unsubscribe; the writes back (create\_contact, update\_contact, unsubscribe\_contact) never resubscribe anyone, and the full read has no watermark a write could move.

## Mapping To Tajo/Brevo

#### `contacts` → Brevo contact

Requires: **workspace api key**.

| Source field | Brevo destination | Via | Note |
| --- | --- | --- | --- |
| `email` | `email` | — |  |
| `firstName` | `attributes.FIRSTNAME` | — |  |
| `lastName` | `attributes.LASTNAME` | — |  |
| `id` | `attributes.RESEND_ID` | — |  |
| `createdAt` | `attributes.RESEND_CREATED_AT` | — |  |
| `tajo_email_marketing_consent` | `filter` | — | the canonical consent pair: consent is always false (Resend records no opt-in), so no contact passes on Resend’s record alone; unsubscribed is a suppression |

Read for context and not projected: `suppressions`, `emails`, `segments`, `topics`, `domains`.

The conventions that apply to every connector — stable external IDs, normalization, backfill and sync strategy, error handling, and the builder checklist — are documented once under “Applies to every connector” on the [connector catalog](https://tajo.io/docs/connectors).

## Sources

- [Vendor documentation](https://resend.com/docs/api-reference/introduction)
- [OpenAPI or schema source](https://github.com/resend/resend-openapi/blob/main/resend.yaml)
- [resend.com/docs/api-reference/pagination](https://resend.com/docs/api-reference/pagination)
- [resend.com/docs/api-reference/rate-limit](https://resend.com/docs/api-reference/rate-limit)
- [github.com/resend/resend-openapi](https://github.com/resend/resend-openapi)