PageCrawl.io + Make.com integrationDeveloper

4 min read
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 a 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 when a change is detected. Watch every monitor in a workspace, specific monitors, monitors with certain labels, monitors in certain folders, or monitors on certain domains. A payload-detail option keeps bundles small or includes every field.
  • Create a monitor (action) - create a new monitor for a URL, with a template or a track type (full page, text, number, price, HTML, JavaScript, and more), plan-aware frequency choices, folder, labels, notifications, and page-preparation steps like removing cookie banners.
  • List monitors (search) - list or search monitors by name or URL.
  • Get a monitor (action) - fetch a monitor's details, tracked elements, and labels.
  • List recent checks (search) - the latest checks for a monitor, including contents, summaries, and diffs.
  • Get a diff (action) - the diff for a monitor's latest or a specific check, as markdown or HTML.
  • Get a diff image (action) - the same change as a PNG image you can attach to an email or upload to Slack and Drive.
  • Make an API call (universal) - an authorized request to any PageCrawl API endpoint your connection can reach, for anything the modules above do not cover.

Every module accepts an optional Workspace selection, so a single connection can serve scenarios across all your workspaces.

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

The PageCrawl app is currently available by invitation while it completes Make's review.

  1. Open the PageCrawl app invitation and accept it. This adds PageCrawl to your Make organization.
  2. Create a new scenario, add a module, 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 what to watch: every monitor in the workspace, specific monitors, or monitors matched by label, folder, or domain.

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.

Ready to Track Changes?

Set up monitoring in under 60 seconds and never miss important updates again.

Track a New Page