Connect business applications
n8nConnect the dots in your workday.
ActivepiecesBuild a repeatable flow between your tools.
AutomatischConnect repeated business steps in a visual flow.
Node-REDYour ideas, connected.22 applications / Automation & workflows
Make the repeatable parts of work repeatable.
Visual integration tools, data orchestrators, background-task systems and notification services sit at different layers of automation. Start with the event that begins the work and the outcome that confirms it finished correctly.
Explore the applications
Choose by the work you want to do.
n8nConnect the dots in your workday.ActivepiecesBuild a repeatable flow between your tools.AutomatischConnect repeated business steps in a visual flow.Node-REDYour ideas, connected.Orchestrate code and data
WindmillTurn scripts into a shared operational tool.
Apache AirflowSchedule the dependencies in a data workflow.
DagsterOrganize data work around the assets it produces.
KestraMake orchestration visible across different systems.Notifications and operations
ntfySend a useful notification from a simple request.
GotifyGive your scripts a personal notification channel.
HealthchecksFind out when a scheduled job goes quiet.
Semaphore UIGive infrastructure playbooks a working interface.Browse this collection
Automation & workflows applications
22 applications to explore
AutomationActivepieces
Build a repeatable flow between your tools.
View hosting & requirementsAutomationApache Airflow
Schedule the dependencies in a data workflow.
View hosting & requirements
AutomationApache NiFi
See how data moves from source to destination.
View hosting & requirements
AutomationApprise
Use one notification layer for different destinations.
View hosting & requirementsAutomationAutomatisch
Connect repeated business steps in a visual flow.
View hosting & requirements
AutomationAWX
Coordinate Ansible automation through a team workspace.
View hosting & requirements
Automationchangedetection.io
Notice when a page you follow changes.
View hosting & requirementsCronicle
Schedule jobs across a controlled set of servers.
View hosting & requirementsAutomationDagster
Organize data work around the assets it produces.
View hosting & requirementsAutomationGotify
Give your scripts a personal notification channel.
View hosting & requirementsAutomationHealthchecks
Find out when a scheduled job goes quiet.
View hosting & requirements
AutomationHuginn
Watch for an event and decide what follows.
View hosting & requirementsAutomationKestra
Make orchestration visible across different systems.
View hosting & requirementsAutomationn8n
Connect the dots in your workday.
View hosting & requirementsAutomationNode-RED
Your ideas, connected.
View hosting & requirementsAutomationntfy
Send a useful notification from a simple request.
View hosting & requirements
AutomationPrefect
Keep Python workflows observable and repeatable.
View hosting & requirements
AutomationRundeck
Make operational procedures easier to run consistently.
View hosting & requirementsAutomationSemaphore UI
Give infrastructure playbooks a working interface.
View hosting & requirements
AutomationTemporal
Keep long-running application workflows on track.
View hosting & requirementsTrigger.dev
Run background work alongside your application.
View hosting & requirementsAutomationWindmill
Turn scripts into a shared operational tool.
View hosting & requirementsChoose with confidence
What starts the workflow, and what proves it finished?
Use test credentials and a harmless sample workflow. Force one step to fail, retry it and check whether the final action happens once. Verify how an operator sees the error and receives an actionable notification.
Choose the level of control
A visual connector can suit a business handoff. A code-oriented orchestrator may fit complex dependencies or custom execution. Match the tool to the people who will maintain the workflow.
Design for the second attempt
Networks fail and jobs retry. Decide how to detect an incomplete run, avoid duplicate actions and recover when an external service changes or stops responding.
Treat credentials as part of the system
Every connection grants access somewhere. Scope tokens, document ownership and test rotation so a useful automation does not depend on one person’s account.
Bring to the hosting conversation: Trigger type, credentials, worker concurrency, outbound connections and failure handling.
How should I compare the automation & workflows in this collection?
Visual integration tools, data orchestrators, background-task systems and notification services sit at different layers of automation. Start with the event that begins the work and the outcome that confirms it finished correctly.
What should I prepare before hosting one of these automation applications?
Trigger type, credentials, worker concurrency, outbound connections and failure handling. Each application's profile links to its official project for current requirements and licensing.
What is a useful first test for a automation application?
Use test credentials and a harmless sample workflow. Force one step to fail, retry it and check whether the final action happens once. Verify how an operator sees the error and receives an actionable notification.