noCRM.io
Manage noCRM.io leads, comments, client folders, users, teams, pipelines, steps, categories, predefined tags and webhooks.
About
noCRM.io ships in the w6w first-party pack. It declares 21 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.nocrm- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management · Communication
Overview
noCRM.io is a lead-management / sales CRM in which every account is served from its own subdomain (https://YOUR_SUBDOMAIN.nocrm.io). This app covers the lead lifecycle end to end: leads can be created, fetched, listed with the documented filters and offset paging, updated and deleted, unassigned leads can be pulled for routing, tags can be added and activities logged through the Simplified API, and comments can be posted on and listed for a lead.
Beyond leads, the app reads the account’s own reference data — users, teams, pipelines, steps, tag categories and predefined tags — so a workflow can resolve the ids and names the lead endpoints expect, and it can create and list client folders and create and list webhooks or email notifications for account events.
Two connections are supported, matching the vendor’s own two schemes: an account-level API key (X-API-KEY) and a user token (X-USER-TOKEN) whose requests run with that user’s own privacy and permissions. A fit for turning an inbound enquiry, form submission or another system’s event into a noCRM lead, keeping leads and their owners in sync with the rest of a sales stack, and reacting to noCRM’s own webhook events.
Build with noCRM.io
Three routes to the same 21 actions. The Workflow tab is generated from noCRM.io'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.
List Categories
category-get-many List the account's tag categories, optionally with each category's predefined tags (GET /api/v2/categories).
Create Client Folder
client-folder-create Create a client folder, optionally with a description and an owner (POST /api/v2/clients).
List Client Folders
client-folder-get-many List the account's client folders, ordered by name or id (GET /api/v2/clients).
Add Tag to Lead
lead-add-tag Add one tag to a lead. Simplified API, so it needs an API-key connection (GET /api/simple/leads/{id}/add_tag).
Comment on Lead
lead-comment-create Post a comment on a lead (POST /api/v2/leads/{lead_id}/comments).
List Lead Comments
lead-comment-get-many Retrieve all comments on a lead (GET /api/v2/leads/{lead_id}/comments).
Create Lead
lead-create Create a lead with its title and description, optionally assigning it, tagging it and placing it in a step (POST /api/v2/leads).
List Leads
lead-get-many List leads, filtered by status, step, tags, owner, email or a duplicate-detection `field_key`/`field_value` pair, with offset paging (GET /api/v2/leads).
List Unassigned Leads
lead-get-unassigned List leads that belong to no user — the set a lead created with an API key and no assignee lands in (GET /api/v2/leads/unassigned).
Log Activity on Lead
lead-log-activity Post an activity (a logged call, meeting or note) on a lead, attributed to a user. Simplified API, so it needs an API-key connection (GET /api/simple/leads/{id}/add_activity).
Update Lead
lead-update Update a lead's title, description, assignee, step, creation date or tags (PUT /api/v2/leads/{id}).
List Predefined Tags
predefined-tag-get-many List the account's predefined tags with their category (GET /api/v2/predefined_tags).
List Steps
step-get-many List the account's pipeline steps with the pipeline each belongs to (GET /api/v2/steps).
List Users
user-get-many List the account's users — including deactivated ones — filtered by name, email, status, role or team (GET /api/v2/users).
Create Webhook
webhook-create Subscribe a URL or an email address to a noCRM event (POST /api/v2/webhooks).
List Webhooks
webhook-get-many List the webhooks and notifications subscribed in the account (GET /api/v2/webhooks).
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 noCRM.io's real ids.
{
"manifestVersion": "2",
"name": "nocrm-example",
"steps": [
{
"id": "client-folder-create",
"uses": {
"app": "io.w6w.nocrm",
"action": "client-folder-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"name": "<name>"
}
}
]
}Here are some of the things you can do
-
Create Client Folder
performclient-folder-create -
List Categories
searchcategory-get-many -
List Client Folders
searchclient-folder-get-many -
Add Tag to Lead
performlead-add-tag -
Comment on Lead
performlead-comment-create
+16 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 noCRM.io, 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 noCRM.io. 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: "client-folder-create",
payload: {
name: "<value>",
// description: "<value>",
// userId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action client-folder-create --payload '{"name":"<value>"}'Give an AI agent noCRM.io — without giving it noCRM.io'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.nocrm#client-folder-create",
"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 noCRM.io 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
noCRM.io'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. noCRM.io itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
noCRM.io declares its own checks, so its health is a property of the app rather than something the host guesses at.
Account subdomain reachable
Unauthenticated `GET /api/v2/ping` on this connection's own noCRM subdomain. Classified from the vendor's `type` field: `unauthorized_missing_token` means the account is there and only wants a credential, `unauthorized_invalid_token` means no account answers for that subdomain, and `suspended_account` means the account exists but its subscription has lapsed.