Data Sent to Activepieces

In the Activepieces Task, you are able to build the data key/value pairs which are sent to the Activepieces Catch Webhook trigger. The key/data pairs you create can then be used within an Activepieces flow.  

Along with the data you specify to send to Activepieces the Activepieces Task automatically sends the Maestro Queue ID and the Maestro Process ID as two separate key/value pairs.  The following is an example of data sent to the Catch Webhook trigger from the Activepieces Task:

body:{
  maestro_queue_id:"851"
  maestro_process_id:"62"
  vendor_name:"Acme Vendor"
  vendor_id:"RUSH-2112"
  vendor_description:"This is a plausible description for a vendor in an example."
  vendor_categories:"IT,Consulting Services,Financial Services,Development"
}

Your will notice the maestro_queue_id and the maestro_process_id in the data stream example above.  This means you are able to call back to the Maestro process or task via Orchestration services and perform tasks such as completing tasks or updating process variables.

maestro_queue_id

This parameter holds the Maestro Queue ID of the Activepieces task which initiated the webhook call.

maestro_process_id

This parameter holds the Maestro Process ID for which the Activepieces task which initiated the webhook call belongs to.

With the queue and process IDs available to you in your Activepieces flow, you're able to reference the calling task and calling process within Maestro.