Form Follow-Up

All tutorials

Every form in Domma CMS can trigger up to four things after a submission is stored:

  1. Send an email notification to one or more recipients
  2. POST to a webhook URL
  3. Execute a CMS Action (Pro)
  4. Redirect the visitor to a success page (or show an inline message)

These are configured per-form in the admin. Open any form in Forms and go to the Settings and Actions tabs.

1. Email notification

Go to the Actions tab of your form and enable Send email on submit. Enter one or more comma-separated recipient addresses. This uses the SMTP settings configured in Site Settings → Email / SMTP.

Recipients:       admin@example.com, team@example.com
Subject Prefix:   [Contact Form]

2. Webhook

Enable POST to webhook on submit and enter a URL. Domma will POST the following JSON body:

{
  "form": "enquiries",
  "data": {
    "full_name": "Jane Smith",
    "email": "jane@example.com",
    "message": "Hello!"
  }
}

Use this to integrate with Zapier, Make, Slack, or any HTTP endpoint.

3. CMS Action (Pro)

Actions are reusable workflow steps defined in Actions. A single action can chain multiple steps: update a field, move an entry to another collection, send an email, call a webhook, or delete an entry.

To wire an Action to a form:

  1. Create an Action in Actions targeting the same collection as your form.
  2. Open the form in Forms → Actions tab → CMS Action card.
  3. Select the Action from the dropdown and save.

The Action runs server-side, after the entry is saved. If it fails (e.g. MongoDB is not configured), the submission is still stored - the action failure is non-fatal and logged as a warning.

4. Success message vs. redirect

After a successful submission the visitor sees one of two things:

  • Inline success message - the form is replaced by the text set in Settings → Success Message. Good for simple acknowledgements.
  • Page redirect - the visitor is sent to the URL set in Settings → Success Redirect URL. Good for registration flows, checkouts, or when you want a full thank-you page with additional content. Takes priority if both are set.

Example: set Success Redirect URL to /thank-you and create a thank-you.md page in the CMS with any content you like.

Execution order

On every submission, the pipeline runs in this fixed order:

  1. Validate fields + honeypot + rate limit
  2. Store entry to collection
  3. Send email (if enabled)
  4. Call webhook (if enabled)
  5. Execute CMS Action (if set)
  6. Return success response → client redirects or shows message

Steps 3-5 are non-fatal: a failure in any of them is logged as a warning but does not prevent the submission from being stored or the success response from being returned.

← Back to all tutorials