Right now, the Text Formatter action only works with contact-level custom fields. When working with opportunity-level fields (like a multi-line field of URLs), it’s not possible to run basic formatting operations (e.g., replacing line breaks with |). The Custom Code step isn’t a reliable workaround because merge tokens don’t resolve inside the sandbox, so the step only returns literal tokens or {}.

This limitation forces us to use external tools like Pabbly or Make for simple text operations, then push the data back into GHL, which breaks automation flow and makes snapshots less portable. Please extend Text Formatter support to opportunity-level custom fields so we can handle formatting entirely within GHL.