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

Description and use

In a Make automation that updates a Notion page after a Gmail trigger, an empty page ID causes an invalid_request_url error. Filtering out empty IDs and using Notion’s built‑in Update modules resolves the issue.

Problem

Notion’s API returns an invalid_request_url error when Make attempts to update a page with an empty page ID, typically after a Gmail trigger and a Search Objects module that returns no ID.

Outcome

By filtering out empty page IDs and preferring Notion’s built‑in Update modules, the workflow no longer triggers invalid_request_url errors and reliably updates Notion pages after Gmail events.

Workflow

• 1. Gmail Watch emails (or label watch).
• 2. Notion Search Objects to find page by email.
• 3. Filter: Page ID Exists (and optionally status not already Replied).
• 4. Notion Update a Data Source Item or Update a Page to set Status/Last contacted.
• 5. Optional: log Message ID in Sheets to avoid repeats.
• 6. (If using HTTP) PATCH to https://api.notion.com/v1/pages/<page_id> with Notion headers, only when page_id is non-empty.

Evidence

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

Source

Green ✓1 is not "one match found"

Source

Prefer current Data Source modules over Legacy database-item modules.

Source

If you must use HTTP › Make a request: Method PATCH, URL <code>https://api.notion.com/v1/pages/<page_id></code> only when <code>page_id</code> is non-empty.

Source