A de facto directory of third party Huginn agents that are built using huginn_agent as a template.
A skeleton for Huginn agent development. Specifically, for developing agents as Ruby gems and not native to the environment. Explains how to use it to stand up the skeleton of an agent for development, how to register it with a Huginn instance so it can be used, and how to run unit tests. Has a short list of agents that are built using this framework.
I wonder if this could be used to re-implement activeworkflow-agent-python or activeworkflow-remote-agent-api.
If you integrate anything with Slack and you need to reconfigure it, you have to go here.
A Huginn agent that can read Google Calendars using the GCal API and emit events based upon what it finds.
Most APIs are undocumented and hidden in plain sight. Being able to find these APIs can provide a rich, reliable, and scalable method of building your own datasets. Learn how to find them in the wild, and how they’ve been used in past investigations.
Queries the OneCall API of OpenWeatherMap for a given location by latitude and longitude. This API returns information about the current weather, forecasts by minute, hour, and day, and national weather alerts.
A Huginn agent that writes events into InfluxDB in line protocol format (primarily). No docs right now but there are only two files and the Huginn on-line docs therein seem helpful.
The active_workflow_agent library helps you to write your own ActiveWorkflow agents in Ruby using ActiveWorkflow's remote agent API. “Remote” in this context means that agents run in separate processes from ActiveWorkflow itself. Communication between agents and ActiveWorkflow takes place via HTTP. Each agent is effectively an HTTP server which ActiveWorkflow connects to and interacts with via the remote agent API protocol.
Github: https://github.com/automaticmode/active_workflow_agent
The activeworkflow_agent library helps you to write your own ActiveWorkflow agents in Python using ActiveWorkflow's remote agent API. “Remote” in this context means that agents run in separate processes from ActiveWorkflow itself. Communication between agents and ActiveWorkflow takes place via HTTP. Each agent is effectively an HTTP service or microservice which ActiveWorkflow connects to and interacts with as long as it supports the remote agent API protocol.
Github: https://github.com/automaticmode/activeworkflow-agent-python
You can create your own agents by developing simple services that implement ActiveWorkflow's Remote Agent API. “Remote” in this context means that agents run in separate processes from ActiveWorkflow itself. Communication between agents and ActiveWorkflow takes place via HTTP. Each agent is effectively an HTTP service or microservice which ActiveWorkflow interacts with via an RPC protocol.
https://github.com/automaticmode/active_workflow/blob/master/lib/remote_agents.rb
https://github.com/automaticmode/active_workflow/blob/master/spec/features/use_remote_agent.rb
https://github.com/automaticmode/active_workflow/blob/master/spec/lib/remote_agents_spec.rb
Claims to be an easy-to-integrate self-hosted tool to monitor the performance of your Ruby on Rails application. This is a simple and free alternative to the New Relic APM, Datadog or other similar services. Realtime monitoring, throughput, average response time, which bits are the slowest, database queries, delayed_job monitoring, and custom events.
Known to work with Rails v4.2 and later. Requires Redis to hold the stats.
Amazingly, plugs right into Huginn using the default instructions.
Agent that monitors a flow of data and uses Isolation Forest techniques to identify statistical outliers and anomalies.
How to add Redis caching support to a Ruby on Rails application.
Liquid is a template language created by Shopify. It's available as an open source project on GitHub, and is used by many different software projects and companies.
This reference documents the Liquid tags, filters, and objects that you can use to build Shopify Themes.
Of course, this applies to anything else that uses Liquid as its templating language.
Huginn agent for publishing message via the Mastodon API.
A Huginn agent for querying SQLite databases. Whatever it finds are emitted as events.
A Huginn agent for writing data into influxdb.
This gem provides two agents for Huginn that can read from and write to SQLite 3 databases.
For detailed instructions on their usage, please see the Markdown descriptions within the agents' source (which will also be displayed in your Huginn dashboard).
Note that this gem relies on the sqlite3 gem which itself requires SQLite3 development headers. If you're running Huginn on a regular server, satisfying this requirement may be simple.
Huginn's native mqtt agent (subscribe only) re-implemented as a LongRunnable. Simply choose a topic (think email subject line) to listen to, and configure your service. Many services run mqtts (mqtt over SSL) often with a custom certificate. You'll want to download their cert and install it locally, specifying the certificate_path configuration.
The UniqueAgent receives a stream of events and remits the event if it is not a duplicate. Uses Redis as its backing store.