> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anycrm.anyreach.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Resend Inbound

> Mail arrived at the assistant's own domain (F23 v2 — Resend receiving).

Replaces the Gmail-filter → Pipedream bridge: notetaker.anyreach.ai has a
real MX now, Resend receives for it, and this route is where the
`email.received` webhook lands. Two trust improvements over the bridge —
the sender is an address Resend actually received mail from (SPF/DKIM
validated upstream, not asserted by whoever holds an HMAC secret), and
the Svix signature proves the event came from Resend. Same refuse-when-
unconfigured contract as every webhook beside it.

The event is metadata-only, so the full message is hydrated back from
Resend's API before extraction. A transient hydration failure answers
503 ON PURPOSE: Svix redelivers on non-2xx, and that retry is the only
thing standing between a blip and a silently lost booking request.
Everything downstream — vetting, dedup on message id, the attach-to-
existing lookup, the lane choice, the running-workflow supersede — is the
same path the old endpoint feeds; the two converge at the RPC.



## OpenAPI

````yaml /openapi-generated.json post /meetings/webhooks/resend-inbound
openapi: 3.1.0
info:
  title: anycrm-api
  version: 0.0.1
servers: []
security: []
tags:
  - name: Customer Intelligence
    description: >-
      Company research and ICP-fit scoring — create a research run, track its
      progress, and read back scored companies as leads.
  - name: Outreach
    description: >-
      The cold-email management console — domains, mailboxes, and campaigns — as
      a thin control plane over the SalesForge stack.
  - name: AnyCard
    description: >-
      Authenticated CRUD for AnyCard, the org's digital business-card /
      lead-capture product.
  - name: AnyCard Events
    description: >-
      Event-attribution analytics for AnyCard — which captured leads converted,
      broken down by source, owner, and deal.
  - name: AnyCard Share Links
    description: >-
      Unauthenticated endpoints reached by anyone who scans a QR code or opens a
      shared AnyCard link.
  - name: AI
    description: >-
      A streaming (SSE) AI chat endpoint with account-commit actions it can take
      on the caller's behalf.
  - name: Analytics Assistant
    description: >-
      The natural-language analytics assistant — a guarded text-to-SQL loop
      (SSE) that answers ad-hoc questions over the org's CRM data as a
      least-privilege, read-only database role.
  - name: Account Readiness
    description: >-
      Account Readiness Profiles — AI-scored signals on whether an account is
      ready for outreach or expansion, computed via a Temporal workflow.
  - name: Integrations
    description: >-
      Pipedream Connect — issuing connect tokens and managing the org's
      connected third-party accounts.
  - name: Feedback
    description: >-
      User-submitted platform feedback (bug reports, feature requests) — global,
      not scoped to one organization.
  - name: Public Media
    description: >-
      Unauthenticated image reads for publicly-embeddable assets (card photos,
      inline email images) — allowlisted by key shape; everything else in the
      storage bucket stays private.
  - name: Service Health
    description: Service liveness.
paths:
  /meetings/webhooks/resend-inbound:
    post:
      tags:
        - Meetings
      summary: Resend Inbound
      description: >-
        Mail arrived at the assistant's own domain (F23 v2 — Resend receiving).


        Replaces the Gmail-filter → Pipedream bridge: notetaker.anyreach.ai has
        a

        real MX now, Resend receives for it, and this route is where the

        `email.received` webhook lands. Two trust improvements over the bridge —

        the sender is an address Resend actually received mail from (SPF/DKIM

        validated upstream, not asserted by whoever holds an HMAC secret), and

        the Svix signature proves the event came from Resend. Same refuse-when-

        unconfigured contract as every webhook beside it.


        The event is metadata-only, so the full message is hydrated back from

        Resend's API before extraction. A transient hydration failure answers

        503 ON PURPOSE: Svix redelivers on non-2xx, and that retry is the only

        thing standing between a blip and a silently lost booking request.

        Everything downstream — vetting, dedup on message id, the attach-to-

        existing lookup, the lane choice, the running-workflow supersede — is
        the

        same path the old endpoint feeds; the two converge at the RPC.
      operationId: resend_inbound_meetings_webhooks_resend_inbound_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Resend Inbound Meetings Webhooks Resend Inbound Post

````