Action

Dojobase lookup

Look up a record by column

Dojobase lookup finds a matching record in one of your stored tables (a Dojobase) and attaches its details to the current job, like pulling up a customer by account number.

How it works

This node connects the job in front of you to what you already know. It takes a value on the current job (an account number, an email, a reference code) and searches a Dojobase, your stored table of records, for the row that matches, then attaches that row's details so the rest of the flow can use them.

The payoff is that a thin incoming submission becomes a full picture. A form that only gives you an account number can be enriched with the customer's name, terms, and history, so later steps can personalize a reply, apply the right pricing, or check the request against what is on file.

It reads from your stored data rather than writing to it, so it is safe to run on every job. Pair it with the step that saves records (data-store-out) elsewhere in your flows, and this lookup becomes the way you read them back.

Common use cases

Real situations where this node earns its place in a flow.

Fill in what you know

Match an incoming applicant against your existing records to pull in their history or account.

Recognize a repeat customer

Look a record up by email or ID to decide whether this is new business or a returning one.

Attach reference data

Pull a rate, a tier, or a contact from a lookup table to use later in the flow.

Dojobase lookup in a workflow

A simple example of where this node sits in a flow.

Extract PDFs → structured data Dojobase lookup Look up a record by column Render document Merge data + template → document

What you set up

  • Choose which Dojobase (stored table) to search.
  • Pick the column to match on and the value from the current job to match against it.
  • Decide what happens when no matching record is found (continue or branch off).

Common questions

What if there is no matching record?

You decide: the job can continue without the extra details, or branch down a separate path so you can handle unknown accounts on purpose rather than by accident.

Does this change my stored data?

No. Dojobase lookup only reads. It pulls details onto the current job and leaves the stored record untouched, so it is safe to run on every job that passes through.