> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pylar.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Make

> Connect Pylar MCP tools to Make (Integromat) for visual automation workflows with data access

## Overview

Make (formerly Integromat) is a visual automation platform. Connect your Pylar MCP tools to Make to access your data in automation scenarios without writing code.

## Prerequisites

* ✅ Make account
* ✅ Pylar project with published MCP tools
* ✅ MCP HTTP Stream URL and Bearer Token from Pylar

## Step 1: Get Your Pylar Credentials

1. In Pylar, navigate to your project
2. Click **"Publish"** in the right sidebar
3. Copy both:
   * **MCP HTTP Stream URL**: `https://mcp.publish.pylar.ai/mcp`
   * **Authorization Bearer Token**: Your unique token

## Step 2: Create HTTP Module in Make

1. In Make, create a new scenario
2. Add an **"HTTP"** module
3. Choose **"Make a Request"**

## Step 3: Configure HTTP Request

**URL**: `https://mcp.publish.pylar.ai/mcp/tools/call`

**Method**: `POST`

**Headers**:

```
Authorization: Bearer YOUR_BEARER_TOKEN_HERE
Content-Type: application/json
```

**Body Type**: `Raw`

**Body Content (JSON)**:

```json theme={null}
{
  "name": "fetch_engagement_scores_by_event_type",
  "arguments": {
    "event_type": "{{1.event_type}}"
  }
}
```

Replace `YOUR_BEARER_TOKEN_HERE` with your token and `{{1.event_type}}` with your Make data field.

## Step 4: Parse Response

1. Use Make's JSON parser to extract data
2. Map data to subsequent modules
3. Build your automation workflow

## Example Scenario

**Trigger**: New record in Google Sheets

**Module 1**: HTTP - Call Pylar tool

* Get customer data based on email

**Module 2**: Update CRM

* Use Pylar data to update customer record

**Module 3**: Send notification

* Alert team with customer insights

## Benefits

* ✅ **Visual Workflows**: Build automations visually
* ✅ **No Code**: Drag-and-drop interface
* ✅ **Centralized Updates**: View changes reflect automatically
* ✅ **Secure**: Data through governed views
* ✅ **Monitoring**: Track usage in Pylar Evals

## Troubleshooting

### Issue: Request fails

**Solutions**:

* Verify Bearer Token in headers
* Check JSON body format
* Ensure tool name is correct
* Test in Pylar first

## Next Steps

* [Publishing Tools](/learn/publishing-tools/publishing-your-tools) - Publish tools
* [Evals](/learn/evals/overview) - Monitor usage
* [Other Builders](/learn/connecting-agent-builders/overview) - More platforms