Nintex Workflow Cloud

[gabriel_russ]

I am working with a product called Nintex Workflow Cloud. It has a Adobe Sign connector. It allows me to connect my Adobe Sign account and then select a template to use and send to users to sign. I create a custom library template to use and it is not showing up within Nintex. The only templates that I am allowed to select are the out of the box default W-4 and I-9 templates. Does anybody have experience with Nintex? Is there a special setting I need to check in my account in order to allow my custom library templates to be accessible through the API?

[gabriel_russ · Accepted solution]

Problem resolved itself. I am not sure if it had something to do with my Adobe account being new or what but the "fix" for this issue seems to be:

• Create Adobe Sign account
• Create custom templates
• Wait ~24 hours
• Create Nintex Workflow Cloud connection to Adobe Sign

Once you see the first custom template, you can create new templates and they show up almost immediately in the Nintex Workflow once you refresh.

[SimonATS]

Hi Gabriel,

Thanks for the update.

I was looking at your trial account and noticed that the first Oauth connection from the Nintex app was made only about 20-30 minutes ago.

without this connection Nintex could not know about any templates nor your account.  You can check this by logging in Adobe Sign via the Sign webportal and going to account>personal>preferences>Account tokens

I don't know what happened yesterday though.

[gabriel_russ]

Thanks for the reply Simon. Is it possible to know if the connection wasn't being made because of something on the Adobe side? I was definitely making requests starting yesterday around 4 PM EST.

[SimonATS]

no we can only go by what's logged, and if the 3rd party app cannot connect we cannot log it. There may be logs on Nintex side maybe.

The connection is done via oauth, so in Nintex you'll get prompted to sign in Adobe sign and provide Nintex the required permissions to access your Adobe Sign account. After than the secret access token are generated and used to make the required api calls. (nintex calling the adobe sign api)

it could maybe be that your trial account hadn't been fully verified perhaps, or maybe you used different Adobe sign credentials, or didn't go through the full oauth process. Or atl least that would have been my initial thoughts. I've not got access to Nintex cloud so don't know the full application context, though these oauth sign-ins are quite standard accross the board.