JSON API Poller

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:

  1. Set Timer Trigger as the automation entry (triggerNodeId) with a cron expression.
  2. Connect Timer Trigger → JSON API Poller → rest of flow.
  3. Persist contentHash between 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

FieldDescription
urlJSON API URL
authTypenone or bearer
authTokenBearer token (secret)

Inputs (from upstream / variables):

FieldDescription
previousHashHash from last successful poll
previousValueOptional prior payload for diff UX

Outputs

FieldDescription
dataParsed JSON body
contentHashSHA-256 of response
changedtrue if hash differs from previousHash
currentValue / previousValuePayload snapshot
fetchedAtISO timestamp

Example

After poller, branch on changed:

timer_trigger (cron: */5 * * * *)
  → json_api_poller
  → if_condition (changed == true)
  → set_variable (store contentHash)
  → notify

Requires

ExtensionWhy
timer_triggerProvides the schedule; poller only fetches and compares
Was this helpful?
historyLast updated: May 10, 2026