# Create Google Doc block resolves referenced variables to literal "undefined"

**URL:** <https://community.mindstudio.ai/t/create-google-doc-block-resolves-referenced-variables-to-literal-undefined/2145>\
**Category:** Bug Reports\
**Created:** [September 15, 2026, 12:12am UTC](https://community.mindstudio.ai/t/create-google-doc-block-resolves-referenced-variables-to-literal-undefined/2145 "2026-09-15T00:12:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ValiantFjord20](https://avatars.discourse-cdn.com/v4/letter/v/c68b51/32.png) [@ValiantFjord20](https://community.mindstudio.ai/u/ValiantFjord20)\
**Post date:** [September 15, 2026, 12:12am UTC](https://community.mindstudio.ai/t/create-google-doc-block-resolves-referenced-variables-to-literal-undefined/2145/1 "2026-09-15T00:12:55Z")

</div>

Agent: SPORT\_M0\_Research\_Orchestration, Main.flow, Create Google Doc block (follows a Deep Research block).

Agent link: [https://app.mindstudio.ai/agents/5d632103-77a4-4abd-b64f-dc3a552bffcd/edit](https://app.mindstudio.ai/agents/5d632103-77a4-4abd-b64f-dc3a552bffcd/edit)

Expected: A field referencing a variable like {{VariableName}} (e.g. Content: {{Research}}) should substitute the variable’s actual value at runtime.

Actual: The field resolves to the literal string “undefined” instead, and that literal text gets written into the created Google Doc.

Reproduction / isolation steps:

1. Deep Research block outputs to a variable (confirmed working - verified real content produced via the block’s own Test Block run).

2. Create Google Doc block references that variable in its Content field: {{Research}}. Full-flow run: Content resolves to “undefined”; a real Google Doc is created but its body is just the word “undefined”.

3. Isolated Test Block on the Create Google Doc block, supplying an explicit mock value for the variable via the Test Block modal. MindStudio correctly detects and prompts for the variable, but even with a real mock string value supplied, Content still resolves to “undefined”.

4. Renamed the output variable to a unique name to rule out a naming collision - same result.

5. Retyped the field using real keystrokes rather than any external tooling to rule out a stale UI/backend desync, and confirmed via a full page reload that the saved config was correct - same result.

6. Tested a second field on the same block (Document Name, referencing the same variable) - it also resolved to “undefined”, so this is not Content-field-specific. It affects variable substitution across the whole Create Google Doc block.

This points to a bug in the Create Google Doc block’s variable-resolution step, not a workflow configuration issue. Happy to share screenshots or more detail if useful for reproduction.

---

<div class="post-metadata">

**Author:** ![Alex\_MindStudio](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.mindstudio.ai/alex_mindstudio/32/27_2.png) [@Alex\_MindStudio](https://community.mindstudio.ai/u/Alex_MindStudio)\
**Post date:** [September 16, 2026, 2:14pm UTC](https://community.mindstudio.ai/t/create-google-doc-block-resolves-referenced-variables-to-literal-undefined/2145/2 "2026-09-16T14:14:13Z")

</div>

Hi @ValiantFjord20,

Thank you for the detailed post.

Could you let me know how you’re launching the agent? Are you using the Open Draft or Preview Published options, or something else?

 ![image](https://canada1.discourse-cdn.com/flex008/uploads/mindstudio/original/2X/5/58580388f03f3f73b60e815faa9f49362da2d206.png)