In a large Alteryx Server enterprise—think hundreds or even tens of thousands of workflows—new content is published every day. As an admin, you want to ensure you have access to every workflow: to audit schedules, tweak logic, or reassign ownership. But Server’s subscription siloing means you only see content in the subscriptions you belong to. Manually switching through dozens or hundreds of subscriptions in the UI? That can take days.

Welcome to Subscription Hopping:

a way to automate hopping from one studio to the next, grab newly published workflows, add them to your collection, and keep your admin toolbox up to date—fast. But it's not limited to just this example.

Let me explain

Why is this needed

In Alteryx Server, every user and their workflows are scoped to a single subscription (formerly studios), and (some) API calls against content will only succeed if your account belongs to that subscription. This subscription‐level permissioning effectively creates isolated silos, preventing even an admin from programmatically enumerating or modifying workflows across all studios in one pass.

No single user can make changes to all content, even admins

What is Subscription Hopping?

Subscription Hopping uses API calls in sequence to make changes to any piece of content:

1. GET /v3/workflows to retrieve every workflow (or any other piece of content) and its ownerId.

2. GET to map each ownerId to their subscriptionId—either by calling /v3/subscriptions/{subId}/users or /v3/users/{userId}.

3. PUT /v3/subscriptions/{subscriptionId}/users to move your service account into that subscription.

Once ‘inside’ that studio, you call POST /v3/collections/{collectionId}/workflows for each workflow (or similar with other content types) in that subscription, adding it to a centralised collection (or any other API call on content). Then you hop to the next subscription and repeat until every subscription—and every workflow—has been processed.

Prerequisites & Setup

Here’s what you need to set this up yourself:

• A service-account user with the Curator role, that owns no content*.

• Its API Access Key & Secret (from Gallery → User Settings).

• Alteryx Server 2024.2+ (for the Subscriptions endpoint).

• A scripting tool like python or just using Alteryx Designer itself to make the series of API calls and process the data

\* the service account should own no content because if their subscription is changed that will also move their content with them if they are the last user in that subscription.