ActiveWorkflow is an intelligent process automation platform that uses software agents; autonomous entities that act on schedule or react to external triggers. These unsupervised agents connect to APIs, process information, perform routine tasks, and enable you to automate internal or external workflows.
ActiveWorkflow is an intelligent process automation platform that uses software agents. A key objective when using ActiveWorkflow is to automate and orchestrate activities that would typically require human time and involvement. Thus, think more along the lines of replacing manual checking of websites, APIs, emails, and calendars rather than building low-level data pipelines (though that's also certainly possible). The basic concepts in ActiveWorkflow are agents and workflows. An overview of each follows below.
Agents are of different types and each type typically knows how to perform a simple task. For example, the HTTP Status Agent checks the status returned from an HTTP request and emits a corresponding message, while the Twilio Agent sends SMS messages or initiates phone calls.
Agents emit and receive messages (some only emit, or only receive). A structure of agents designated as message sources and message targets forms a network. This is what allows a group of agents to coordinate themselves and transform a collection of simple tasks into sophisticated and complex behaviour.
Some agents are self-contained, like the Trigger Agent that watches for specific values in the messages it receives. Others depend on complex third party services, like the aforementioned Twilio Agent.
Agents perform actions either on schedule or when they receive a message. There are also agents that can be triggered by external events. Agents are generally stateful and can have memory. For example, the IMAP Folder Agent remembers the last email it retrieved.
Each instance of an agent is configured by giving it a name, setting its schedule, selecting the sources of the messages it receives (other agents), and choosing among other common options:
Settings specific to a type of agent are often configured by editing the agent's "options" presented as a JSON document:
Each agent type has in-line documentation explaining its functionality and all its configuration options.
A network of agents can quickly become crowded, making it hard to discern the whole picture. This is where the other key ActiveWorkflow concept comes into play. Agents sharing common goals can be organised into workflows.
Workflows allow you to view and control groups of agents all at once. They can also be exported and imported, so you can share automation solutions as a unit.
Below is a list of 30+ agents that come with ActiveWorkflow. These cover a wide spectrum of functionality and can be extensively configured and composed in workflows. Each agent comes with inline documentation within the web interface.
For writing your own custom agents see Custom Agents.
These are agents that connect your workflows to the outside world. Some of them can be used to interface with third party services when a dedicated agent is not (yet) available.Webhook Agent Creates messages by receiving webhooks from any source. Data Output Agent Outputs received messages as either RSS or JSON. Use it to output a public or private stream of ActiveWorkflow data. HTTP Status Agent Will check a URL and emit the resulting HTTP status code with the time that it waited for a reply. Additionally, it will optionally emit the value of one or more specified headers. FTP Site Agent Checks an FTP site and creates messages based on newly uploaded files in a directory. When receiving messages it creates files on the configured FTP server. Website Agent Scrapes a website, XML document, or JSON feed and creates Messages based on the results. RSS Agent Consumes RSS feeds and emits messages when they change. Email Agent Sends any messages it receives via email immediately. Email Digest Agent Collects any messages sent to it and sends them all via email when scheduled. IMAP Folder Agent Checks an IMAP server in specified folders and creates messages based on new mails found since the last run.
These agents use third party services to provide functionality. They typically require an account with these services.Evernote Agent Connects with a user’s Evernote note store. Basecamp Agent Checks a Basecamp project for new messages. Human Task Agent It is used to create Human Intelligence Tasks on Mechanical Turk. S3Agent It can watch a bucket for changes or emit a message for every file in that bucket. When receiving messages, it writes the data into a file on S3. Jira Agent Subscribes to Jira issue updates. Twilio Agent Receives and collects messages, and sends them via text message or calls when scheduled. Twilio Receive Text Agent Receives text messages from Twilio and emits them as messages. Aftership Agent Allows you to track your shipments from Aftership and emit tracking status into messages. Google Calendar Publish Agent Creates events on your Google Calendar. Wunderlist Agent Creates new Wunderlist tasks based on incoming messages. Slack Agent Lets you receive messages and send notifications to Slack.
You can create your own custom agents using the custom agent API. Currently agents written in Ruby are supported, but we are working on providing support for multiple languages, beginning with Python.
The easiest way to start using ActiveWorkflow is by deploying it to Heroku.
If you are reading this document in a browser all you need to do is click the
button bellow and fill in the environment variables for your seed user (admin):
A free Heroku plan could be used to try out ActiveWorkflow, but it wouldn't be enough for real use. That's because the limited run time and automatic turning off of unused workers inhibits ActiveWorkflow from running scheduled tasks.
If you would like more control or intend to deploy ActiveWorkflow from a modified source tree, you could do that using Heroku's command line interface.
Please install Heroku's command line interface tool from Heroku Toolbelt.
For your convenience there is a helper script that guides you through all the steps necessary to deploy to Heroku. It helps with Heroku app creation, plugin installation, initial configuration and repository synchronisation. Helper script is run with:
For additional configuration options please take a look at the
Don't forget to set any configuration options you may require using the
heroku config command line tool.
The default ActiveWorkflow configuration uses the same single dyno to run both the web server and workers.
If you want to deploy ActiveWorkflow to a platform that uses docker containers, you could make an ActiveWorkflow image.
Note: currently there is no official ActiveWorkflow image.
To build, use, or try out a docker image you would need the following tools:
docker-compose is required if you plan to
run docker images locally for testing).
On a Mac the recommended way to install docker is here.
On Linux please use your package manager or follow this docker installation guide.
You can build a docker image for deployment with:
This creates an image named
You may prefer to use Heroku in a container mode (instead of deploying via GitHub). Please be sure to login to Heroku docker registry before doing that:
Docker deployment to Heroku happens in two steps. Push:
If you no longer wish to use image based deployment to Heroku you will need to
reset Heroku stack to
heroku-18 like this:
heroku stack:set heroku-18
ActiveWorkflow is built using Ruby and is a Ruby on Rails app.
Install all dependencies with:
gem install bundler bundle
Diagrams are rendered using the
dot tool from
Graphviz. On a Mac install
brew install graphviz
If you want to test out ActiveWorkflow locally you can start a demo instance using a local sqlite database. First prepare the database with:
bundle exec rake db:create bundle exec rake db:migrate bundle exec rake db:seed
You can start the instance by running:
This starts the ActiveWorkflow instance on a local address localhost:3000 with default username "admin" and password "password".
The local instance uses the configuration stored in a
.env file. You could
tweak it or use it as guidance when configuring your deployment target.
Tests can be run with
You can test the docker container you just built locally. Run it (with a PostgreSQL database in a separate container):
This starts ActiveWorkflow instance on a local address localhost:3000 with default login "admin" and password "password".
Stop containers with:
ActiveWorkflow started as a fork of Huginn with the goal of solely targeting business use. ActiveWorkflow is incompatible with Huginn.
ActiveWorkflow is released under the MIT License.