Flatfile
for LuumenAI
Read Flatfile spaces, sheets, and records, and correct data as approved steps
Connect Flatfile and Luumen can trace an import end to end: which space it landed in, which workbook and sheet holds it, how the job finished, and which records failed validation. Reads answer right away. Inserts, updates, and deletes are previewed and held for your approval before anything changes in the sheet.
The Flatfile toolbox
12 tools: 9 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet JobGet detailed status, outcome, result, and diagnostic information for one Flatfile asynchronous job.
- ReadGet SheetGet one sheet's field configuration and record counts before reading or writing records.
- ReadGet SpaceGet safe metadata for one Flatfile space without exposing transient access credentials or token-bearing guest links.
- ReadList EnvironmentsList Flatfile environments visible to the connected environment secret key and return the IDs needed to find spaces.
- ReadList FilesDiscover import or export files and their processing status, optionally within a Flatfile space.
- ReadList JobsFind asynchronous Flatfile jobs by environment, space, workbook, file, or parent job and inspect progress at a glance.
- ReadList RecordsRead one page of records from a Flatfile sheet, optionally filtering by validity, field, record ID, search value, or FFQL expression.
- ReadList SpacesFind Flatfile spaces by environment, text, namespace, archive state, or template status.
- ReadList WorkbooksList workbooks, optionally within a space, with their nested sheets so an agent can continue to sheet and record tasks.
- WriteDelete RecordsPermanently delete one to 100 explicitly identified records from one Flatfile sheet. Approval by default
- WriteInsert RecordsInsert one or more rows into a Flatfile sheet using simple field-key to value objects. Approval by default
- WriteUpdate RecordsUpdate one or more existing Flatfile records by ID using simple field-key to value objects. Approval by default
One prompt, start to finish
What a governed Flatfile run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as delete records, insert records, update records. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Flatfile — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Flatfile to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.