@thomaslarkin the reason that it is asking for a connector is that the DocGen action needs to know where to get your template document from. To use the Generate Document action you need to have a template document that has been tagged with the variable values that you would like to populate with the data from your form / workflow, and that template document needs to be hosted somewhere that NWC can access. 

While the output (the pdf) can then be stored as a variable within the Nintex Workflow Cloud instance and sent somewhere, the input (template document) needs to already be hosted somewhere the workflow can find.

We have a setup walkthrough video here for the action if you'd like to check it out: https://www.youtube.com/watch?v=JPzYDmIwdOY&t=11s&ab_channel=Nintex

hi @butlerj i totally understand that, makes sense.  However, when i try to use the document generation i dont get the option to use a connector to point it to the template.  

@thomaslarkin oh interesting. What region is your tenant in? I'm wondering if there's a bug with the action in the tenants that are running the new version of the engine.

@thomaslarkin I've discovered that this is due to a change in how the new engine interacts with the Document Generation system. You will need to use a 'Get a File' action from your SaaS vendor of choice to pull in the template document and then you can reference that file within the Generate Document action. For example:

awesome, thanks @butlerj  i will give that a go now