Automation tools

Zapier, Make, and Power Automate all work the same way: they give you a URL, you paste it into Parsli, and extracted data flows into your automation.

Between them they reach thousands of applications, which makes this the answer whenever there is no direct integration.

Zapier

1. In Zapier, create a Zap with the Webhooks by Zapier trigger.
2. Choose Catch Hook and copy the URL.
3. In Parsli, under Outbound, add a Zapier integration and paste it.
4. Use the test action to send a sample payload.
5. Back in Zapier, build the rest of the Zap against the fields that arrive.

Step 4 matters — Zapier learns the payload shape from a real sample. Without it you are mapping fields blind.

Make

Identical shape:

1. Create a scenario with a Custom webhook module.
2. Copy the URL.
3. Add a Make integration in Parsli and paste it.
4. Send a test so Make can determine the data structure.

Power Automate

1. Create a flow with the When an HTTP request is received trigger.
2. Save the flow to generate the URL.
3. Add a Power Automate integration in Parsli and paste it.
4. Send a test.

What arrives

All three receive the same payload as a Webhook:

{
  "event": "document.processed",
  "parser_id": "6f3a1c88-...",
  "parser_name": "Supplier invoices",
  "document_id": "b71c9d02-...",
  "timestamp": "2026-08-07T09:14:22.481Z",
  "data": {
    "invoice_number": "INV-2026-0417",
    "total_amount": 1284.5,
    "line_items": [
      { "description": "Steel brackets", "quantity": 40, "unit_price": 12.5 }
    ]
  },
  "metadata": {
    "file_name": "northgate-0417.pdf",
    "source_type": "email",
    "page_count": 2
  }
}

Your extracted values are under data, keyed by your field names.

Tables need a loop

A Table field arrives as an array. Automation tools do not flatten arrays for you — to create one row per line item you need the tool's iterator: a Looping step in Zapier, an Iterator module in Make, Apply to each in Power Automate.

This is the most common thing to get stuck on. If only the first line item is landing, a loop is what is missing.

Empty values

A field the engine could not ground in the document arrives empty rather than guessed. Add a filter step for anything that must not proceed without a value — otherwise a blank total silently becomes a zero-value record downstream.

Sending documents the other way

These tools can also feed documents into Parsli. Point an HTTP action at the parser's Inbound webhook.

A common complete loop:

1. A Zap watches a Dropbox folder
2. It posts new files to the inbound webhook
3. Parsli extracts them
4. The outbound Zapier integration returns the data
5. A second Zap files it wherever it belongs

See from another system.

Automation tool or direct integration?

If Parsli connects to your target directly — QuickBooks, Xero, Zoho Books, Google Sheets — use the direct connection. Fewer moving parts, no per-task cost, and field mapping is handled for you.

Use an automation tool for everything else, or when you need logic in the middle: routing on a value, enriching from another source, notifying someone conditionally.