Parse JSON · Flow · One field per schema entry
Reads fields out of JSON text and saves each one on the record, so later steps can use them.
When to use it
Use it whenever an earlier step produced JSON you need to pick apart — most often an HTTP request's response body, or an AI research answer that came back as JSON.
What it does
You give it some JSON text and describe the fields you want out of it. For each record, it parses the text and saves one record field per entry in your schema, ready to filter, route, or @-mention downstream.
Configure it
Input — the JSON text to parse. Usually an
@-mention of an earlier step's raw output, like an HTTP request's response body.Schema — the fields you want out. Click Set a schema… to open the JSON schema dialog. Paste a sample of the JSON and click Generate schema, or click Create manually and use Add property. Click Save when you are done.
Each property in the schema has:
A name, the property's name as it appears in the JSON, like
email. Ocean saves the value as a field on the record named after it.A type: Text, Number, Integer, Boolean, a list (List of text, List of numbers, List of integers, or List of booleans), Object, or List of objects. Picking the right type matters: an Integer stays
42rather than becoming42.0when it lands in a prompt or a CRM field. An Object or List of objects holds properties of its own, so you can read nested values.
Cost
No credit cost. See Credits in workflows.
Gotchas
If the input isn't valid JSON, that record fails at this step. Switch on Continue anyway under If this step fails if a missing or malformed reply shouldn't stop the record.
You can chain two Parse JSON steps — save a nested object or a list with one, then read deeper into it with the next.