In case you missed the announcement: The Alteryx One Fall Release is here! Learn more about the new features and capabilities here
ACT NOW: The Alteryx team will be retiring support for Community account recovery and Community email-change requests after December 31, 2025. Make sure to check your account preferences in my.alteryx.com to make sure you have filled out your security questions. Learn more here
Start Free Trial

Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.
SOLVED

Azure DevOps pipeline to deploy workflows from git repo

pvd
7 - Meteor

Hello, 

 

We are trying to deploy package files (.yxzp) from git repo to Alteryx gallery using the admin endpoint POST /api/admin/v1/workflows as described in the article here . We were able to successfully do this part. Our use case requires us to search for the workflow by name and retrieve its appId using the subscription endpoint  GET /v1/workflows/subscription/ and then trigger these workflows using subscription endpoint POST /v1/workflows/{appId}/jobs/.

 

When we manually deploy these workflows, we usually replace the old workflow that has same name with the new from the gallery UI. Is there an endpoint (admin  endpoint preferably) to do similar action? or is there an admin endpoint to delete a workflow?

 

Appreciate any guidance on this. Thanks.

3 REPLIES 3
cam_w
11 - Bolide

Hi @pvd !

 

Perhaps the SourceId argument of the POST endpoint is what you're looking for:

 


This is the Source environment appId of the workflow to be migrated. If a workflow with the same sourceId already exists, this will replace that workflow in the target environment. Otherwise, a new workflow will be generated.

 

(Send empty string "" if you do not wish to specify an appID)

I found this in Step 3 of the 'Migrate Workflows' instructions here -- Workflow Migration.

 

Regards,

Cameron

pvd
7 - Meteor

Thanks much @cam_w for the suggestion. Since our workflows are in a repo and our need isn't exactly migrating from one environment to another, we ended up using a unique value for SourceId (workflowName+workflowOwner) in all environments. 

ChrisMasonTampaBay
7 - Meteor

@pvd Can you share an example of the code you used to get from the repo to the gallery? I know it's not ending up in the gallery as you want it.