Make

What You'll Need

• A Pilea workspace (the one you're already using)
• A Make.com account
• Your API key from Pilea
• 5 minutes

Installation

Step 1: Grab Your Pilea API Key

Head to https://<your-workspace>.pileainsights.com/settings/api-keys and copy your key. Don't share it – treat it like your Netflix password.

Step 2: Find Your Product ID

Go to https://<your-workspace>.pileainsights.com/settings/workspace and note down your product ID. You'll need this in a minute.

Step 3: Set Up Make.com

1. Create a new scenario in Make.com
2. Add your trigger (whatever tool you're pulling feedback from)
3. Add a new module: HTTP > Make an API Key Auth request

Step 4: Configure the HTTP Module

Fill in these fields:

• Credentials: Click Add and paste in your Pilea API key
• URL: https://<your-workspace>.pileainsights.com/api/v1/feedbacks
• Method: POST
• Headers: Add X-Client-Id with value <your-workspace>
• Body type: Raw
• Content type: JSON

Step 5: Build Your Request

In the request content field, add:

json

{
 "product_id": "prd_yourid",
 "text": "Your feedback text here" // Select field dropdown
}

Map the feedback text from your trigger tool to the text field. Make.com will handle the data mapping for you.

Step 6: Test & Activate

Hit "Run once" to test. If it works, flip the switch to "ON" and set your preferred polling interval.

Done. Feedback now flows automatically.

‍

Once you've connected your tools, here's what happens:

• No manual work needed
  ‍Feedback hits your connected tool → Make.com picks it up → Pilea organizes it.
• Scheduling
  ‍Set how often Make.com checks for new feedback.
  Every 15 minutes? Every hour? You decide.
• Connect as many tools as you want
  Each one gets its own scenario in Make.com, all feeding into Pilea.
• Custom Logic
  ‍Need to filter or transform feedback before it reaches Pilea?
  Add modules in Make.com to clean up data, filter out noise, or route specific feedback types differently.