AActionAppMySiteUpdated May 2026

What apps exist in this AppMySite workspace?

Short answer: Drop the "AppMySite → List Apps" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

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.

Triggered by

Apps that pair well as the trigger for List Apps.

Any of these apps can fire this action as part of a workflow.

Google Sheets → AppMySite

2 Google Sheets triggers

HubSpot → AppMySite

18 HubSpot triggers

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. Tiny Command handles AppMySite's rate limits automatically so you don't have to throttle manually.

More actions