Workflow External Trigger - use v1 api?

[caryharper (Caroline Harper)]

In ISC workflows - when you use the External Trigger and hit the New Access Token button - the url it gives you is

https://xxxxx.api.identitynow.com/beta/workflows/execute/external/:id

When will this be workflow trigger be updated to use the v1 api?

https://xxxxx.api.identitynow.com/workflows/v1/execute/external/:id

[trettkowski (Tyler Rettkowski)]

In my experience and I just double checked in my own developer and client tenants, the external trigger URL that gets generated is a /v2024/ URL that looks like this:
https://TENANT.api.identitynow.com/v2024/workflows/execute/external/:id

Still a good question since the UI should follow the new API versioning strategy. @tyler_mairose, is there a planned update date for WF’s to be switched to the new versioning strategy?

[caryharper (Caroline Harper)]

Yes - I just noticed that while doing some work on a new workflow

I’ve been busy today updating all my http operations in workflows to use v1 api calls, making sure they’re all switched over to use parameter storage, and updating email actions to use the new bcc field

[tyler_mairose]

@trettkowski

Still a good question since the UI should follow the new API versioning strategy. @tyler_mairose, is there a planned update date for WF’s to be switched to the new versioning strategy?

I just had a conversation with the PM for workflows about this. It’s on the list for the topic of discussion for their daily meeting tomorrow!

[trettkowski (Tyler Rettkowski)]

Sounds great. Thanks for the update!