Skip to content

All samples

Samples by technique

A technique is one reusable idea you can carry to another flow. Each sample lists the techniques it shows.

Local function with a contract

A local subflow with declared inputs and outputs, called in one CALL line. Copy it into any flow, create its variables, call it.

  • Business days between two dates: Count the business days between two dates, weekends and holidays left out, for France or another country: the public holidays come from an open data API, the days of your company from a file, and one PowerShell action counts.
  • Excel range to an email-ready HTML table: Turn any Excel range into an HTML table that keeps its look (fills, fonts, borders, number formats), ready for an Outlook email.
  • Email triage by a local AI model: Sort the emails of a shared inbox by category and urgency with a model that runs on the PC, each with a one-sentence summary; no email leaves the PC. Trained on your own sorted emails, it goes from 68 % to 92 % right.
  • Process framework template: A desktop flow template to start every process from: one transaction per work item, business and system exceptions, retries with recovery, log, run report, settings per environment and 24 tests, in local functions with a note on every action.

Errors returned, never thrown

The subflow sets every output first, then reports a failure through a flag and a message. The caller decides what to do; the flow never stops inside a reusable part.

  • Business days between two dates: Count the business days between two dates, weekends and holidays left out, for France or another country: the public holidays come from an open data API, the days of your company from a file, and one PowerShell action counts.
  • Excel range to an email-ready HTML table: Turn any Excel range into an HTML table that keeps its look (fills, fonts, borders, number formats), ready for an Outlook email.
  • Email triage by a local AI model: Sort the emails of a shared inbox by category and urgency with a model that runs on the PC, each with a one-sentence summary; no email leaves the PC. Trained on your own sorted emails, it goes from 68 % to 92 % right.
  • Process framework template: A desktop flow template to start every process from: one transaction per work item, business and system exceptions, retries with recovery, log, run report, settings per environment and 24 tests, in local functions with a note on every action.

One PowerShell action for what PAD cannot do

A single Run PowerShell script action covers the missing capability; its inputs are PAD variables, its output is parsed back into variables.

  • Business days between two dates: Count the business days between two dates, weekends and holidays left out, for France or another country: the public holidays come from an open data API, the days of your company from a file, and one PowerShell action counts.
  • Excel range to an email-ready HTML table: Turn any Excel range into an HTML table that keeps its look (fills, fonts, borders, number formats), ready for an Outlook email.

Excel driven through COM

The script opens Excel hidden and read-only, and uses Excel's own engines (here the HTML publisher) instead of reading cell by cell.

Email-safe HTML

Inline CSS on every cell (the styling email clients keep), no style block, hidden cells removed, non-ASCII characters as entities.

Outlook draft instead of a send

The message is saved as a draft and opened on screen, so a person checks it before it leaves.

  • Excel range to an email-ready HTML table: Turn any Excel range into an HTML table that keeps its look (fills, fonts, borders, number formats), ready for an Outlook email.
  • Process framework template: A desktop flow template to start every process from: one transaction per work item, business and system exceptions, retries with recovery, log, run report, settings per environment and 24 tests, in local functions with a note on every action.

A language model served on the PC

The Invoke Local LLM action calls a model that runs on the PC (Ollama), with no account and no key; the data never leaves the PC. Temperature 0 gives the same answer to the same text.

  • Email triage by a local AI model: Sort the emails of a shared inbox by category and urgency with a model that runs on the PC, each with a one-sentence summary; no email leaves the PC. Trained on your own sorted emails, it goes from 68 % to 92 % right.

JSON answers read field by field

Each field of a JSON answer is read with its own regular expression and checked against the allowed values, so a missing or unexpected field becomes a clear error instead of stopping the flow.

  • Business days between two dates: Count the business days between two dates, weekends and holidays left out, for France or another country: the public holidays come from an open data API, the days of your company from a file, and one PowerShell action counts.
  • Email triage by a local AI model: Sort the emails of a shared inbox by category and urgency with a model that runs on the PC, each with a one-sentence summary; no email leaves the PC. Trained on your own sorted emails, it goes from 68 % to 92 % right.

A small classifier trained on your own sorted data

An embedding model turns each text into a vector; a logistic regression learns your categories from a few dozen sorted examples in seconds on the CPU, and gives a confidence that sends doubtful cases to a person.

  • Email triage by a local AI model: Sort the emails of a shared inbox by category and urgency with a model that runs on the PC, each with a one-sentence summary; no email leaves the PC. Trained on your own sorted emails, it goes from 68 % to 92 % right.

Test cases replayed from a file

A subflow replays the lines of a CSV file through the function and compares each result with a value computed elsewhere (here by Excel). A new test is a new line in the file.

  • Business days between two dates: Count the business days between two dates, weekends and holidays left out, for France or another country: the public holidays come from an open data API, the days of your company from a file, and one PowerShell action counts.

A public API chosen for its licence

One GET per unit of work with Invoke web service, retried when the network stumbles, its failure returned as a flag. The source is open data that allows commercial use and asks for no key, and an empty answer is treated as an error instead of a result.

  • Business days between two dates: Count the business days between two dates, weekends and holidays left out, for France or another country: the public holidays come from an open data API, the days of your company from a file, and one PowerShell action counts.

A desktop flow template to start every process from

The flow is saved with Save as and the type Template, then published; New › Flow from template gives each process its own copy, subflows, variables and notes included. Comments marked TEMPLATE say what a process replaces.

  • Process framework template: A desktop flow template to start every process from: one transaction per work item, business and system exceptions, retries with recovery, log, run report, settings per environment and 24 tests, in local functions with a note on every action.

Numbered regions, one colour per role

Each subflow is cut into numbered regions coloured by role (cyan state and settings, red guards, green reading, purple processing, blue sub-steps, gold output). Collapsed, the canvas reads in a few lines, and a region number names the place to change.

  • Process framework template: A desktop flow template to start every process from: one transaction per work item, business and system exceptions, retries with recovery, log, run report, settings per environment and 24 tests, in local functions with a note on every action.

A note on every action

The note of each action (Add note, at the top of its dialog) says why the action is there - the technical reason, the business rule or what a learner should keep. The notes travel with the pasted code and with the template.

  • Process framework template: A desktop flow template to start every process from: one transaction per work item, business and system exceptions, retries with recovery, log, run report, settings per environment and 24 tests, in local functions with a note on every action.

One outcome per work item, retries only for system exceptions

Each item ends SUCCESS, BUSINESS_EXCEPTION (the data breaks a rule, never retried) or SYSTEM_EXCEPTION (an action failed - screenshot, applications closed, pause, retry). A circuit breaker stops the run after a number of system exceptions in a row.

  • Process framework template: A desktop flow template to start every process from: one transaction per work item, business and system exceptions, retries with recovery, log, run report, settings per environment and 24 tests, in local functions with a note on every action.

Settings in a CSV file, overridden per environment

The defaults live in the flow, a CSV file editable in Excel overrides them for every environment, and its rows for the current environment (DEV, TEST, PROD) win. Numbers are checked before use and a missing file is created with the defaults.

  • Process framework template: A desktop flow template to start every process from: one transaction per work item, business and system exceptions, retries with recovery, log, run report, settings per environment and 24 tests, in local functions with a note on every action.

A Tests subflow that calls every function

A global subflow calls each local function with fixed inputs, its recovery paths included, and writes one PASS or FAIL line per case to a report. Run it before every change.

  • Process framework template: A desktop flow template to start every process from: one transaction per work item, business and system exceptions, retries with recovery, log, run report, settings per environment and 24 tests, in local functions with a note on every action.