What data sources and integrations does Pilea support?

Updated

Pilea accepts two kinds of input: files you upload directly (CSV, interview recordings, call notes) and connected tools (Slack, Intercom, HubSpot). You can start with uploads alone — the site states no integrations are needed to begin and no admin access is required. Integrations are connected "when you're ready," so they're optional rather than a setup prerequisite.

Direct uploads

These work without connecting anything:

  • CSV files — bulk feedback data exported from wherever it currently lives.
  • Interview recordings — user research sessions.
  • Call notes — written notes from customer or renewal calls.

The product description frames this as turning "the feedback already sitting in Slack, Intercom and HubSpot" into a scored backlog, and the page confirms uploads produce a scored backlog "in minutes."

Connected integrations

Source What it contributes
Slack Feedback mentions from channels
Intercom Support tickets and conversations
HubSpot Customer and deal context

The interface shows mentions tagged by source — for example, a Slack message from a named customer and an Intercom ticket, each marked "Processed" with a timestamp and item count. Deal size (e.g. €62,000) appears alongside mentions, which suggests CRM data from HubSpot feeds prioritization rather than just text.

What you need to get started

  • No admin access — stated explicitly on the page.
  • No integrations required — you can upload files first and connect tools later.
  • EU-hosted — data residency is listed as a product attribute.
  • Free to start — the page says "Free to start · No credit card." Pricing details beyond that aren't specified here; check the pricing page for current terms.

Practical implications

If your feedback is scattered across Slack threads and Intercom tickets, connecting those two sources gives Pilea the raw material automatically. If your research lives in recordings and call notes, uploads cover it without touching your workspace permissions. The combination — uploads for depth, integrations for volume — is what the product seems designed around.

One thing to verify before committing: how each integration authenticates and what scope it requests. The page confirms no admin access is needed, but doesn't detail the permission model per tool.