Skip to content
Nappai Documentation

Holded Accounting Component

The Holded Accounting Component lets you interact with Holded’s accounting data directly from your Nappai dashboard.
You can list existing entries or create new ones in either the Daily Ledger or the Chart of Accounts, all without writing code.

How it Works

When you run the component, it connects to Holded’s API using the API key you stored in a Holded Task API credential.
Based on the Resource and Operation you choose, the component builds the appropriate request, sends it to Holded, and returns the API’s response as a Message.
If you connect the component as a tool, it also exposes a Tool output that can be used by Nappai’s AI agents.

Inputs

Mapping Mode

This component has a special mode called “Mapping Mode”. When you enable this mode using the toggle switch, an additional input called “Mapping Data” is activated, and each input field offers you three different ways to provide data:

  • Fixed: You type the value directly into the field.
  • Mapped: You connect the output of another component to use its result as the value.
  • Javascript: You write Javascript code to dynamically calculate the value.

This flexibility allows you to create more dynamic and connected workflows.

Note: This component requires a Holded Task API credential.

  1. Configure the credential in the Nappai credentials section.
  2. Select that credential in the component’s Credential field.

Input Fields

The following fields are available to configure this component. Each field may be visible in different operations:

  • Resource: Select the Holded resource you want to work with, such as Daily Ledger or Chart of Accounts.
  • Operation: Choose the action to perform on the selected resource, like List all entries or Create entry.
  • Tool Name: The name of the tool that will be used when this component is connected as a tool. This name will be displayed to the agent when it selects tools to use.
  • Tool Description: A detailed description of what this tool does. This description will help the agent understand when and how to use this tool effectively.
  • Tools arguments metadata: Defines the arguments metadata for the tools.

Outputs

  • Response: A Message containing the raw response from Holded’s API. You can use this output to feed into other components or to display results to users.
  • Tool: A Tool object that can be used by Nappai’s AI agents when the component is connected as a tool.

Usage Example

  1. Set up the credential

    • Go to Credentials → Add Credential → Holded Task API
    • Enter your Holded API Key and save.

  2. Add the component to your workflow

    • Drag the Holded Accounting Component onto the canvas.

  3. Configure the component

    • Credential: Select the credential you just created.
    • Resource: Choose Daily Ledger.
    • Operation: Choose List all entries.
    • (Optional) Set Tool Name and Tool Description if you plan to use it as a tool.

  4. Run the workflow

    • Click Run.
    • The Response output will contain a JSON list of all ledger entries, which you can then parse or display.
  • Holded API Component – A lower‑level component that lets you call any Holded API endpoint directly.
  • Data Formatter Component – Use this to transform the JSON response into a table or CSV for easier analysis.

Tips and Best Practices

  • Use Mapping Mode when you need to process many records at once; it lets you feed a list of IDs or data objects into the component.
  • Keep your API key secure by storing it in a credential, not in the component’s fields.
  • Test with the List all entries operation first to verify connectivity before attempting to create new records.
  • If you’re using the component as a tool, give the tool a clear, descriptive name so the AI agent can choose it confidently.

Security Considerations

  • The API key is stored in a credential and never exposed in the component’s UI.
  • Ensure that only trusted users have access to the credential in Nappai.
  • When sharing workflows, avoid exporting the component with the credential attached; instead, share the workflow template and let each user configure their own credential.