Skip to content
Back to news
workflows9/7/2026

Trigger Workflows from Any Webhook

Workflows can now be triggered by an incoming webhook from any external tool, alongside the existing schedule and in-platform triggers like Tasks and Chat.

workflowswebhooksautomation

Workflows has been able to trigger off events inside Piskes AI Studio for a while — a task moving stage, a scheduled time, a form submission — but starting a workflow from something happening outside the platform meant no direct path in. Today's release adds webhook triggers, opening workflows up to any external tool that can make an HTTP request.

How it works

Any workflow can now start with a webhook trigger, which generates a unique, workspace-scoped URL to configure in whatever external system you want to trigger from — a payment processor, a form tool, a third-party CRM, a custom script. When that system sends a request to the URL, the workflow starts immediately, with the request's payload available to every step downstream the same way trigger data from an internal event already is. Incoming payloads are validated against an optional schema you define, so a malformed or unexpected payload can be rejected before it reaches your workflow's logic rather than causing a confusing failure three steps in.

Where this is useful

This is aimed at closing the gap between Piskes AI Studio and everything a business runs outside it — a webhook from a payment provider that should kick off a Finance invoice and a CRM update together, a form submission from an external site that should create both a CRM lead and a Tasks follow-up, or a deployment notification from outside the platform that should post to a Chat channel. Combined with the error handling and retries shipped earlier, webhook-triggered workflows now have the same reliability guarantees as internally triggered ones.

What's included

Webhook trigger URLs, payload validation, and full downstream access to payload data are live today. Signature verification for providers that sign their webhook payloads, so a workflow can confirm a request genuinely came from the expected sender, is planned for a follow-up release.

Webhook triggers are available now on every plan that includes Workflows, created from any workflow's trigger settings.