You’ve set up your workspace. Now you need data. The integration you connect first determines how quickly Pilea can start structuring feedback and computing priority scores. This article helps you choose the right one based on where your team’s customer feedback already lives.

ℹ️ Note: If you picked tools during onboarding, they’re waiting for you in a Your tools card at the top of the Integrations page. Connect them from there.

What each integration type gives you

Before choosing, understand what each category contributes:

Support integrations: (Intercom, Zendesk, HubSpot, AppFollow) bring in customer conversations, support tickets and app-store reviews. This is typically the highest-volume feedback source. If your team handles support through one of these tools, start here.

Meeting recorders: (Gong, Fireflies, Granola, Jiminny) import your sales calls, user interviews, and meeting transcripts as interviews, so spoken feedback gets structured alongside your written signals. They’re being rolled out per organization - if you don’t see them on your Integrations page, email us and we’ll enable them.

Communication & CRM integrations: Slack and your CRM (HubSpot or Attio) serve different but complementary roles in Pilea. Slack captures the informal, real-time layer of customer insight: team-sourced feedback, sales/demo notes, and signal from conversations that would otherwise get lost. HubSpot goes deeper on the customer data side: it syncs structured CRM records, including deal values, which directly powers the revenue signal in Pilea’s priority scores. Attio does the same for teams on Attio: companies, notes and deal sizes, plus call transcripts if you record calls there. Together, they ensure Pilea surfaces both the qualitative context your team is discussing and the quantitative customer weight behind it.

Context sources: Notion pages and GitHub repositories give Pilea background on your product. Notion pages can be imported as feedback to analyze or as knowledge documents.

Issue tracker integrations: (Linear, Jira, GitHub Issues) let you export backlog items from Pilea to your development workflow, with status kept in two-way sync. These don’t bring feedback in - they send prioritized items out. Connect these after you have feedback flowing.

Which integration to connect first

If your team uses a support tool (Intercom, Zendesk)

Start with your support tool. Support conversations are usually the richest source of customer feedback - bug reports, feature requests, complaints, and usability issues all surface in tickets.

After connecting, Pilea syncs your conversations every 6 hours (or whenever you click Sync now) and structures them into backlog items. You’ll see patterns you’d miss by reading tickets one at a time.

If your team uses HubSpot as a CRM

Start with HubSpot. It gives you two things at once: feedback from support tickets, sales emails, notes and meetings, plus customer data with deal values. The deal data powers the revenue impact signal in priority scores, which means your scores will be more meaningful from day one.

If your team collects feedback in Slack

Start with Slack. It gives your team a lightweight way to capture signals in the moment, right where conversations are already happening. React to any message with the 🌱 emoji and Pilea captures it straight away, with a prompt to add customers and tags. Mention @Pilea in a message to log it just as fast, type /pilea to enter feedback in a form, or set up listen channels so every message in a channel is captured automatically. It’s the quickest way to turn an internal conversation into structured feedback in Pilea, without breaking your flow.

ℹ️ Seedling emoji (🌱), because Pilea is a plant 😉

💡 Pro tip: Democratize feedback by creating a dedicated #feedback channel in Slack and adding it as a listen channel, or encouraging everyone to tag messages with 🌱 as they come across them. The more teams contribute, the richer your signal.

If you don’t use any of the supported tools

If you use a tool we don’t support yet, you can connect it directly via the Pilea API. It’s straightforward to set up, but don’t hesitate to reach out, we’re happy to help.

You can also start by adding feedback manually. Bulk upload text, audio and video files, then add integrations or hook into the Pilea API later.

What to expect after connecting

Immediate: Pilea begins syncing data from the connected tool. You’ll see an Integration connected toast, and for most integrations a setup dialog where you pick the sync date and filters for this workspace.
Within minutes: Feedback entries start appearing. The AI analyzes each one, extracts backlog items, and links them to customer profiles.
Within an hour: Priority scores appear on backlog items as enough data accumulates for the scoring signals to activate.

The more feedback Pilea has, the better the scores and insights.

ℹ️ Note: Integrations are connected at the organization level. All workspaces in your organization can access the data. Each workspace can turn Auto sync on or off independently from Integrations in the sidebar.

What to connect next

Once your first integration is running, consider adding:

HubSpot or Attio (if you started with a support tool) to add deal data to your priority scores
Slack to capture feedback from internal team conversations
A meeting recorder (Gong, Fireflies, Granola, or Jiminny - or Attio’s call transcripts) to bring spoken feedback from calls and interviews into Pilea
Notion or GitHub Repositories to give Pilea more context on your product
An issue tracker (Linear, Jira, or GitHub Issues) to export prioritized items to your development workflow

You don’t need to connect everything at once. Add integrations as your team’s workflow expands.

Choosing your first integration