while sending mule event to http endpoint, resulting message cannot be routed back to bpm, because it does not contain correct headers (properties) such as - processId, processType and so on. This makes calling REST and simple http services from bpm impossible. for now, i have temporarily fixed problem by applying custom message properties transformer, able to rename properties names to contain MuleConstants.MULE_PREFIX (e.g. processID -> MULE_PROCESS_ID , processType -> MULE_PROCESS_TYPE). this way http connector can cache these properties and restore them properly for the outgoing message. then use of reverse transformer ( MULE_PROCESS_ID -> processId, MULE_PROCESS_TYPE -> processType) allows for the message to be recognized and consumed properly by the process connector. the issue may be easily fixed by renaming mule bpm constants, like process type property and others to contain MuleConstants.MULE_PREFIX. I didn't try to route jbpm messages over soap transport, but i expect similar problem with properties