Assembly Triggers
Every way an APIANT automation can start a run — polling and webhooks.
Every automation starts with a trigger. APIANT offers six flavors; the right one depends on whether the source can push events, whether it has webhooks at all, and how strictly the work is time-driven.
- New Item Polling — poll an endpoint on a schedule and fire when a new record appears.
- New or Updated Polling — poll and fire when a record is created or modified, with automatic last-seen cursor tracking.
- Manual Webhook — you paste a URL into the source app; incoming invocations fire the automation.
- Self-Registering Webhook — APIANT creates and tears down the webhook automatically via the target app's API.
- Service Webhook — credential-based webhook URL with event filtering; multiple event types on a single endpoint.
- Unary Protocol Thread Webhook — for apps that send every webhook for every customer to a single URL; the platform splits the firehose by customer and event type.
For the broader trigger-vs-polling-vs-schedule decision, see Scheduling.
In this section
New Item Polling
Poll an endpoint on a schedule and fire when a new record appears. The workhorse trigger.
New or Updated Polling
Poll and fire when a record is created or modified. Tracks last-seen cursor automatically.
Manual Webhook
You paste a URL into the source app. Incoming invocations fire the automation.
Self-Registering Webhook
APIANT creates and tears down the webhook automatically via the target app's API. Zero manual setup.
Service Webhook
Credential-based webhook URL with event filtering. Multiple event types route on a single endpoint.
Unary Protocol Thread Webhook
For apps that send every webhook for every customer to a single URL — the platform splits the firehose by customer and event type.