Procfu
for LuumenAI
Podio automation helpers, Sheets reads, and file moves with approval on the write
ProcFu adds a toolkit around Podio: array comparisons, sorting, dummy data, Google Sheets reads, and OpenAI calls. Luumen reads any of it for context, then holds the changes — copying Podio files to FTP, uploading an image to an item field, deleting a Drive file — for your approval first. Connects with an API key.
The Procfu toolbox
12 tools: 8 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadArray Difference DeletionsReturn items removed when comparing two JSON arrays.
- ReadArray Diff NewReturn items added in the second JSON array.
- ReadArray Diff SameGet items present in both JSON arrays.
- ReadArray SortSort a JSON array of values.
- ReadGenerate dummy dataGenerate dummy data.
- ReadAsk question to OpenAI GPTAsk a question to OpenAI GPT.
- ReadGet Google Sheet contents as arrayGet sheet contents as array.
- ReadGet Google Sheets MetadataRetrieve metadata of a Google Sheets spreadsheet, including sheet names, IDs, and properties.
- WriteCopy Podio files to FTPCopy files matching a pattern from a Podio item to an FTP server. Approval by default
- WriteGoogle Drive DeleteDelete a Google Drive file or folder. Approval by default
- WriteGenerate Image with OpenAIGenerate an image via OpenAI API. Approval by default
- WriteUpload image to Podio item fieldUpload a remote image file by URL to a Podio item image field. Approval by default
One prompt, start to finish
What a governed Procfu 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.
Read actions answer immediately. Anything that writes — copy podio files to ftp, google drive delete, generate image with openai, upload image to podio item field — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
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 Procfu — 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 Procfu to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.