Changelog
Kevin Coleman
Co Founder
4 Minutes
We’re excited to announce one of our most powerful workflow upgrades yet: the HTTP Request Action. This feature allows you to make HTTP request from within a Ravenna workflow.
What Is IT?
HTTP Action allows you to make outbound HTTP requests from any step within a Ravenna workflow. That means you can call APIs, trigger webhooks, or push/pull data from external systems.
It supports GET, POST, PUT, and DELETE requests, and you can fully customize headers, query params, and body payloads using workflow data.
Why We Built It
Ravenna is great at automating internal workflows but until now, it couldn’t easily reach beyond its own walls. We kept seeing teams build clever workarounds just to connect Ravenna to their external tools, APIs, or internal systems.
Your operations rely on a whole ecosystem of apps, services, and custom endpoints. So instead of forcing you to jump between tools or bolt on scripts, we brought that connectivity directly into Ravenna.
Now, with the HTTP Request Action, Ravenna can talk to anything with an API, cleanly, flexibly, and in real time.
What You Can Do With It
The possibilities are (almost) endless. Here are a few practical use cases:
Trigger third-party services: Kick off a CI/CD job, or notify a CRM when a workflow stage is reached.
Sync data across systems: Push updates from Ravenna into an internal tool or database.
Call internal APIs: Use Ravenna to interface with your own backend services or business logic.
Chain together automations: Use a Ravenna workflow as the central brain, coordinating actions across multiple systems in real time.
Bonus: You can pass dynamic data from previous workflow steps directly into the HTTP request. That makes the whole thing even more powerful.
Ready to Get Started?
You’ll find the HTTP Action in the workflow editor today. Just drag it in, configure your request, and you’re ready to talk to the outside world.
As always, we’d love to hear what you build with it!
