Form notifications

By default, every form submission creates a notification in your in-app bell for your org’s owners and admins. You can also wire up email and Slack notifications per form for finer-grained control.

​

In-app notifications

Automatic. When a submission lands, the bell in the top-right of your dashboard shows a new dot. Click it to see what came in. Owners and admins all get notifications by default; team members can opt in via Settings → Notifications.

​

Notify a team member

By default, both the email and the in-app bell go to all org owners and admins. To route a form’s leads to one person instead:

1. Open the form in Forms → [your form] → Settings → In your CRM.
2. Under Notify a team member, pick who should hear about this form’s submissions.

That person then gets the email and a bell notification on every submission. Leave it on Every owner & admin to keep the default fan-out.

​

Also create a follow-up task

Also create a follow-up task (right below the picker) is on by default on new forms — each submission opens a task assigned to the notified team member (or an owner, if you left it on the default). The task is attached to the new contact and due a few business hours out, so a fresh lead lands in someone’s task list and doesn’t slip through. Turn it off for a form where a task per submission would be noise (say, a high-volume newsletter sign-up).

​

Confirmation email to the person who submitted

By default, the visitor who fills out your form doesn’t get an automatic reply (unless you’ve turned on AI auto-reply). To send them a simple “thanks, we got it” email:

1. Open the form in Forms → [your form] → Settings → After submission.
2. Tick Email a confirmation to the person who submitted.
3. Leave the subject and body blank to use the default wording, or write your own. Use {{first_name}} and {{business_name}} — if you didn’t collect a name, {{first_name}} becomes “there”.

It’s sent from your business (with your branding), to the email address they entered. If AI auto-reply is on for the form, this is skipped automatically — the AI reply is the response, and you don’t want to send both.

​

Slack notifications

If you’ve connected Slack at Settings → Integrations → Slack, you can route form submissions there too:

1. Pick a channel from the channel selector (defaults to #general).
2. Enable Form submission under “Notify on” in the Slack section.

Every submission posts to your chosen channel with the form name, the contact’s name, and a link back to the dashboard. Doesn’t replace email — runs in parallel. More on Slack integration →

​

Disable notifications for a form

If a form is purely internal (e.g., a feedback survey you don’t need real-time alerts on), disable the form in your team’s notification preferences. Submissions still save; you just don’t get pinged.

​

Per-user preferences

Each team member can manage their own notification preferences in Settings → Account → Notifications. They can opt out of email notifications, in-app notifications, or both — without affecting what other admins receive.

​

Webhook notifications (advanced)

If you want submissions delivered to your own backend (a Zapier-style trigger, a custom CRM sync, an internal system), use outgoing webhooks at Settings → Integrations → Webhooks. Subscribe a webhook URL to the form.submitted event and you’ll get a JSON POST per submission. More on webhooks →

​

Common setup

Most owners do:

• In-app: on (default).
• Email + tasks: route a few critical forms to a specific teammate (with a follow-up task); let everything else fall back to admins.
• Slack: on for high-volume forms (so the team sees them in flow) and off for low-volume ones.

That gives you a real-time pulse during the day and a central inbox to clear at end-of-day.

​

Next

You’re done with Forms. Next: