Make.com Integration

Overview

Make.com (formerly Integromat) uses a visual drag-and-drop builder for automation scenarios. You'll use the HTTP > Make a request module to call Brainpercent's API. This guide shows every field you need to configure in Make.com's interface.

Prerequisites

• A Make.com account (Free plan: 1,000 ops/month; Core plan recommended for production)
• A Brainpercent API key (bp_ prefix) with read + write permissions, created at brainpercent.app/chat/developers. Keys cannot be created over the API.
• A project id. Every generation call needs one. Fetch it with GET https://www.brainpercent.app/api/v1/projects and store it, or add that call as the first HTTP module. Projects are created in the app, not over the API.
• Basic familiarity with Make.com's visual editor

HTTP Module: Field-by-Field Setup

Add an "HTTP > Make a request" module to your scenario. Here is every field in the module configuration panel:

Headers Array

Click "Add a header" twice to create two header items:

Request Content (JSON Body)

Paste this into the "Request content" field. Use Make.com variables with the {{moduleNumber.field}} syntax to reference data from previous modules:

{
  "topic": "Your Article Topic",
  "project_id": "d290f1ee-6c54-4b01-90e6-d701748f0851",
  "keywords": ["keyword1", "keyword2"],
  "tone": "professional",
  "word_count": 1200
}

Scenario: Automated Content Pipeline

Full pipeline: Trigger → Generate Article → Sleep → Check Status → Router → Generate Social

Module 1: Schedule Trigger

Module 2: HTTP > Make a Request (Generate)

Configured exactly as shown in the HTTP Module Setup above with POST /articles/generate.

Module 3: Sleep

Module 4: HTTP > Make a Request (Check Status)

Module 5: Router (Conditional Branching)

Add a Router module after the status check. Configure two routes:

Module 6: HTTP > Make a Request (Generate Social)

{
  "source_url": "https://www.brainpercent.app/articles/{{4.data.slug}}",
  "platforms": ["twitter", "linkedin", "facebook"],
  "project_id": "d290f1ee-6c54-4b01-90e6-d701748f0851",
  "angle": "Practical takeaways for busy marketers"
}

Module 7: Publish or Schedule

Add a Sleep, then an HTTP module that polls https://www.brainpercent.app/api/v1/social/content/{{6.data.content_id}} until status is ready or completed. Then POST to /api/v1/social/publish. Publishing content that is still generating returns 412.

{
  "content_id": "{{6.data.content_id}}"
}

Only content_id is required. Omit platforms to publish every variant. Without scheduled_at the API returns 202 and publishes immediately; with it, 200 and scheduled. A 412 also means no social accounts are connected.

Scenario: Credit Monitor

Get notified when credits run low. You have one balance for everything: 1 credit equals $1.00, an article costs 1.5 credits, and social costs 0.6 credits per platform, so pick a threshold that covers a few runs. Three modules:

JSON Parsing & Data Mapping

With "Parse response: Yes" enabled, Make.com automatically maps JSON fields. Reference them using {{moduleNumber.path.to.field}}. Note that error sits next to data, not inside it, and social captions are keyed by platform name rather than sitting in a list:

Error Handling

Right-click any HTTP module and select "Add error handler". Make.com provides four error handler types:

Handling 429 Rate Limits

Add a Break error handler with automatic retry:

Scenario Schedule Settings

Click the clock icon at the bottom of your scenario to configure run frequency. In the scheduling panel:

Tips & Best Practices

• Always enable "Parse response: Yes" on HTTP modules for automatic JSON field mapping
• Store your API key in a Make.com Data Store or use the "Keys" feature for centralized management
• Add error handlers to every HTTP module: use "Resume" for batch processing, "Break" for critical paths
• Use the Router module for conditional branching, and branch on data.is_complete rather than a status string
• Social generation returns one row for all platforms, so there is no items array to iterate. Read each caption directly from data.platforms.<platform>, or use an Iterator over that object if you need one bundle per platform.
• Use data.image_urls for images. Those links are permanent.
• Use Sleep (under Tools) for polling delays, not Code modules with setTimeout
• Monitor operations usage in scenario settings: each HTTP request is 1 operation