Alteryx Server Ideas

Hello,
One of the frustrations we have faced in using Alteryx Gallery is the question "How do we set up many users with their respective collections easily?".

If we take for an example, the scenario where a company has 300 potential users of the gallery, who are all going to login and generate a report based on their department.
In order for them not to be able to generate the reports on other departments, the report generation workflows are put into collections. The current solution to this (atleast on SAML Authentication), is for a user to sign up, and then a Curator to assign them to their given collection. This is fine for small scale solutions, but the purpose of server is allowing for large scale deployment and automation of tasks, and this is far from ideal for a larger company.

If the server is setup on Windows Authentication, the users are able to be categorised within the Windows Active Directory, and then these groups (which may pre-exist) are able to be added to the gallery straight from the AD (see here), however this is not a feature within SAML Authentication.

From my knowledge, SAML Authentication should easily allow for this functionality, and it works very similar to Windows Active Directory. I mentioned this on a call with a Customer Support Engineer, and he explained that this wasn't part of his known roadmap for the Alteryx Gallery. 

I do believe this to be an extension of a current post on the Alteryx forum, however, this details opening the API to allow for this on an API level, however I would also suggest for this to be integrated within Alteryx Gallery, as not all users are experienced with using, or building tools around, the API.
 
Cheers,
TheOC

There are two key APIs that we use for extracting canvasses for governance & surveillance:

- the Workflows API which lists all canvasses on the server;

-  and the API call which returns a packaged version of the application by AppID

Unfortunately - when we query for all workflows to get the first list - there is no flag to indicate that a subset of these are actually deleted.   The result is that you need to make the second call to find this out which is wasteful.

Please add a "deleted" flag to the Workflows API so that we can identify which applications have been deleted without having to call the specific App ID post.

CC: @jalvarezv

We are taking an incremental feed of all server canvasses in order to look for patterns - however there is no option on the server admin APIs (the Workflow API specifically) that allow you to filter by date.

Please can you add to this API to allow API users to specify an upload/updated date filter and only take items after this date.

cc: @jalvarezv

Our corporation has multiple private studios set up (depending on various teams within our infrastructure); when we provide a user access to one private studio, they cannot be part of another private studio (to update/add/remove their workflows); they can view/see them within the collections, but cannot action them.

If possible within the Alteryx Server interface, could users be added to multiple/different private studios (and be authorized for all), and have a toggle that would allow them to switch back and forth? This would alleviate a lot of our issues we have with users reporting/being involved with multiple teams (who are requiring access to different private studios).

We've confirmed with @KevinP that the Alteryx Gallery / Server API does not currently support downloading canvasses in unzipped data-stream format. (https://community.alteryx.com/t5/Alteryx-Server-Discussions/Server-API-Download-packages-for-surveil...)

Please can we add an API end-point that allows the following:

• Connect to the gallery and download a canvas; along with all of its sub-canvasses and helper macros. 
• Format required:
  • Plain XML (not zipped)
  • Provided in a data stream so that we can perform analytics and surveillance on this data
  • Fields required
    
    • Canvas filename
    • Application ID
    • Some unique ID per macro / sub-macro
    • XML for the canvas
    • Last run date
    • Last changed date
    • Environment (this is important once Server actually allows a Dev; UAT; Prod progression cycle - so we can see which environment people are in)
    • User details who uploaded
    • User details who are marked as the owners
    • Any other meta-tags on the canvas (important once server allows for meta-tagging of canvasses for categorisation)

Current API only allows this to be downloaded to a zipped file; which then needs to be unzipped; and then loaded back into a data stream.

Thank you

S

CC: @revathi @AshwiniChezhiyan @LizaNemchynova 

Hello,

Tableau has a nice Postman Collection available... it's really easy to use since you can download or forkt it on Postman and all you have to do is to write the variable values.

I would like the same thing but for Alteryx.

Best regards,

Simon

Hello everyone,

I created before a post about managing chained workflows using the API.
After reaching out the support, it turns out to be impossible, which is unfortunate.

So I post this idea here, in case anyone is needing it too.

Feels free to ask me details if needed.

Thanks.

Enhance the v3 APi for workflows - /v3/workflows/{workflowid} - to get information for first n versions and/or last n versions of the workflow.

The problem

The current API will return information about all versions of a workflow. If a workflow has several hundred versions, you'll get all version information, much of which is useless and can take a long time to process.

The (potential) solution

Allow the API to take parameters like first n versions and last n versions. This will allow the API to return only the respective version information that would be of interest to the user.

The red box in the image is the enhancement in swagger:

My team utilizes the Gallery API extensively and have found that we have processes that the API has listed as actively running, but cannot be found via the Controller's GUI.  As a gallery artisan, I can call flows via API, but cannot cancel these executions unless I reach out to the administrator group to kill them manually. 

It would be extremely helpful to add an endpoint with the ability to submit a specific job GUID and have the server/controller kill the execution of that flow and clear up the server capacity.  This could then be scheduled on a regular basis as a maintenance  task to keep the server clean.

Thanks

It might be helpful to be able to use an API to call and pass parameters to/from an Alteryx App or Workflow on an Alteryx Server.  Then a user could use a  browser or another application to call an Alteryx app/workflow.

We have a usecase where we want to check how often a workflow runs via the API so we can automate the consumption reporting we do internally. Right now the API only reads out workflows that were scheduled using said API. That doesn't make a whole lot of sense. Enabling it to also read out all the other workflows would really make this a powerful feature for us and I suspect others.

Today the v3 api requires curator access.  V3 has Getters that should work for users with API permission.  The Getter should return the objects that user has access to.   Example:   GetCredentials for a normal user with API access should return credentials that the user has access to.  Today they get a 401 auth error.

We don't want to make these users curators just to let them access the V3 api.

The full question tree is not visible within the JSON object returned when requesting the 'Questions' in the .yxwz file on the Alteryx Server. There are nested questions that are visible but there is no indication that they are nested, missing label groups, tabs and no indication whether a question should be shown or hidden. This is limiting.

A full question tree in the JSON would allow for dynamic interpretation of the 'Questions' in the .yxwz file as structured through the Interface Designer.

Regards,

Ben

Alteryx Server API should be allowed to publish the workflow in the gallery. 

During a recent project, I explored the Alteryx Server Download a Workflow Package API Endpoint, which includes an optional versionId parameter. The documentation suggests that this parameter should allow users to retrieve specific, prior versions of a workflow package by supplying the appropriate version ID. However, in practice, I found that regardless of which valid prior version ID was provided, the API always returned the current published version of the workflow.

This behavior presented a challenge for our automation use case, where we aimed to implement version control and retrieval solely through Alteryx Server, rather than relying on external tools like Git. After thorough testing and validation, I shared these findings with Zach Hamilton and Marty Moravec at Inspire 2025, who were able to confirm the behavior.

I appreciate the continued enhancements and support the Alteryx team provides for the Server platform and its APIs. Resolving this issue would greatly benefit users who depend on robust version management and automation capabilities within Alteryx Server. Thank you for considering this feedback, and I look forward to future improvements in this area.

The current Enterprise Utility Workflow does not have a match/look-up in place between the two environments for user ID's.  Thus, the migration workflow doesn't work without adding in a couple extra API calls.  When we upgrade to a new version of the utility, I have to add this back in. 

It would be nice if the workflow would come with this already configured.

You cannot currently upload a new workflow and specify your own workflow_id GUID.  This would be useful for systematic workflows that need to be referenced in code.  Currently, you either to search for a workflow by name, but you are not guaranteed it a workflow instance you uploaded.  This would be helpful for server and workflow administration.

Given there are multiple api versions.  I need a way to call the api and get the server version so I can make the correct API call or construct code logic which provides the user code requirement based on the versions features or limitations.

I propose a api call ../getserverinfo/ that returns server metadata like version, default worker thread count, and default memory allocation.

There is currently not a way to call the API and find out the calling user.  For instance, if I have a user API key and secret, I  to return the rest of the user info for the calling user or who is calling the api.  I propose a api call like ../user/whoami