The free Zapier/IFTTT alternative for developers to automate your workflows based on Github actions
The free IFTTT/Zapier alternative for developers to automate their workflows based on GitHub actions, option to run self-hosted without GitHub as well
📝 Table of Contents
😁 About
Actionsflow helps you 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 to build your workflows. The configuration format is the same as Github actions, which makes it easy for you to get going if you've explored Github actions before. You can also use any Github actions as your job's steps.
You can learn more about the core concepts of Actionsflow here.
If you want a lighter, simpler workflow that doesn't rely on Github Actions, consider Denoflow, another workflow tool made by me, based on Deno with YAML , you can try it at an online playground
🔥 Features
🎓 Documentation
Full documentation for Actionsflow lives on the website.
You can also view it on Github if you prefer.
👀 How Actionsflow works
Actionsflow uses Github Actions' repository_dispatch
event and scheduled
event every 5 minutes to run Actionsflow triggers. Those triggers generate result items, which are cached and deduplicated, generating a standard Github actions workflow file with the trigger result. Finally, the workflows are executed using act (a tool for running GitHub Actions locally).
To learn more about how Actionsflow works, please see Core Concepts of Actionsflow.
🏁 Getting Started
For self-hosted version please see here
Create a public Github repository by using this link.
A typical Actionsflow repository structure looks like this:
├── .github │ └── workflows │ └── actionsflow.yml ├── .gitignore ├── README.md └── workflows │ └── rss.yml │ └── webhook.yml └── package.json
Uncomment .github/workflows/actionsflow.yml
schedule event
on: schedule: - cron: "*/15 * * * *"
Note: To prevent abuse, by default, the schedule is commented, please modify the schedule time according to your own needs, the default is once every 15 minutes. Learn more about schedule event, please see here
Create your workflow files inside the workflows
directory
A typical workflow file rss.yml
looks like this:
on: rss: url: https://hnrss.org/newest?points=300&count=3 jobs: request: name: Make a HTTP Request runs-on: ubuntu-latest steps: - name: Make a HTTP Request uses: actionsflow/axios@v1 with: url: https://hookb.in/VGPzxoWbdjtE22bwznzE method: POST body: | { "link":"${{ on.rss.outputs.link }}", "title": "${{ on.rss.outputs.title }}", "content":"<<<${{ on.rss.outputs.contentSnippet }}>>>" }
For more information about the Actionsflow workflow file, see the Actionsflow workflow reference.
You can find examples and inspiration on the Trigger List and on Awesome Actionsflow Workflows.
Commit and push your updates to Github
Pushing to Github makes Actionsflow run the workflows you defined. You can view logs at your repository's actions tab on Github.
For more information about getting up and running, 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.
Twice a month we will interview people behind open source businesses. We will talk about how they are building a business on top of open source projects.
We'll never share your email with anyone else.