For the complete documentation index, see llms.txt. This page is also available as Markdown.

Pullbay x Make Integration

Make.com (formerly Integromat) is a visual automation platform that lets you connect apps and APIs without code. This guide shows you how to use Pullbay's App Store Reviews API within Make scenarios—today with the HTTP module, and with a native Pullbay module coming soon.

What You Can Build with Pullbay and Make

Make + Pullbay enables you to:

  • Automate daily review collection: Pull fresh reviews on a schedule and route them automatically

  • Filter and alert on critical reviews: Catch 1–2 star reviews and send instant notifications

  • Log reviews to Google Sheets: Build a live spreadsheet of all customer feedback

  • Send Slack notifications: Post reviews to team channels in real-time

  • Feed reviews to Airtable: Create structured databases for analysis and collaboration

  • Update CRM records: Sync reviews to Pipedrive, HubSpot, or other CRM systems

  • Create email digests: Send summaries of high-priority reviews to stakeholders

How the Integration Works

Make uses a visual, modular approach. You'll chain together modules—a scheduler, an HTTP request module to call Pullbay, a JSON parser, filters, and actions. No native Pullbay module exists yet, but the generic HTTP module gives you full API access today. A native Pullbay module is coming soon.

1

Create a New Scenario

  1. Log in to make.com

  2. Click Create a new scenario

  3. Choose a name (e.g., "Pullbay Daily Reviews to Slack")

  4. You'll see the scenario builder with a blank canvas

2

Add a Schedule Trigger

  1. Click Add a module (or the + icon)

  2. Search for Scheduled (the built-in scheduler)

  3. Select Schedule > Trigger

  4. Configure the schedule:

    • Type: Choose "Daily," "Weekly," or "Monthly"

    • Repeat every: Set to 1 (runs daily)

    • Start time: Choose a time (e.g., 9 AM)

    • Interval: Daily (or your preference)

  5. Click OK

Your scenario now runs on schedule.

3

Add an HTTP Module to Fetch Reviews

  1. Click the + icon below the Schedule module

  2. Search for HTTP and select HTTP > Make a request

  3. Configure the HTTP module with these settings:

    Setting
    Value

    URL

    https://api.pullbay.com/v1/app-store/reviews/all

    Method

    GET

    Headers

    Authorization: Bearer YOUR_API_KEY

    Query string

    app_id=YOUR_APP_ID

    Parse response

    Yes (checked)

Here's what each field does:

  • URL: Points to Pullbay's endpoint that returns all reviews for your app

  • Method: GET because we're retrieving data (not creating or updating)

  • Headers: Contains your API authentication. Replace YOUR_API_KEY with your actual Pullbay API key

  • Query string: Tells Pullbay which app to fetch reviews for. Replace YOUR_APP_ID with your actual App Store app ID

  • Parse response: Tells Make to parse the JSON response automatically

  1. Click OK

Make will test the request and show you the response structure—a JSON object with a data array containing review objects.

4

To make the response easier to work with, add a JSON parser:

  1. Click + below the HTTP module

  2. Search for JSON and select JSON > Parse JSON

  3. In the JSON string field, select the response body from the HTTP module (the field should show a dropdown with output from the HTTP step)

  4. Click OK

This creates a clean data structure you can map to the next steps.

5

Filter Reviews (Optional)

To act only on critical reviews, add a filter:

  1. Click + below the JSON parser

  2. Search for Router or Filter

  3. Select Flow control > Router (or Filter)

  4. Set up a condition:

    • Field: rating (from the parsed reviews)

    • Operator: < (less than)

    • Value: 2

This routes only 1–2 star reviews to the next step.

6

Choose Your Action

Now route the reviews to your destination. Here are common workflows:

  1. Click + below the filter

  2. Search for Slack

  3. Select Slack > Send a message

  4. Connect your Slack workspace

  5. Choose the channel (e.g., #app-reviews)

  6. In the Message field, format your review. Map fields from the HTTP response:

    • [rating] stars from [author]

    • Title: [title]

    • Review: [content]

    • Country: [country]

  7. Click OK

  1. Click + below the filter

  2. Search for Google Sheets

  3. Select Google Sheets > Add a row

  4. Connect your Google account

  5. Choose your spreadsheet and worksheet

  6. Map the columns:

    • Column A: Today's date (use now function)

    • Column B: Rating (map to rating field)

    • Column C: Title (map to title field)

    • Column D: Review (map to content field)

    • Column E: Author (map to author field)

    • Column F: Country (map to country field)

  7. Click OK

  1. Click + below the filter

  2. Search for Email

  3. Select Email > Send an email

  4. Set:

    • To: your email or team distribution list

    • Subject: New critical review from [author]

    • Body: Compose a formatted message with review details

  5. Click OK

Example Scenario: Daily Reviews to Google Sheets + Slack

Here's a complete, ready-to-use scenario:

  1. Module 1: Schedule → Runs daily at 9 AM

  2. Module 2: HTTP Request → Fetches all reviews from Pullbay

  3. Module 3: JSON Parser → Parses the response

  4. Module 4: Router → Filters for rating < 2

  5. Module 5: Google Sheets → Logs all low-rated reviews to a spreadsheet

  6. Module 6: Slack → Posts a summary to #app-reviews

When this scenario runs:

  • It wakes up at 9 AM

  • Pulls overnight reviews from Pullbay

  • Filters for 1–2 star reviews

  • Adds them to your review tracking sheet

  • Alerts your team on Slack with the critical reviews

All hands-off, no manual copying.

Example Scenario: Weekly Digest with Aggregation

For a higher-level view:

  1. Schedule → Runs weekly on Monday at 8 AM

  2. HTTP Request → Fetches all reviews

  3. Filter → Separate into rating buckets (5-star, 4-star, 1-2 star)

  4. Aggregator (optional Make module) → Groups reviews by rating

  5. Email → Sends a formatted digest showing review counts and top comments by rating

Securing Your API Key

Never hardcode your Pullbay API key in a scenario. Instead:

  1. Click the key icon next to the Authorization header field

  2. Select Add a variable or Create a custom variable

  3. Name it pullbay_api_key and paste your API key

  4. Click OK

Make encrypts the variable and only uses it at runtime. You can reuse this variable in all your scenarios.

Understanding the Pullbay API Response

The HTTP module returns a JSON response like this:

In Make, you can map any of these fields (rating, title, content, author, country, etc.) to your actions.

Rate Limits and Pricing

Your Make scenarios count against your Pullbay API plan:

  • Free: 10 requests/minute

  • Starter: 60 requests/minute

  • Growth: 300 requests/minute

  • Scale: 1000+ requests/minute

Check the Pullbay dashboard for current pricing.

Troubleshooting

HTTP module returns "401 Unauthorized"

  • Verify your API key is correct and active

  • Ensure the Authorization header is exactly: Bearer YOUR_API_KEY (with the space)

  • Check that your API key hasn't expired

No reviews returned

  • Confirm your app ID is correct

  • Verify that your app actually has reviews on the App Store

  • Check the response body—look for error details

Scenario runs but takes too long

  • If you're fetching for a large app with thousands of reviews, the HTTP request may slow down

  • Consider filtering by date in a custom module or post-processing the response

Can't map fields to actions

  • Ensure you've enabled "Parse response" in the HTTP module

  • Run a test execution first to populate the response data

  • Click on the field in the action module and select from the dropdown

Advanced: Custom Aggregation and Reporting

For sophisticated reporting, use Make's built-in modules:

  • Aggregator: Group reviews by rating or country

  • Text aggregator: Concatenate review bodies for a summary

  • Math: Calculate average rating across all reviews

  • Array functions: Filter or transform review data before sending

These let you build insights beyond simple logging.

Native Integration Coming Soon

A native Pullbay module for Make is in development. When available, you'll get:

  • Pre-configured fields with no manual mapping needed

  • Built-in error handling and retry logic

  • Faster setup and cleaner scenarios

  • Direct access to Pullbay-specific features

Until then, the HTTP module approach is fully supported and powerful.

Next Steps

  1. Create a new scenario in Make

  2. Set up a Schedule trigger for daily at a time that works for your team

  3. Add the HTTP module and fill in your API key, app ID, and endpoint

  4. Add one action (Slack, Google Sheets, or email) to start

  5. Run a test execution to verify everything works

  6. Enable the scenario and monitor the first run

For more on Pullbay's API, see the API documentation. For Make-specific help, visit Make's help center.