Skip to main content

PDF form output

End point of a form portfolio: the job returns the PDF received as input, with the fields chosen by the agent(s) in Form filling mode wired to it. A pipeline can contain only one node of this type, and never together with a document Output, a JSON output or a chat entry.

A form portfolio only accepts PDFs as input. A PDF without fillable fields fails the job with an explicit message.

Ports​

  • Input (left, form type): to wire from the « form » handle of one or more agents in Form filling mode.
  • No output.

Configuration​

  • Flatten the PDF (not editable):
    • unchecked (default): the PDF keeps its fields. The values can be reviewed and corrected before the document is sent. Viewers redraw the fields with their own fonts;
    • checked: the values are printed into the pages and the fields removed. The document can no longer be edited and displays identically everywhere.

Getting the result​

The file is named <document>_filled.pdf.

  • In the app, the ⬇ button of the history downloads the filled PDF.
  • In the editor, the test panel offers Download once the job is done. The Node detail tab lists the value entered in each field.
  • Through the API, GET /api/jobs/{id}/download, as for an annotated document.
  • Over MCP, the get_job_result tool returns a temporary download link (see Pipeline as an MCP server).

Fields the agent left empty stay empty: nothing is made up to fill a gap.

Several form-filling agents​

With a Switch upstream, only one route runs. If several form-filling agents run for the same form, their values are combined, and for a given field the first agent's value is kept.