Skip to content
Nappai Documentation

Holded CRM Component

The Holded CRM Component lets you interact with Holded’s CRM system directly from your Nappai dashboard.
Choose a resource (Funnels, Leads, Events, or Bookings) and an operation (List, Create, or Get) to retrieve or modify data.
All requests are sent to Holded’s API using the API key you store in a credential, so you never have to type the key into the component itself.

How it Works

When you run the component, Nappai builds a request to Holded’s REST API.
The component first reads the selected Resource and Operation.
It then calls the corresponding helper function (holded_funnels_execute, holded_leads_execute, etc.) which builds the correct HTTP request, sends it to Holded, and returns the JSON response wrapped in a Message.
If the component is used as a tool for an agent, the to_toolkit method turns the same information into a tool object that the agent can call.

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: Select the type of CRM resource you want to work with, such as Funnels, Leads, Events, or Bookings.
  • Operation: Choose the action you want to perform on the selected resource, like List, Create, or Get.
  • Tool Name: Specify the name that will appear to the agent when this component is used as a tool.
  • Tool Description: Provide a detailed description of what the tool does so the agent can decide when to use it.
  • Tools arguments metadata: Define the metadata for the arguments that the tool will accept.

Outputs

  • Response: A Message object containing the raw JSON response from Holded’s API. This can be passed to other components or displayed in the dashboard.
  • Tool: A Tool object that can be used by an agent when the component is connected as a tool.

Usage Example

  1. Set up the credential

    • In the Nappai credentials section, create a new Holded Task API credential.
    • Sign in to Holded and copy your API key into the credential.
    • In the component, select this credential from the Credential field.

  2. List all leads

    • Set Resource to Leads.
    • Set Operation to List.
    • Run the component.
    • The Response output will contain a list of all leads in your Holded account.

  3. Create a new event (optional)

    • Set Resource to Events.
    • Set Operation to Create.
    • Provide the required fields for the event (e.g., title, date) in the dynamically generated input fields that appear after selecting the operation.
    • Run the component.
    • The Response output will show the details of the newly created event.
  • Holded CRM Component – The primary component for interacting with Holded CRM resources.
  • Holded API Component – (If available) A lower‑level component that exposes all Holded API endpoints.

Tips and Best Practices

  • Use Mapping Mode when you need to process many records at once; it saves time and reduces manual input.
  • Keep your API key secure by storing it in a credential and never hard‑coding it in the component.
  • Define clear tool names and descriptions so agents can choose the right tool quickly.
  • Validate the Response before passing it to downstream components to avoid errors in your workflow.

Security Considerations

  • The component never exposes your Holded API key in the UI; it is retrieved securely from the credential store.
  • Ensure that only trusted users have access to the credential that contains the API key.
  • When using the component as a tool, limit the tool’s visibility to agents that require access to Holded data.