Build it
What do you want DocuPipe and Reepay to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with DocuPipe and Reepay
Triggers and actions 1 trigger ยท 35 actions
Trigger
Document ProcessedTriggers when a document finishes parsing and OCR is complete.
Action
Add schemaCreates a new extraction schema in DocuPipe from a JSON schema you supply, and returns its schema ID.
Action
Analyze documentAsks DocuPipe a list of plain-language questions about one document and starts the analysis, returning the analysis ID to fetch the answers with.
Action
Classify DocumentSends one or more documents to DocuPipe to be sorted into your classes, and returns the job that is doing the work.
Action
Delete documentRemoves a document from your DocuPipe account.
Action
Delete schemaRemoves an extraction schema from your DocuPipe account.
Action
Extract Data From DocumentPulls structured data out of a document using one of your schemas, and returns the extraction to fetch the results with.
Action
Find documents by criteriaFinds documents in your DocuPipe account whose file name or document ID matches what you search for.
Action
Get DocumentReturns one document from your DocuPipe account, with its file details, processing status, parsed text and your own metadata.
Action
Get Extraction ResultReturns the data DocuPipe pulled out of a document, shaped by the schema that was used, along with per-field confidence details.
Action
Get schemaReturns one extraction schema from your DocuPipe account, including the JSON schema it applies and its guidelines.
Action
List documentsReturns the documents in your DocuPipe account, optionally narrowed to one dataset or a date range.
Action
List extractionsReturns the data extractions in your DocuPipe account, optionally narrowed to one schema, one document, or a specific set of extractions.
Action
List schemasReturns the extraction schemas in your DocuPipe account.
Action
Upload and Extract DataSends a file to DocuPipe and immediately starts pulling structured data out of it, returning both the new document and the extraction.
Action
Upload DocumentSends a file to DocuPipe to be read and turned into a document you can extract data from.
Action
Add couponCreate a new coupon. POST /v1/coupon
Action
Add creditCreate a credit note/credit for a customer. POST /v1/credit
Action
Add customerCreate a new customer. POST /v1/customer
Action
Add invoiceCreate an invoice for a customer. POST /v1/customer/{handle}/invoice
Action
Add planCreate a new subscription plan. POST /v1/plan
Action
Add subscriptionCreate a new subscription for a customer. POST /v1/subscription
Action
Cancel subscriptionCancel a subscription by handle. POST /v1/subscription/{handle}/cancel
Action
Delete customerDelete a customer by handle. DELETE /v1/customer/{handle}
Action
Get chargeRetrieve a charge by handle. GET /v1/charge/{handle}
Action
Get couponRetrieve a coupon by handle. GET /v1/coupon/{handle}
Action
Get customerRetrieve a customer by handle. GET /v1/customer/{handle}
Action
Get invoiceRetrieve an invoice by id. GET /v1/invoice/{id}
Action
Get planRetrieve the current version of a plan by handle. GET /v1/plan/{handle}/current
Action
Get subscriptionRetrieve a subscription by handle. GET /v1/subscription/{handle}
Action
List customersList all customers. GET /v1/list/customer
Action
List invoicesList all invoices. GET /v1/list/invoice
Action
List plansList all plans. GET /v1/list/plan
Action
List subscriptionsList all subscriptions. GET /v1/list/subscription
Action
Update customerUpdate an existing customer by handle. PUT /v1/customer/{handle}
Action
Update subscriptionChange/update an existing subscription by handle. PUT /v1/subscription/{handle}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.