OWNER SUBMISSION REQUIRED

ZAPIER CONNECTOR

Put an AP control step inside a Zap.

The connector package is implemented, tested, and clean against Zapier's current CLI validator. It is not yet listed in the Zapier App Directory; the owner must create the developer integration, run live Zap tests, and submit it for review.

INSTANT TRIGGER

New Invoice Analysis Result

Starts a Zap from a verified AP Control webhook when an analysis completes, requires review, is blocked, or fails.

ACTION

Submit Invoice for Analysis

Queues a normalized invoice with a retry-stable idempotency key derived from the Zap and upstream source reference.

ACTION

Validate Invoice

Returns deterministic field, date, currency, line, and arithmetic exceptions immediately.

SEARCH

Find Invoice History Matches

Returns exact and near-match candidates from only the connected organization.

CONNECTION SECURITY

A separate key, with explicit permissions.

Zapier sends the workspace key only in the authorization header. Users can issue and revoke a dedicated key with read, write, and webhook permissions. Signed result hooks are verified with HMAC-SHA256 before a Zap receives the minimized event.

Open API-key settings →

PRODUCT BOUNDARY

Control results, never accounting writes.

The connector cannot approve an invoice, create a bill, change vendor details, post a reconciliation, or initiate payment. Consequential actions remain in the customer's separately authorized workflow.

Review security controls →

Use the available integration paths today.

Until Zapier approves and lists the connector, use the live REST API, remote MCP server, Postman collection, n8n starter flow, or the public RapidAPI listing.