Scheduling

Most automations start on a schedule or in response to an event. APIANT offers three trigger flavors; the right one depends on whether the work is time-driven or data-driven, and whether the source supports push or only pull.

Polling trigger

Check a source API on a schedule and fire the automation once per record that's new or changed since the last check. The polling interval is configurable; most connectors default to 5–15 minutes. Use when the source has no webhooks but you need near-realtime pickup of new data.

Scheduled trigger

Run on a cron-like schedule: every hour, weekdays at 9am, the 1st of every month. Use when the work is time-driven — nightly reports, weekly rollups, scheduled reminders.

Webhook trigger

The source system pushes an event and the automation runs immediately. Lowest latency; no polling cost. Three webhook sub-flavors:

• Manual webhook — the URL is yours to give to the source (a curl target).
• Service-provided webhook — the connector ships the URL and the source auto-configures it.
• Self-registering webhook — the automation registers the webhook with the source's API on save.

See Assembly Triggers for the skill catalog that builds each flavor.

Picking between them

Related

Snooze pauses a running automation until a future datetime — the "sleep" counterpart to these "wake" triggers.