hdls CRM

hdls CRM gives your AI assistant a complete sales backend — accounts, the people who work at them, the deals in flight, and a timeline of everything that happened — without a single screen to navigate. Tell your assistant "create an account for Northwind, add Ada as the champion, open a Q3 expansion deal, and log today's call," and it does exactly that.

Because the headline entity is the account, the natural flow is top-down: create the account first, then hang contacts and deals off it, then keep the relationship warm by logging activity and reading it back with a single summarize_account.

Common workflows

  • Land a new logo: create_accountcreate_contactcreate_deallog_activity.
  • Advance a deal: move_deal_stage as it progresses, log_activity after every touch.
  • Prep for a call: summarize_account to pull the record plus its recent timeline in one shot.

hdls CRM is a headless, MCP-native customer relationship management backend. It manages accounts (companies), contacts (people), deals, and activity timelines, operated entirely through named tools your AI assistant calls. It stands in for tools like Salesforce, HubSpot — same job, no UI to run.

💬 Just ask

"Add Acme as an account and log that I had a kickoff call." · "Show me the deals closing this month."

You don't call these tools yourself — just tell your assistant in plain English. Everything below is the reference for when you (or your assistant) want the exact details.

How CRM is organized

The headline entity is the account — start there, then attach the rest to it. Records connect by reference: a contact links to an account; a deal links to an account and a contact. The activity table is an append-only timeline — every change and note lands there and is never edited or deleted.

EntityPurposeRelates to
accountThe headline account — every other record hangs off this.
contactA contact linked to an account.account
dealA deal linked to an account and a contact.account, contact
activityAppend-only timeline of changes and notes.

Tools

Call these at https://hdls.ai/api/mcp/crm. Required fields you must supply; optional fields refine the call. You never pass tenant_id — it is stamped server-side.

Create

ToolWhat it doesRequiredOptional
create_accountCreate a new account.namedomain, industry, website, owner, annual_revenue, employee_count
create_contactCreate a new contact.nameaccount_id, email, company, title, tags, data
create_dealCreate a new deal.titleaccount_id, contact_id, stage, value, currency, owner

Update & advance

ToolWhat it doesRequiredOptional
update_accountUpdate an existing account by id.idname, domain, industry, website, owner
update_contactUpdate an existing contact by id.idname, account_id, email, company, title
move_deal_stageMove a deal to a new pipeline stage (sets its stage).id, stage

Find & read

ToolWhat it doesRequiredOptional
search_accountsSearch accounts by free-text and/or column filters (tenant-scoped, paginated).search, filters, limit, orderBy
search_contactsSearch contacts by free-text and/or column filters (tenant-scoped, paginated).search, filters, limit, orderBy
summarize_accountFetch an account plus its most recent timeline activity in one call.idactivityLimit

Timeline

ToolWhat it doesRequiredOptional
log_activityAppend an entry to the append-only activity timeline.entity_type, entity_id, kindbody

Field lists come from the product's live schema and are embedded in each tool's own description — read the tool description for the exact, current fields.

Field reference

Every field you can set on each record. Custom fields you add live alongside these in data.

account

FieldTypeRequiredNotes
nametextYesDisplay name.
domaintext
industrytext
websitetext
ownertext
annual_revenuenumeric(16,2)
employee_countnumber
statustextLifecycle state.
tagslistFree-form labels.
datajsonFree-form JSON — custom fields live here.

contact

FieldTypeRequiredNotes
account_ididLinks to an account.
nametextYesDisplay name.
emailtext
companytext
titletextDisplay name.
tagslistFree-form labels.
datajsonFree-form JSON — custom fields live here.

deal

FieldTypeRequiredNotes
account_ididLinks to an account.
contact_ididLinks to a contact.
titletextYesDisplay name.
stagetextLifecycle state.
valuenumeric(14,2)
currencytext
ownertext
close_datedate
datajsonFree-form JSON — custom fields live here.

Tailor it with custom fields

Add fields without a schema change. add_custom_field defines one, list_custom_fields shows what's defined, and promote_custom_field (admin) shares a personal field with the whole workspace. The value lives in each row's data (JSON) and is set and read through the normal record tools. See Products, tools & custom fields for the full model.

Roles & safety

  • Tenant isolation is automatic. Your credential is pinned to one workspace; you never pass tenant_id, and you can only ever see your own data (enforced by Postgres row-level security).
  • Role-gated. Permissions run reader < member < admin < owner. Installing a product and promoting a custom field workspace-wide need admin/owner.
  • History is append-only. The activity timeline is never edited or deleted — it's your audit trail.

Connect

On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "crm" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/crm as a connector in your assistant — see Connect your assistant.

A worked example

The literal call your assistant makes when you ask it to create the headline record:

Tool: create_account
Arguments: {
  "name": "Acme Corp"
}

See All products · Connect your assistant · Automation