Triggers
Subscribe a tenant to provider events, by webhook or polling.
A trigger turns a provider event — a new invoice, an inbound message — into a normalized event Stacklink delivers to your app. You subscribe; Stacklink handles ingestion, normalization, and delivery.
Trigger types vs subscriptions
A trigger type is what a provider can emit (e.g. zoho_books.invoice.event). A subscription
is your tenant subscribing to one, with a delivery mode.
curl -X POST http://localhost:4100/v1/triggers/subscriptions \
-H "authorization: Bearer $STACKLINK_API_KEY" \
-H "content-type: application/json" \
-d '{"tenantId":"biz_123","triggerTypeId":"<id>","deliveryMode":"webhook"}'| Delivery mode | How it works |
|---|---|
webhook | The provider pushes to Stacklink, which verifies the signature and ingests. |
polling | A Stacklink worker polls the provider API on a cursor and diffs results. |
The event pipeline
provider event → recorded raw → normalized → matched to subscriptions → delivered to your webhook (signed)Stacklink dedupes by (providerKey, eventScope, externalEventId), so the same event isn't delivered
twice. Polling stores a small cursor (a pagination token), not the full result set.
Once a tenant is subscribed, move on to Webhooks to receive and verify the deliveries.
React to real events, free
Trigger subscriptions, polling, and event deliveries are standard ops — 20,000 free every month, hard-capped.