Connects directly to Apple with your team API key.
BUILDRELEASEAUTOMATE
Illustrative data. Every key can follow a different app or workflow.
THREE FOCUSED AREAS
From build to release.
Each key has its own selection and saves changes automatically. Four
actions show status and open details; Distribute Build and Run
Workflow send requests to Apple when you press their physical Stream
Deck keys.
01 / TEST
Builds & TestFlight
Build Status
Track the build number, version, processing or beta state, and
time until expiry.
Configure
Choose an app and platform, then follow the latest uploaded
build or select a fixed build.
On key press
Opens that build in TestFlight in your browser.
Distribute Build
Assign a fixed build to a TestFlight group.
Configure
Choose an app, platform, fixed build and destination group.
On key press
The first press previews the build and group. Press again
within eight seconds to assign it. Changing settings or
leaving the page cancels confirmation.
External builds must already meet Apple’s beta review and
compliance requirements. Assignment may notify testers.
02 / RELEASE
App Store & Releases
Release Status
See a version’s review or publication state, such as In review
or Available.
Configure
Choose an app and platform, then the newest version or a
fixed version. Newest means most recently created, including
drafts.
On key press
Opens the selected version in App Store Connect. Submit or
release the version from there.
Phased Release
See the rollout state and day, such as Active on day 3/7. No
rollout means the selected version has no phased release.
Configure
Choose an app, platform and version. Pin a version to keep
watching its rollout when a newer draft exists.
On key press
Opens that version in App Store Connect, where you manage
the rollout.
The day indicator describes the rollout schedule, not the
percentage of users who have installed the update.
03 / AUTOMATE
Xcode Cloud
Workflow Status
Follow the latest execution number, progress and completion
result of a workflow.
Configure
Choose an Xcode Cloud product and workflow.
On key press
Opens the latest run’s results in App Store Connect for app
products. Products without an app record open the Xcode
Cloud overview.
Run Workflow
Start a new Xcode Cloud execution on your chosen branch.
Configure
Choose an Xcode Cloud product, an enabled workflow and a
branch. Changes save automatically.
On key press
One press of the physical Stream Deck key sends the start
request. Accepted confirms Apple accepted it; follow its
progress and final result with
Workflow Status.
Duplicate requests to the same workflow and branch are blocked
while a request is in flight and for 15 seconds after
acceptance.
A GLANCE IS ENOUGH
Clear states. Deliberate actions.
Status keys refresh every minute while visible. Failed refreshes are
marked as stale, and the inspector explains what needs attention.
Tap a sample below to explore the look. These are illustrative
states, not a live connection.
GET CONNECTED
Your team. Your apps. Your keys.
01
Install the plugin
Open the .streamDeckPlugin package with Stream Deck
7.1 or later. Drag an action from App Store Connect Deck onto a
key.
02
Connect your Apple team
In the inspector, enter your Issuer ID, Key ID and the absolute
path to your team API key’s .p8 file. Keep the file
outside the plugin folder.
Apple’s API key guide ↗
03
Choose what each key follows
Select Test connection to confirm your key can
list apps, then choose the resources for each key using the
action guide above. Test connection does
not start builds. To launch a workflow, press its physical
Run Workflow key after configuration.
Your API key needs the appropriate resource access and roles. Xcode
Cloud workflows must already be configured. External TestFlight builds
must satisfy Apple’s review and compliance requirements.
Inspector controls
Reload resources updates the selection lists.
Refresh status requests a fresh status check.
These inspector controls do not distribute a build or start a
workflow.
Use Key label for a short display name. Long
names wrap on keys, and full selection names appear below lists
when needed. Complete key details remain in the inspector.
If a request’s outcome is unknown
Apple may have accepted it even if the response was lost. Check
App Store Connect before retrying, then select
Mark outcome as checked in the inspector. This
clears the local warning without starting another run or
distributing a build.
The warning follows the operation during the running plugin
session, including page or label changes. Another attempt requires
a separate key press after its cooldown.
DIRECT BY DESIGN
Your key stays on your machine.
The plugin reads your external signing key to authenticate directly
with Apple. Private-key contents and access tokens are never saved in
Stream Deck settings. Connection IDs, the key’s local path and per-key
selections are stored locally; settings are not encrypted credential
storage.
No telemetry or intermediary service. API responses are cached briefly
in memory. Pressing informational keys opens App Store Connect in your
browser.