---
title: Auto-Submit to a Store
description: Automatically build and submit your app to the Apple App Store or Google Play on every push or tag with a Capawesome Cloud automation.
---

# Auto-Submit to a Store

Attach a [store destination](../app-store-publishing/destinations/index.md) to an automation and it will build **and submit** your app automatically — a complete Git → build → store pipeline that ends with the build on TestFlight or a Google Play track, without you opening Xcode or the Play Console.

## Set it up

1. Create a [store destination](../app-store-publishing/index.md) (Apple App Store or Google Play).
2. Create an [automation](trigger-on-tags.md) — tags (`v*`) are a natural fit for releases.
3. In the automation's [build settings](attach-build-settings.md), select the **Store destination**.

Now every matching tag (or branch push) builds your app and submits the artifact to the store — to TestFlight for Apple, or to the configured track for Google Play.

!!! tip "Pair with signing"

    Store submissions require a signed build. Attach the matching [signing certificate](../native-builds/certificates/index.md) to the same automation so the triggered build is signed correctly.

## What happens after submission

The automation's job ends once the build is submitted. The stores then run their own processing and review, so a finished submission means the build *reached* the store — not that it's live yet. Track the result on the [Deployments](https://console.cloud.capawesome.io/apps/_/deployments){:target="_blank"} page, just like a manual submission. See [Submit a Build](../app-store-publishing/submit-a-build.md#after-submitting) for what each store does next.

## Next steps

- [Submit a Build](../app-store-publishing/submit-a-build.md) — how submissions work and how to track them.
- [Trigger on tags](trigger-on-tags.md) — the recommended trigger for releases.
- [Auto-publish a Live Update](auto-publish-live-update.md) — the over-the-air equivalent for web builds.