ethos

n8n community node for ETHOS browser automation

Package Information

Released: 3 mo ago
Downloads: 186 weekly / 186 monthly
Latest Version: 0.1.0
Author: ETHOS

Available Nodes

ETHOS
Run an ETHOS autonomous browser workflow from a plain-English goal

Documentation

n8n-nodes-ethos

An n8n community node for ETHOS — drop autonomous browser workflows into any n8n pipeline using a plain-English goal.

Installation

  1. In n8n, open Settings → Community Nodes.
  2. Click Install.
  3. Enter n8n-nodes-ethos and confirm.
  4. After install, restart n8n if prompted.

Credentials

The node uses an ETHOS API credential with two fields:

Field Required Description
API Key Yes Your ETHOS API key (starts with ethos_sk_). Get one at https://ethos.so/dashboard/api-keys.
Base URL No Defaults to https://api.ethos.so. Override only for self-hosted ETHOS.

Node inputs

Name Type Default Description
Goal string — Plain-English browser task (10–2000 chars)
Execution Mode options headless Only headless is supported via API today
Poll Interval number 3000 (Additional Options) Milliseconds between polls
Timeout number 120 (Additional Options) Maximum wait time, in seconds

Node outputs

Two output branches:

Branch When Payload
Success Workflow status is completed { workflowId, status, result, taskCount, tasksDone }
Error Status is failed, timed out, or hit an HTTP error { workflowId, status, error }

The Error branch is used instead of throwing, so downstream nodes can react.

Error messages

  • Invalid ETHOS API key — 401 from the API
  • Quota exceeded — 429 from the API
  • Workflow timed out after Xs — exceeded the configured timeout
  • Other HTTP errors are retried up to twice with a 2-second backoff before being routed to the Error branch

Example

Goal:

Get the top 5 trending repositories from github.com/trending with name, stars, and description

Drop the ETHOS node after a trigger, paste the goal, connect the Success branch to your data sink (Slack, Sheets, Notion, etc.), and the Error branch to a notification node.

Limitations

  • Headless execution only — extension mode is coming soon.
  • Maximum timeout is bounded by your n8n execution timeout; the node default cap is 120 seconds.
  • Each node execution submits and waits for one workflow; for high throughput, fan out with the n8n Split In Batches node.

License

MIT

Discussion