Podio API Functions

If you are searching for Podio API functions, you have probably hit the wall where visual automation stops being practical. You need a calculation that involves five variables. Or you need to call an external API mid-workflow. Or the same logic runs in 12 places and you want one reusable function instead of 12 copy-pasted flow branches.

ProcFu gives you two ways to write and execute Podio API functions: the Functions API for callable endpoints, and ProcScript for full scripts. Both run pre-authenticated against your Podio account — link once, never deal with OAuth tokens per call again. Both have access to 300+ built-in functions that cover Podio operations, external integrations, data processing, and AI.

Two Execution Models

Functions API — Callable Endpoints

The Functions API lets you define functions and call them via HTTPS from anywhere that can make an HTTP request:

• Podio Workflow Automation (GlobiFlow/PWA) — the most common entry point. Keep your existing visual flows; call a ProcFu function where the logic gets complex.
• Zapier — add a webhook step that calls your function.
• External servers — any backend, with IP whitelist for security.
• ProcFu Flows — one flow calling another function.
• Other ProcScript blocks — compose functions from functions.

Every call is pre-authenticated. You link your Podio account once during setup. From that point, every function call has full access to your Podio data without any token management in the calling system.

This is the bridge for teams that already have working GlobiFlow or Zapier setups. You do not rip and replace anything. You write a function for the part that is painful, and call it from your existing automation. Read more in Break Podio Workflow Limits.

ProcScript — Full Scripting Language

ProcScript is a complete programming language, not a template with placeholders. PHP-like syntax with JavaScript conveniences (use + for string concatenation). Untyped variables. IF/THEN/ELSE, FOREACH, WHILE. Functions with parameters and return values. Multi-line strings. Error handlers.

It does not have += or ++ operators — use direct assignment. This is intentional; the language stays simple enough that non-developers can read and modify scripts after watching someone build one.

ProcScript is what runs inside ProcFu Flows, what powers code events in Mini Apps, and what the Functions API executes behind the scenes. Learn ProcScript once, use it everywhere.

Development Tools

ProcFu is not a text box where you paste code and hope. The development environment includes:

• Syntax-highlighted code editor with inline function documentation — hover or click any function name to see parameters, return values, and usage examples.
• Step-through debugging with breakpoints. Set a breakpoint, run against a real Podio item, and walk through execution line by line. Inspect every variable at every step.
• Full execution logs with timestamps. When something breaks at 2am, you open the log and see which line failed, what the inputs were, and what the variables contained.
• Async execution via call_procscript_async() for long-running jobs. Standard function calls have a 30-second timeout. Async scripts can run for up to 2 hours — useful for bulk imports, report generation, or batch operations across thousands of items.
• Include statements for code reuse. Shared logic goes in one script, gets included everywhere it is needed. Change it in one place.

300+ Built-In Functions

Every function is available in both the Functions API and ProcScript. Organized by what they do:

Podio Operations

Read, write, and delete items across any app in your workspace. Create and manage tasks. Post comments. Attach files. Filter and search with conditions that go well beyond what Podio's native views support. Traverse relationships — follow linked items across apps, walk reference chains, aggregate data from related records.

External Integrations

• remote_curl() / api_request_send() — call any REST API with custom headers, methods, and bodies.
• mysql_query() — query any MySQL database directly. Combine with ProcFu's data sync (which mirrors Podio to MySQL) and you get SQL JOINs across Podio apps.
• email_send_smtp() — send email through any SMTP server with full control over headers, body, and attachments.
• google_drive_* — create, read, move, and share Google Drive files.
• sheets_* — read and write Google Sheets cells, rows, and ranges.
• notion_* — create and query Notion pages and databases.
• FTP/SFTP file transfer for legacy system integration.
• Amazon S3-compatible storage for file operations.
• OAuth2 support for any service that uses it.

Data Processing

• Excel and CSV parsing and creation — read uploaded spreadsheets, validate rows, output new files.
• JSON and XML handling for API responses.
• Markdown-to-HTML conversion.
• All standard string manipulation: trim, split, replace, regex, format.
• Date and time calculations with timezone support.
• Math operations including rounding, aggregation, and financial calculations.

AI

• podio_ai_ask_general() — general AI query with item context.
• podio_ai_ask_trained() — AI with your custom knowledge base.
• jev_noul(), jev_choice(), jev_score() — fast AI micro-decisions (~100ms). Yes/no classification, categorization against a list, numeric scoring. Fast enough to run inline without slowing down a flow.

More on AI capabilities: Podio AI Automation.

State and Storage

• var_get() / var_set() — persistent key-value storage that survives across executions. Track counters, store intermediate results, manage state between flow runs.
• Session management for building stateful web apps with Mini Apps.

Pre-Connected vs Bring-Your-Own Services

Some services connect once through the ProcFu dashboard and are available to all your scripts:

Pre-connected (one-time setup): Podio (automatic on account creation), Google Drive, Notion, Citrix ShareFile.

Bring-your-own (you provide credentials): MySQL databases, SMTP mail servers, FTP/SFTP servers, Amazon S3-compatible storage, any OAuth2 service. Store the credentials securely in ProcFu; reference them by name in your scripts.

Real-World Examples

These are actual patterns, not hypotheticals.

Service quote generation. A function receives service type, location zone, customer history, and required tech level. It calculates the base price, applies zone surcharges, checks repeat-customer discount eligibility, adjusts for tech-level requirements, checks whether the total exceeds the approval threshold, and returns a formatted quote number with line-item breakdown. In GlobiFlow, this would be 20+ flow steps with nested conditions. As a ProcFu function, it is about 40 lines of readable code.

Multi-app cascade on deal close. When a deal moves to "Won," one function call creates items in three Podio apps (project, billing, onboarding), links them to the deal and to each other, assigns tasks to the right people based on deal type, and sends notifications. What would require 10+ separate GlobiFlow actions happens in a single function that you can debug, test, and modify in one place.

External API integration. Call a shipping carrier's API to get tracking status, parse the JSON response, update the Podio item with current status and estimated delivery date. Or call a payment gateway to generate a payment link and write it back to a Podio field. The remote_curl() function handles any REST API.

CSV validation and import. Parse an uploaded CSV file, validate each row against business rules (required fields, format checks, range constraints), flag errors with row numbers and reasons, create Podio items for valid rows, and return an error report for the invalid ones. Bulk import with data quality enforcement.

Cross-app reporting. Query your MySQL-synced Podio data with SQL JOINs across apps that have no direct Podio relationship. Aggregate, filter, calculate derived metrics. Format as an HTML report and email it, or write the results to Google Sheets. Reporting that would be impossible through Podio's API alone.

Availability checking. A scheduling function that checks technician schedules, crew assignments, parts inventory, and blackout dates across four different Podio apps. Returns available time slots to an AppFrame booking form where a customer selects their preferred slot.

Functions API vs ProcScript: When to Use Each

The distinction is not rigid. Functions API calls execute ProcScript under the hood. The difference is how the code gets triggered and how complex the logic needs to be. Start with the Functions API if you have existing GlobiFlow or Zapier flows you want to extend. Start with ProcScript and Flows if you are building new automation from scratch.

Getting Started

Start a free trial — no credit card required. Connect your Podio account and write your first function in under 10 minutes.

If you already use GlobiFlow, the fastest path is the Functions API: write one function for the part of your flow that is currently painful, call it from your existing setup, and see the result immediately. No migration required. Read Podio Workflows Hit a Wall for a walkthrough.

If you are building new automation, start with ProcFu Flows and write directly in ProcScript.

View plans and pricing | ProcScript reference | Podio Automation overview | GlobiFlow Alternative | Podio Workflow Automation