Output

Decline

Reject applicant + decline email

The rejection endpoint of a workflow: it marks a job as declined and can send a decline notice. Usually the 'no' branch after a Classify or Score step.

How it works

Every review flow needs a clean way to say no. This node is that ending. When a job lands here, dojobase marks it declined, giving you a definitive record that this one was turned down and why, rather than leaving it in limbo.

It typically sits on the 'no' branch coming out of a Classify or Score step: the ones that don't meet your criteria get routed here while the approved ones continue elsewhere. That keeps your decision logic explicit and auditable instead of hidden in someone's head.

Beyond marking the status, it can send a decline notice to the applicant so they aren't left waiting. You control the wording, and you can keep it courteous and standard across every rejection.

Common use cases

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

Decline and notify at once

When a rule fails, mark the applicant declined and send the decline email in one step.

End the unqualified path

Give a Classify branch a proper terminal that records the outcome cleanly.

Say no consistently

Send a templated, reviewed decline every time so the wording never varies.

Decline in a workflow

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

Extract PDFs → structured data Classify Select Case · branch per rule Decline Reject applicant + decline email

What you set up

  • Connect it to the reject branch of a Classify or Score step (the outcome you want to turn down).
  • Optionally enable a decline notice and write the message the applicant receives.
  • Include job values (like the applicant's name) so the notice reads properly.

Common questions

Does declining always email the applicant?

Only if you turn on the decline notice. You can also decline silently to just mark the status internally, or write a custom message when you do want to notify them.

Where does this go in my flow?

On the rejection branch, usually right after a Classify or Score step routes the failing cases to it, while the passing cases continue down a different path.