Skip to content

Release Notes

Each version lists what you notice after updating. The complete technical history, including every earlier version, is in the plugin’s CHANGELOG.md.

  • Fixed: on Promptless Forms’ entry list, a form that sends its own notification showed Sent by workflow instead of its own tick, linking to a run whose email may have been the customer’s auto-reply rather than your team’s. FlowMint now reports there only when Promptless Forms has nothing of its own to show.
  • Promptless Forms’ Entries screen now shows what your workflow did with the team email — Sent by workflow, Workflow failed or Workflow running, each linking to the run. Before this the column had nothing to show, which looked like a delivery failure. Needs Promptless Forms 1.12.0.
  • A run the server cuts off no longer stays RUNNING for good. A time limit or crash in the middle of a step used to leave the run stuck, with no notification and none of the later steps. It now fails as interrupted and notifies you, or is retried from that step if it has on_error: retry.
  • Large uploads have more time. Each run asks the server for up to five minutes, and Drive uploads go in 8 MB parts instead of 1 MB.
  • A failure to queue a run notifies you, like any other failed run.
  • Automatic retries work, and carry on from the failed step. A step with on_error: retry is tried again after 1, 5 and 15 minutes without repeating the steps before it. Other failures now fail at once and notify you; until now a retryable failure left the run stuck in Queued with no notification. Runs stuck that way are marked Failed (retry_stranded) when you update, so you can replay them.
  • Conditions work as written. A function call next to !, a comparison, && or || inside one {{ }} is now called — {{ !has_file(entry, 'photo') }} used to be always true — and a comparison in one of several {{ }} blocks no longer comes out empty. The Workflows screen lists any saved condition whose result changed, so you can check it.
  • HTTP steps can use a stored API key. Store it as a credential named http_<name> and name it in the step’s auth; it is added when the request is sent and no longer sits in the workflow or its run history.
  • Deleting the plugin keeps workflows, run history and credentials unless FMW_REMOVE_ALL_DATA is set in wp-config.php. Up to version 0.9.0 it always removed them.
  • Requires PHP 8.1 or later (was 7.4). The bundled Google library already needed it; now WordPress checks it before installing or updating, so a site on older PHP keeps its current version instead of failing when a Drive step runs.
  • Steps inside a try_catch can use values from earlier steps in the same try list. Until now they received empty strings, for example after a set_variable or a lookup. A try_catch that relied on the old behaviour now receives the real values.
  • Run history records what a step evaluated. A conditional’s if, then and else, a try_catch’s lists and an import’s map are kept as written instead of blanks. Other settings are still recorded filled in.
  • {{ workflow.title }} and {{ form.title }} hold the titles. They were always empty.
  • Failure alerts name the workflow by its title instead of its id.
  • The connector’s tool descriptions now say skip_if (there is no when key; a step given when ran every time) and that flowmint_test_workflow needs a saved workflow. Regenerate the connector to get the new descriptions.
  • The record import step maps featured_image_url. Each image address is downloaded once and set as the record’s featured image; an image that cannot be fetched is a warning, not a failure. Needs Promptless CPT Pages 0.10.0 or later.
  • A maintenance release that passes the WordPress Plugin Check with no errors. Nothing changes in how workflows run.
  • New step pre_upsert_records imports records fetched from another system into Promptless CPT Pages, without duplicates, with guards that fail the run on an empty or broken feed. See Importing records.
  • Declares compatibility with WordPress 7.1.
  • New labels values give the option labels a visitor saw, for dropdowns, radio buttons and checkboxes, where data gives the stored values. Use them in anything a person reads.
  • The connector works with local HTTPS sites created in Local: the setup command points Node.js at Local’s certificate. Certificate errors now explain the real cause.
  • Regenerating the connector setup command keeps settings you added to Claude Desktop’s configuration by hand.
  • On the Connector screen, Copy Command sits below the command instead of covering it.
  • Documentation only; nothing changes in the plugin.
  • Requires WordPress 5.6 or later, the version the connector’s application passwords need.
  • Failure notifications. A run that fails for good sends an alert to Slack, or by email to the notification address or the site’s admin email. See Failure notifications.