When should I create a Base44 entity?

Use an entity when submissions belong in the app, relate to users, need app permissions, or drive native workflows.

Can I use a Base44 backend function instead?

Yes. A backend function is appropriate for private credentials or custom transformations. A credential-free public endpoint can be called directly.

Should I also call SendEmail?

Usually not when Form Plume already owns notification delivery. Doing both can create duplicate emails with separate retries.

Which values are private?

The public form slug is visible by design. Base44 credentials, integration tokens, protected-form keys, and webhook signing secrets must remain private.

Does Form Plume work with Base44?

Yes. Form Plume gives you one endpoint that works from your app. Start with the quickstart docs, then drop the endpoint into your form.

Where do Base44 form submissions go in Form Plume?

Submissions are stored in your Form Plume dashboard, sent to your email, and can trigger integrations like webhooks, Slack, Discord, Google Sheets, Mailchimp, and ActiveCampaign. See the feature overview for the full flow.

Can I try Form Plume before wiring it into my app?

Yes. You can create an endpoint on the free plan, test it from localhost, preview, or a staging URL, and upgrade only when your form volume or team needs grow. Compare limits on pricing or ask a question on the contact page.

New:Build with AI agents

Send Base44 form submissions straight to your inbox.

Use one endpoint to handle contact requests outside your app data. Form Plume manages notifications, storage, spam protection, webhooks, and integrations.

Free foreverNo credit cardExternal inbox and downstream delivery

contact action

// Choose one operational owner for the submission.
const response = await fetch(FORM_PLUME_ENDPOINT, {
  method: "POST",
  headers: { Accept: "application/json" },
  body: new FormData(form),
});
if (!response.ok) throw new Error("Submission failed");

The full guide

One form, one operational owner.

Choose native app workflows or external delivery deliberately, keep secrets private, and avoid duplicate records and notifications.

Base44 already provides application data, authentication, backend functions, SendEmail, connectors, and custom integrations described with OpenAPI. It can build a working contact workflow natively. Form Plume is useful when contact operations need an external inbox, spam controls, notifications, signed webhooks, or downstream delivery without making submissions another Base44 entity.

1
Create your Form Plume accountStart free and give your Base44 form a hosted endpoint for email, submissions, spam filtering, uploads, integrations, and webhooks.Start free
2
Create the form and copy the endpointCopy the endpoint URL from Form Plume. It looks like https://api.formplume.com/f/your-slug
3
Connect it inside Base44Review the generated integration, test from preview, publish, and verify the final app origin and downstream delivery. Send one test submission from the real Base44 app or preview environment and confirm it reaches Form Plume.

Ask for direct public submission

Keep the existing Base44 contact form and visual design. On submit, send FormData to:
https://api.formplume.com/f/your-public-slug
 
Add accessible pending, success, and error feedback. Reset only after a successful
response and retain values after failure. Do not create a Base44 entity, SendEmail
automation, backend function, connector, or custom integration solely for this form.
The Form Plume endpoint is public. Never place Base44 credentials, protected-form
keys, integration tokens, or webhook signing secrets in client code. Show what changed
and how to verify both preview and the published app.

const response = await fetch("https://api.formplume.com/f/your-public-slug", {
  method: "POST",
  headers: { Accept: "application/json" },
  body: new FormData(form),
});
if (!response.ok) throw new Error("Submission failed");

This is intentionally not a claim that Base44 lacks email or integrations. It has both. The point is to choose one operational owner for contact submissions rather than duplicating storage and notifications across two systems.

Native Base44 versus Form Plume

Use a Base44 entity when the submission must appear in the app, relate to users, participate in permissions, or drive native automations. Use Base44 SendEmail when email is part of that application workflow. Use backend functions or custom OpenAPI integrations when private credentials or custom server transformations are necessary.

Use Form Plume directly when the form is public intake and you want dedicated storage, email routing, spam handling, integrations, and signed webhooks independent of the app's schema.

Do not submit to Form Plume and also create an entity or call SendEmail unless duplication is intentional. Otherwise one visitor action can create two records and two notifications with different retry behavior.

Preview and published checks

Inspect the generated behavior and confirm it did not also create an entity or SendEmail call.
Verify each field has a stable submitted name.
Submit in preview and check the Form Plume record and notification.
Test an invalid slug and confirm input is retained.
Publish, retest from the final hostname, and exercise any webhook or connector destination once.

Compare the other full-stack builders: Lovable, v0, Bolt, and Replit. For a code-owned client, see the React guide.

Primary sources

FAQ

Base44 questions
before you connect it.

Yes. Base44 includes app entities, SendEmail, connectors, backend functions, and custom integrations. Form Plume is an external operational destination, not a replacement required to make Base44 functional.

One line. Zero backend.

The form backend you don’t have to build.

Free foreverNo credit cardSet up in under a minute