Duaer

Build

Give people tasks in Duaer with the tasks table

In Duaer, every project comes with one built-in data table named Duaer tasks. A workflow inserts a row to assign a task, push a decision card, or write a note. When the person clicks Done or picks an option in the Duaer employee portal, the result is written back to that row and a waiting workflow continues.

The built-in Duaer tasks table

Every Duaer project comes with one Duaer tasks table. You do not create it, and the data tables list marks it Built-in. The table is locked: it cannot be deleted or renamed, and its columns cannot be added, removed, or renamed. Only rows change.

  • assignee: the email the person signs in with, lowercase, matched exactly
  • title: one line saying what to do
  • detail: optional context
  • due: optional deadline
  • status: open when created; done after the person clicks Done or picks an option, later after Not today
  • link: optional related link, shown only for http or https
  • resume_url: optional, the continue address of a waiting workflow
  • done_at: when the person clicked Done, decided, or put it off, filled in by Duaer
  • done_by: the email of the person who did it, filled in by Duaer
  • kind, pressure: a short tag on the card (such as Stock) and what gets worse if it waits (such as Sold out by the weekend)
  • urgent, rank: urgent cards come first, then higher rank
  • rule: the line that was crossed, such as Stock below safety level
  • facts: JSON, up to 8 label and value pairs
  • change: JSON {"from", "to", "note"}, what changed, drawn as from → to instead of facts
  • reading, basis: two or three sentences on what the facts mean, and where they came from
  • actions: JSON, up to 4 next steps the person can pick
  • choice: the id of the option the person picked, filled in by Duaer
  • comment_box: optional, a comment box on the card: a short text is the label of an optional box; JSON {"label": "Reason", "required": ["reject"]} makes it required for those options, required true for every decision, and done stands for Done on a plain task
  • comment: what the person wrote with the decision, filled in by Duaer
  • form: optional, a JSON list of up to 10 fields to fill in with the decision, each {"id", "label", "type", "options", "required"}; type is text, number, date, choice, file or person (a colleague; the value is their email), and required works as for comment_box
  • form_values: what the person entered, JSON by field id (for a file field, the list of file ids), filled in by Duaer
  • closed_by: source when the case was handled in its own system and the card closed by itself, filled in by Duaer
  • sync_status, sync_target, sync_error, sync_attempts, sync_next_at, synced_at: how the decision went back to the system the case is in (pending, synced or failed), filled in by Duaer; refer to write-back
  • lane: read or quiet for a note; empty for tasks and cards

A row without actions is a plain task the person marks Done. A row with actions is a decision card where the person picks one option. A row with lane set is a note that is only shown.

Assign a Duaer task from a workflow

  1. Add a Data table node, select Duaer tasks, and choose Insert.
  2. Set assignee to the person’s email, for example {{ $json.email.toLowerCase() }}, title to what to do, and status to open. Fill due, detail, and link as needed.
  3. After the run, the task shows on the home page of that person’s Duaer employee portal, across every project in the organization, ordered by urgent, rank, then due, overdue in red.
[
  {
    "assignee": "li.na@acme.com",
    "title": "Review the September receivables statement",
    "detail": "37 statements in the East region, 4,210 total difference",
    "due": "2026-10-08T10:00:00.000Z",
    "status": "open",
    "resume_url": "{{ $execution.resumeUrl }}"
  }
]

The person must be a member of the organization; inviting them as Employee is enough. You can also ask Duaer Designer to build it: say who gets the task, what to do, and whether to wait until they finish.

Continue after the person is done

  1. In the Insert node, set resume_url to {{ $execution.resumeUrl }}.
  2. Follow it with a Wait node: Resume On Webhook Call, HTTP Method POST. Turn on Limit Wait Time when there is a deadline.
  3. When the person clicks Done, Duaer calls that address and the workflow continues from the Wait node. The Wait node output body has taskId (the task row id) and doneBy (the email of the person who clicked Done).

Duaer only calls addresses that point at a waiting execution on this instance, so always use {{ $execution.resumeUrl }}, never a hand-written or external address.

Ask one person to decide with the Duaer Task node

When a workflow needs one person’s decision before it goes on (approve an expense, name who signs), use one Duaer Task node (Send and Wait for Decision) instead of a Set, an Insert and a Wait node, and without writing JSON.

Fill in Assignee (the email the person signs in with) and Title. Options: up to 4 (ID, Label, and whether a comment is required to pick it). Comment Box: the box’s label. Fields: up to 10 (ID, Label, Type: Text, Number, Date, Choice, File or Colleague; Choices for a Choice field; Required: For Every Decision, or For Some Options with their IDs, done for Done). Card Details: detail, due, kind, link and urgent.

When the node runs, the card appears in the person’s Duaer employee portal and the workflow waits. Once they decide, the workflow goes on and the next node gets taskId, doneBy, choice, comment, values and files, read as {{ $json.choice }} and {{ $json.values.amount }} (no body). Each run sends one card, from its first input item; for several people, loop over them. The node waits until the person decides. When the card needs facts, reading or change, a note, or a wait time limit, use the way below.

A parameter that would break the card stops the node and says what is wrong: an assignee that is not an email, an option or field ID used twice, a Choice field without choices, or a field required for an option the card does not have.

Push a Duaer decision card

The Duaer employee portal speaks first: the person opens it and sees what needs their call today, and what each option would do. Options are fixed when you build the workflow; the person can only pick one. Each step does one thing:

  1. Schedule Trigger: run at the hour the person starts work.
  2. Read: a Data table, database, or HTTP node reads the numbers the rule needs.
  3. Rule: one Filter or IF node keeps only what crossed the line. Nothing crossed means no card; you can write a quiet note instead.
  4. Facts: one Set node computes the numbers shown on the card. When the line crossed is a change (for example a column header renamed from Tracking no. to Waybill no.), write change instead.
  5. Reading: one AI step writes reading and basis from those facts only. It does not choose or add options.
  6. Card: Insert into Duaer tasks with title, kind, pressure, urgent, rule, facts, reading, basis, and actions, status open, and resume_url {{ $execution.resumeUrl }}.
  7. Wait: Resume On Webhook Call, HTTP Method POST, with Limit Wait Time on.
  8. Switch: branch on {{ $json.body.choice }}, one output per option id.
  9. Each branch does only the one step its option’s hint promised, then ends.
[
  {
    "assignee": "li.na@acme.com",
    "kind": "Stock",
    "urgent": true,
    "pressure": "Sold out by the weekend",
    "title": "Longjing 50g covers only 2.1 days",
    "rule": "Stock below safety level",
    "facts": "{\"On hand\":\"13 boxes\",\"14-day daily average\":\"6.4 boxes\",\"Lead time\":\"4 days\"}",
    "reading": "Not slow-moving. With a 4-day lead time, no reorder today means it sells out this weekend.",
    "basis": "Stock table, last 14 days of orders",
    "actions": "[{\"id\":\"draft\",\"label\":\"Draft a reorder of 40\",\"hint\":\"Writes a purchase draft for 40 boxes. Nothing is sent to the supplier.\"},{\"id\":\"stop\",\"label\":\"Stop restocking\",\"hint\":\"Marks this item as no restock. No more alerts after it sells out.\"}]",
    "status": "open",
    "resume_url": "{{ $execution.resumeUrl }}"
  }
]

Write each option in actions as {"id", "label", "hint"}: id is what the Switch matches, label is the button text, and hint is one sentence on what the step does and does not touch, shown before the person clicks. The first option is drawn as the primary button, so put the safest one first. When the person picks, Duaer writes choice, sets status to done, and continues the execution with {"taskId", "doneBy", "choice"}, plus "comment" when the card has a comment box and the person wrote one, and "values" when the card has fields and the person filled some in. A decision cannot be undone. Not today sets status to later and does not continue the workflow. When the card names a case, Duaer appends one Duaer activities row with activity later and source Duaer, and the case path shows Not today. The person can take the card back the same day. The step stays on the path. Duaer Designer can build this for you.

Record Duaer activities from a list

Every Duaer project also includes the locked tables Duaer activities and Duaer cases. Turn a list the organization already stores into activities with the Data table node. Do not add a node for one kind of list.

  1. Add a Data table node and read the rows of that list. Turn on Execute Once when the next step should run once for the whole list.
  2. Keep only the rows that crossed the line with an IF or Filter node.
  3. Add a Data table node and insert one Duaer activities row per remaining item: case_id, activity, happened_at, source, and extracted_at.
  4. Insert or update the Duaer cases row for that case_id: owner_email, signal_date, signal_status, and pointer. The pointer is an https link or a source:id token. Do not write a document body.
  5. If several rows remain and this run should open one card, add a Limit node set to 1 before the card.
  6. Add one more Data table node: Resource Table, Operation Run Case Signal, with Continue This Workflow After the Pick turned on. Follow it with a Wait node: Resume On Webhook Call, HTTP Method POST. Skip this step when the cards need no step after them: Duaer runs the case signal by itself once a day.

The Cases column on the Duaer employee portal lists those steps, earliest first, for cases the person’s column rule allows: the activity, when it happened, and the source. Duaer Designer can build this from the list table, the line that counts, and who should see the card.

Send Duaer cards for overdue samples

When a laboratory sample is past its keep-until date and still unhandled, Duaer can put it in front of the sample owner every day, with no workflow to build. Someone who can change data tables sets it up once in the project.

  1. Open the project › Data tables › Duaer cases and select Sample overdue cards.
  2. Under Samples, paste the samples from a spreadsheet, one per line: sample ID, owner email, keep-until date. A header row is skipped, and a date can be written 2026-10-03, 2026/10/3, or 2026.10.3.
  3. Under Owners, add the sign-in email of any owner who is not in the list, one per line. An owner must already be a member of the organization; the Employee role is enough.
  4. Under Time zone, enter the laboratory’s time zone, for example Asia/Shanghai. Keep-until dates are compared in this time zone.
  5. Under Card language, choose Chinese or English. It is chosen at the first setup; later setups keep the language the samples were stored in.
  6. With no list yet, turn on Add six example items to see it working.
  7. Select Set up. Duaer sends the first cards at once and says how many samples it added and updated and how many cards it sent.

Each owner sees only their own samples on the Duaer employee portal, most overdue first. An English card reads Sample S-0412 is 9 days overdue, and lists Sample ID, Keep until, and Overdue. A sample seven or more days overdue is marked urgent. The card has three options, and each one changes only that sample’s status: Handled sets Handled, Request an extension sets Extension requested, and Discard sets Discarded. Once the status changes, that sample gets no more cards. A sample that is due today gets no card.

You can paste the list again at any time. A sample already stored keeps its status and takes the new owner and date; a new sample is stored as Open. Lines Duaer cannot read are listed by line number with the reason (the sample ID is missing, the owner is not an email address, the date is not a date, or the ID is repeated). The other lines are stored, so correct those lines and paste again. One paste takes up to 2,000 lines.

After the setup, one line above the Duaer cases table shows where things stand: how many samples are open, overdue, handled, extension requested, and discarded; how many cards are to do, Not today, and decided; and the day of the last daily run.

When the samples live in another system, a Data table node can also write Duaer cases on a schedule: case_id is the sample ID, owner_email is the owner’s email, signal_date is the keep-until date, signal_status is Open, and pointer is the sample’s link in its own system or a source:id token. With Chinese cards the open status is a Chinese word; copy it from the signal_status of a stored sample.

Setting up again only adds owners and leaves the organization’s other case registrations alone. Only when another registration uses the same case ID name or open status does the dialog say so, and the button becomes Replace and set up. Replacing removes that registration and its cases get no more cards, so check before you select it.

Send Duaer cards for instruments past calibration

When an instrument is past its calibration due date and not calibrated, Duaer can put it in front of the instrument owner every day in the same way. The setup matches sample overdue cards, and both can be used together.

  1. Open the project › Data tables › Duaer cases and select Calibration due cards.
  2. Under Instruments, paste from a spreadsheet, one per line: instrument ID, owner email, calibration due date.
  3. Fill in Time zone and Card language, then select Set up.

An English card reads Instrument EQ-0412 calibration is 9 days overdue, and lists Instrument ID, Calibration due, and Overdue. An instrument seven or more days overdue is marked urgent. Each of the three options changes that instrument’s status: Calibrated sets Calibrated, Sent for calibration sets Sent for calibration, and Take out of service sets Out of service. Once the status changes, that instrument gets no more cards.

Samples and instruments are stored in the same Duaer cases table and told apart by status: an open sample is Open, and an instrument is Calibration due. One daily case signal covers both, and both kinds of cards sit together on the Duaer employee portal. Each has its own overview line above the table, counting only its own.

A registration of the organization’s own can also be used beside these two. Two registrations cannot share a case ID name or an open status; Duaer refuses the one set up later.

When Duaer runs the case signal

The case signal reads Duaer cases and sends one card for each case that is past its date and still open. When the same person already has an open card for the same case, no second card is sent.

  • Every day, by itself: once an organization is registered, Duaer runs the signal once a day after 08:00 in the registered time zone, in every project of the organization. Duaer checks every 15 minutes, so cards appear between 08:00 and 08:15. Picking an option on these cards does not continue a workflow.
  • From a workflow: add a Data table node with Resource Table and Operation Run Case Signal. To do a step after the person picks, turn on Continue This Workflow After the Pick, follow the node with a Wait node, and branch with a Switch on {{ $json.body.choice }}.

Cards sent by one run share one waiting address. The first pick continues the workflow. A later pick on another card from that run records the choice and the status, and continues nothing. When every card needs its own next step, keep one case per run before the signal.

When an option is registered on the activity table, picking it appends one activity to that case and leaves the stored activities as they are.

Write Duaer notes

Notes tell the person what the workflow looked at and what is fine. Insert a row with assignee, title, and lane set to read (Checked overnight, such as Orders, 90 days, 1,284 rows) or quiet (All normal, such as 81 items cover 7+ days). Notes show beside the queue on the Duaer employee portal home page only on the day they are written, in the order written, with no buttons and no status.

Where to see Duaer task results

  • Tasks table: open the project › Data tables › Duaer tasks. The row’s status is done, done_at and done_by record when and who, and choice on a decision card records which option was picked.
  • Employee portal: a completed plain task no longer shows; a decided card moves to Decided, marked Done. The detail the workflow wrote after the step appears under the decision, such as whether a message was sent.
  • Workflow: for a task with resume_url, that execution in the executions list goes from waiting to running again, and the Wait node output is the completion feedback.
  • Employee portal: if the workflow cannot continue (for example the execution already ended or was canceled), the person sees “Marked done. The workflow did not continue.” The task is still recorded as done.

To act on completed tasks without keeping an execution waiting, leave resume_url empty and add a scheduled workflow that reads rows whose status is done.

Questions

Does Duaer delete the task row when someone clicks Done?

No. Duaer only sets status to done and fills in done_at and done_by. The row stays in the Duaer tasks table.

Can I give a Duaer task to someone outside the organization?

No. Only members of the organization can sign in to its Duaer employee portal. Invite them under Duaer Settings › Organization settings first; the Employee role is enough.

Can a person undo a decision in the Duaer employee portal?

No. Duaer continues that one branch as soon as the option is picked, and the card is marked Done. Only a card put off with Not today can be taken back the same day.

How does a list become a case path in Duaer?

A Data table node inserts one Duaer activities row per event. The Duaer employee portal then lists those steps, earliest first, for cases the person’s column rule allows.

Do Duaer sample overdue cards need a workflow?

No. Set them up once with Sample overdue cards on Duaer cases, and Duaer sends the cards every day after 08:00. Build a workflow with Run Case Signal only when a step must follow the pick.

In this section