AActionAppMySiteUpdated September 2026

How do I check an AppMySite build's state?

Short answer: You can get build status in AppMySite by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the AppMySite Get Build Status action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Build Status in AppMySite — start free All 3 AppMySite actions

Get Build Status in AppMySite — start free

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
App ID app_id	string	Required	The App ID assigned by Appmysite. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.
Build ID build_id	string	Required	–

Sample request

{
  "app_id": "{{trigger.app_id}}",
  "build_id": "{{trigger.build_id}}"
}

Returns

{
  "status": "ready",
  "build_id": "bld_abc",
  "completed_at": "2026-05-12T15:30:00Z",
  "download_url": "https://cdn.appmysite.com/builds/bld_abc.apk"
}

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

Triggered by

Apps that pair well as the trigger for Get Build Status.

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 Get Build Status.

What does the Get Build Status action do in AppMySite?

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.

What inputs does Get Build Status require?

Required: App ID, Build ID. Every input accepts a static value or a variable from any upstream node in your workflow.

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 run history shows the failed step with its input and the error message AppMySite returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Build Status support batch operations?

Run Get Build Status inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within AppMySite's rate limits.

More actions

Other AppMySite actions.

Action

List Apps

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.

Action

Trigger App Build

Starts a new build for a specific app on iOS, Android, or both. Builds take 10-30 minutes per platform. The common automation: WordPress content/plugin update → trigger rebuild so the next App Store submission has the latest assets bundled.

Get Build Status in AppMySite — start free