Why Your JSON Parses Fine but Your Automation Still Breaks (And How Match Pattern Fixes It)
A really common problem people run into when working with webhooks is this: the JSON comes in fine, but one of the fields you actually need is buried inside a messy block of text. For example, a webhook sends a message that includes a ClickUp task link, email, phone number, and notes all mashed together in one string. When you try to map that directly into another app, it either errors out or pulls the wrong value because Make can’t tell what part of the text you actually want. This is where the Match Pattern (Text Parser) saves you. Instead of fighting the JSON structure, you let Make parse the JSON first, then use a regex pattern to extract only the exact piece you need, like a task ID or order number. Once that value is isolated, downstream modules stop breaking, filters work properly, and your automation becomes predictable instead of fragile. I recommend using https://regex101.com/ when doing regex.