Skip to content
Nappai Documentation

Holded Invoice Component

The Holded Invoice Component lets you interact with the Holded API to manage a wide range of invoice‑related resources. Whether you need to list existing Treasury Accounts, create new Contacts, or retrieve a specific Tax record, this component handles the communication with Holded and returns the data you need for your workflow.

How it Works

When you add the component to your dashboard, it connects to the Holded API using the API key you provide through the Credential field. The component then performs the action you select in the Operation dropdown (List, Create, or Get) on the resource you choose in the Resource dropdown. The result is returned as a Message that can be used by other components or by an AI agent.

If you enable Mapping Mode, the component can process many records at once. Each input field can receive a single fixed value, a value from another component, or a value calculated with JavaScript, allowing you to build powerful batch workflows.

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.

Input Fields

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

  • Mapping Mode: Enable mapping mode to process multiple data records in batch.
  • Resource: Choose which type of invoice resource you want to work with. Options include Treasury Accounts, Contacts, Expenses Accounts, Numbering Series, Products, Sales Channels, Warehouses, Payments, Taxes, Documents, Contact Groups, Remittances, and Services.
  • Operation: Select the action you want to perform on the chosen resource. Options are List, Create, and Get.
  • 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 the Holded API. This can be parsed or passed to other components in your workflow.
  • Tool: A Tool object that can be used by an AI agent to call this component programmatically.

Usage Example

  1. Add the component to your dashboard.
  2. Select a Credential: In the Credentials section, choose the pre‑configured Holded Task API credential that contains your Holded API Key.
  3. Configure the fields:
    • Resource: Treasury Accounts
    • Operation: List
  4. Run the component. The Response output will contain a JSON list of all Treasury Accounts in your Holded account. You can then feed this output into another component, such as a data transformer or a database writer.

If you want to create a new Contact, simply change Resource to Contacts and Operation to Create, then provide the required fields (e.g., name, email) in the dynamic input area that appears.

None

Tips and Best Practices

  • Start simple: Test the component with a single record before enabling Mapping Mode to ensure your API key and field mappings are correct.
  • Use fixed values for quick tests: When experimenting, set inputs to Fixed values to avoid accidental data changes.
  • Leverage Mapping Mode for batch jobs: When you need to process thousands of records, enable Mapping Mode and connect the component to a data source that streams records.
  • Validate responses: Use a JSON viewer or a data transformer to inspect the Response output before passing it to downstream components.

Security Considerations

  • Keep your Holded API Key confidential. Store it in the Holded Task API credential and never expose it in plain text.
  • Use the credential system in Nappai to manage API keys securely. Only users with the appropriate permissions can view or edit credentials.
  • When enabling Mapping Mode, be cautious about the volume of data you process to avoid unintentionally sending large payloads to the Holded API.