I’m trying to use a regular expression with Apps Script to locate specific text patterns in a Google Doc. My goal is to find code blocks that are wrapped with triple backticks.
var pattern = '`{3}([\s\S]*?)`{3}'; // Pattern to match text between three backticks
var result = document.findText(pattern); // This returns null
The search keeps returning null even though I can see the triple backtick blocks in my document. I think maybe my regex syntax isn’t compatible with the RE2 engine that Google uses, but I can’t figure out what’s wrong with it. Has anyone run into this issue before? What am I missing here?
Been there with Google Apps Script. The findText() method is pretty limited beyond basic string searches.
You’re hitting a classic issue - Google Docs splits your text across multiple runs internally, even when it looks continuous. Your regex is fine, but findText() can’t piece together text spanning different formatting elements.
I used to waste hours fighting Apps Script limitations like this. Now I automate the whole document processing pipeline instead. Set up a workflow that extracts content from your Google Docs, runs proper regex matching with full JavaScript support, then updates the document or exports results wherever you need.
You get real regex engines, not the stripped down Apps Script version. Plus you can handle multiple documents, set up triggers, and turn this into a robust system instead of a fragile script.
I’ve automated similar tasks and it’s night and day compared to fighting Apps Script’s quirks. Way more reliable and scales easily.
This is super common with Google Apps Script’s findText() method. Your regex pattern is probably fine - the real issue is how findText() handles formatted text in Google Docs. I’ve run into this exact problem before. The method gets unreliable when searching across paragraphs or when there are formatting breaks you can’t see. Triple backticks often get split into different text elements internally, which breaks your regex match. Here’s what works: extract all the document text first with getBody().getText(), run your regex on that string, then use the position info to find and change the actual document elements. It’s more code but way more reliable than trying to make findText() work with complex patterns.
Had this exact problem last month building a documentation parser. Your regex isn’t the issue - Google Docs splits text runs unpredictably behind the scenes. Even simple stuff like triple backticks gets fragmented across multiple elements.
What worked for me: ditch findText() and use searchText() instead. It handles cross-element matching way better. Try document.getBody().searchText(pattern) with your regex - returns a RangeElement you can actually use.
One more thing - sometimes you need editAsText().searchText() on the body element instead, depends on your doc structure. Flattens the formatting and makes regex matching predictable. Switching from findText() to searchText() saved me hours of debugging.
Google Apps Script’s findText() method is broken when it comes to regex, despite what the docs claim. I ran into this same issue - findText() only handles literal strings and super basic patterns reliably. For triple backticks, you’ll need a different approach. Skip findText() entirely and iterate through the document manually instead. Grab the full text with getBody().editAsText().getText(), then use regular JavaScript regex to find your code block positions. Once you’ve got the indices, use replaceText() or other editing methods to make your changes. Yeah, it’s more code, but you’ll actually get working regex that plays nice with Google’s document structure.
findText() struggles with backticks since Google Docs treats them as special characters. Try escaping them a different way, or just search for what’s inside the backticks rather than the backticks themselves. Fixed it for me when I ran into the same thing.