AI agent tools
The Instafill.ai agent turns a pile of uploaded documents into a finished package. It reads what you gave it and works out where each piece belongs.
Tools the agent calls
No agent has all of them. Each workflow gets its own toolset, and every page says which workflows its tool is available in.
Package Assembly
List Available Sub-Forms
Lists the sub-forms a package type can contain, with each one's image slot count and whether it is required.Add Sections to a Package
Creates the sub-form sections a package is made of in one call, each at a fixed position, without duplicating what exists.Fill Sections from Source Documents
Starts filling a package's sections in one call, each from only the source documents mapped to it.Remove Sections from a Package
Deletes sections a package shouldn't contain, such as over-created addenda. Repeating it is safe.Insert Source Pages into the Deliverable
Records pages of an uploaded PDF for insertion into the assembled package when the deliverable is put together.Split a Filled Package into Sub-Forms
Cuts a completed package into one piece per form, so a prior deliverable becomes a filling reference for the new one.Set Subject Property Facts
Records the subject property's address and facts, carried into later runs and printed in the delivered report's header.Name the Output Package
Sets the name a finished package is listed under in your workspace. The downloaded file's name is unchanged.Sources & Data
List Package Attachments
Inventories every document attached to a package across every run, with each file's inferred role and page count.Inspect an Attachment
Returns one uploaded document's stored details plus a preview of the text already inside the file.Parse a Pre-Bid Invitation
Crops the first two pages of an HPD invitation to bid into images ready to place in the bid form.Read Records from a Spreadsheet
Reads a spreadsheet's records tab: the header row it detects, the context lines above it, and the data rows beneath.Create One Form per Spreadsheet Row
Turns chosen spreadsheet rows into filled forms, one per row, ordered by row number and safe to re-run.Images
Document Processing runs automatically
These are not agent tools. They build the finished document before the agent sees a file and after it finishes, with settings fixed per workflow. The agent doesn't choose them and neither do you.
| Step | What it does |
|---|---|
| Merge PDFs | Combines the filled parts of a document package into one deliverable PDF, in the sequence fixed for that package type - automatically, at the end of a run. |
| Fill AcroForm Fields | Writes values into a PDF's own interactive form fields - text, checkboxes, radio options and dropdowns - so the output stays a real fillable PDF, not flat text. |
| Extract Form Fields | Reads a PDF's field inventory - names, types, pages, character limits and dropdown choices - which is what has to happen before anything can be filled. |
| Extract Document Text | Reads a source document page by page so a form can be filled from it - every page read the same way, whether it started out digital or as a scan on a copier. |
| Flatten Forms | Locks the values in a filled PDF into the page so they cannot be edited or cleared. Every page comes back as a fixed rendering - no fields, no selectable text. |
| Rasterize Pages | Renders a PDF page as an image - so a page can be placed in an image slot, shown on screen, or handled as a picture rather than as a searchable document. |
| Extract and Place Images | Pulls the images embedded in a source PDF back out as separate photos, then stamps assigned images into a form's slots at the size and place it defines. |
| Crop and Normalize Images | Turns photos upright and standardizes them to a single format before they go into a form's image slots. Pixel dimensions are never reduced. |
| Stamp Headers and Page Numbers | Applies a running header and one page sequence across an assembled appraisal package, so a deliverable built from many separate forms reads as one report. |
| Stamp Signatures | The step that places a captured signature onto a form once - drawn or uploaded - and carries it onto every filled copy of that form, with no print-and-scan loop. |
| Remove Watermarks | Takes DRAFT and SAMPLE marks out of PDFs on the way in - the ones drawn as a full-page overlay, and the ones the file itself labels as a watermark. |
How agent tools work
What is an agent tool?
A traditional automation follows steps someone wrote in advance: open this file, copy cell B4, paste it into that field. Change the input and it breaks.
An AI agent works differently. You give it a goal - "produce the finished appraisal package from these documents" - and a set of tools. A tool is a single, well-defined action the agent can take: send a source document to the form it feeds, add a section to the package, put a photo in a numbered slot, read the rows of a spreadsheet.
Which of those it calls, and with what, is decided as it works - from what it actually finds in your files, not from a branch someone wrote in advance. Twenty-two photos and a form with six slots is a judgement call. So is a folder where the survey, the tax record and last year's report all arrived with unhelpful filenames.
The agent decides the matching
Which uploaded document belongs to which form. Which image goes in which slot. Which text is wrong and what it should say instead. How many sections a spreadsheet's rows require.
It does not decide the shape of the deliverable
Which forms make up a package, and in what order, is fixed per workflow before the agent runs. Neither does it choose the document processing - merging the parts, stamping headers, flattening the result.
That division is deliberate, and it is what makes the output reviewable. Two packages produced from the same workflow have the same forms in the same order, so a reviewer knows where to look. The agent's judgement is spent on the messy half of the problem - your input pile - and not on the half that should never vary.
One agent per workflow, not one agent for everything
There is no single agent with every tool above. Each workflow we deploy gets its own agent and its own toolset: appraisal packages, contractor bid responses, and inspection records built from a spreadsheet are three separate agents today. They overlap, but only one tool - listing what has been uploaded - is common to all three.
So this catalog is the union, not a menu any one agent sees. We add tools as we take on new workflows, so it grows. If your process needs something that isn't here, building it is part of the setup work - see pricing for how that works.