---
modificationDate: July 13, 2026
title: Get started with EAS Workflows
description: Learn how to use EAS Workflows to automate your React Native CI/CD development and release processes.
---

<AgentInstructions>

## Submitting Feedback

If you encounter errors, misleading or outdated information, report it so Expo can be improved:

Preferred command:
npx --yes submit-expo-feedback@latest --category docs --subject "/eas/workflows/get-started/" "<actionable feedback>"

Direct HTTP fallback:
curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/eas/workflows/get-started/","feedback":"🤖 Agent feedback for docs: <specific, actionable description> (<model>, <harness>)"}'

Only submit when you have something specific and actionable to report. Try to give the most context.

## Navigation

When answering a related or follow-up question, fetch the relevant page below as Markdown (.md) instead of guessing; use llms.txt for the full map.

You are here: EAS > EAS Workflows
Pages in this section:
- [Introduction](https://docs.expo.dev/eas/workflows/introduction.md)
- [Get started](https://docs.expo.dev/eas/workflows/get-started.md) (this page)
- [Pre-packaged jobs](https://docs.expo.dev/eas/workflows/pre-packaged-jobs.md)
- [Syntax](https://docs.expo.dev/eas/workflows/syntax.md)
- [Environment variables](https://docs.expo.dev/eas/workflows/environment.md)
- [Automating EAS CLI commands](https://docs.expo.dev/eas/workflows/automating-eas-cli.md)
- [REST API](https://docs.expo.dev/eas/workflows/rest-api.md)
- [Troubleshooting](https://docs.expo.dev/eas/workflows/troubleshooting.md)
- [Limitations](https://docs.expo.dev/eas/workflows/limitations.md)
Full documentation tree: [llms.txt](https://docs.expo.dev/llms.txt)

</AgentInstructions>

This documentation is available as Markdown for AI agents and LLMs. See the [full Markdown index](/llms.txt) or append .md to any documentation URL.

# Get started with EAS Workflows

Learn how to use EAS Workflows to automate your React Native CI/CD development and release processes.

This page walks you through creating your first EAS Workflow: development builds of your app for Android emulators, iOS simulators, physical devices, and production builds for the app stores.

## Get started

#### Prerequisites

##### Sign up for an Expo account

You'll need to [sign up](https://expo.dev/signup) for an Expo account.

##### Create a project

You'll need to create a project with the following command:

```sh
# npm
npx create-expo-app@latest --template default@sdk-57

# yarn
yarn create expo-app --template default@sdk-57

# pnpm
pnpm create expo-app --template default@sdk-57

# bun
bun create expo --template default@sdk-57
```

##### Install EAS CLI

You'll need to install EAS CLI to create and run workflows:

```sh
npm install -g eas-cli
```

Run the following command to create a workflow that creates development builds for Android and iOS:

```sh
eas workflow:create --template build
```

Then follow the prompts and the `[Action requested]` steps when they appear. The command generates a workflow file at **.eas/workflows/build.yml** and sets up your project for building on EAS.

Run the workflow with the following command:

```sh
eas workflow:run .eas/workflows/build.yml
```

Once you do, you can watch your workflow run on your project's [workflows page](https://expo.dev/accounts/%5Baccount%5D/projects/%5BprojectName%5D/workflows).

When the builds finish, you can install them on your physical devices via the website UI. You can also run the following commands to install the latest builds on your Android Emulator and iOS Simulator:

```sh
eas build:run -p android --latest
```

```sh
eas build:run -p ios -e development-ios-simulator --latest
```

Then, start a development server so the development build can load your app:

```sh
npx expo start
```

## Create production builds

When you're ready to build for the app stores, generate a release workflow with the `deploy` template:

```sh
eas workflow:create --template deploy
```

This sets up your project for automated deployment: it configures EAS Build and EAS Update and sets your app identifiers, then writes a complete release workflow to **.eas/workflows/deploy.yml**.

When you run it, the workflow fingerprints your project, then builds and submits a new production build when there are native changes so they're ready for submission, or publishes an over-the-air update when a matching build already exists, which will be sent to your users immediately.

For a walkthrough of the generated workflow, see the [Deploy to production example](/eas/workflows/examples/deploy-to-production.md).

If you only need to create production builds, use a workflow with a `build` job for each platform:

```yaml
name: Create Production Builds

jobs:
  build_android:
    type: build # This job type creates a production build for Android
    params:
      platform: android
      profile: production
  build_ios:
    type: build # This job type creates a production build for iOS
    params:
      platform: ios
      profile: production
```

This workflow uses the `production` profile from your **eas.json**. Production builds require app signing credentials. Set them up for each platform with the following commands:

```sh
eas credentials:configure-build -p android -e production
```

```sh
eas credentials:configure-build -p ios -e production
```

Then, run the workflow:

```sh
eas workflow:run .eas/workflows/create-production-builds.yml
```

## More

### Automate workflows with GitHub events

You can trigger a workflow by pushing a commit to your GitHub repository. You can link a GitHub repo to your EAS project with the following steps:

-   Navigate to your project's [GitHub settings](https://expo.dev/accounts/%5Baccount%5D/projects/%5BprojectName%5D/github).
-   Follow the UI to install the GitHub app.
-   Select the GitHub repository that matches the Expo project and connect it.

Then, add the [`on` trigger](/eas/workflows/syntax.md#on) to your workflow file. For example, if you want to trigger the workflow when a commit is pushed to the `main` branch, you can add the following:

```yaml
name: Create Production Builds

on:
  push:
    branches: ['main']

jobs:
  build_android:
    type: build
    params:
      platform: android
      profile: production
  build_ios:
    type: build
    params:
      platform: ios
      profile: production
```

### Trigger workflows from App Store Connect events

You can also trigger workflows from App Store Connect events using [`on.app_store_connect`](/eas/workflows/syntax.md#onapp_store_connect).

Before using App Store Connect triggers, configure your App Store Connect connection in EAS dashboard:

-   Open EAS dashboard and select your project.
-   Navigate to **[Project settings > General > Connections](https://expo.dev/accounts/%5Baccount%5D/projects/%5Bproject%5D/settings)**.
-   Connect your App Store Connect app.

Example workflow:

```yaml
name: React to App Store Connect events

on:
  app_store_connect:
    app_version:
      states:
        - ready_for_review
        - waiting_for_review

jobs:
  send_slack_notification:
    type: slack
    environment: production
    params:
      webhook_url: ${{ env.SLACK_WEBHOOK_URL }}
      message: 'App version is ready for review or waiting for review.'
```

The example reads the webhook URL from a `SLACK_WEBHOOK_URL` [environment variable](/eas/environment-variables/manage.md#manage-environment-variables). [Create it](https://expo.dev/accounts/%5Baccount%5D/settings/environment-variables) in the `production` environment before running the workflow.

### VS Code extension

Download the [Expo Tools VS Code extension](https://marketplace.visualstudio.com/items?itemName=expo.vscode-expo-tools) to get descriptions and autocompletions for your workflow files.

> Got feedback or feature requests? Send us an email at [workflows@expo.dev](mailto:workflows@expo.dev).