Service Webhook

A webhook trigger keyed by the connected account's credentials, with server-side event filtering. One URL serves many event types; the trigger fires only when the inbound event matches its filter.

When to use

• The source app sends many event types to a single webhook URL (Stripe, Shopify, HubSpot).
• Different automations should handle different event types.
• Credential-scoped webhooks — one URL per connected account.

How it works

1. APIANT issues a URL keyed by the connection ID.
2. The source sends every event type to that URL.
3. APIANT matches the inbound payload against each automation's event-type filter.
4. Only automations whose filter matches the event fire.

Event filtering

Each trigger is configured with an event-type field (e.g. customer.created, order.fulfilled). The skill adds a conditional at trigger-time that ignores non-matching events, so downstream steps only run for the expected event.