# PageCrawl.io + Make.com integration

Source: PageCrawl.io Help Center
URL: https://pagecrawl.io/help/integrations/article/pagecrawl-make-integration

---

[Image: PageCrawl Integrations settings showing available connections]

The native PageCrawl app for Make.com lets you start a scenario the moment PageCrawl detects a change, and create new monitors from inside any scenario. You connect once with a single click (OAuth, no API token to paste), then build scenarios that route changes into thousands of apps.

### Native app vs custom webhook

There are two ways to use PageCrawl with Make.com:

- **Native app (recommended):** Connect with OAuth and use the **Watch Changes** instant trigger. PageCrawl registers the webhook for you, so there is no URL to copy or data structure to redetermine. You can also use the **Create Monitor** action.
- **Custom webhook:** Add a PageCrawl webhook notification by hand and receive it with Make.com's Custom Webhook module. This still works and is covered in the Make.com automation guide, but the native app is simpler to set up and maintain.

### What the app provides

- **Watch Changes** (instant trigger) - fires the moment a change is detected, for a single monitor or every monitor in the workspace.
- **Create Monitor** (action) - create a new monitor for a URL, with the track type, frequency, folder, labels, and notifications you choose.
- **List Monitors** (search) - look up monitors to reference in later modules.

### Setting up the integration

#### Step 1: Sign in to PageCrawl.io

If you are not already a PageCrawl.io user, sign up for an account. The free tier is enough to build and test scenarios.

#### Step 2: Configure a page to monitor

Set up the page you want to track, choosing the elements to watch and your notification preferences.

#### Step 3: Add the PageCrawl app in Make.com

1. In Make.com, create a new scenario and add a module.
2. Search for **PageCrawl** and add the **Watch Changes** trigger.
3. Click **Create a connection**. You are redirected to PageCrawl.io to authorize Make.com. There is no token to paste.
4. Choose the monitor to watch, or leave it empty to watch every monitor in the workspace.

#### Step 4: Build the scenario

Add the modules that should run when a change is detected: post to Slack, append a row to Google Sheets, open a Jira issue, or any of the thousands of apps Make.com supports. Reference PageCrawl fields like **AI summary**, **Short summary**, **Page URL**, and **Screenshot URL** directly in those modules.

#### Step 5: Activate

Save the scenario and turn it on. PageCrawl pushes each detected change to Make.com in real time.

### The trigger payload

The **Watch Changes** trigger delivers the same payload as a PageCrawl webhook. The fields you will use most often:

- **`title`** - the monitor name.
- **`short_summary`** and **`ai_summary`** - human-readable descriptions of what changed. `ai_summary` requires AI to be enabled for the workspace.
- **`ai_priority_score`** - importance score you can filter on.
- **`page.url`** and **`page.link`** - the monitored URL and the PageCrawl page link.
- **`page_screenshot_image`** - a link to the screenshot for visual verification.
- **`markdown_difference`** - the change as a readable diff.
- **`changed_at`** - ISO 8601 timestamp.

For the full field reference, see [API & Webhooks](/help/features/article/api-webhooks-for-custom-integrations.md).

### Related Articles

- Make.com automation guide - Scenarios, patterns, and the custom-webhook approach
- [Zapier Integration](/help/integrations/article/pagecrawl-zapier-integration.md) - Automate with Zaps
- [n8n Integration](/help/integrations/article/pagecrawl-n8n-integration.md) - Open-source workflow automation
- [API & Webhooks](/help/features/article/api-webhooks-for-custom-integrations.md) - Programmatic access and full payload reference

---

Need more? The complete PageCrawl.io help center, with every article, is available as a single document at https://pagecrawl.io/llms-full.txt. Read it for context on anything this page does not cover.