ProcFu enhances Podio's capabilities by providing a suite of automation tools and functions, enabling users to create scripts, mini apps, and integrate with various services to streamline workflows.
ProcFu enhances Podio's capabilities by providing a suite of automation tools and functions, enabling users to create scripts, mini apps, and integrate with various services to streamline workflows. On Nagent, Procfu is exposed as a fully-configurable developer tools integration that any agent can call — 12 actions, and API key authentication. No code is required to wire Procfu into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Procfu to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Procfu into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Procfu, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PROCFU_ARRAY_DIFF_DELTool to return items removed when comparing two JSON arrays. Use when you have two arrays and need to know which elements were deleted.
Input parameters
First JSON array to compare against the second array
Second JSON array to compare against the first array
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCFU_ARRAY_DIFF_NEWTool to return items added in the second JSON array. Use when you need to identify new elements between two list versions. Example: Compare \[1,3,4\] vs \[1,3,6\] to get \[6\].
Input parameters
First JSON array to compare against the second.
Second JSON array. Items present here but not in the first will be returned.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCFU_ARRAY_DIFF_SAMETool to get items present in both JSON arrays. Computes the intersection locally to avoid external API dependency. Rules: - Two items are considered equal if their JSON representations match (with sorted keys for objects). - The result contains unique items present in both arrays, preserving the order they appear in json_array_b.
Input parameters
First JSON array
Second JSON array
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCFU_ARRAY_SORTTool to sort a JSON array of values. Use when you need to order elements ascending or descending.
Input parameters
True for descending order; defaults to ascending order.
JSON array to sort (e.g., \[3, 1, 2\]).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCFU_COPY_PODIO_FILES_TO_FTPTool to copy files matching a pattern from a Podio item to an FTP server. Use when you need to transfer specific files from Podio to an external FTP/SFTP location based on file name patterns.
Input parameters
File pattern to match (e.g., '*.pdf' for all PDF files, '*.png' for PNG images). Use wildcards to specify which files to copy.
Name of the (S)FTP connection configured in ProcFu to use for the file transfer.
Target directory path on the FTP server where files should be copied (e.g., '/uploads', '/documents/invoices').
The ID of the Podio item containing the files to copy.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCFU_DUMMY_DATATool to generate dummy data. Use when you need random emails, text, numbers, dates, people, addresses, or images for testing or placeholder data.
Input parameters
Type of dummy data to generate. Choose one of the supported types for numbers, text, people, addresses, etc.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCFU_GOOGLE_DRIVE_DELETETool to delete a Google Drive file or folder. Use after obtaining a valid Google Drive ID.
Input parameters
ID of the Google Drive file or folder to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCFU_OPEN_AI_GPTTool to ask a question to OpenAI GPT. Use when you need a conversational answer from GPT.
Input parameters
Model to use; default is 'gpt-4o-mini'.
Prompt for GPT.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCFU_OPEN_AI_IMAGETool to generate an image via OpenAI API. Use when you need programmatic image creation from a text prompt.
Input parameters
Text prompt describing the desired image to generate.
Orientation of the generated image.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCFU_SHEETS_GETTool to get sheet contents as array. Use when you need to retrieve Google Sheet data as an associative array.
Input parameters
Name of the sheet/tab within the spreadsheet to retrieve.
Google Sheet ID to fetch data from.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCFU_SHEETS_GET_METADATATool to retrieve metadata of a Google Sheets spreadsheet, including sheet names, IDs, and properties. Use when you need sheet-level details for a given spreadsheet ID.
Input parameters
ID of the Google Sheets spreadsheet to retrieve metadata for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCFU_UPLOAD_PODIO_ITEM_IMAGETool to upload a remote image file by URL to a Podio item image field. Use when you need to attach an image from a web URL to a specific field in a Podio item.
Input parameters
Whether to create a hook event in Podio for this file upload. Set to true to trigger webhooks, false to skip them.
Whether to include the silent flag when uploading. Set to true to suppress notifications in Podio.
Optional HTTP headers to send when fetching the remote file. Use comma-separated format for multiple headers (e.g., 'User-Agent: MyBot, Accept: image/*').
Web address (URL) of the remote file to upload. Must be a publicly accessible image URL.
Identifier for the Podio item to attach the image to.
External ID of the image field in the Podio item where the file will be uploaded.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 41 agents privately built on Nagent that already use Procfu.
Build on Nagent
Connect Procfu to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Procfu, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Procfu is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Procfu is connected, you configure its 12 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Procfu steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Procfu event fires, the agent kicks off automatically.
Every Procfu action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Procfu ships with 12 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Procfu together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Procfu-based workflows tailored to your business.