actionsflow/actionsflow-action

Actionsflow action for github

Actionsflow

---

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
• Features
• Documentation
• How Actionsflow Works
• Getting Started
• Contributing
• Authors

😁 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

• Totally Free! Actionsflow is based on Github actions. To run an Actionsflow workflow, all you need to do is create a repository from the Actionsflow template repository, or, you can also deploy a self-hosted version.
• Leverage Community Triggers. You can use community-provided triggers like Slack, RSS, Webhook, Typeform, Email, Reddit, NPM, Telegram, Twitter, etc. You can also easily create your own triggers.
• Support Almost ALL Actions of Github Actions. Actionsflow uses act (a tool for running GitHub Actions locally) to run the jobs on your workflow file. With these awesome Github actions, you can connect with IFTTT, Zapier, or other services like Slack, Telegram, Facebook, Twitter, Line, etc.
• Support Self-Hosted You can run Actionsflow based on both GitHub Repository or a self-hosted version.
• Simple Workflow Configuration. The Actionsflow configuration format is the same as Github actions. If you've written a Github actions file before, you'll find defining an Actionsflow workflow file really easy.
• Run triggers every 5 minutes. The workflow can check and run every 5 minutes based on Github actions scheduled events.
• Support complex workflows. With Actionsflow you can make complex advanced workflows. Actionsflow provides a MongoDB query language for you to filter your data as you want.

🎓 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

1. 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

2. 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

3. 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.

4. 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.

• Workflow Syntax for Actionsflow - Learn more about the Actionsflow workflow file syntax
• Trigger List - Explore Actionsflow triggers
• Awesome Actionsflow Workflows - Explore and get inspired by other Actionsflow workflow use-cases
• Core Concepts - Learn more about how Actionsflow works
• Creating Triggers for Actionsflow - Learn more about how to create your own trigger for Actionsflow
• FAQs - Actionsflow FAQs
• Join Actionsflow on Slack - Chat with other users and contributors on Slack, if you have already joined, please signin directly
• Join Actionsflow on Telegram - Chat with other users and contributors on Telegram

👏 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

• @theowenyoung - Idea & Initial work

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

📝 License

Licensed under the MIT License.

actionsflow-action's Issues

Add an output with the number of total items found

Currently, the output states if the build was successful or not.

But sometimes the build is successful, although no new items have been found (in the case of RSS polling for example).

In that case, having this kind of informations could be used as a condition to run the subsequent steps (setup act, etc.).

If there is no new item, I could totally skip the next steps and end the task even sooner.

Flow fails - Error: HttpError: Server Error

Description

• My actionflow setup randomly fails. Some days more often than the others
• I do not see any useful error from the Actions output

Action file:

https://github.com/quicoto/actionsflow/blob/main/.github/workflows/actionsflow.yml

Current

Action fails with this output:

Error: HttpError: Server Error
Error: Actionsflow error: HttpError: Server Error

Example failed action: https://github.com/quicoto/actionsflow/actions/runs/3328329214/jobs/5504196930

Expectation

It used to never fail until a few days ago.

• Is there a way to get more verbose error output?