Skip to content
nofeb

Follow up when nobody replies

When the agent sends, write follow_up_at on the thread. If a reply comes in, the agent clears or moves it. If the time passes first, nofeb emits a thread.due event with the thread's metadata to your webhooks and the event feed, and the agent sends the follow-up and sets the next follow_up_at.

Checked against the engine on .

What do you need?

  • A webhook endpoint or an event-feed consumer
  • An inbox the agent sends from

Steps

  1. 1. Arm the timer when sending

    Pass thread_metadata with the send, or set it after.

    Send and arm
    const sent = await nf.messages.send(inbox.id, {
      to: ["carrier@example.com"], subject: "Lane CHI→ATL, 2 pallets", text,
      thread_metadata: { stage: "quote_requested", follow_up_at: in48h() },
    });
  2. 2. Disarm on reply

    On message.received for the thread, record the new stage and clear follow_up_at (null deletes a key).

    On a reply
    await nf.threads.setMetadata(threadId, { stage: "quote_received", follow_up_at: null });
  3. 3. Act on thread.due

    Subscribe to thread.due. The event carries thread_id, inbox_id, due_at and the thread's metadata.

    On thread.due
    if (event.type === "thread.due") {
      const { thread_id, metadata } = event.data;
      if (metadata.stage === "quote_requested") {
        const thread = await nf.threads.get(thread_id);
        const last = thread.messages.at(-1)!;
        await nf.messages.reply(last.id, { text: "Following up on the quote request below." });
        await nf.threads.setMetadata(thread_id, { follow_up_at: in48h(), nudges: (metadata.nudges ?? 0) + 1 });
      }
    }
A thread as a state machine with a follow-up timer Stages quote_requested, quote_received, negotiating, booked are stored as the thread's stage metadata. An agent writing follow_up_at arms a timer; when the time passes, a thread.due event carrying the thread's metadata is delivered by webhook and the event feed, and the agent takes the next step. Moving follow_up_at moves the timer and clearing it cancels it. stage, stored on the thread quote_requested reply quote_received reply negotiating reply booked Thread metadata stage: "quote_sent" owner_agent: "freight-desk" follow_up_at: "2026-10-03T09:00Z" Timer armed by nofeb moves when follow_up_at moves cancelled when it is cleared no scheduler of your own thread.due by signed webhook or the event feed with thread_id, inbox_id, due_at and the thread's metadata Agent takes the next step chase, escalate or close writes the new stage and the next follow_up_at
The thread carries its own state. A reply or an agent moves the stage; setting follow_up_at arms a timer, and if nothing changes before it passes, thread.due wakes the agent with the thread's metadata attached.

Frequently asked questions

How do I send a follow-up email if there is no reply in three days?

Set follow_up_at to three days out when you send, clear it when a reply arrives, and handle thread.due: it fires only if the time passes with the key still set.

What happens if I change follow_up_at?

The timer moves with it. Setting it to null cancels it.

Do I need a cron job or a queue?

No. The timer lives with the thread in nofeb, and the event arrives through the same webhooks and feed as every other event.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
Follow-up timers Set follow_up_at on a thread and, when that time passes, a thread.due event carrying the thread's metadata goes to your webhooks and the event feed, so agents need no scheduler of their own. Shipped
Typed metadata on messages, threads and inboxes Merge-patch keys onto a message, a thread or an inbox, and declare a key's type so every write to it is validated. Shipped
Signed webhooks with required scope Standard Webhooks signatures, retries and a delivery log. Scope (organization, pod or inbox) is required, so a subscription never silently widens to everything. Shipped
Durable event feed A pull feed of every event, oldest first after a cursor, for consumers that cannot receive webhooks. Shipped
Send, reply, reply-all and forward Threading headers are set for you, replies default to the original sender, and forwards carry the original attachments. Shipped