Teamleader Focus
Manage contacts, companies, deals and users in Teamleader Focus, the Belgian CRM / invoicing / project-management SaaS.
About
Teamleader Focus ships in the w6w first-party pack. It declares 15 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.teamleader- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management
Overview
Teamleader Focus is a Belgian CRM, invoicing and project-management SaaS. This app covers its core CRM surface over the vendor’s HTTP RPC API (api.focus.teamleader.eu): full CRUD on contacts and companies, creating and updating deals, and listing the account’s users — the identifiers deals, tasks and responsible-user fields elsewhere in the API all reference.
Teamleader’s API is action-based RPC rather than REST — every call, including reads, is a POST to a <resource>.<action> path (contacts.list, deals.create, companies.update) — and its update endpoints replace array collections (emails, telephones, addresses, tags) wholesale rather than merging them, both called out where they matter in each action’s own documentation.
Authentication is OAuth 2.0 only; Teamleader publishes no API-key alternative for third-party integrations, and scopes are fixed once per integration at registration on the Teamleader Marketplace rather than requested per connection.
Build with Teamleader Focus
Three routes to the same 15 actions. The Workflow tab is generated from Teamleader Focus's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Add Company
companies-add Create a new company. Each call creates a new record — Teamleader publishes no upsert-by-VAT-number endpoint, so de-duplicate with Companies List first if that matters.
List Companies
companies-list Get a list of companies, optionally filtered by VAT number, tags, status or a free-text search term.
Update Company
companies-update Update a company. Collections (emails, telephones, addresses, tags) are REPLACED wholesale — provide the full set, not just the change. Custom fields can be updated partially via `custom_fields_update_strategy`.
Add Contact
contacts-add Create a new contact. Each call creates a new record — Teamleader publishes no upsert-by-email endpoint, so de-duplicate with Contacts List before calling this if that matters to your workflow.
List Contacts
contacts-list Get a list of contacts, optionally filtered by company, tags, status or a free-text search term.
Update Contact
contacts-update Update a contact. Collections (emails, telephones, addresses, tags) are REPLACED wholesale — provide the full set you want, not just the change. Custom fields can be updated partially instead, via `custom_fields_update_strategy`.
List Deals
deals-list Get a list of deals, optionally filtered by customer, phase, status, pipeline or a free-text search term.
Update Deal
deals-update Update a deal's title, customer, ownership or estimates. To move a deal between pipeline phases use Move Deal instead — this endpoint does not accept `phase_id`.
List Users
users-list Get a list of all users (Teamleader account members) — useful for resolving a responsible_user_id or an assignee before creating a deal or task.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Teamleader Focus's real ids.
{
"manifestVersion": "2",
"name": "teamleader-example",
"steps": [
{
"id": "companies-add",
"uses": {
"app": "io.w6w.teamleader",
"action": "companies-add",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"name": "<name>"
}
}
]
}Here are some of the things you can do
-
Add Company
performcompanies-add -
Get Company
readcompanies-info -
List Companies
searchcompanies-list -
Update Company
performcompanies-update -
Add Contact
performcontacts-add
+10 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Teamleader Focus, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Teamleader Focus. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "companies-add",
payload: {
name: "<value>",
// businessTypeId: "<value>",
// vatNumber: "<value>",
// nationalIdentificationNumber: "<value>",
// emails: "<value>",
// telephones: "<value>",
// website: "<value>",
// addresses: "<value>",
// responsibleUserId: "<value>",
// remarks: "<value>",
// tags: "<value>",
// customFields: "<value>",
// marketingMailsConsent: "<value>",
// preferredCurrency: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action companies-add --payload '{"name":"<value>"}'Give an AI agent Teamleader Focus — without giving it Teamleader Focus's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.teamleader#companies-add",
"input": {
"name": "<name>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Teamleader Focus connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Teamleader Focus's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Teamleader Focus itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Teamleader Focus declares its own checks, so its health is a property of the app rather than something the host guesses at.
Teamleader Focus platform status
The 'API endpoints' component from status.teamleader.eu — the specific part of Teamleader's own status page that answers for api.focus.teamleader.eu, distinct from the web-app-only components this integration never touches.
API rate-limit headroom
The sliding-window request budget from the x-ratelimit-* headers on POST /users.me — Teamleader's only published metering surface for this API.