Assessor Financeiro ToolInstall

Summary

Create a financial transaction for the specified user, recording an expense, income, or transfer through the Assessor Financeiro API. Connect the node as an AI Tool and provide the user’s phone number in the workflow; the AI can supply transaction details such as amount, description, category, accounts, dates, payment method, and optional receipt or category splits.

Inputs

• Telefone (required) — User’s phone number, supplied by the workflow rather than the AI.
• Descrição da Tool — Optional guidance that tells the AI when to use this tool.
• Tipo, Valor (R$), Descrição, Categoria — Transaction kind (expense, income, or transfer), amount in reais, short description, and category name. These fields default to expense, 0, and empty strings; category should match the user’s category list.
• Conta Bancária, Conta Destino — Optional source or receiving account name. For transfers, set the source in Conta Bancária and the receiving account in Conta Destino; leave account names blank to use the default account where applicable.
• Data, Status, Data de Vencimento, Data do Pagamento — Optional transaction date (YYYY-MM-DD; blank means today), confirmed or pending status, due date for pending transactions, and actual payment date when it differs from the transaction date. Do not set Data do Pagamento for pending transactions.
• Notas, Forma de Pagamento, Cartão, Natureza (PF/PJ) — Optional notes, payment method, card name, and transaction nature (pf or pj).
• Input Original da IA, Confiança da IA — Optional original user message and AI confidence score from 0 to 1.
• URL do Comprovante, Comprovante (Base64), Nome do Arquivo, Tipo do Arquivo, ID do Attachment — Optional receipt details: provide a URL or base64 file with its filename and MIME type, or an existing temporary attachment ID.
• Splits (Divisão por Categoria) — Optional JSON array of category splits. Each split can include categoryId, amountCents, and description; product details such as quantity, unit, and unitPriceCents are also supported. The split amounts should sum to the transaction total.

Output shape

A list of items, each containing the API response for the created transaction.

The node sends a create_transaction request with the phone and non-empty transaction fields. Invalid splits JSON is ignored. If Continue On Fail is enabled, a failed item returns an error field instead of stopping the node.

Links

• n8n community nodes installation guide