Email Steps

Both steps send through WordPress’s own mail function, wp_mail, so they use whatever delivers the rest of your site’s email: the host, or an SMTP or email-service plugin. Neither needs a FlowMint credential.

send_email

Setting	Required	What it does	Default
to	Yes	One address, or a list.	—
subject	Yes	The subject line.	—
body	Yes	The message.	—
is_html	No	Send the body as HTML.	false (plain text)
from_email	No	The sender address. Without it, WordPress’s default sender is used.	—
from_name	No	The sender name. Used only with from_email.	—
reply_to	No	The Reply-To address.	—
cc, bcc	No	One address, or a list.	—

Output: sent, recipients, deduplicated.

{ "name": "confirm", "type": "send_email",
  "skip_if": "{{ is_empty(data.email) }}",
  "config": {
    "to": "{{ data.email }}",
    "subject": "Your booking for {{ labels.workshop }}",
    "body": "Hi {{ labels.first_name }},\n\nYour place on {{ labels.workshop }} is held.",
    "reply_to": "bookings@example.com"
  } }

Use labels.* for anything the recipient reads, so a dropdown shows its label rather than its stored value.

send_email_template

Sends a message whose body is a template file.

Setting	Required	What it does
to	Yes	One address, or a list.
subject	Yes	The subject line.
template	Yes	The template name, without extension.
is_html	No	Overrides the format the file’s extension gives.
from_email, from_name, reply_to	No	As for send_email.

There is no cc or bcc on this step.

Output: sent, recipients, template, deduplicated.

Template files

Templates live in wp-content/uploads/fmw-templates/ as <name>.html (sent as HTML) or <name>.txt (sent as plain text); if both exist, the .html file is used. Names are lowercase letters, digits, - and _. Placeholders in the file are filled in like any other.

Put files there over SFTP, or with the REST API (PUT /wp-json/flowmint/v1/connector/templates/<name> with content and extension, up to 256 KB; saving one extension removes a file with the other). The connector can list templates and read one (flowmint_list_templates, flowmint_get_template) but not write them.

A missing template fails with template_not_found, which is not retried.

You can also pull a template into any text setting with {{ template('name') }}, for example as the body of send_email.

Warning

The uploads folder is served by your web server, so anyone who guesses a template’s file name can read it. Keep personal data and secrets out of template files; they come from the placeholders at send time.

Duplicate sends

Both steps remember each message for an hour, keyed by run, recipient and subject. A second send in the same run with the same recipient and subject is skipped and reports deduplicated: true. A replay is a new run, so it sends again.

Limits and common problems

• sent: true means WordPress accepted the message, not that it was delivered. If it never arrives, check your mail setup: many hosts block outgoing mail, and an email-sending service plugin that delivers over HTTPS fixes that.
• A blank recipient or subject fails with config_error: the path in to or subject did not resolve.
• The mailer refused the message fails with email_send_failed and the mailer’s reason.

Related pages

• Variables and Expressions — The {{ }} placeholder syntax, every value a workflow can read (data, labels, entry, steps, vars and more), the built-in functions, and how conditions are written.
• Your First Workflow — Build a workflow that emails your office when a contact form is submitted, test it, turn it on, and confirm the run in Run History.
• Troubleshooting — Fixes for the problems people meet with FlowMint Workflows — runs that never start, blank values, conditions that misfire, email, Google Drive, Printavo and the connector.