Skip to content
Promptless Docs

Your First Workflow

This walkthrough builds a workflow that emails your office whenever the contact form is submitted, with the visitor’s address as the reply-to. It takes about ten minutes and uses the FlowMint connector.

Before you start

Section titled “Before you start”
  • A Promptless Forms form that stores entries. Note its form id (for example contact) and the field keys you want to use (for example name, email, message).
  • The FlowMint connector set up in Claude Desktop. See Connector setup. You can do the same through the REST API instead.
  • A site that sends email. FlowMint sends through WordPress’s own mail function, so whatever delivers your other site email delivers this.

The workflow

Section titled “The workflow”
{
  "trigger": { "type": "form", "form_id": "contact" },
  "steps": [
    {
      "name": "notify_office",
      "type": "send_email",
      "config": {
        "to": "office@example.com",
        "reply_to": "{{ data.email }}",
        "subject": "New enquiry from {{ labels.name }}",
        "body": "{{ labels.name }} ({{ data.email }}) wrote:\n\n{{ labels.message }}\n\nEntry #{{ entry.id }}"
      }
    }
  ]
}
  • trigger binds the workflow to the contact form.
  • The one step is named notify_office and has the type send_email.
  • {{ data.email }} is the value stored in the email field. labels.* gives the same fields as a person saw them, which matters for dropdowns and checkboxes. See Variables and expressions.

How to build and switch it on

Section titled “How to build and switch it on”
  1. Ask the assistant to create the workflow with the id contact-office-email, the title “Contact form → office email”, the config above, and enabled set to false. It calls flowmint_create_workflow. Creating it switched off means no real submission runs it before you have checked it.
  2. Ask the assistant to test it. flowmint_test_workflow returns valid, a list of errors and a list of warnings. Fix anything listed and update the workflow.
  3. Ask the assistant to enable it. It calls flowmint_update_workflow with enabled set to true.
  4. Submit the contact form on the site, as a visitor would.
  5. Open FlowMint Workflows → Run History. The newest row shows your workflow, the form, the entry number and a status. Wait for COMPLETED (refresh the page; a run is picked up when WP-Cron next fires).
  6. Select the run number. Under Steps, notify_office shows SUCCESS. Open show to see its output: {"sent":true,"recipients":["office@example.com"],"deduplicated":false}.
  7. Check the office inbox.

Limits and common problems

Section titled “Limits and common problems”
  • The run stays QUEUED. WP-Cron has not fired. Load any page of the site, or set up a real cron job as described in Installation and setup.
  • The run completed but a value is blank in the email. A path that does not exist, such as a misspelt field key, becomes an empty string and the step still succeeds. Check the field keys against the entry, and remember form values are under data.*, not entry.*.
  • No run appears at all. The workflow is not enabled, the form id does not match, the form does not store entries, or another enabled workflow is bound to the same form: only one workflow runs per form, the most recently updated enabled one.
  • Sent is true but no email arrived. WordPress handed the message to its mailer, which accepted it. Look at your mail delivery, not at FlowMint. Many hosts block outbound mail; an email-sending service fixes that.

Next, read Workflow structure and browse the Step library.