Create CMS items from incoming content emails
When a structured submission email is received in Resend, automatically create a new content item in Netlify.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Netlify Explore Netlify →
TriggersFires when a new page or post is published on Netlify.
Fires when a form on Netlify is submitted.
Fires when a CMS item is updated on Netlify.
Publishes or updates a page on Netlify.
Creates a new CMS item on Netlify.
Updates existing content on Netlify.
Resend Explore Resend →
TriggersFires when a new email arrives in Resend.
Fires when an email is sent from Resend.
Fires when a tracked email sent via Resend is opened.
Fires when an email sent via Resend bounces.
Sends an email via Resend.
Creates a draft email in Resend.
Applies a label or folder to an email in Resend.
Moves an email into a different folder in Resend.
More Netlify + Resend workflows
See all Netlify + Resend integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Create CMS items from incoming content emails” between Netlify and Resend?
Yes — describe it in the box above and Knit's Integrations Agent researches Netlify and Resend's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
How does integrating Resend and Netlify assist web administrators?
Web teams get immediate email notifications whenever users submit web forms or when website content is updated.
Can incoming emails publish content to a website?
Yes, receiving formatted emails in Resend can automatically create or publish new CMS items in Netlify.