Holded connector for AI agents

Tools your back office agent reaches for on Holded, scoped per user.

CALL ANY TOOL

109 tools for accounting in Holded: create, send, and convert invoices, estimates, and orders, record payments and ledger entries, manage contacts and funnel leads, track product stock, and log project time.

holded_accounting_account_create

Create accounting account

Create an account in the chart of accounts, using a group prefix and optionally a specific number. Returns the id of the affected record. Use to add ledger accounts; prefix is the 1-4 digit group code, not the full account number.

Parameters

Name

Type

Required

Description

name

string

Required

Display name for the accounting account. Example: Acme Corp.

prefix

integer

Required

Chart-of-accounts group code (1-4 digits). The full account number is auto-assigned within this group when `number` is absent. Must be 1-4 digits. Example: 4300.

color

string

Optional

Hex color code for UI display. Example: blue.

description

string

Optional

Optional description of the account purpose. Example: Consulting services for Q1.

number

integer

Optional

Exact account number to assign (e.g. 70000013). Must start with `prefix`. When provided the number is used as-is and must be unique; otherwise the next available number in the group is assigned.

holded_accounting_accounts_list

List accounting accounts

holded_bank_account_get

Get bank account

holded_contact_update

Update contact

Update an existing contact; only the fields you pass are changed. Returns status. Use to edit a contact; use the create tool for new records. Needs the contact ID from holded_contacts_list.

Parameters

Name

Type

Required

Description

contact_id

string

Required

Contact ID (24-char hex ObjectId). Example: 507f1f77bcf86cd799439011.

name

string

Required

Contact full name or company name. Example: Acme Corp.

bill_address

object

Optional

Billing address. Example: {"address": "Calle Mayor 1", "city": "Madrid", "postal_code": "28013", "country_code": "ES"}.

client_record

integer

Optional

Number of the accounting account (chart of accounts) used when this contact acts as a client. Example: 430000.

code

string

Optional

Tax identification number (NIF, CIF, etc.). Example: B12345678.

contact_persons

array

Optional

Linked contact persons (by their contact ID). Example: [{"person_id": "507f1f77bcf86cd799439011"}].

custom_fields

array

Optional

User-defined custom fields. Example: [{"field": "Example field", "value": "5000"}].

defaults

object

Optional

Default settings applied to documents created for this contact. Example: {"payment_method_id": "507f1f77bcf86cd799439011"}.

string

Optional

Primary email address. Example: billing@example.com.

iban

string

Optional

IBAN bank account number. Example: ES9121000418450200051332.

is_person

boolean

Optional

True if the contact is an individual, false if a company. Example: true.

mobile

string

Optional

Mobile phone number. Example: +34600000000.

phone

string

Optional

Landline phone number. Example: +34910000000.

sepa_date

string

Optional

Date the SEPA direct debit mandate was signed. Example: 2026-01-15.

sepa_ref

string

Optional

SEPA mandate reference for direct debit collections. Example: MANDATE-001.

supplier_record

integer

Optional

Number of the accounting account (chart of accounts) used when this contact acts as a supplier. Example: 400000.

swift

string

Optional

SWIFT/BIC code of the bank. Example: CAIXESBBXXX.

tags

array

Optional

Tags attached to the contact. Example: ["priority","2026"].

trade_name

string

Optional

Commercial or trade name, if different from legal name. Example: Acme Corp.

type

string

Optional

Contact classification. Allowed values: client, debtor, supplier, creditor, lead. Example: client. One of: `client`, `debtor`, `supplier`, `creditor`, `lead`.

vat_number

string

Optional

EU VAT number. Example: ESB12345678.

website

string

Optional

Website URL. Example: https://www.example.com.

holded_contacts_list

List contacts

holded_contacts_search

Search contacts

holded_credit_note_get

Get credit note

holded_document_convert

Convert document

holded_estimate_create

Create estimate

Create a estimate in Holded. Returns the id of the affected record. Use to create a new estimate for a contact; use holded_document_convert to derive one from an existing document instead. Needs a contact ID from holded_contacts_list or holded_contact_create.

Parameters

Name

Type

Required

Description

contact_id

string

Required

Identifier of an existing contact. Example: 507f1f77bcf86cd799439011.

items

array

Required

Line items to include. Example: [{"name": "Consulting services", "units": 1, "price": 100}].

contact_name

string

Optional

Name of the contact. Example: Acme Corp.

currency

string

Optional

ISO 4217 currency code. Example: EUR.

currency_change

number

Optional

Exchange rate. Example: 1.08.

custom_fields

array

Optional

Custom field values. Example: [{"field": "Example field", "value": "5000"}].

date

string

Optional

Issue date in ISO 8601 format. Accepts date (YYYY-MM-DD) or datetime (e.g. 2026-01-15T00:00:00+00:00).

description

string

Optional

Free-text description. Example: Consulting services for Q1.

design_id

string

Optional

Identifier of the design template to apply to the document. Example: 507f1f77bcf86cd799439011.

discount

number

Optional

Global discount percentage. Example: 10.

due_date

string

Optional

Expiry date in ISO 8601 format. Accepts date (YYYY-MM-DD) or datetime (e.g. 2026-01-15T00:00:00+00:00).

language

string

Optional

ISO 639-1 language code. Example: es.

notes

string

Optional

Internal notes visible only to your team. Example: Payment due within 30 days.

number

string

Optional

Custom document number. Use only if you do not want to assign the number via one of the numbering series created in Holded (e.g. to replicate exactly the number from another platform). The value is saved as-is, without correlativity validation. If this field is sent, number_line_id is ignored. Warning: do not use a value that matches the format of an existing numbering series. The series keeps its own counter regardless of manually assigned numbers -- e.g. if a series is at number 24 and you manually create a document with 27, the series will keep issuing 25, 26, and when it reaches 27 it will try to create a number that already exists: the request will fail and the series will have lost its correlativity and order. If you need custom numbering, use a prefix or format that does not match any active series, or manage every document in that series with number_line_id.

number_line_id

string

Optional

Identifier of the numbering series used to automatically assign the next correlative number. This is the recommended option, as it preserves the document order and correlativity. If both fields are sent, number takes priority and number_line_id is ignored. Example: 507f1f77bcf86cd799439011.

payment_method_id

string

Optional

Identifier of the default payment method. Example: 507f1f77bcf86cd799439011.

sales_channel_id

string

Optional

Identifier of the sales channel. Example: 507f1f77bcf86cd799439011.

show_total

boolean

Optional

Whether to show the total row in the PDF. Example: true.

tags

array

Optional

List of tag names. Example: ["priority","2026"].

taxes

array

Optional

Tax keys applied to this product. Accepts the human tax name (e.g. "IVA 21%") or the internal key (e.g. "s_iva_21"); resolved automatically.

variants

array

Optional

Variants of the product (for variants, lots and serial numbers product types). Sending this field replaces all existing variants. Example: [{"price": "100", "sku": "SKU-1001", "id": "507f1f77bcf86cd799439011"}].

warehouse_id

string

Optional

Default warehouse identifier for this product. Example: 507f1f77bcf86cd799439011.

weight

number

Optional

Weight in account default unit. Example: 1.5.

holded_project_create

Create project

holded_project_summary_get

Get project summary

holded_project_time_entries_list

List project time entries

holded_purchase_payment_create

Create purchase payment

holded_purchase_update

Update purchase

holded_remittances_list

List remittances

holded_sales_order_get

Get sales order

holded_service_create

Create service

holded_tags_list

List tags

holded_task_get

Get task

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Holded tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["holded"], toolNames: [
    "holded_invoices_list",
    "holded_invoice_send",
    "holded_contacts_list"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Find last month's unpaid invoices and email each one to its customer again" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["holded"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Find last month's unpaid invoices and email each one to its customer again" }],
  tools,
});

// Execute the tool call with the user's vaulted Holded access token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["holded"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Find last month's unpaid invoices and email each one to its customer again" }],
  tools,
});

// Tool call runs with the user's vaulted Holded access token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["holded"] }, pageSize: 100,
});

const agent = new Agent({
  name: "back_office_agent",
  model: "gemini-2.5-pro",
  instruction: "Holded tools scoped to this user",
  tools,
});

await agent.run("Find last month's unpaid invoices and email each one to its customer again");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Holded tool. Click to copy, paste into your agent, done.

Invoicing

Copy the prompt

Copied

Create an invoice for Distribuciones Norte for 40 units of SKU-118.

Copy the prompt

Copied

Email invoice F260112 to the customer.

Copy the prompt

Copied

Convert the accepted estimate for Bodega Sur into an invoice.

CRM and contacts

Copy the prompt

Copied

Add a lead for Café Lumen to the Wholesale funnel.

Copy the prompt

Copied

Move the Café Lumen lead to the Proposal stage.

Copy the prompt

Copied

Find contacts whose name starts with Mar.

Stock and projects

Copy the prompt

Copied

What is the stock of SKU-118 in each warehouse?

Copy the prompt

Copied

Lower SKU-118 stock in the Madrid warehouse by 12.

Copy the prompt

Copied

Log 4 hours on the Website Relaunch project for today.

SEE HOW AUTH WORKS

Each user connects their own Holded access token once, and Scalekit sends it with every call. Access tokens stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Holded

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Holded

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Holded

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Holded

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other accounting and CRM connectors.

GTM and RevOps Teams

Revenue forecast commentary

Pulls open pipeline from Salesforce and HubSpot, calculates coverage against quota, flags at-risk stages, posts commentary to Slack, and logs every snapshot to Google Sheets.

GTM and RevOps Teams

CRM AI agent

Reads the Granola transcript after every call, extracts next steps and updates the HubSpot record, drafts the follow-up in Gmail, and confirms in Slack, all on the rep's own delegated OAuth.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Holded access token looks fine in a demo. In production every invoice and ledger entry looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Holded today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Holded as the user or through a shared access token?

As the user. Each user connects their own Holded access token once, and Scalekit sends it with every call. Audit logs attribute every invoice, payment, and ledger entry to that user, not a shared service account.

Where is the Holded access token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new access token. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Holded?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example the list and get tools without holded_invoice_cancel, which voids a sales invoice, or holded_ledger_entry_create, which posts manual journal entries. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Holded access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does the agent reach Holded projects and team data too?

Yes. Besides invoicing and accounting, the tools list projects, tasks, and time entries, create tasks and log time on projects, and read employees and time-off requests such as holidays and sick leave.