Connect Podio to Propera with GlobiFlow

Overview

Podio Workflow Automation (still widely known as GlobiFlow) includes a Remote HTTP Call action that can POST to Propera's API and read the JSON response back into your Podio fields. That means a fully native Podio integration with no extra subscription beyond Podio Premium.

What you'll build

One GlobiFlow flow: trigger on item create or update → Remote HTTP Call (Propera) → parse the response → Update Item.

Before you start

• A Propera account on the Pro or Business plan, and a Propera API key (Step 1).
• Podio with Workflow Automation (GlobiFlow) enabled (included with Podio Premium).
• A Podio app/item with fields for the address, property type, beds, baths, sqft, year, comp radius, and a status field plus result fields (ARV, summary, notes).

Step 1 — Generate your Propera API key

In Propera, go to Account Settings → API Keys, click Generate API Key, name it (for example Podio), and copy it. It's shown only once.

Step 2 — Create a flow with a "ready" trigger

In GlobiFlow, create a flow on your leads app triggered when an item is created or updated. Add a filter so it only runs when a status field equals something like Run ARV, that way the analysis runs only when you say the lead is ready.

Step 3 — Add a Remote HTTP Call action

• Method/URL: POST to https://getpropera.com/api/v1/arv
• Headers (open the (OPT) header section): Content-Type:application/json and X-API-Key:YOUR_KEY
• POST Params: the JSON body, with your Podio field tokens inserted:

{
  "address": "[(Lead) Property Address]",
  "property_type": "[(Lead) Property Type]",
  "bedrooms": "[(Lead) Bedrooms]",
  "bathrooms": "[(Lead) Bathrooms]",
  "sqft": "[(Lead) Square Footage]",
  "year_built": "[(Lead) Year Built]",
  "comp_radius": "[(Lead) Comp Radius (miles)]"
}

(See the GlobiFlow Remote HTTP Call docs.)

Step 4 — Parse the response and update the item

The Remote HTTP Call captures Propera's JSON response into a variable. Give it a name (for example propera) in the call's Capture Result setting. Then add an Update Item action and extract each value with GlobiFlow's preg_match_gf() function.

Three details make or break this step:

• Use calculation mode, not value mode. In each field of the Update Item action, switch the value to a calculation. In value mode GlobiFlow writes your formula into the field as literal text instead of running it.
• Reference the variable as [(Variable) propera] inside the calculation (not <propera>, which is the syntax used elsewhere).
• preg_match_gf needs a third argument — the capture-group index to return. Leaving it off throws ArgumentCountError: Too few arguments... 2 passed... 3 expected. Pass 1 to return the first capture group as a string.

Map these calculations onto your result fields:

The comps_text field is a ready-to-paste block with one comparable per line (address, price, sqft, beds/baths, price per sqft, distance, sold date, and a Zillow link). Map it to a large (multi-line) text field. The extra str_replace('\n', "\n", ...) wrapper turns the JSON line breaks into real line breaks in Podio; without it the whole list still lands, just on one line. (Prefer the structured per-comp data instead? Every comp is also in the response's comps array.)

Then set the status field to Done. On a failure response the error calculation fills in and arv comes back empty, so you can branch the status to Error.

Request fields

Response fields

Troubleshooting