Procfu for AI agents
ProcFu extends Podio with automation tools and scripting so teams can build mini apps and integrate with other services. Podio power users use it to automate workflows Podio cannot handle natively. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Procfu.
Generate an image with AI
Create an AI-generated image and attach it to a Podio item field.
Pull data from a Google Sheet
Fetch a Google Sheet's contents as an array to sync into a Podio workflow.
Delete a file with approval
Remove a file from Google Drive only after confirming it is no longer referenced.
12 Procfu actions, graded by risk.
Every Procfu action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
0Look things up. Allowed by default.
- No read actions.
write
11Create and change things. Allow, or ask the user first.
- procfu.array_sortArray Sort
- procfu.dummy_dataGenerate dummy data
- procfu.sheets_getGet Google Sheet contents as array
- procfu.open_ai_gptAsk question to OpenAI GPT
- procfu.open_ai_imageGenerate Image with OpenAI
- procfu.array_diff_delArray Difference Deletions
- procfu.array_diff_newArray Diff New
- procfu.array_diff_sameArray Diff Same
- procfu.sheets_get_metadataGet Google Sheets Metadata
- procfu.copy_podio_files_to_ftpCopy Podio files to FTP
- procfu.upload_podio_item_imageUpload image to Podio item field
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- procfu.google_drive_deleteGoogle Drive Delete
Procfu in three steps.
- 01Your users connect ProcfuThey add their Procfu api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “array Sort” can wait for the user, and “google Drive Delete” can be denied outright.
- 03Any agent can actYour agent calls Procfu through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('procfu', { read: 'allow', write: 'ask', // array_sort destructive: 'deny', // google_drive_delete }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Procfu connects.
Users add their Procfu api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Procfu connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Procfu from any agent.
Procfu and Arc0, answered.
Can I use Procfu with Claude, ChatGPT or Cursor?
Yes. Connect Procfu to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Procfu actions you allow.
How do users connect Procfu?
Users add their Procfu api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Procfu actions can my agent take?
12 in total: 0 read, 11 write and 1 destructive, such as “array Sort”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Procfu?
Yes. Actions like “google Drive Delete” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Procfu too?
Yes. The same Procfu connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Procfu into your agent.
Your users connect Procfu once, under your brand. Your agent gets 12 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan