Input

Dojobase read

Read records from a Dojobase

Dojobase read starts or feeds a workflow from rows already sitting in one of your Dojobases, the structured tables the platform keeps for you. Instead of uploading a file, the job picks up data you have already collected and stored.

How it works

A Dojobase is your own table inside the platform, filled over time by earlier jobs or imports. This node reaches into one of those tables and pulls the rows you point it at, handing them to the workflow as its starting material.

It is how you act on information you already have. Take last week's saved applications and score them, grab every unpaid row and send a reminder, roll up a set of records into a report: the data is in the table, and this node feeds it forward.

Pair it with the Schedule trigger and you get hands-off routines: on a timer, read the latest rows and do something with them, over and over, with no file ever touched.

Common use cases

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

Start from saved records

Read rows you have already collected in a Dojobase and run new work over them without re-uploading anything.

Regenerate outputs

Pull past records to rebuild a report or export without re-extracting the source files.

Feed a scheduled export

Combine with a schedule to read the day's records and push them somewhere on a timer.

Dojobase read in a workflow

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

What you set up

Pick which Dojobase table to read from.
Choose which rows the job should pull, such as recent or unprocessed ones.
Select the columns the later steps will need.

Common questions

Where does the data come from in the first place?

From earlier jobs that saved rows to the table, or from data you imported. This node just reads what is already there.

Can it read only new rows each run?

Yes. You can point it at recent or not-yet-processed records so a scheduled run only handles fresh data.

Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.

Field	Type	Default	What it controls
`dataStoreId`req	string	—	Id of the Dojobase whose records seed the job; without it there is no source to read.
`filter`	string	—	Optional substring matched across column values to narrow which records are pulled.
`recordKindFilter`	string	—	Optional record kind; only records with this kind are pulled when set.
`recordLimit`	number	`500`	Maximum records to read (max 5000).
`includeDeleted`	boolean	`false`	Pull soft-deleted records too.

dataStoreIdreq
Id of the Dojobase whose records seed the job; without it there is no source to read.
Type: string
filter
Optional substring matched across column values to narrow which records are pulled.
Type: string
recordKindFilter
Optional record kind; only records with this kind are pulled when set.
Type: string
recordLimit
Maximum records to read (max 5000).
Type: numberDefault: 500
includeDeleted
Pull soft-deleted records too.
Type: booleanDefault: false

How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.

{
  "id": "data-store-in",
  "type": "card",
  "position": {
    "x": 160,
    "y": 120
  },
  "data": {
    "type": "data-store-in",
    "kind": "input",
    "title": "Dojobase read",
    "subtitle": "Read records from a Dojobase",
    "config": {
      "dataStoreId": "",
      "filter": "",
      "recordKindFilter": "",
      "recordLimit": "500",
      "includeDeleted": "false"
    }
  }
}