# PageCrawl Is Now a Native Make.com App: One-Click OAuth and Six Modules Source: PageCrawl.io Blog URL: https://pagecrawl.io/blog/native-make-com-integration Published: 19 August, 2026 --- Until now, connecting PageCrawl to Make.com meant copying a webhook URL from one tab to another, triggering a manual check to teach Make the payload shape, and repeating the dance for every scenario. That approach still works, and the [Make.com automation guide](/blog/make-com-website-monitoring-automation) covers it in depth. But there is now a much shorter path: PageCrawl ships as a native Make.com app. You connect once with OAuth, and every scenario after that starts from a dropdown, not a copy-paste. The app registers webhooks for you, knows your monitors, workspaces, folders, and labels by name, and exposes the most useful parts of PageCrawl as ready-made modules. ### What is the native PageCrawl app for Make.com? The native app is a first-party PageCrawl integration inside Make.com's app catalog. It connects to your PageCrawl account with OAuth (no API token or webhook URL to paste), fires the Watch Changes trigger when a monitor detects a change, and provides modules to create monitors, list and read them, and fetch diffs from any scenario. Make classifies Watch Changes as an instant trigger, which means it is webhook-based rather than polled: Make does not burn operations checking for news, and your scenario runs as soon as a completed check detects a change. Detection itself follows your monitor's schedule, with checks as often as every 2 minutes depending on plan. ### How do I connect PageCrawl to Make.com? Add any PageCrawl module to a scenario, click Create a connection, and approve the request on PageCrawl.io. That is the whole setup: no API keys, no webhook URLs, no payload redetermination. The connection is labelled with your account email, so multiple accounts stay easy to tell apart. 1. Accept the [PageCrawl app invitation](https://www.make.com/en/hq/app-invitation/a432cffa25806d1ba9ae1fb5fa2df647) to add PageCrawl to your Make organization. The app is invitation-only while it completes Make's review. 2. Create a scenario, add a module, and search for **PageCrawl**. 3. Pick **Watch Changes** (or any other module) and click **Create a connection**. You are redirected to PageCrawl.io to authorize the app, then straight back. 4. Configure the module from dropdowns: workspace, monitors, folders, labels, and check frequencies are all listed by name. ### What can the Watch Changes trigger watch? Watch Changes can watch every monitor in a workspace, a hand-picked set of monitors, monitors carrying any of your chosen labels, monitors inside chosen folders, or monitors on chosen domains. One trigger covers whole categories of pages, so adding a monitor to a folder later automatically brings it into the scenario. A payload detail option controls bundle size: - **Essential** (recommended) sends the fields most scenarios use: monitor name, status, current value, short summary, AI summary, priority score, markdown diff, screenshot link, and page metadata. - **Full** includes everything, including raw contents and previous-check data, for scenarios that need exact before-and-after values. ### Which modules does the app include? Six modules cover the create, watch, and read sides of monitoring. Each one accepts an optional workspace selection, so a single connection serves scenarios across all your workspaces. | Module | Type | What it does | |--------|------|--------------| | Watch Changes | Trigger | Starts the scenario when a change is detected, with monitor, label, folder, or domain filters | | Create Monitor | Action | Creates a monitor with a template or track type, plan-aware frequency, folder, labels, and notifications | | List Monitors | Search | Lists monitors, filtered by name or URL | | Get Monitor | Action | Fetches a monitor's details, tracked elements, and labels | | List Recent Checks | Search | Returns the latest checks with contents, summaries, and diffs | | Get Diff | Action | Returns the diff for the latest or a specific check, as markdown, HTML, or a PNG image | Create Monitor mirrors what the PageCrawl UI offers: full page or element tracking (text, number, price, HTML, JavaScript, and more), templates, page preparation steps like removing cookie banners, and label assignment with labels created on the fly. ### How is the native app different from a custom webhook? The native app removes every manual step the custom webhook path requires. OAuth replaces URL copying, registered webhooks replace payload redetermination, and named dropdowns replace numeric IDs. The custom webhook remains useful when you want one endpoint shared by non-Make consumers or full control over the raw payload. | | Native app | Custom webhook | |---|---|---| | Setup | OAuth, one click | Copy webhook URL into PageCrawl settings | | Payload shape | Pre-declared fields, mappable immediately | Redetermine data structure from a sample | | Scope | Workspace, monitors, labels, folders, domains | Whatever the webhook notification is attached to | | Extra modules | Create, list, read monitors and diffs | Trigger only | | Maintenance | Managed by the app | URL and payload managed by hand | ### What can I build with it? Any scenario that starts with "when a page changes" and ends in another tool. Three patterns that come up constantly: 1. **Competitor price watch to Slack and Sheets.** Watch Changes filtered to a "competitors" folder, a router that checks the AI priority score, a Slack message for high-priority changes, and a Google Sheets row for everything, using the markdown diff as the changelog. 2. **Docs and changelog tracking into Jira.** Watch Changes on a "vendor docs" label, Get Diff for the exact wording, and a Jira issue with the diff in the description so engineers see precisely what the vendor changed. 3. **Monitor provisioning from a form.** A form submission or CRM update calls Create Monitor with the URL, a template, and labels, so sales or research teams add pages to watch without leaving their own tools. For deeper scenario walkthroughs, routing patterns, and troubleshooting, the [Make.com automation guide](/blog/make-com-website-monitoring-automation) covers the full toolkit. ### Getting started The native app is available on every plan, including Free. Set up a monitor for a page that matters to you, add the Watch Changes trigger in Make.com, connect with OAuth, and route the first change into Slack or a spreadsheet. The [Make.com integration guide](/help/integrations/article/pagecrawl-make-integration.md) has the step-by-step setup, and the [Zapier](/help/integrations/article/pagecrawl-zapier-integration.md) and [n8n](/help/integrations/article/pagecrawl-n8n-integration.md) integrations are there if your automation stack lives elsewhere. --- 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.