Import from Podio

Bring a Podio app — fields, records, attachments, views, and comments — into a new InfoLobby table.

Prerequisites

  1. Add a Podio OAuth2 integration on the integrations page:
    • Authorize URL: https://podio.com/oauth/authorize
    • Access Token URL: https://podio.com/oauth/token
    • Resource Owner Details URL: https://api.podio.com/user/status
    • Client ID / Client Secret: register a Podio API client at podio.com/settings/api and paste them here
  2. Click Authenticate on the integration and complete the Podio login.
  3. The target workspace must already have file storage configured (managed or BYO S3/FTP) — attachments and comment files require it.

Once a Podio integration exists, the workspace overview adds an Import from Podio option to the Add Table dialog.

What gets imported

Podio InfoLobby
App fields (text, number, money, date, category, location, embed, image, contact, phone, email) Mirror fields with closest equivalent types
Single-relationship fields Lookup fields (target table picked by you during the wizard)
Items Records — Podio item id preserved on a hidden podio_id column
Item attachments + image fields File field uploads in your storage
Views (filter and sort) Grid views, best-effort filter translation
Comments Comments, with original timestamps preserved
Comment attachments + inline image markdown Files uploaded to storage; markdown rewritten
Calculation fields Skipped — formulas don't translate
Multi-relationship fields Aborts the import with an explanation
Unsupported field types Aborts the import with an explanation

How comment authors are resolved

For each Podio comment, InfoLobby tries to attribute it to the closest workspace member:

  1. Match the Podio user's email to a workspace member.
  2. If no email match, match their display name to a workspace member's display name.
  3. Otherwise post as System with a leading Originally posted by <name>: line.

Created-at timestamps are always preserved verbatim from Podio.

Lookups & limitations

  • One Podio app per import. To pull a related app, import that one first and then map the lookup back to the new table.
  • During the wizard, every relationship field shows the Podio target app and a dropdown of existing tables in the destination workspace. Pick the corresponding InfoLobby table or choose Drop this lookup to skip.
  • Lookup values are resolved before each record is inserted, using the hidden podio_id column on the target table — items that weren't part of an earlier import become NULL.

Rate limits

Podio's API has per-user rate limits. The import handles 420/429 responses automatically by waiting and retrying. While waiting, you'll see progress messages saying it has paused.

Troubleshooting

  • "No Podio integration is connected" — Add and authorize a Podio OAuth2 integration first.
  • "Failed Refreshing expired Token" — Click Authenticate again on the Podio integration, complete Podio login, then save the integration.
  • "Target workspace has no file storage configured" — Connect S3, FTP, or use the managed storage included with paid plans.
  • "Field X is a Podio multi-relationship — import not supported" — Remove the field from the Podio app or split it before importing.
  • Import is slow — Each item with attachments and comments triggers multiple Podio API calls. Large apps can take a while; the progress bar tells you where you are.