Pick the capabilities, say where each field gets its value, and run it before you save it. Building one costs nothing: what an account changes is where it is kept. Every rule the server enforces is checked here as you type, so saving cannot fail for a reason you could not see.
This is the "What will my holiday allowance be?" example with its sample values filled in. It is not saved yet: change anything, test it, then save it as your own.
· What it is called
· What it asks for
Declare a value here when it changes from run to run. Steps read it by its key. Anything that never changes belongs in the step itself as a fixed value, not here. A workflow may declare up to 10 inputs, and none at all is fine.
· What it does
Steps run top to bottom, one after another. A step can use a fixed value, one of the inputs above, or the output of any step above it. Up to 12 steps.
Every one of its 2 steps is pure computation, so a test run in the builder happens on your own machine and costs nothing. Your input is not sent to us for it.
Run from your saved workflows, from your code or from an assistant, the work happens on our machines and is metered: 2 credits, one call per step across 2 steps.
Adding a step that needs our side, meaning anything touching a key we hold, a database, the network or a file, would move the whole run onto our servers and it would be charged there too.
· Step 1 of 2 · 1 credit
Dutch Holiday Allowance Calculator
Calculate Dutch holiday allowance (vakantiegeld) from a gross monthly salary and the months worked: the gross amount at the given percentage (statutory minimum 8%) and an estimate of the net payout after the special payroll tax rate (bijzonder tarief).
Reads: monthlySalary from input "monthlySalary" · monthsWorked from input "monthsWorked"
Gives back:ok yes/nogrossAllowance numbertaxWithheld numbernetAllowance numberallowancePercent numberspecialRatePercent numbernote text, usable by every step below as “Output of an earlier step”
· Where each field comes from
monthlySalary (required)Number
Gross salary per month in euros. Example: 3500
monthsWorked (optional)Number
How many months of the accrual period were worked, 0 to 12. Defaults to 12. Example: 12
allowancePercent (optional)Number
Holiday allowance percentage. Defaults to the statutory 8; some collective agreements pay more. Example: 8
Left out. The capability will use its own default.
specialRatePercent (optional)Number
The special payroll tax rate (bijzonder tarief) printed on the payslip, as a percentage. Defaults to 42.01. Example: 42.01
Left out. The capability will use its own default.
A later step reading this one can take the whole object, or a path into it such as ok.
· Step 2 of 2 · 1 credit
Percentage Calculator
Answer one percentage question from two numbers: what x% of y is, what percent x is of y, the percentage change from x to y, or x increased or decreased by y%. Returns the number and a sentence stating it.
Reads: mode is fixed · x from "netAllowance" of Holiday allowance · y from "grossAllowance" of Holiday allowance
Gives back:mode textx numbery numberresult numberresultIsPercent yes/nosentence text
· Where each field comes from
mode (required)Text (String)
One of percentOf, whatPercent, change, increase or decrease. Example: percentOf
x (required)Number
First number. For percentOf this is the percentage, for the other modes the starting amount. Example: 15
Takes number from “Holiday allowance”, for example 1948.46.
y (required)Number
Second number. The base amount, the new value for change, or the percentage for increase and decrease. Example: 200
Takes number from “Holiday allowance”, for example 3360.
What this step gives back
{
"mode": "percentOf",
"x": 15,
"y": 200,
"result": 30,
"resultIsPercent": false,
"sentence": "15% of 200 is 30."
}
A later step reading this one can take the whole object, or a path into it such as mode.
· Test it before you save
This runs the workflow exactly as written, without saving it. It uses the real capabilities, so what you see is what a later run will do. Inputs are prefilled from the examples you gave them.
Stays on your device
This runs in your browser. What you put in is never sent to ToolForte, so we could not read it if we wanted to.
One exception, so the sentence above stays true: when a run finishes here we record that it happened, which ready made workflow it came from if it came from one, how many steps it had and how long it took. Never what you put in, never what came back, and never anything written into the steps themselves. It is how we can tell which tools are worth keeping.
Runs in your browser. No credits, nothing sent to us.
Saved in this browser
This is saved by your browser on this device. It is not sent to ToolForte, so it is not on your other devices and we cannot recover it for you.
Clearing your browser data removes it, and so does the delete button here.