> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testyourappnow.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Started: 5-Minute Quickstart

> Create your first application flow, run it against production, and get alerted the instant it breaks — all in under five minutes, no code required.

This guide walks you through everything you need to go from a blank workspace to a monitored production flow. By the end, you'll have a real flow running against your live application and alerts set up so you know the instant something breaks — all without writing a single line of test code.

<Steps>
  <Step title="Sign up or log in">
    Go to [testyourappnow.com](https://testyourappnow.com) and create your free account, or log in if you already have one. No credit card is required to get started. Once you're in, you'll land on your dashboard where all your workspaces and flows live.
  </Step>

  <Step title="Create a workspace">
    Click **New Workspace** and give it a name that maps to your product or team — for example, `acme-production` or `growth-team`. Workspaces keep your flows, schedules, and alert settings organized in one place. You can create multiple workspaces if you manage more than one application or environment.
  </Step>

  <Step title="Build your first flow">
    Inside your workspace, click **New Flow** and give it a descriptive name like `User Signup` or `Checkout Completion`. Then add steps using the visual flow builder:

    | Step type               | What it does                                                |
    | ----------------------- | ----------------------------------------------------------- |
    | **Visit URL**           | Navigate to a page in your production app                   |
    | **Fill form field**     | Type into an input using a CSS selector or label            |
    | **Click button**        | Click any element by text, label, or selector               |
    | **Assert text visible** | Confirm that expected text appears on the page              |
    | **Wait**                | Pause for a condition or a fixed duration before continuing |

    String these steps together to mirror exactly what a real user does. For example, a signup flow might visit your homepage, click **Get Started**, fill in an email and password, click **Create Account**, and then assert that the dashboard heading is visible.

    <Tip>
      Start with the single most important journey in your app — the one that, if broken, would cost you the most users or revenue. A signup funnel or checkout flow is usually the right place to begin.
    </Tip>
  </Step>

  <Step title="Run the flow">
    Click **Run** to execute your flow immediately against your production URL. You'll see a live step-by-step trace as each action is performed in a real browser. Steps turn green as they pass. If any step fails, it turns red and a screenshot is automatically captured so you can see exactly what the browser encountered at the moment of failure.

    A completed run gives you a full pass/fail result with timing data for every step, shareable via a direct link.
  </Step>

  <Step title="Set up monitoring">
    To keep your flow running automatically, click **Schedule** and choose a recurrence interval. Common options include:

    * Every **15 minutes** for high-stakes flows like checkout or login
    * Every **hour** for secondary journeys like profile updates or onboarding steps
    * Every **day** for lower-priority or infrequently-changed paths

    Scheduled runs execute in the background and appear in your run history. You can pause or adjust the schedule at any time.
  </Step>

  <Step title="Set up alerts">
    Go to **Workspace Settings → Notifications** and connect your preferred alert channel:

    * **Slack** — paste your webhook URL and choose the channel to post failure alerts
    * **Email** — add one or more email addresses to notify when a flow fails
    * **Webhook** — send a POST request to any URL so you can route alerts into PagerDuty, Linear, or any other tool

    TYAN sends an alert the moment a scheduled run fails and another when it recovers, so your on-call rotation always has the full picture.
  </Step>
</Steps>

<Note>
  Your API key is available under **Workspace Settings → API**. Use it to trigger flow runs directly from your CI/CD pipeline so every deployment is automatically verified before it goes live. See the [API Reference](/api/overview) for the full endpoint documentation.
</Note>

<CardGroup cols={2}>
  <Card title="How It Works" icon="gears" href="/how-it-works">
    Understand how flows are executed in production and how monitoring is handled.
  </Card>

  <Card title="CI/CD Integration" icon="infinity" href="/integrations/ci-cd">
    Plug TYAN into GitHub Actions, GitLab CI, CircleCI, and more.
  </Card>
</CardGroup>