Add your existing native Framer forms to Brew. Each submission adds or updates a contact, and a published automation on the form's trigger can send a welcome or follow-up email.
Each form gets its own webhook URL, signing secret, and trigger. A brand can have several named forms. You do not need a Brew API key or a relay server.
Brew saves the contact even when no automation is published. A repeated email address updates the existing contact in the brand, and missing optional fields do not erase stored values.
Submissions cannot change subscription, suppression, or routing fields. An existing unsubscribe stays in effect.
Automations dispatch only after the contact write succeeds. If storage fails, Brew retries before starting anything.
When Framer marks a submission as possible or likely spam, Brew discards it without saving a contact or starting an automation.
Every form requires an email field. firstName and lastName are optional. Custom fields can be text, integer, or checkbox values. Use text for dates. Nested objects, lists, and file uploads are not supported.
The Framer form can carry extra inputs. Brew reads only the declared fields and lists the rest as ignored in Submissions.
Each field except email saves to a contact column of the same name, created on the first submission. Contact columns can point a field at an existing column instead, so an input named name can save to First name.
Declared fields are the merge tags for automations on that form. Editing fields updates the trigger and its contract. Brew blocks incompatible edits while a published automation uses the form.
A form submission is not consent to marketing email unless your form asks for it. Add a clear consent field if you plan promotional sends.
No. Use Framer's built-in form with its Webhook destination. A code component posts from the visitor's browser, cannot produce Framer's signature, and would expose the secret in the page. Brew answers such requests with a 401.
Receipt, contact saving, and automation dispatch are separate outcomes in the Submissions tab. Confirm an automation on the form's trigger is published, then check its filters, execution history, and the sending domain. A submission rejected for invalid fields or marked as spam starts nothing.
