Create agents that monitor and act on your behalf. Your agents are standing by!
Huginn is a system for building agents that perform automated tasks for you online. They can read the web, watch for events, and take actions on your behalf. Huginn’s Agents create and consume events, propagating them along a directed graph. Think of it as a hackable version of IFTTT or Zapier on your own server. You always know who has your data. You do.
Join us in our Gitter room to discuss the project.
Want to help with Huginn? All contributions are encouraged! You could make UI improvements, add new Agents, write documentation and tutorials, or try tackling issues tagged with #“help wanted”. Please fork, add specs, and send pull requests!
Really want a fix or feature? Want to solve some community issues and earn some extra coffee money? Take a look at the current bounties on Bountysource.
Have an awesome idea but not feeling quite up to contributing yet? Head over to our Official ‘suggest an agent’ thread and tell us!
Please checkout the Huginn Introductory Screencast!
And now, some example screenshots. Below them are instructions to get you started.
The quickest and easiest way to check out Huginn is to use the official Docker image. Have a look at the documentation.
If you just want to play around, you can simply fork this repository, then perform the following steps:
git remote add upstream https://github.com/huginn/huginn.git
to add the main repository as a remote for your fork..env.example
to .env
(cp .env.example .env
) and edit .env
, at least updating the APP_SECRET_TOKEN
variable.DATABASE_ADAPTER=postgresql
.)bundle
to install dependenciesbundle exec rake db:create
, bundle exec rake db:migrate
, and then bundle exec rake db:seed
to create a development database with some example Agents.bundle exec foreman start
, visit http://localhost:3000/, and login with the username of admin
and the password of password
.git fetch upstream
and then git checkout master && git merge upstream/master
to merge in the newest version of Huginn.Note: By default, email messages are intercepted in the development
Rails environment, which is what you just setup. You can view
them at http://localhost:3000/letter_opener. If you’d like to send real email via SMTP when playing
with Huginn locally, set SEND_EMAIL_IN_DEVELOPMENT
to true
in your .env
file.
If you need more detailed instructions, see the Novice setup guide.
All agents have specs! And there’s also acceptance tests that simulate running Huginn in a headless browser.
npm install phantomjs
brew install phantomjs
bundle exec rspec
bundle exec rspec path/to/specific/test_spec.rb
.Huginn Agents can now be written as external gems and be added to your Huginn installation with the ADDITIONAL_GEMS
environment variable. See the Additional Agent gems
section of .env.example
for more information.
If you’d like to write your own Huginn Agent Gem, please see huginn_agent.
Our general intention is to encourage complex and specific Agents to be written as Gems, while continuing to add new general-purpose Agents to the core Huginn repository.
Please see the Huginn Wiki for detailed deployment strategies for different providers.
Try Huginn on Heroku: (Takes a few minutes to setup. Read the documentation while you are waiting and be sure to click ‘View it’ after launch!) Huginn launches only on a paid subscription plan for Heroku. For non-experimental use, we strongly recommend Heroku’s 1GB paid plan or our Docker container.
Try Huginn on OpenShift Online
Create a new app with either mysql
or postgres
:
oc new-app -f https://raw.githubusercontent.com/huginn/huginn/master/openshift/templates/huginn-mysql.json
or
oc new-app -f https://raw.githubusercontent.com/huginn/huginn/master/openshift/templates/huginn-postgresql.json
Note: You can also use the web console to import either json file by going to “Add to Project” -> “Import YAML/JSON”.
If you are on the Starter plan, make sure to follow the guide to remove any existing application.
The templates should work on a v3 installation or the current v4 online.
Have a look at the installation guide.
See private development instructions on the wiki.
In order to use the WeatherAgent you need an Weather Data API key from Pirate Weather. Sign up for one and then change the value of api_key: your-key
in your seeded WeatherAgent.
We assume your deployment will run over SSL. This is a very good idea! However, if you wish to turn this off, you’ll probably need to edit config/initializers/devise.rb
and modify the line containing config.rememberable_options = { :secure => true }
. You will also need to edit config/environments/production.rb
and modify the value of config.force_ssl
.
Huginn is provided under the MIT License.
Huginn was originally created by @cantino in 2013. Since then, many people’s dedicated contributions have made it what it is today.