Bit FlowsでのJSON、CSV、XMLパーサーの使用方法

Raw data is not ready for automation until your workflow can read it.

A webhook may send order details as JSON. A report may arrive as CSV rows. An older API may return product data in XML.

Bit Flows includes built-in parser tools to read these formats and turn them into clean fields. After that, you can map the values to Google Sheets, WooCommerce, CRM tools, email apps, Slack, Telegram, AI Agent, or any other step in your workflow.

Quick answer: JSON, CSV, and XML parsers help Bit Flows read raw data from webhooks, APIs, reports, and feeds. Once parsed, the data becomes available as separate fields. You can then map those fields to Google Sheets, WooCommerce, CRMs, emails, Slack, Telegram, AI Agent, or other workflow steps.

What are Parsers in Bit Flows?

Parsers are Bit Flows tools that read structured data and make it usable inside a workflow. Bit Flows currently includes three parser tools:

• JSON Parser
• CSVパーサー
• XML Parser

Each parser is made for a different data format. The goal is simple: take raw data, extract the values, and use those values in the next workflow step.

For example, if a webhook sends customer data, you can parse the customer name, email, order ID, and payment status. Then you can send those values to a spreadsheet, CRM, email, or notification app.

When do you need a parser?

You need a parser when the data arrives as one raw block, not as separate fields.

For example, an incoming webhook may send the full order payload in one JSON body. An API may return product details inside XML tags. A CSV file may contain many rows that need to be processed one by one.

You usually do not need a parser when the previous app already sends clean fields, such as name, email, phone, and message.

Most WordPress automation workflows depend on field mapping.

If a form sends clean fields, mapping is easy. But API responses, webhook payloads, feeds, and exported files often come in formats that need to be processed first.

A parser saves you from writing custom code for simple data extraction. With Bit Flows, you can parse the data inside the visual workflow builder and use the result in later nodes.

JSON Parser

The JSON Parser reads JSON data and converts it into workflow fields. JSON is common in APIs, webhooks, SaaS apps, and custom app responses. If you work with modern API data, this parser will be used often.

Example JSON data

{
  "order_id": 5821,
  "customer_name": "Sarah Khan",
  "email": "sarah@example.com",
  "payment_status": "paid"
}
コピー

After parsing, Bit Flows can use each value separately:

• order_id
• customer_name
• email
• payment_status

Bit Flows receives order data from a webhook. The JSON Parser extracts the values. And now each data can be mapped separately.

CSVパーサー

The CSVパーサー reads comma-separated data and turns rows into structured fields. CSV is common in lead lists, exported reports, product sheets, booking data, and bulk records.

Example CSV data

After parsing, Bit Flows can read values like:

• id
• name
• department
• status

Bit Flows reads a CSV source, parses the rows, and uses an Iterator to process each row. Each contact can then be added to a CRM or sent to Google Sheets.

XML Parser

The XML Parser reads XML data and extracts values from tags. XML is still used in product feeds, legacy APIs, booking systems, payment systems, and enterprise platforms.

Example XML data

<product>
  <id>303</id>
  <name>Keyboard</name>
  <stock>45</stock>
  <price>79.00</price>
</product>
コピー

After parsing, Bit Flows can use:

• id
• name
• stock
• price

Example workflow

An external API returns data in XML. Bit Flows parses the XML response and maps the values to the next action.

Which Parser Should You Use?

Choose the parser based on how your incoming data is structured. The right parser turns raw data into clean fields, so you can map it to the next workflow step without manual cleanup.

A quick way to choose:

• Data with { } または [ ] usually needs JSON Parser
• Row-based data separated by commas needs CSVパーサー
• Data with tags like <product> または <user> needs XML Parser

How to Use a Parser in Bit Flows

The setup is simple.

1. Create a new flow.
2. Choose the trigger that receives the raw data. Common options are Incoming Webhook, Schedule, API, or a previous app action.
3. Run a test once so Bit Flows can capture sample data.
4. Add JSON Parser, CSV Parser, or XML Parser.
5. In the parser input field, select the raw body, file content, API response, or mapped value from the previous step.
6. Test the parser.
7. Check whether Bit Flows returns clean fields, rows, tags, or nested values.
8. Map the parsed fields to the next action.
9. Use logs to confirm what data was received, parsed, and sent.

Once the parser creates clean fields, you can use those fields in actions, conditions, routers, AI Agent prompts, emails, logs, and app connections.

For CSV files with multiple rows or JSON arrays with multiple items, add Iterator after the parser. This lets Bit Flows process one row or item at a time.

Practical Parser Use Cases

Bit Flows parsers are useful when your workflow needs to handle structured data before sending it somewhere else. Common use cases include:

• Parse webhook data and save it to Google Sheets
• Extract order values from a JSON payload
• Process CSV lead records and add them to a CRM
• Parse XML product feeds before updating WooCommerce
• Read API response data and send alerts to Slack or Telegram
• Send parsed support data to AI Agent for summary or routing
• Use parsed values inside Gmail, webhooks, or custom API requests

Common Parser Issues and How to Fix them

Parser issues usually come from wrong input mapping, invalid data format, or missing loop handling. Use the checks below to find the cause faster and fix the workflow before sending data to the next step.

Cleaner data, better workflows

Parser tools are small, but they solve a common automation problem. They turn messy webhook, API, feed, and report data into fields your workflow can actually use.

Use JSON Parser for API and webhook payloads. Use CSV Parser for row-based records. Use XML Parser for feeds and older systems. After that, you can route, filter, map, summarize, notify, or send the data anywhere your Bit Flows workflow needs it.

よくある質問