Connectors

PolDex connects to existing workflows without replacing them.

The connector layer is deliberately thin: every adapter runs on the same API, webhook, processor, signed-link, and export rails. No duplicate workflow product. No second truth system.

PolDex is the first dedicated insurance truth layer, turning raw documents or parser output into evidence-backed, schema-controlled insurance data.

Keep your existing parser. Send parsed text, markdown, JSON, tables, or parser events to PolDex for FastScript adjudication and insurance schema enforcement.

Read Connector Docs ->Parser Compatibility

Phase 1

First connector tracks.

These are source-ready connector packages in the repo. Public marketplace listing still depends on each platform account, review, and approval process.

Source Ready

n8n

Self-hosted automation nodes for credits, schemas, batch estimate, batch creation, status polling, result download, flattening, and completed-work triggers.

Marketplace Ready

Zapier

Zapier app source with API-key auth, URL/text/batch actions, status lookup, credit lookup, and a polling trigger powered by connector events.

Source Ready

Google Sheets

CSV/XLSX import workflow plus Apps Script direct-write connector that checks credits, creates batches, polls status, flattens results, and writes rows.

Source Ready

Parser Output

Generic import rail for customer-provided text, markdown, JSON, tables, and parser events from Hyperscience, Docugami, Unstructured, LlamaParse, cloud OCR, or internal parsers.

Source Ready

Reducto

Compatibility rail for teams that already use Reducto. Keep Reducto in place, then import Parse output into PolDex for insurance truth, evidence, exports, and connector events.

Parser Output

Use Hyperscience, Docugami, Reducto, Unstructured, or your own parser.

PolDex sits underneath the workflow as the insurance truth layer. Parser output is treated as customer-provided input. FastScript then applies insurance-specific evidence, conflicts, truth states, abstention, and schema contracts.

Because the customer has already paid the parsing cost elsewhere, parser-output import uses a lighter credit policy: 50% off the normal page-band credit estimate, with a 1-credit minimum.

HyperscienceDocugamiReductoUnstructuredLlamaParseGeneric markdownTextJSON

curl -X POST https://poldex-api.plain-water-cd0f.workers.dev/v1/connectors/parser-output/import \
  -H "x-api-key: pd_live_YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{
    "schema": "coi",
    "source_parser": "docugami",
    "client_ref": "existing-parser-run-001",
    "markdown": "CERTIFICATE OF LIABILITY INSURANCE..."
  }'

Workflow Rails

One extraction engine, many entry points.

API

For developers wiring PolDex into backend systems.

Webhooks

For real-time completion delivery into existing services.

Processor

For operations teams that need upload, process, download.

Email Intake

For inbox-led workflows where documents arrive as attachments.

Signed Links

For third-party submissions without a customer portal.

CSV/XLSX

For legacy spreadsheets, procurement teams, and ops handoffs.

SDK

Shared connector SDK.

Connector authors use @poldex/connector-sdk instead of rewriting auth, errors, retries, result downloads, webhook verification, and flattening logic.

getCreditslistSchemasgetSchemaclassifygetCorpusStatusgetBenchmarkStatusgetSchemaVersionsgetSchemaMemoryestimateBatchcreateBatchgetBatchgetJoblistJobArtifactsdownloadResultdownloadBatchArtifactlistConnectorEventslistExtensionApisgetExtensionApiclassifyExtensionestimateExtensionextractExtensiongetParserOutputConnectorimportParserOutputgetReductoConnectorimportReductoParseOutputsendWebhookTestverifyWebhookSignatureflattenResultToRows

Polling Rail

Connector events for automation tools.

Webhooks remain the preferred real-time path. For tools that require polling, connectors read completed work through GET /v1/connector/events.

curl "https://poldex-api.plain-water-cd0f.workers.dev/v1/connector/events?since=2026-04-24T00:00:00Z&limit=25"   -H "x-api-key: pd_live_YOUR_KEY"

Reducto Import

Use PolDex alongside Reducto without switching.

Customers already using Reducto can keep their existing parsing workflow and post parse JSON, markdown, text, or adapted async event payloads into PolDex. PolDex does not expose its internal document-reading stack. This rail simply lets Reducto users add FastScript's insurance schema truth layer after their current Reducto step.

curl -X POST https://poldex-api.plain-water-cd0f.workers.dev/v1/connectors/reducto/import \
  -H "x-api-key: pd_live_YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{
    "schema": "coi",
    "client_ref": "reducto-parse-001",
    "parse_result": { "markdown": "CERTIFICATE OF LIABILITY INSURANCE..." }
  }'

Template Universe

Automation templates are source-ready.

These local templates are ready-to-submit packages and workflow shapes. Public marketplace approval remains unclaimed until each platform review accepts PolDex.

MakePipedreamAirtableSmartsheetGoogle DriveOneDriveSharePointDropboxBoxSlackMicrosoft TeamsHubSpotSalesforce

Build on the connector rail.

Start with docs or use the processor review cockpit to confirm the workflow before wiring an adapter.

Reducto Integration ->Parser Compatibility ->Read Connector Docs ->Connector Roadmap