Description
@hypeline-io/n8n-nodes-hypeline
Give your agents and workflows eyes on the web. This is an n8n
community node for Hypeline: point it at any feed,
streaming source, or web page, and act on genuinely new content inside n8n.
Hypeline detects whether a URL is a feed, a web page, or a streaming source,
renders JavaScript apps when a plain fetch comes back empty, and tells a real
change apart from a rotated ad or a ticking timestamp. It hands you one
deduplicated event stream. This node lets an n8n workflow start on those events
and manage the monitoring itself, so the automation platform an agent already
lives in can watch the web.
Installation
Nodes
Credentials
Usage
Compatibility
Resources
Installation
Follow the community nodes installation guide:
in n8n, go to Settings > Community Nodes, select Install, and enter
@hypeline-io/n8n-nodes-hypeline.
Nodes
Hypeline Trigger
Starts a workflow when Hypeline surfaces new content.
On activation it creates a webhook destination (optionally creating a new alert
from a query first) pointed at the workflow’s webhook URL. Every delivery is
verified with an HMAC signature on the raw body before the workflow runs, so a
tampered or replayed request never fires it. On deactivation it removes the
destination it created, and the alert too if it created that alert. A
pre-existing alert you attach to is never deleted.
#### Webhook verification
Every delivery is checked against the raw request bytes before JSON.parse, so
a tampered or replayed body never reaches the workflow. A destination can have
more than one active signing secret at a time, during a secret rotation or a
storage migration overlap, and the signature header then carries one entry per
active secret. The verifier shipped here accepts the delivery when any entry
matches, so a rotation needs no change to an activated workflow. When the
trigger attaches to a destination that already exists, and therefore gets no
secret revealed to it, it rotates that destination’s secret to obtain one it can
verify with; the previous secret keeps signing through the overlap window, so a
delivery in flight is not dropped.
Hypeline
Manages monitoring from inside a workflow, with three resources:
- Source: create, get, list, delete, delete many. A source turns any feed,
- Alert: create, list, update, delete. An alert is a keyword or Boolean
- Destination: create, create standalone, attach, detach, list, update,
- Hypeline documentation
- n8n community nodes documentation
streaming source, or web page into an event stream. The tier is detected
automatically. Delete Many removes up to 200 sources in one request, taking
a comma-separated list of IDs (or an expression returning an array), and reports
a per-ID outcome so one bad ID never aborts the batch.
query matched against the content of changes from a set of sources. Set an
optional Name to give the alert a human-friendly label; leave it blank to
fall back to the derived scope-and-filter sentence. Choose a Delivery Mode
(instant, every 15 minutes, hourly, or daily) to set the alert’s default
cadence, and toggle Health Notices to mute source-health alerts (a source
going quiet) for this alert without affecting content-change delivery.
delete. A delivery target (webhook, Slack, Discord, Telegram, or ntfy). One
destination is a single shared object that can deliver for several alerts, so
Create under an alert reuses a channel you already have instead of
duplicating it, Create Standalone registers one before any alert uses it,
and Attach adds an existing destination to another alert with an optional
cadence for that alert only. The two removal verbs differ: Detach removes
the destination from one alert and leaves it delivering for the others,
Delete removes the destination itself, with its signing secret and
delivery history, for every alert at once.
Credentials
You need a Hypeline account and an API key.
1. Sign up at hypeline.io and create a hype_ API key
under Settings > API keys.
2. In n8n, create a new Hypeline API credential and paste the key.
3. Click Test to confirm it authenticates against the API.
The key is sent as an Authorization: Bearer header on every request.
Usage
React to new content:
1. Add a Hypeline Trigger node.
2. Choose Create New. Leave the filter query blank to fire on all new
content, or narrow it with a keyword or Boolean query (for example
acquisition OR "series a"), optionally scoped to specific source ids. Or
choose Attach Existing and paste an alert id.
3. Activate the workflow. The trigger registers itself and fires on each new
matching change, with the event as JSON.
Manage monitoring:
1. Add a Hypeline node.
2. Pick a resource (Source, Alert, or Destination) and an operation.
3. For example, Source > Create with a URL starts watching a page; the
detected tier and health come back in the response.
Compatibility
Requires n8n with n8nNodesApiVersion 1. Tested against current n8n releases.
