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.
What each integration type gives you
Before choosing, understand what each category contributes:
Support integrations: (Intercom, Zendesk, Freshdesk, AppFollow, Hubspot) bring in customer conversations and support tickets. This is typically the highest-volume feedback source. If your team handles support through one of these tools, start here.
Communication & CRM integrations: Slack and HubSpot 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 MRR and deal data, which directly powers the revenue signal in Pilea's priority scores. Together, they ensure Pilea surfaces both the qualitative context your team is discussing and the quantitative customer weight behind it.
Project management integrations: (Linear, Jira, GitHub, Monday, Asana, ClickUp, Trello, Notion) let you export backlog items from Pilea and keep status in 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, Freshdesk)
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 once a day (or when you click sync) 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 and sales notes, plus customer data with MRR and deal values. The revenue 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 to trigger a modal where you can tag customers and add tags, or simply @pilea to log it even faster. It's the quickest way to turn an internal conversation into structured feedback in Pilea, without breaking your flow.
ℹ️ Seedling-emoji (🌱), because Pilea is plant 😉
💡 Pro tip: Democratize feedback by creating a dedicated #feedback channel in Slack and encouraging everyone to tag messages with 🌱 as they come across it. 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, 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 a toast notification confirming the connection.
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 enable or disable sync independently from Integrations in the sidebar.
What to connect next
Once your first integration is running, consider adding:
A CRM (if you started with a support tool) to add revenue data to your priority scores
Slack to capture feedback from internal team conversations
An issue tracker (Linear, Jira, or GitHub) 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.