Workflow app · v1.1.0 · In review
Fulcrum Data and Logic Tools
Data shaping and real conditional branching for workflows: read JSON, work with lists, compare values, and send each contact down the right path.
Submitted for marketplace review on 9 September 2026. All five steps are built, published and covered by an automated suite of more than three hundred assertions, and every one was verified running on the platform itself, not only locally — including the branching step, driven end to end in a real workflow.
- JSON from webhooks
- List operations
- Multi-path branching
- No server
The gap it closes
A webhook arrives carrying a block of JSON and the platform hands you a string. Getting one value out of it means a chain of find-and-replace steps that break the moment a field moves.
Branching is worse: one If/Else with a short list of operators, so a decision with five outcomes becomes five nested workflows that nobody can follow six months later.
Fulcrum adds a step that reads a value straight out of JSON by path, steps that work on lists properly, and a branching step that picks one of many named paths from a single comparison.
How it works
Three steps, then it runs itself.
- 01
Read the data
Point a step at a JSON payload and pull out the value you want by path — order.customer.email, items[0].sku, items[-1].price. A field that itself holds JSON text is opened up automatically, which is the shape most incoming webhooks arrive in.
- 02
Shape it
Split, join, deduplicate, count, sort, reverse, slice and total lists; keep or drop the items that match a condition and get both halves back at once; compare two values with the operator you actually need.
- 03
Branch on it
Feed the result into a branching step that sends the contact down one of several named paths, so one decision stays one decision — and anything that matches nothing takes a built-in fallback path.
What it adds
5 steps in the action list.
-
Read a Value From JSON
Pull any value out of a JSON payload by path, with a clear error naming where the path broke and which fields do exist.
-
Work With a List
Split, join, deduplicate, count, sort, reverse, take or skip the first or last few, and total, average or find the smallest or largest.
-
Filter a List
Keep or drop the items that match a condition, and get both halves back at once with counts for each.
-
Compare Two Values
Thirty operators for text, numbers, dates, lists, patterns and emptiness, returning a plain yes or no plus the reason.
-
Choose a Path
A branching step that sends each contact down one of several named paths from a single decision, with a built-in fallback.
How it behaves
The decisions that matter.
-
A missing path is an error, not an empty string
If the value you asked for is not there, the step names the exact point the path broke and lists the fields that do exist, instead of returning nothing and letting the rest of the workflow act on a blank. You can still choose to carry on with a blank or a value of your own — it is a setting, not an accident.
-
Real multi-path branching, with nowhere to fall through
Built on the platform’s own branching support rather than nested If/Else steps, so a five-outcome decision reads as five outcomes on the canvas. A fallback path ships set to catch everything, so no contact is left with nowhere to go. Narrow it deliberately and the step says so rather than dropping anyone quietly.
-
It will not tell you that "tiktok" is greater than 1000
Numbers are compared as numbers and dates as dates, automatically. Where one side is a number and the other is text, the step says they cannot be put in order rather than quietly falling back to alphabetical order — which is how a router path meant for big spenders ends up catching a lead source. A SKU like B2 is likewise not read as the number 2.
-
Every answer comes with its reason
Each comparison returns a plain-English sentence saying what was compared, which way it went, and whether it was treated as text, a number or a date — so a decision made weeks ago can still be read back.
-
Deliberately not a text tool
Case conversion, cleaning and number formatting live in Lexicon. Fulcrum stays on data, lists and logic so the two do not overlap.
-
Nothing leaves the workflow
Pure computation. No API key, no external service, no server of ours.
Pricing
One price, unlimited runs.
Billed through the marketplace, which handles all payment processing, and every paid plan starts with a 14-day free trial. There is no per-run charge from us: the subscription covers unlimited executions. The marketplace may display its own per-execution tag on premium steps, which is set by the platform and not by us.
Monthly
$19/mo
or $190/yr
Documentation & data handling
Everything it touches, stated plainly.
Installing & getting started
- Install Fulcrum Data and Logic Tools and approve the permission listed below.
- Open any workflow, add a step, and pick it from the action list.
- Follow the three steps above. Every field accepts a merge field.
- Stuck? Email [email protected] — one business day response, from the developer who built it.
Permissions, and why each one
workflows.readonly- The only scope the app requests. It is required to register workflow actions so the steps appear in the action list. It grants read-only visibility of workflows and nothing else — no contact, conversation, calendar or payment access is requested.
What is stored, and where
- Fulcrum operates on the values you pass into it, in memory, and returns a result. Nothing is written to disk, cached, or retained after the step finishes.
- No contact record, message, or account detail is read.
- There is no server operated by us, so no data reaches our infrastructure at any point.
- No analytics, telemetry or usage tracking is embedded in the app.
Technical detail
- Version
- 1.1.0
- Status
- In review
- Hosting
- None. The code runs inside the automation platform.
- Runtime
- Code-backed workflow actions — JavaScript executed by the automation platform itself
- Authentication
- Standard marketplace OAuth, least-privilege scopes
- Workflow steps
- 5
- App ID
6aa0b6260c8061bd2288adbb- Support
- [email protected]
- Support SLA
- One business day
- Publisher
- Builds By Luke, Canada
Questions people ask.
How is this different from Lexicon?
Lexicon reshapes text and numbers — case, cleaning, names, formatting. Fulcrum handles data structures and decisions — JSON, lists, comparison and branching. The split is deliberate so neither duplicates the other, and the two sit side by side in the same workflow perfectly happily.
What happens when nothing matches on the branching step?
The contact takes the fallback path, which ships named “None of the above” with its condition set to Always, so it catches everything the paths above it did not. The step reports that the fallback was used and why, so a run that fell through is visible rather than silent. You can rename it; if you deliberately narrow its condition and a contact then matches nothing at all, the step stops with an explanation instead of quietly dropping them.
Does it start a workflow when data arrives?
No. Fulcrum provides actions — steps you place inside a workflow — not triggers. Pair it with whatever trigger already starts the automation.
What does it do with a date like 09/08/2026?
It refuses to guess, by default. A slash date is either 9 August or 8 September depending on where it came from, so unless you tell the step which order to read, it says so rather than picking one. ISO dates, written dates and timestamps are read without any setting.
Does it need an API key or an account anywhere?
No. Every step is pure computation running inside the automation platform. There is nothing to connect and nothing to keep working.
Put Fulcrum in a workflow.
Every plan starts with a free trial, so it can prove itself on a real workflow before you pay for it.