Poll a JSON HTTP endpoint and detect whether the response changed since the last run (SHA-256 hash).
Type: ACTION · Handler: BUILT_IN · Requires: timer_trigger (enforced on save)
How scheduling works
This node does not replace Timer Trigger. Use this pattern:
- Set Timer Trigger as the automation entry (
triggerNodeId) with a cron expression. - Connect Timer Trigger → JSON API Poller → rest of flow.
- Persist
contentHashbetween runs with Set Variable (automation or bot scope).
If you add JSON API Poller without a Timer Trigger node on the same graph, validation fails with MISSING_REQUIRED_EXTENSION.
Configuration
| Field | Description |
|---|---|
url | JSON API URL |
authType | none or bearer |
authToken | Bearer token (secret) |
Inputs (from upstream / variables):
| Field | Description |
|---|---|
previousHash | Hash from last successful poll |
previousValue | Optional prior payload for diff UX |
Outputs
| Field | Description |
|---|---|
data | Parsed JSON body |
contentHash | SHA-256 of response |
changed | true if hash differs from previousHash |
currentValue / previousValue | Payload snapshot |
fetchedAt | ISO timestamp |
Example
After poller, branch on changed:
timer_trigger (cron: */5 * * * *)
→ json_api_poller
→ if_condition (changed == true)
→ set_variable (store contentHash)
→ notify
Requires
| Extension | Why |
|---|---|
timer_trigger | Provides the schedule; poller only fetches and compares |
Was this helpful?
historyLast updated: May 10, 2026
