Finmei is an invoicing tool designed to simplify billing processes, allowing users to create and manage invoices and track expenses efficiently.
Finmei is an invoicing tool designed to simplify billing processes, allowing users to create and manage invoices and track expenses efficiently. On Nagent, Finmei is exposed as a fully-configurable accounting integration that any agent can call — 24 actions, and API key authentication. No code is required to wire Finmei into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Finmei to automate the kinds of tasks accounting teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Finmei into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Finmei, with input parameters and output schema. Drop these into any step of an agent built in Helix.
FINMEI_CREATE_EXPENSETool 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 seller information.
Input parameters
Date of the expense in YYYY-MM-DD format
Receipt file (PDF or image).
Total amount of the expense, must be non-negative
Name of the seller/vendor from the invoice or receipt
Uppercase three-letter ISO 4217 currency code
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_CREATE_INVOICECreates 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 quantities and prices - Invoice type (regular, VAT, preliminary, credit) - Currency, dates, and custom notes Example: "Create an invoice for Tech Solutions Inc with 3 months of support services at $99.99/month"
Input parameters
Optional custom invoice code or reference
Invoice type required by API. Valid values: 'regular_invoice', 'vat_invoice', 'preliminary_invoice', 'preliminary_vat_invoice', 'credit_invoice', 'credit_vat_invoice'
Buyer object; required by API when not using customer_id
Optional notes to appear on the invoice
Seller object if not using default
Series code/prefix for the invoice
ISO 4217 three-letter currency code
Inline customer details; mutually exclusive with `customer_id`
Payment due date (YYYY-MM-DD)
Products array as required by API
Date the invoice was issued (YYYY-MM-DD)
List of line items for the invoice
ID of an existing customer; mutually exclusive with `customer`
Invoice date as expected by the API (YYYY-MM-DD)
If true, API will use default seller info instead of requiring seller object
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_DELETE_CUSTOMERTool to delete a specific customer by their ID. Use after confirming the correct customer_id to remove the record.
Input parameters
Unique identifier of the customer to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_DELETE_INVOICETool to delete an invoice. Use when you need to remove an existing invoice by its ID.
Input parameters
The unique identifier of the invoice to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_DELETE_PAYMENTDelete 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 incorrect, duplicate, or obsolete payment records.
Input parameters
Unique identifier of the payment to delete. This is typically returned from payment creation or list operations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_DELETE_PRODUCTDeletes 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 maximize compatibility across different Finmei API deployments. Use this when you need to: - Permanently remove a product from the catalog - Clean up discontinued or obsolete products - Remove test or duplicate product entries Note: If all API endpoints return 404, the action will succeed with a message explaining that the product doesn't exist or the API doesn't support deletion. This follows idempotent DELETE semantics.
Input parameters
Unique identifier of the product to delete. This is the product's ID as returned by list_products or get_product operations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_DOWNLOAD_EXPENSE_FILETool 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.
Input parameters
Unique identifier of the expense to download the file for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_DOWNLOAD_INVOICE_PDFTool to download an invoice as a PDF file. Use when you need to retrieve the PDF version of an invoice.
Input parameters
The unique identifier of the invoice to download as PDF
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_GET_EXPENSETool 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.
Input parameters
Unique identifier of the expense to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_GET_INVOICETool to retrieve a single invoice by its ID. Use when you need full invoice details including buyer, seller, items, amounts, and payment options.
Input parameters
Invoice ID to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_GET_PAYMENTTool to retrieve details of a specific payment by its ID. Use after creating a payment or when you need to confirm payment details.
Input parameters
Unique identifier of the payment to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_GET_PRODUCTTool to retrieve a product by its ID. Use when you need detailed information about a single product.
Input parameters
Unique identifier of the product to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_GET_PROFILETool 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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_LIST_CURRENCIESTool to list all currencies supported by Finmei. Use when you need to retrieve available currency codes before creating transactions.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_LIST_CUSTOMERSTool to list all customers with optional filters and pagination. Use when needing to browse or search customer records.
Input parameters
Page number to retrieve (must be >= 1)
Sort order, e.g., 'name_asc' or 'created_at_desc'
Search term to filter customers by name or email
Number of customers per page (1-100)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_LIST_EXPENSESTool to list all expenses for the business. Use when you need a paginated list of expenses with metadata.
Input parameters
Page number to retrieve (must be >= 1)
Number of expenses per page (1-100)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_LIST_INVOICESTool to list invoices. Use when you need a paginated list of invoices with basic details.
Input parameters
Page number to retrieve (must be >= 1)
Number of invoices per page (1-100)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_LIST_PAYMENTSTool to retrieve a list of payments. Use when you need to view past payment records with optional filters and pagination.
Input parameters
Number of payments to retrieve (default 20, max 100)
Number of payments to skip for pagination
Filter payments by status
Filter payments created on or before this date (ISO 8601 format)
Filter payments created on or after this date (ISO 8601 format)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_LIST_PRODUCTSTool to retrieve a list of products with optional filters and pagination. Use when you need to browse or filter the product catalog.
Input parameters
Filter products by name substring.
Page number for pagination (1-indexed).
Filter products by their status.
Number of products per page.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_UPDATE_CUSTOMERTool to update an existing customer's details. Use after confirming the customer ID to modify their information.
Input parameters
Full name of the customer
Email address of the customer
Phone number of the customer
Mailing address details
Additional metadata for the customer as key-value pairs
Unique identifier of the customer to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_UPDATE_EXPENSETool 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.
Input parameters
Unique identifier of the expense to update. Must be a valid existing expense ID.
Date of the expense in YYYY-MM-DD format. This field is required.
Total amount of the expense. Must be non-negative. This field is required.
Name of the seller from invoice. This field is required.
Uppercase three letter currency code (ISO 4217 format). Example: USD, EUR, GBP. This field is required.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_UPDATE_EXPENSE_FILEUpdates 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 Update Expense action for updating other expense fields like amount, date, or description. The file is uploaded using multipart/form-data content type and typically should be a PDF or image file of the bill/receipt.
Input parameters
Unique identifier of the expense to update the file for. Must be a valid existing expense ID.
File to upload as the expense attachment (usually PDF or image file of the bill).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_UPDATE_INVOICETool to update an existing invoice in Finmei. Use when you need to modify invoice details such as buyer information, products, dates, or currency.
Input parameters
Optional custom invoice code or reference
Invoice type. Valid values: 'regular_invoice', 'vat_invoice', 'preliminary_invoice', 'preliminary_vat_invoice', 'credit_invoice', 'credit_vat_invoice'
Buyer object with customer information
Optional notes to appear on the invoice
Seller object if not using default
Series code/prefix for the invoice
ISO 4217 three-letter currency code
Payment due date (alias). Format: YYYY-MM-DD
Products array with line items for the invoice
Unique identifier of the invoice to update
Date on the invoice. Format: YYYY-MM-DD
Payment due date. Format: YYYY-MM-DD
If true, API will use default seller info instead of requiring seller object
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FINMEI_UPDATE_PRODUCTUpdates 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 to update. The action returns the complete updated product details. Prerequisites: - The product must already exist in the system (obtain product_id from List Products action) - At least one update field (name, description, price, or currency) must be provided Note: This action will fail if the product doesn't exist or if the Finmei API instance doesn't support product management endpoints.
Input parameters
Updated name for the product. If provided, replaces the existing product name.
Updated price for the product in the specified currency. Must be non-negative. If provided, replaces the existing price.
Updated currency code for the product price (ISO 4217 format, e.g., USD, EUR, GBP). If provided, replaces the existing currency.
Unique identifier of the product to update. Must be a valid existing product ID.
Updated description for the product. If provided, replaces the existing description.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 44 agents privately built on Nagent that already use Finmei.
Build on Nagent
Connect Finmei to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Finmei, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Finmei is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Finmei is connected, you configure its 24 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Finmei steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Finmei event fires, the agent kicks off automatically.
Every Finmei action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Finmei ships with 24 pre-built accounting actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Finmei together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Finmei-based workflows tailored to your business.