tanitall / actionsflow

The best Zapier/IFTTT free alternative for developers to automate your workflows based on Github actions

Home Page:https://actionsflow.github.io/docs

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Project logo

Actionsflow

Actionsflow Build Status GitHub Issues GitHub Pull Requests License

Actionsflow - Automate Workflows -  IFTTT/Zapier free alternative, based on Github Actions | Product Hunt

If you like Actionsflow, please vote for us on Product Hunt


The free IFTTT/Zapier alternative for developers to automate your workflows based on Github actions

πŸ“ Table of Contents

😁 About

Actionsflow helps you to automate workflows, it's a free IFTTT/Zapier alternative for developers. With Actionsflow, you can connect your favorite apps, data, and APIs, receive notifications of actions as they occur, sync files, collect data, and more. We implemented it based on Github actions, and you use a YAML file (The configuration format is the same as Github actions) to build your workflows. If you have already written a Github actions file, it's very easy to define an Actionsflow workflow file, and you can use any Github actions as your job's steps.

You can see core concepts of Actionsflow at here.

πŸ”₯ Features

πŸŽ“ Document

Full documentation for Actionsflow lives on the website.

You can also view it at Github if you prefer.

πŸ‘€ How Actionsflow worked

Actionsflow uses Github Actions' repository_dispatch event and per 5 minutes' scheduled event to run Actionsflow triggers for getting result items, and do some caching and deduplication works, then generating a standard Github actions workflow file with the trigger result, then calling act(a tool for running GitHub Actions locally) to run the built workflow files.

Learn more about How Actionsflow worked, please see Core Concepts of Actionsflow.

🏁 Getting Started

Build an Actionsflow workflow is a three-step process:

  1. Create a public Github repository by this link.

    A typical Actionsflow repository structure looks like this:

    β”œβ”€β”€ .github
    β”‚   └── workflows
    β”‚       └── actionsflow.yml
    β”œβ”€β”€ .gitignore
    β”œβ”€β”€ README.md
    └── workflows
    β”‚   └── rss.yml
    β”‚   └── webhook.yml
    └── package.json
  2. Define your workflow file at workflows directory

    A typical workflow file rss.yml looks like this:

    on:
      rss:
        url: https://hnrss.org/newest?points=300
    jobs:
      ifttt:
        name: Make a Request to IFTTT
        runs-on: ubuntu-latest
        steps:
          - uses: actionsflow/ifttt-webhook-action@v1
            with:
              event: notice
              key: ${{ secrets.IFTTT_KEY }}
              value1: ${{on.rss.outputs.title}}
              value2: ${{on.rss.outputs.contentSnippet}}
              value3: ${{on.rss.outputs.link}}

    For more information about the Actionsflow workflow file, see the Actionsflow workflow reference.

    You can explore Triggers List or Awesome Actionsflow Workflows to get more inspired.

  3. Commit and push your updates to Github

Then, Actionsflow will run your workflows as you defined, you can view logs at your repository actions tab at Github

For more information about quick started, see Getting Started

πŸŽ“ Learn More

Full documentation for Actionsflow lives on the website.

πŸ‘ How to Contribute

Whether you're helping us fix bugs, improve the docs, or spread the word, we'd love to have you as part of the Actionsflow community! πŸ’ͺπŸ’œ

Check out our Contributing Guide for ideas on contributing and setup steps for getting our repositories up and running on your local machine.

βœ‹ Authors

See also the list of contributors who participated in this project.

πŸ“ License

Licensed under the MIT License.

About

The best Zapier/IFTTT free alternative for developers to automate your workflows based on Github actions

https://actionsflow.github.io/docs

License:MIT License


Languages

Language:TypeScript 84.0%Language:JavaScript 12.9%Language:Handlebars 3.1%