Fillo can email one team address about each accepted response or a persistent delivery failure, and can send a confirmation receipt to the first answered email field.
Team notification email
Open the form's Notifications settings and enter the team address that owns the next action. The address autosaves and controls new-response mail; clear it to stop those messages. Fillo can also alert that address when a destination stays in a persistent failed state. If the address is empty, persistent delivery-failure alerts fall back to the workspace owner.
Use a team inbox when several people share the work. The email is a handoff signal, not your system of record — review and delete data in Fillo or the downstream destination, not from an email copy.
The notification names the form and links to its response workspace. It does not copy answers, respondent contact details, filenames, or other response content into the email.
Respondent receipt
Enable the receipt when respondents need confirmation that Fillo accepted the form. The renderer uses the first answered email field, so make that field required if every response needs a receipt destination.
The receipt confirms submission without echoing answer content, so less respondent data ends up sitting in mail systems.
Code-defined forms
notifyEmail and sendReceipt exist in FormSettings, but public publishable-key sync strips incoming values for both. They trigger server-side mail, so they stay dashboard-owned on synced forms.
Define and sync the form structure in code, then configure notifications in the dashboard. A stale code deployment won't overwrite the dashboard values.
const request = defineForm({
id: "support-request",
pages: [{
id: "main",
blocks: [
{ id: "email", kind: "email", label: "Email", required: true },
{ id: "issue", kind: "long_text", label: "What happened?", required: true },
],
}],
});Trust, updates, and limits
A held unverified submission sends no team notification and no receipt. Releasing it runs the normal accepted-response notification flow.
An update-in-place response produces the current response event, but email isn't a programmable per-answer routing engine. Fillo currently supports one owner address and the first answered email field. For conditional recipients, rich templates, attachments, or escalation rules, use a signed webhook, Zapier, or another destination.
Email delivery depends on provider acceptance, recipient suppression, and abuse throttles. Keep operational work in a destination where your team can see delivery state and retry it.
Plan status
The team notification email and respondent receipts are available on every plan, Free included.
Related
- Integrations: Choose a durable destination for the next action.
- Submission trust: See why held submissions don't send mail.
- Webhooks: Build conditional server-side notification logic.