---
title: Submit Automatically After a Build
description: Submit native builds to the App Store, Google Play, Huawei AppGallery, or Firebase App Distribution after every build using Capawesome Cloud Automations.
canonical_url: https://capawesome.io/docs/cloud/automations/auto-submit/
---

# Submit Automatically After a Build

You can submit to a store automatically on every build by attaching a [destination](destinations/index.md) to an [automation](../automations/index.md). When a Git event triggers a build, Capawesome Cloud builds the app and submits the resulting artifact to the destination — a complete Git → build → store pipeline.

## Set it up

1. Create a [destination](destinations/index.md) for the store you're targeting.
2. Create an [automation](../automations/index.md) with the trigger you want (for example, a `v*` tag for releases).
3. In the automation's build settings, select the **destination** to submit to.

Now every matching push or tag builds your app and submits it automatically. See [Auto-submit to a store](../automations/auto-submit.md) for the full walkthrough.

Automations can't provide [release notes](release-notes.md), and an App Store Connect destination with [beta groups](submit-for-app-review.md#distribute-to-beta-groups) requires them, so submit to such a destination with the CLI instead.

## Recommended pattern

A common setup is to submit release tags to TestFlight or an internal track:

- Trigger on tags matching `v*`.
- Attach the signing certificate and the store destination.

This keeps releases deliberate (they ship when you create a tag) while removing all the manual upload steps.

## Next steps

- [Auto-submit to a store](../automations/auto-submit.md) — the full walkthrough.
- [Submit a build](submit-a-build.md) — submit a build manually.
- [Add release notes](release-notes.md) — not available for automations.