---
title: "Setting up your first Automations workflow"
slug: "setting-up-your-first-automations-workflow"
description: "Click here to learn how to set up your first Automations workflow."
updated: 2026-10-22T20:59:45Z
published: 2026-10-22T20:59:45Z
canonical: "learn.allspice.io/setting-up-your-first-automations-workflow"
---

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

# Setting up your first Automations workflow

## **Setting up your first Automation**

Automations require the repository owner be an organization, not an individual. If you need to transfer a personal repository to an organization, please refer to [How to transfer ownership of a repo](/v1/docs/how-to-transfer-ownership-of-a-repo)

### Workflow files

Automations are defined in workflow.yml files.

Your repository needs one or more workflow files to trigger an Automation workflow run.

**Note:** you must put workflow files in `.allspice/workflows/` folder

### Creating your first workflow file

Follow along with this interactive demo to see how easy it is to create your first workflow.

[Allspice-Demos/My-first-action: A simple "hello world" demo to show how easy it is to create a workflow file and trigger an action. - My-first-action - Allspice Hub](https://demo.arcade.software/LyatW6jWd9NaUryXJPQx?embed&embed_mobile=tab&embed_desktop=inline&show_copy_link=true)

1. Create a file in your repo `.allspice/workflows/hello-world.yml`
  1. Select `repository→Add File→New File`

![https://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/image(73).png](https://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/image(73).png)

1. Make sure the file is saved to /.allspice/workflows/your-file-name.yml ![new allspice file.gif](https://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/new%20allspice%20file%282%29.gif)
2. Copy the following example workflow into the web text editor:

```
name: Workflow-hello-world

on:
  push:
  issues:
    # Trigger on issue open, close, or reopen
    types: [opened, closed, reopened]

jobs:
  Job-Hello-World:
    runs-on: ubuntu-latest
    steps:
      - name: "Print Hello World 🔎"
        run: echo "Hello World"
```

1. After you have pasted the code block, click the “Commit Changes” button to commit the workflow file to the repository.

![paste workflow.gif](https://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/paste%20workflow%284%29.gif)

### Trigger your first Automation

The example above should trigger an Automation as soon as you commit the files.

This workflow specifies that Automations will trigger on `push` or `issue open/close`

To trigger this Automation again do one of the following:

- Push changes to the repo
- Open/New issue (This is the easiest to check)
- Close an issue

### View Automations results

Visit the Automations tab and see the Automations result. [] Add gif

Click on a workflow run. Explore the run by clicking on the Step toggles.

![view action runner clean.gif](https://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/view%20action%20runner%20clean%281%29.gif)