Make Notion invalid_request_url: fix the empty page ID after Gmail and Search Objects

Description and use

In Make, syncing Gmail to Notion triggers invalid_request_url when Search Objects outputs an empty page ID. Fix by filtering for a non‑empty ID and using Notion’s Update modules instead of raw HTTP.

Problem

Notion’s API returns invalid_request_url when Make builds a request to /v1/pages/ with an empty page ID after Gmail and Search Objects modules.

Outcome

By ensuring Search Objects returns a valid page ID and filtering before updates, the invalid_request_url error is eliminated, enabling reliable Gmail-to-Notion sync on Make’s free plan.

Workflow

• Watch emails in Gmail (or label watch).
• Search Notion objects by email using Search Objects module.
• Filter: Page ID exists (and optionally status not already Replied).
• Update Notion page or data source item using Update a Page or Update a Data Source Item module. (Optional) Log Message ID in Sheets to avoid repeats.
• Attach Retry module for transient failures, but not for empty-ID errors.

Evidence

Notion's API returns invalid_request_url when the page URL ends at /v1/pages/ with no page ID.

Source

Treat "module success" and "business match found" as two different checks. Add a filter after Search Objects: Page ID (or equivalent) Exists before any update module runs.

Source

Prefer current Data Source modules over Legacy database-item modules. Make documents that from 3 September 2025 Notion API 2025-09-03 uses data_source_id for new modules; Legacy modules still use database_id.

Source