MuxForms on Bubble configures an API Connector call to POST /api/v1/forms/FORM_UUID/submit with JSON body keys matching your schema and Bearer ingest secret. Map input elements to the connector body in a workflow.
Docs
Bubble
Bubble API Connector can POST JSON to external APIs—wire your Contact button to MuxForms submit with the ingest secret in connector auth.
Bubble
| Bubble piece | Setting |
|---|---|
| API Connector | POST submit URL |
| Auth | Bearer private key |
| Workflow | Button → API call |
| Fields | Dynamic body from inputs |
API Connector setup
Name: MuxForms Submit. Method: POST. URL: use the submit endpoint with your form id. Headers: Content-Type application/json, Authorization Bearer <ingest secret> (private).
Body JSON (initialize call)
{
"email": "<email_input's value>",
"message": "<message_input's value>",
"_hp": ""
}Workflow
When Button Contact is clicked → API Connector MuxForms Submit → Show success group if success, else show error text from API response.
Common questions
- Expose secret in Bubble?
- Mark connector private; do not pass secret to client-visible elements.
- Bubble native forms plugin?
- MuxForms when you also need non-Bubble properties in one inbox.
- Error handling?
- Branch workflow on returned status code; show alert on 422.
- Rate limits?
- Same MuxForms limits as other clients.
No-code front, real inbox.
Prototype in Bubble; keep MuxForms when you add a Next.js marketing site.
Upgrade to Pro