Action

Failure PDF

Document which rule triggered

Creates a short PDF that records which rule caused a job to fail or be declined, giving you a paper trail that explains the outcome in plain terms.

How it works

When a job is stopped by one of your rules, this node writes down which rule did it and produces a small PDF stating the reason. Instead of a bare declined status, you get a document you can point to.

That record is worth having when someone later asks why a submission was turned away. It captures the specific rule that triggered, so the answer is on paper rather than in someone's memory.

It fits naturally on the rejection side of a flow, right after a Classify or Decline step has decided the job does not pass, turning that decision into a filed explanation.

Common use cases

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

Explain a rejection on paper

When a rule declines an application, produce a PDF stating which rule triggered and why.

Record the reason

Generate a document capturing the failing condition for the file's record.

Tell them what fell short

Attach a clear, written explanation to a decline.

Failure PDF in a workflow

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

Classify Select Case · branch per rule Failure PDF Document which rule triggered Email outbound Send report link

What you set up

  • Place it on the failure branch, after the rule check that can decline the job.
  • Confirm the triggering rule's information is available for the PDF to record.
  • Route the finished PDF to wherever you keep records, or attach it to a reply.

Common questions

When does this node run?

On the failure or declined path of your flow, after a rule check (a Classify or Decline step) has determined the job does not pass. It documents that specific decision.

Why keep a PDF instead of just a status?

A filed document gives you an auditable paper trail. If anyone questions an outcome later, you can show exactly which rule caused it rather than reconstructing it from memory.