Workflows

[tmehta3]

I’m building a workflow to ingest Apigee proxy metadata into BizEvents. My HTTP Request step is successfully returning JSON data. For the workflow creation, should I:

• Add a JavaScript step to transform the raw JSON into BizEvents format, and then ingest it?

• Or can I directly ingest the JSON from the HTTP Request step into the “Ingest BizEvents” action, provided the JSON is already in BizEvents format?

I want to confirm the recommended approach for converting JSON data into BizEvents in workflows — whether transformation is mandatory or direct ingestion is supported.

[MaximilianoML · Accepted solution]

Hello @tmehta3,

Transformation is not mandatory in all cases.

Direct ingestion is supported when the HTTP response is already clean and ready to ingest.

JavaScript transformation is recommended when the source JSON needs mapping, flattening, filtering, renaming fields, adding event.type, adding event.provider, or converting nested arrays into one event per proxy.

For Apigee proxy metadata, I would usually use the JavaScript step, because API responses often contain nested objects and fields that are better normalized before storing them as BizEvents. Also keep in mind that complex JSON objects may be converted to strings, so flattening important fields before ingestion is usually better for later DQL queries.

So, I recommended this approach for the workflow: HTTP Request -> JavaScript transform -> Ingest BizEvents, unless your HTTP response is already exactly in the final BizEvent format.

I hope this helps you 😃