Team
Shared credential for production and unattended runs.
Finmei is an invoicing tool designed to simplify billing processes, allowing users to create and manage invoices and track expenses efficiently.
Tools and triggers
Available tools and events after Finmei is connected.
Tool to create a new expense with file upload (receipt or invoice). Use when you need to record an expense with supporting documentation. Requires multipart/form-data submission with file, date, total, currency, and…
Creates a new invoice in Finmei with buyer information and line items. Use this when you need to generate an invoice for a customer. You can specify: - Buyer details (person or company) - Products/services with…
Tool to delete a specific customer by their ID. Use after confirming the correct customer_id to remove the record.
Tool to delete an invoice. Use when you need to remove an existing invoice by its ID.
Delete a payment record by its unique identifier. This action permanently removes the payment from the system. Returns success even if the payment doesn't exist (idempotent operation). Use this when you need to remove…
Deletes a product from the Finmei catalog by its unique identifier. This operation is idempotent - calling it multiple times with the same product_id will return success. The tool attempts multiple endpoint patterns to…
Tool to download the file associated with an expense. Returns the expense document file (PDF or image). Use when you need to retrieve the actual file content for an expense.
Tool to download an invoice as a PDF file. Use when you need to retrieve the PDF version of an invoice.
Tool to retrieve a single expense by its ID. Use when you need to get details about a specific expense including date, total, currency, and seller information.
Tool to retrieve a single invoice by its ID. Use when you need full invoice details including buyer, seller, items, amounts, and payment options.
Tool to retrieve details of a specific payment by its ID. Use after creating a payment or when you need to confirm payment details.
Tool to retrieve a product by its ID. Use when you need detailed information about a single product.
Tool to retrieve main information about the business to which the API token is assigned. Use when needing business ID, title, type, address, VAT code, company name, or company code.
Tool to list all currencies supported by Finmei. Use when you need to retrieve available currency codes before creating transactions.
Tool to list all customers with optional filters and pagination. Use when needing to browse or search customer records.
Tool to list all expenses for the business. Use when you need a paginated list of expenses with metadata.
Tool to list invoices. Use when you need a paginated list of invoices with basic details.
Tool to retrieve a list of payments. Use when you need to view past payment records with optional filters and pagination.
Tool to retrieve a list of products with optional filters and pagination. Use when you need to browse or filter the product catalog.
Tool to update an existing customer's details. Use after confirming the customer ID to modify their information.
Tool to update an existing expense's fields including date, total, currency, and seller. Use when you need to modify expense details. To update the invoice/bill file, use the Update Expense File endpoint instead.
Updates the file attachment of an existing expense in Finmei. Use this action when you need to attach or replace a receipt/invoice file for an expense. This endpoint is specifically for updating the file only - use the…
Tool to update an existing invoice in Finmei. Use when you need to modify invoice details such as buyer information, products, dates, or currency.
Updates an existing product in the Finmei product catalog. Use this action when you need to modify product details such as name, description, price, or currency. You must provide the product ID and at least one field…
Setup
Pick a scope, then confirm what can start a Protege and what it can do.
What can start a Protege from this app.
What a Protege can do after it starts.
Prefer team for production.
Shared credential for production and unattended runs.
Tied to one user—only when the workflow needs their account.
Team-scoped for supported chat surfaces.
Build with us
Request early access or book a live walkthrough with the team.