Builds By Luke
All GHL apps

Workflow app · v1.1.0 · In review

Lexicon Text and Number Tools

Seven text and number steps for workflows: change case, clean, split names, find and replace, extract, spin, and format numbers.

Submitted for public marketplace review on 8 September 2026. Version 1.0.0 is live as a private app while the public listing is reviewed.

  • Real title case
  • Name splitting
  • Safe find & replace
  • No server
Lexicon Text and Number Tools icon

The gap it closes

Data arrives from forms, imports and integrations in whatever shape it was typed. A contact called MARIA VAN DER BERG gets an email addressed to MARIA. A form field carries invisible HTML into an SMS. A single "full name" column has to become a first name before you can greet anyone by it.

The usual fix is a pile of find-and-replace steps that break the first time a full stop appears inside a sentence, or an AI step that costs money and is non-deterministic for a job that is pure string manipulation.

Lexicon does these seven jobs precisely and predictably, every time, with no model and no API call.

How it works

Three steps, then it runs itself.

  1. 01

    Add a step

    Pick a Lexicon step in a workflow and map a merge field into it. Every field accepts contact data or the output of a previous step.

  2. 02

    Set the switches

    Each step is explicit about what it will do — strip HTML, flatten accents, keep only digits, truncate on a whole word. Nothing happens that you did not turn on.

  3. 03

    Use the extras

    Every step returns the result plus useful counts — characters, words, lines — so you can branch on message length before you send.

What it adds

7 steps in the action list.

  • Change Text Case

    Ten styles including a real title case, plus slug, camel, Pascal, snake and kebab for technical fields.

  • Clean Text

    Strip HTML, flatten accents, remove emoji, keep only digits or letters, collapse spacing, truncate on a whole word.

  • Split and Format a Name

    Turn one full-name field into first, middle, last, prefix, suffix, initials and greeting names.

  • Find and Replace

    Literal by default; regular expressions with capture groups when you need them.

  • Extract From Text

    Pull the first email, URL, phone digits or number out of any message, or the text between two markers.

  • Spin Text

    Rotate wording with {this|that} spintax so outreach does not read like a template. Seedable for repeatability.

  • Format a Number

    Read messy input such as "$1,234.5678" and return a clean value plus a display string.

How it behaves

The decisions that matter.

  • Title case that is actually correct

    Small words stay lowercase, and McDonald, O’Brien and Mary-Jane all come out right. Surname particles such as van der stay with the surname.

  • Find and replace that is safe by default

    Plain mode is literal, so a full stop means a full stop. Regular expressions are opt-in, and a pattern that could hang is rejected with an explanation instead of stalling the workflow.

  • Numbers are read tolerantly, never guessed

    Currency symbols, thousands separators and European decimal commas all parse. Anything that genuinely is not a number is reported, never silently treated as zero.

  • Nothing leaves the workflow

    Lexicon is pure computation. No API key, no external service, no server of ours. Your text is never transmitted anywhere.

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

All seven text and number steps, unlimited runs, one business day support

Documentation & data handling

Everything it touches, stated plainly.

Installing & getting started

  1. Install Lexicon Text and Number Tools and approve the permission listed below.
  2. Open any workflow, add a step, and pick it from the action list.
  3. Follow the three steps above. Every field accepts a merge field.
  4. 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. Lexicon reads no contacts, no conversations and no account data of any kind.

What is stored, and where

  • Lexicon manipulates the text 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. The only values it sees are the ones you explicitly map into its fields.
  • 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.

Full policy: Privacy · Terms

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
7
App ID
6a9fb301bd98d8444d99abd0
Support SLA
One business day
Publisher
Builds By Luke, Canada

Questions people ask.

Why not just use an AI step for this?

Because these are deterministic string operations. A model costs money per run, can return a different answer twice, and cannot guarantee that a phone number keeps all its digits. Lexicon gives the same answer every time, for free, in milliseconds.

Is my text sent anywhere?

No. Lexicon runs entirely inside the automation platform. There is no external service and no server of ours, so the text never leaves the workflow that is using it.

Can I use regular expressions?

Yes, in Find and Replace and in Extract From Text. They are opt-in, and any pattern that could hang is screened and rejected with a clear explanation before it runs.

Does it handle non-English names?

Accented characters are preserved unless you explicitly ask for them to be flattened, and surname particles such as van, von, de and della are kept with the surname rather than treated as middle names.

Put Lexicon in a workflow.

Every plan starts with a free trial, so it can prove itself on a real workflow before you pay for it.