folk
Manage folk CRM groups, people and companies via the folk External API.
About
folk ships in the w6w first-party pack. It declares 12 actions, 1 health check, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.folk- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management
Overview
folk is a CRM built around Groups — contact lists of People and Companies, each carrying its own set of custom fields. This app covers the vendor’s public ‘External API’ in full: listing a network’s groups and creating/updating/finding people and companies within one, reading a group’s available custom fields, listing the folk teammates on a network, and checking that a key can reach a given network.
Good for syncing leads or portfolio contacts into a folk group from a form or another CRM, keeping a company record current as deal data changes elsewhere, or looking a contact up by name/email before deciding whether to create a duplicate.
Build with folk
Three routes to the same 12 actions. The Workflow tab is generated from folk'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 Company Custom Fields
company-custom-fields-list List the custom fields available for companies in a group.
Find Company
company-find Find a company in a group by a free-text query (folk does not document exactly which fields it matches against).
List Network Members
list-network-members List the folk teammates who have access to this network (NOT CRM contacts — see person-* actions for those).
List Person Custom Fields
person-custom-fields-list List the custom fields available for people in a group.
Find Person
person-find Find a person in a group by a free-text query (folk does not document exactly which fields it matches against).
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 folk's real ids.
{
"manifestVersion": "2",
"name": "folk-example",
"steps": [
{
"id": "company-create",
"uses": {
"app": "io.w6w.folk",
"action": "company-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"groupId": "<groupId>"
}
}
]
}Here are some of the things you can do
-
Create Company
performcompany-create -
Check Network Access
readcheck-network-access -
List Company Custom Fields
readcompany-custom-fields-list -
Find Company
readcompany-find -
Update Company
performcompany-update
+7 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 folk, 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 folk. 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: "company-create",
payload: {
groupId: "<value>",
// name: "<value>",
// emails: "<value>",
// phones: "<value>",
// urls: "<value>",
// addresses: "<value>",
// customFields: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action company-create --payload '{"groupId":"<value>"}'Give an AI agent folk — without giving it folk'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.folk#company-create",
"input": {
"groupId": "<groupId>"
}
}
}
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 folk 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
folk'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. folk itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
folk declares its own checks, so its health is a property of the app rather than something the host guesses at.
folk platform status
Instatus component status for folk.instatus.com's 'folk rest API' component — the component name folk itself gave the surface this app calls. Unauthenticated and unsigned.