Assign approved work and track delivery
Connect
SPIRITT
Fillout FormsFillout Forms
Run the work behind it
SPIRITT builds and operates systems around your Fillout databases, tables, and records. Turn stored requests into assigned work, maintained statuses, and useful custom apps.
What you can do with Fillout Forms.
Requests reach an owner
Route requests stored in Fillout tables using your assignment rules, coordinate the handoff, and keep each record's status current.
An intake system that fits
Build a custom review desk or request portal backed by Fillout records, with tables and fields shaped around your team's process.
Data stays workable
Find incomplete records, standardize fields, and resolve conflicting entries so growing Fillout databases remain useful for everyday decisions.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the intake, review, or database operations you want handled.
02
Connect Fillout Forms
Connect Fillout Forms with an API key that provides access to the databases and forms needed for your mission.
03
Delegate an outcome
Give SPIRITT a concrete goal, such as routing requests from a Fillout table into assigned projects and maintaining their progress.
Hand over a mission.
Choose a mission. Make it yours.
Put Fillout Forms to work.
Put your intake to work
Questions
Fillout Forms, with SPIRITT.
01What can SPIRITT do directly in Fillout Forms?+
SPIRITT can list forms and databases, inspect database tables and fields, retrieve and filter records, and create or update tables, fields, and records. It can also create Zite databases and manage database webhook subscriptions for workflows driven by database changes.
02What access does the connection need?+
The Fillout Forms connection uses an API key. Provide access to the databases and forms relevant to the mission, then identify the tables SPIRITT should operate on. Actions in Asana, Gmail, or other connected apps require their own connections and appropriate access.
03Can it read submissions or edit my forms?+
The available form action lists forms; it does not provide submission retrieval or form editing. Record-based workflows use data stored in accessible Fillout database tables. Listing forms is separate from reading their responses, so an existing form alone is not enough to supply a response-processing workflow.
04How can workflows keep running after records change?+
SPIRITT can create database webhook subscriptions to receive change notifications and use scheduled record checks to reconcile the work. A routing workflow can track processed record IDs, update handoff fields, and catch requests that need attention without creating duplicate downstream tasks.
05What custom systems can it build around Fillout data?+
SPIRITT can build a reviewer portal, equipment loan register, or internal request desk around Fillout tables. The custom app provides the interface, while record creation and updates maintain the underlying data. Additional tables and fields can hold assignments, review notes, task references, and operational status.
06How is this different from forwarding a form response?+
A response handoff moves one piece of information. SPIRITT can maintain the operation around database records: assign ownership, create Asana work, link Linear issues, send Gmail follow-ups, and reconcile progress back into Fillout. The database becomes a maintained work register rather than just a destination for collected information.