I know we’ve got basic HTTP GET support in the current HTTP Client Input plugin. That’s sufficient for some very simple web services work. I’ve seen, though, an upswing in projects that have requirements to work with “X” or “Y” REST API. Even the SOAP clients these days are getting used less and less as REST has been adopted as THE standard for most cloud based systems.
REST interaction can be done today in Workflow with scripting or interaction with outside executables (cURL). But I’d love to see some type of native plugin added. Maybe it’s just wrapping cURL in a GUI interface (kind of like what was done with WinSCP for the SFTP plugin) or something deeper such as folding in a full library like poco.
It would be complex for sure, but in my mind not any more complex than some of the Metadata plugins. Those present some fairly complex options in a pretty intuitive manner.
Adding a HTTP Client “2.0” plugin to support richer interaction (POST, PUT, etc.) would be a killer feature!
I’ll take a look at it. It appears to be tuned for input vs. output though. (What I was primarily looking for was a better HTTP client not a HTTP server)
From the help file:
While you can insert the NodeJS Server Input task anywhere in your process as a secondary input task, in reality the NodeJS Server Input task will only function when used as the initial input, as it is triggered when Workflow’s NodeJS Server receives a request and passes
One thing at a time though. This looks good… an updated HTTP server… maybe an updated HTTP client isn’t too far behind!
An updated HTTP Client is on our TODO list. It will support standard HTTP Verbs (GET, POST, PUT, DELETE), will allow specifying a payload and attachments and will allow you to specify how to store the results from the HTTP call.
We don’t have a timeframe yet, but given the rapidly growing popularity of REST-based communication, it should come sooner than later.
