SolutionEngine LogoSolutionEngine
HomeProductUse CasesPricing

Datasource: HTTP GET

Use HTTP GET when your source system does not push events and must be polled.

The datasource sends a GET request at a fixed interval and emits each response as a workflow event.

Best Use Cases

  • Polling REST APIs for status updates
  • Periodic synchronization jobs
  • Integrating legacy systems without webhook support

Configuration Fields

FieldRequiredTypeDefaultPurpose
urlYesstring-Target endpoint to poll
intervalNonumber5Poll interval in seconds
headersNojson-Optional request headers

How to Configure Correctly

  1. Create datasource and select HTTP GET.
  2. Set url to a stable, reachable API endpoint.
  3. Set interval based on source update frequency and rate limits.
  4. Add auth headers if required (Authorization, API key headers).
  5. Save datasource and bind it to a workflow via Datasource Trigger.
  6. Activate and validate first events in execution logs.

Recommended Validation Rules

  • Endpoint must return consistent payload shape
  • Response timeout should be lower than poll interval
  • Avoid polling intervals below source capacity limits
  • Always handle empty/error responses in workflow logic

Example Config

{
  "url": "https://api.example.com/v1/sensor/state",
  "interval": 10,
  "headers": {
    "Authorization": "Bearer <token>",
    "Accept": "application/json"
  }
}

Workflow Pattern

HTTP GET -> Datasource Trigger -> Validation -> Transform -> Save/Notify

Common Problems

  • 401/403: invalid or missing auth headers
  • Frequent failures: interval too aggressive or endpoint unstable
  • No useful output: response format mismatch with downstream nodes

Related Pages

  • Continue with Datasources for architecture and operations.
  • Continue with Workflows for trigger and downstream processing design.
PreviousAPI Reference
NextDatasource - HTTP Event Stream