AActionAppMySiteUpdated June 2026

What apps exist in this AppMySite workspace?

Short answer: You can list apps in AppMySite by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the AppMySite List Apps action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this action All 3 AppMySite actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Page page	number	Optional	–

Sample request

{
  "page": "{{trigger.page}}"
}

Returns

{
  "data": [
    {
      "id": 123,
      "name": "My Store App",
      "platform": "both",
      "build_status": "ready"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Apps.

What does the List Apps action do in AppMySite?

Returns every app configured in the workspace with current platform (iOS, Android, both) and bundle/package IDs. Useful for resolving app IDs at workflow-build time when scheduling rebuilds.

What inputs does List Apps require?

List Apps has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if AppMySite returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Apps support batch operations?

Yes. Run List Apps inside a Loop node to process arrays. TinyCommand handles AppMySite's rate limits automatically so you don't have to throttle manually.

More actions

Other AppMySite actions.

Action

Get Build Status

Returns the current state of an iOS or Android build — queued, building, completed, failed — plus artifact URLs and failure reasons when applicable. Poll for completion or configure the build's callback for push notification.