Crossposting social media workflow repository powered by Actionsflow.

Building an Socialflows workflow is a five-step process:

1. Create a public Github repository by this link.

   Your Socialflows repository structure looks like this:

   ├── .github
   │   └── workflows
   │       └── actionsflow.yml
   ├── .gitignore
   ├── README.md
   └── workflows
   │   └── on-post.yml
   └── package.json

2. Uncomment .github/workflows/actionsflow.yml schedule event and trigger

   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

   on:
     activitypub:
       host: toot.io
       user: <toot-user>

3. Uncomment the jobs for your socials

   Configure the social media account that you'll use as the source of your posts by uncommenting them in on-post.yml. For example, we've enabled the send tweet workflow here:

   on:
     activitypub:
       host: toot.io
       user: testgrislyeye
   
   jobs:
     print:
       name: Print
       runs-on: ubuntu-latest
       steps:
         - name: 🏁 Running Socialflows
           env:
             uri: ${{on.activitypub.outputs.uri}}
             message: ${{on.activitypub.outputs.message}}
             replyTo: ${{on.activitypub.outputs.replyTo}}
           run: echo 🔫 Socialflows triggered by $uri
   
   jobs:
     twitter:
       runs-on: ubuntu-latest
       
       ...
   
         - uses: rg-wood/[email protected]
           with:
             status: ${{ on.activitypub.outputs.message }}
             replyto: ${{ steps.load-history.outputs.status }}
             consumer-key: ${{ secrets.TWITTER_CONSUMER_API_KEY }}
             consumer-secret: ${{ secrets.TWITTER_CONSUMER_API_SECRET }}
             access-token: ${{ secrets.TWITTER_ACCESS_TOKEN }}
             access-token-secret: ${{ secrets.TWITTER_ACCESS_TOKEN_SECRET }}
   
         ...

   Comment out the social media jobs you want to crosspost to.

4. Configure you credentials

Setup the credential secrets for you social media accounts:

You need to set-up consumer and access tokens as GitHub Action secrets in your workflow project. See the send-tweet-action documentation for full instructions.

You need to configure the authority and login credentials for your Bluesky account as GitHub Action. See the send-bluesky-post documentation for full instructions.

5. 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, see Full documentation

You can run self-hosted Actionsflow manually or by docker:

1. Install docker
2. Install act
3. Install dependencies by running npm install

Start Actionsflow locally:

npm run start
# Then, the cron job and webhook server will start running
# The webhook endpoint will be ran at http://localhost:3000/webhook/

npm run build
# Then, the standard workflow files will be built at ./dist/workflows

Actionsflow build will use cache for deduplicating the data, if you want to test your workflow with the same data, you may need to clean the cache by the following command:

# Clean the cache and dist folder.
npm run clean