Inputs

Modules that produce records — HTTP polling, SOAP polling, webhooks, databases.

Every pipeline has exactly one input. It produces records the filter chain consumes, either on a CRON schedule (HTTP polling, SOAP polling, database) or as a long-running listener (webhook).

httpPolling

GET an HTTP endpoint on a CRON schedule. Page, offset, or cursor pagination; state persistence; OAuth2.

soapPolling

Call a SOAP operation, parse XML records, and support SOAP pagination, MTOM, and WS-Security.

webhook

Listen for HTTP POSTs. HMAC-SHA256 verification, in-memory queue, rate limiting.

database

PostgreSQL, MySQL, or SQLite. Cursor or limit-offset pagination, incremental queries.

What an input does

Fetches a batch of records — one HTTP response page, one SQL query result, one webhook delivery.
Hands the batch off to the filter chain, one record at a time.
On scheduled inputs, persists state (cursor, last ID, timestamp) between runs so the next batch picks up where the previous one left off.

See Input → Filters → Output for the full record-flow model.