Building Camunda as a Web Service API

[chrysalis]

I’ve been digging the forums and found some similar projects…

Similar projects:

Function as a Service API

We are working on a Function as a service API / Middleware / wrapper around Camunda BPMN processes that return variables. would be interested to get some feedback on the design and features. Overall goal is to provide a way to control the Rest API response based on the BPMN returned variables.

Rest Api based workflow - Http-Connector and handeling errors

Hello, I am thinking about using Camunda while focusing on its Rest API capabilities mostly in order to avoid the usage of Java. For a starting “demo” project i built a pretty simple workflow which relays on the http-connector component. I found enough info and examples to make it work. So at the moment i got something like 6-7 synchronic external tasks and i also added an event boundy for handeling bad http responses ( 404, 500 ,400 etc ). Every one of those tasks has an event boundy and at …

The difference though is that, the implementation I am trying to achieve is one without using Java, this would mean that all of my service tasks would be External.

The question I have now are.

1. How do you return JSON messages as results from the entire workflow processes.

• From what I am seeing, JSON messages are handled by the use of Connectors + Input/Ouput mapping via scripting.

• Or an alternative approach would be to persist the actual JSON response and assign it as a process variable, you would then have to call another API call to get process instance variables ( this I haven’t tried)