The trigger no third-party tool has
OpFlow lives inside the platform that emits the events — so a form submission or a metric crossing a threshold can start a bot with zero webhook plumbing.
A standalone automation tool can only react to what you pipe into it. To act on something happening in your platform, you set up a webhook, register it, secure it, and hope the source keeps sending. It works — it's just plumbing you have to build and maintain.
Events, not plumbing
OpFlow is Opscend's own automation layer, which means it can subscribe to first-party platform events directly. A form submission, a metric crossing a threshold, a traffic spike — these fire a bot natively, with no webhook to stand up or secure.
on: metrics.threshold_crossed
on: analytics.traffic_spike
on: form.submittedThe best integration is the one you never had to build.
All four ways in
Platform events sit alongside the other three triggers — webhook (signed test + production URLs, configurable auth and responses), schedule (cron, to the minute), and manual. Pick the one that fits; the rest of the engine is the same underneath.
For everything outside the platform, the webhook trigger and the HTTP node still reach anything with an API. But when the event already lives where OpFlow runs, you skip the plumbing entirely.