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

# Quickstart

> Set up Workflow Machine, connect your first app, and publish a simple workflow.

## What you will do

This quickstart walks you through the shortest path to a working workflow:

1. Sign up and onboard.
2. Connect apps.
3. Create a workflow via prompting.
4. Test the workflow.
5. Publish it and verify the first run.

If this is your first time using Workflow Machine, keep the first workflow small. A simple trigger and two or three steps is enough to learn the product.

## Before you start

Choose one outcome you want to automate. Good first examples include:

* Send a Slack message when a webhook is received
* Run a scheduled workflow that summarizes updates
* Collect data from one app and write it into another

You will also want access to at least one app account you can connect, such as Slack, Gmail, Notion, Google Sheets, or Stripe.

## Step 1: Open Workflow Machine

After signing in, you will land in the main product area. The most important sections for a new user are:

* [**Home**](https://app.workflowmachine.com/) for entry points and templates
* [**Templates**](https://app.workflowmachine.com/templates) for prebuilt workflow ideas
* [**Connections**](https://app.workflowmachine.com/connections) for app authentication
* [**Workflows**](https://app.workflowmachine.com/workflows) for creating and editing automations
* [**Settings**](https://app.workflowmachine.com/settings) for profile, subscription and usage information

If you are not sure where to begin, use a template. If you want to understand the product from first principles, start from a blank workflow.

## Step 2: Connect your first app

Before many steps can work, you need a connection.

Open [**Connections**](https://app.workflowmachine.com/connections) and create a connection for the app you plan to use. Depending on the integration, this may use OAuth or API keys.

Good first connection choices:

* Slack for notifications
* Gmail for inbox workflows
* Notion for creating or updating pages
* Google Sheets for logging records

Once a connection is created, you can reuse it across multiple workflows.

## Step 3: Create a workflow

Under [**Home**](https://app.workflowmachine.com/):

* Describe your use case
* Send the prompt

After you send the prompt, Workflow Machine uses AI to work through the workflow setup and assemble the trigger and steps needed for your use case. This gives you a starting workflow structure that you can review, refine, and test before publishing.

## Step 4: Review and refine the workflow

Once the workflow draft is created, review it in the editor and make any changes you want. You can update the trigger, adjust the step order, edit field mappings, remove steps that are not needed, or add new ones yourself.

The workflow does not need to stay exactly as AI generated it. You can manually shape it until it matches the process you actually want to run.

For a first workflow, keep the structure simple and focus on one clear outcome. After the basic flow looks right, move on to testing.

## Step 5: Test before publishing

Before publishing, run a test.

You can test the workflow in different ways depending on what you want to validate:

* Test a single trigger
* Test a single step
* Test a full run using a specific trigger

Testing helps you:

* Check whether the trigger is configured correctly
* Confirm that connected accounts work
* Inspect step outputs
* Catch mapping mistakes before the workflow goes live

If something looks wrong, you can also use AI to help diagnose the issue and suggest what to adjust in the workflow.

If a test fails, inspect the step that failed first. Most early problems come from:

* Missing connection setup
* Required fields not being filled in
* Data shape mismatches between steps
* A trigger that was configured differently than expected

## Step 6: Publish and verify the first run

Once the test passes, publish the workflow.

After publishing:

* Trigger it with a real input
* Open the run history
* Verify that each step completed as expected

This matters because a passing test is helpful, but a real run confirms that your trigger, connection, and downstream actions all behave correctly in normal conditions.

## Recommended first workflow patterns

If you want something easy to prove out quickly, start with one of these:

* Webhook in, Slack message out
* Schedule in, AI summary out
* Form response in, spreadsheet row out
* Email in, AI classification plus notification out

Each pattern teaches one core part of the product without requiring a large setup.

## Next steps

<Columns cols={2}>
  <Card title="Take the product tour" icon="map" href="/getting-started/product-tour">
    Learn how the main areas of the app fit together.
  </Card>

  <Card title="Build your first workflow" icon="diagram-project" href="/getting-started/first-workflow">
    Follow a more detailed workflow creation guide.
  </Card>

  <Card title="Connect your first app" icon="plug" href="/getting-started/first-integration">
    Learn how connections work and how to avoid common auth issues.
  </Card>

  <Card title="Understand workflows" icon="book" href="/concepts/workflows">
    Learn the core concepts behind triggers, steps, runs, and versions.
  </Card>
</Columns>
