Docs / Forms & Automation

Email notifications

Send an email on submission using a Workflow, not a per-form setting.

There's no "notification email" field on the Form widget itself — its own Save Submission setting says as much: "For email, webhooks, Mailchimp, Slack automation use Craftor → Workflows." Every notification email, from a simple admin alert to a branded autoresponder, is a Send Email step on a Workflow triggered by Form Submitted.

Sending a basic notification

  1. 1Go to Craftor → Workflows → Add New.
  2. 2Set the trigger to Form Submitted and pick the form.
  3. 3Add a step, choose Send Email as its action.
  4. 4Set To — a fixed address (you@yoursite.com), or a merge tag if you want it to go somewhere the visitor specified, e.g. {email}.
  5. 5Set Subject, e.g. "New submission: {all_fields}" or something more specific like "New quote request from {name}".
  6. 6Leave Email Template empty to send a plain-text-style body — write it in the Body field below.
  7. 7Save the workflow. It fires automatically on every future submission of that form; nothing needs to be enabled on the form widget itself.

Merge tags available in Send Email

  • {fieldName} — any field's value, using its auto-generated name (see "Building a form").
  • {all_fields} — every submitted field, formatted as one "label: value" line per field — the fastest way to get a complete notification without listing each field by name.
  • {post_id} — the ID of the page/post the form was submitted from.
  • {source_url} — the URL the visitor actually submitted from.

{actor_name}, {actor_email}, {actor_ip}, and {action_time} only resolve on the Entry Updated and Entry Deleted triggers (who made the change, not who originally submitted) — they're always empty on a Form Submitted trigger, since a public submission has no logged-in "actor." See "Workflows & automations."

Using a branded Email Template

Set Email Template to a template built under Craftor → Email Templates instead of leaving it empty — the template's own widget-built layout becomes the email body, with the submitted field values available inside it the same way they'd be in the plain Body field. This is the way to send a designed, on-brand autoresponder to the person who filled out the form (To: {email}) as well as a plain internal alert to your team from the same workflow, as two separate Send Email steps.

Other notification options

  • From and Reply-To — both optional; Reply-To commonly gets set to {email} so replying to the notification emails the visitor directly.
  • Only send a step conditionally — every step has its own condition (e.g. only email a manager when Budget is greater than or equal to 10000), independent of any conditional logic configured on the form's own fields.
  • Send more than one notification — add multiple Send Email steps to the same workflow (an internal alert plus a visitor autoresponder), or multiple workflows on the same Form Submitted trigger if you'd rather keep them as separate, independently-toggleable automations.