2026-08-20
LoopCraft adds webhook triggers to start loops from any HTTP event (2026-08-20)
Any loop can now be started by an incoming HTTP request — a dedicated endpoint per loop, payload passed straight into the first node, response streamed back from the final node, and every webhook run recorded in the trace view.
← Back to NewsStarting 2026-08-20, LoopCraft ships webhook triggers. Every loop you build now gets its own HTTPS endpoint: POST a JSON payload to it, and the loop starts with that payload as the input of its first node. When the run finishes, the final node's output is returned as the HTTP response — synchronously for fast loops, or as a callback to a URL you configure for long-running ones.
The trigger carries the same governance as every other part of LoopCraft. Each webhook run records the request headers, the payload, and the full trace, so a run started by an external system is just as inspectable as one you started by hand. Iteration caps and cost budget guards apply unchanged, and a signature secret lets the endpoint verify that requests really come from your integration. Rate limits protect the endpoint from accidental floods, and rejected requests return structured errors instead of silent drops.
Typical uses: an inbox rule that starts a triage loop per incoming ticket, a CMS publish hook that runs an SEO-check loop per article, or a form submission that kicks off a personalization loop. Webhook triggers are available on all plans. Try them at https://getloopcraft.com. Feedback: sapsap@qq.com.