folk_add_group_member
ChatGPTAdd a workspace member to a group with the given role.
By Folk
folk is a CRM built for relationship-driven teams. Connect it to ChatGPT to search your contacts, log interactions, and stay on top of your pipeline — all in conversation. Ask folk to find a contact, add context after a call, or tell you who needs a follow-up. It works across people, companies, and deals, so your CRM stays up to date without the busywork. Key capabilities: • Search people, companies, and deals • Create and update contacts • Add notes and interactions • Identify next steps and create tasks • Analyse your pipeline and performance
scheduled campaign can be cancelled. A campaign whose schedule fired meanwhile is sending: stop it with folk_stop_campaign instead. A draft or in_review campaign has no schedule.Z, at least a minute ahead). It is processing for a few seconds, may read in_review for a moment while it launches, then sending or scheduled: check with folk_get_campaign, and don't launch it again yourself. If the launch fails, for instance once the plan's messages are used up, the campaign stays in_review with an error: fix it, then launch it with folk_launch_campaign, which says why. This sends emails that cannot be unsent. Before launching, show the user the campaign (its recipients, steps and when it sends) and get their explicit approval in the chat. Never launch on your own initiative. target "draft" stores it to finish later. target "review" generates the message of every recipient without sending, to read with folk_list_campaign_messages and edit with folk_update_campaign_message once the campaign is in_review, then launch with folk_launch_campaign. Each step is an email template sent to every recipient: subject in plain text, body in HTML, both with {{variables}} filled in for each recipient. Variables: For people: {{fullName}}, {{firstName}}, {{lastName}}, {{jobTitle}}, {{description}}, {{urls}}, {{companies.name}}, {{companies.urls}}. For companies: {{name}}, {{description}}, {{fundingRaised}}, {{lastFundingDate}}, {{foundationYear}}, {{industry}}, {{employeeRange}}. Array fields use their first value. A text or numeric custom field of the campaign's group is {{customFieldValues.grp_<uuid>.<field name>}}. A variable without a value for a recipient is removed. Write \{{ for literal braces. Signature: end the body with <p>{{signature}}</p> to sign it with the sender's signature. Don't write the signature yourself: a body without {{signature}} is sent unsigned. Unsubscribe link (custom_domain senders only): <a href="{{unsubscribeLink}}">Unsubscribe</a>. bodyFormat: How body is written. html (default) is read as HTML. text is plain text: a blank line starts a new paragraph, each further blank line adds an empty paragraph, a single newline is a line break, and < and & are literal characters. Bodies always read back as HTML. Follow-ups (steps after the first) take delayDays (1-365, default 1; 0 is only for the first step, as read back) and sameThread (reply in the thread of the previous step, with no subject of their own). More than one step needs sequences on the plan and a sender that is not Gmail. Sender: a root sender for every step, or a sender on every step, as { id } or { email }; not both. Recipients: { type: "contacts", ids } with person (per_) or company (com_) ids, all of the same type; or, with groupId, { type: "group", entityType, filter?, search?, excludeIds? }, with the filter syntax of folk_search_people. A text or numeric custom field of the group can be used as a variable. stopOnReply defaults to true. With follow-ups, it needs a sender whose replies are tracked, its mailbox connected in the app: with any other sender, set it to false for the campaign to go to review. warnings lists recipients that were skipped or have no email address, and HTML that was simplified.objectField, entityType person or company (same result: the object type is shared by people and companies). The object type is named after the field and can be used as objectType right away. person and company are reserved: an object type can't be named after them, whatever the case. - Add a custom field to an object type: pass the name of the object type as entityType. Objects accept textField, numericField, dateField, singleSelect, multipleSelect and userField. An object type can't have contactField or objectField custom fields. - Creating an object type also creates a default status single-select field on it, with five pipeline options from lead to closed-won and closed-lost. Its Pipeline view is grouped by it. Its name and options are written in the language of the user who creates the object type (e.g. Status or Statut), so find it with folk_list_group_custom_fields rather than by name. To track another lifecycle, update that field with folk_update_group_custom_field (rename it, add/update/remove options) instead of creating another select field. Example, tracking partnerships with their own lifecycle in a group: 1. { "groupId": "grp_…", "entityType": "company", "type": "objectField", "name": "Partnerships" } 2. Find the default status field with folk_list_group_custom_fields { "groupId": "grp_…", "entityType": "Partnerships" } (the single-select field created with the object type), and get the ids of its default options with folk_get_group_custom_field { "groupId": "grp_…", "entityType": "Partnerships", "customFieldName": "<status field name>" }. 3. Turn the status field into your lifecycle with folk_update_group_custom_field { "groupId": "grp_…", "entityType": "Partnerships", "customFieldName": "<status field name>", "name": "Stage", "addOptions": [{ "label": "Prospect", "color": "#879aab" }, { "label": "Active", "color": "#20cea9" }], "removeOptions": ["<ids from step 2>"] }. 4. Create the partnerships with folk_create_objects, objectType "Partnerships".per_<uuid>) or company (com_<uuid>) the interaction is linked to - dateTime — when the interaction happened, as an ISO 8601 timestamp (e.g. "2025-07-17T09:00:00.000Z") - title — short summary of the interaction - content — the multi-line body of the interaction - activityType — the kind of interaction: a predefined activity (call, meeting, message, coffee, lunch, event, drink), a messaging app (slack, whatsapp, linkedin, telegram, etc.), or a single emoji Returns the full created logged interaction.per_<uuid> for a person, com_<uuid> for a company and obj_<uuid> for an object . Obtain entity IDs from folk_search_people, folk_search_companies or folk_search_objects. content: required — note body in markdown (max 100 000 chars). visibility: "public" (visible to all workspace members) or "private" (visible only to you). Defaults to "public". parentNote.id: optional — attach as a reply to an existing note on the same entity. Returns the full created note object.objectField). Provide name, and optionally link people and companies by their folk IDs. People and companies must already be in the group of the object: an unknown id, or one not in the group, is silently ignored. Check the people and companies of the object afterwards to know which ones were linked. customFieldValues is a flat record keyed by field name (e.g. { "Status": "Active" }) — no group nesting needed. A name that is not a custom field of the object type fails the call. Returns the full created object.{ "Status": "Active" }) — no group nesting needed. Use folk_get_workspace_structure first to discover available groupIds and object types. An object type that does not exist in the group fails the whole call: create it first with folk_create_group_custom_field (type objectField). Accepts at most 100 records per call: split a larger set into several calls, or narrow it down first. Each record is processed on its own: one that fails does not prevent the others from being written. Returns one result per record, in the order of records, with only its id, status and error: call the matching get tool for a full record. Records cannot be deleted through the folk MCP.per_<uuid> | com_<uuid> | obj_<uuid>. Obtain IDs from folk_search_people, folk_search_companies, or folk_search_objects. assignedUsers: accepts user IDs or emails. Defaults to the current user if omitted. Returns the full created task object.groupId is required; groupId, entityType (person, company or the name of an object type, as in folk_get_workspace_structure) and type (table or kanban) never change afterwards. The settings that aren't sent get the defaults of the entity type and the view type. Filter: { combinator: "and" | "or", conditions: [{ field, operator, value }] }. Unlike the filter map of folk_search_people, folk_search_companies and folk_search_objects, conditions is a list: the same field can appear in several conditions. Field keys and operators are those of these search tools, but values differ: - empty and not_empty: no value, not "". - in, not_in, all, and eq / not_eq on select, user and reference fields: always a list, even for a single value. eq and not_eq then mean "exactly this set". Select options by label (["Active"]), users as [{ id: "usr_…" }] or [{ email }], people, companies, objects and groups as [{ id: "com_…" }], never { id: [...] }. - other operators: a single string, or a number on number fields. Dates as YYYY-MM-DD or relative dates (today, 7-days-ago, in-3-months). Kanban: groupBy is the key of a single select field of the view's entity type. If none exists, create one first with folk_create_group_custom_field (needs "Full access"). The pipelines of folk_get_workspace_structure list the existing kanbans. columns: every option of the groupBy field once, plus null for the "No value" column, in display order, each with hidden. Position: { after: <viewId> | null } or { before: <viewId> | null }, relative to a view of the same group. { after: null } puts the view first, { before: null } last. Reads return { after }. Last by default. Native field keys, for filter, visibleFields and sort: - people views: companies, jobTitle, emails, interactionMetadata.user.lastInteractedAt (not filterable), interactionMetadata.workspace.lastInteractedAt, interactionMetadata.workspace.lastInteractedBy (not filterable), urls, description, interactionMetadata.user.approximateCount (not filterable), strongestConnection, phones, addresses, firstName, lastName, birthday, gender, groups (not sortable), createdAt, createdBy, addedToGroupAt, addedToGroupBy, fullName (not filterable, not a visible field) - people views, fields of their company: company.emails, company.urls, company.phones, company.addresses, company.fundingRaised, company.lastFundingDate, company.foundationYear, company.employeeRange (not sortable), company.industry - company views: people (not filterable, not sortable), urls, phones, emails, addresses, description, fundingRaised, lastFundingDate, foundationYear, employeeRange (not sortable), industry, groups (not sortable), createdAt, createdBy, addedToGroupAt, addedToGroupBy, name (not a visible field), strongestConnection (not a visible field) - object views: people (not sortable), companies, createdAt, createdBy, name (not a visible field) Custom field keys, from folk_get_workspace_structure: customFieldValues.<groupId>.<Field name> on people and company views, customFieldValues.<Field name> on object views.{ "filter": { "groups": { "in": { "id": ["grp_<uuid>"] } }, "emails": { "empty": "" } }, "idsOnly": true, "limit": 500 }. Collect every page first (follow nextCursor until there is none), then start one enrichment per page of up to 500 ids. ids: person ids (per_<uuid>), from folk_search_people (with idsOnly: true). Duplicates are enriched once. Ids that don't match a person you can access and edit (enriching needs the contributor role or above on one of the person's groups) are not rejected: they are reported with the "skipped" status. Returns the enrichment, usually with status "pending".{{key}} (for example {{firstName}}, or {{customFieldValues.grp_<uuid>.<field name>}} for a group custom field). A signed body ends with <p>{{signature}}</p>, which stands for the sender's signature; an unsubscribe link is <a href="{{unsubscribeLink}}">. To see what each recipient receives, use folk_list_campaign_messages.filter, visibleFields, and sort for table views or groupBy and columns for kanban views. - groupId: the group of the view, null for a personal view, which belongs to no group. It never changes. - entityType: person, company or the name of an object type, as in folk_get_workspace_structure. It never changes. - type: table or kanban. It never changes. - position: { after: <viewId> | null }, the view just before this one in its group, null for the first one.company.<key> fields, which filter people on their primary company. Custom field keys are built from customFieldsByEntityType: customFieldValues.<groupId>.<fieldName> for people and companies, company.customFieldValues.<groupId>.<fieldName> for the custom fields of a person's primary company, customFieldValues.<fieldName> for objects. Object types (custom objects): Deals, opportunities, projects, partnerships, job applications… are all custom objects: records of an object type defined in a group. When the user talks about "deals" (or "opportunities", "partnerships"…), they mean the objects of the matching object type in a group. The object type name is chosen by each workspace and is case-sensitive: it can be "Deals", "deals", "Opportunities" or anything else. Never assume "Deals": use the exact name found in the group. An object type that does not exist in the group fails the call, and the error lists the object types of the group. The object types of a group are its objectField custom fields, listed under person and company in customFieldsByEntityType: the name of the field is the object type to pass as objectType. Each object type of a group also appears under its own name in entityTypes and customFieldsByEntityType (with the custom fields of its objects), and in the entityType of its pipelines. Use that name as objectType in the object tools, and as entityType in the custom field tools. An object type named person or company is not listed under its own name, as these names always mean the native entity types here.Z, at least a minute ahead). This sends emails that cannot be unsent. Before launching, show the user the campaign (its recipients, steps and when it sends) and get their explicit approval in the chat. Never launch on your own initiative. The campaign becomes sending, or scheduled until scheduledAt; its steps read scheduled until they send. Track delivery with folk_get_campaign and folk_list_campaign_messages. The launch runs the app's checks: the messages left on the plan, the daily quota of a Gmail sender, and every step's sender, which the user must be allowed to send from. A failed check leaves the campaign in review, with the reason in the error. Once launched, a campaign flagged as spam goes back to in_review with error "spam_detected". Only a campaign in_review can be launched: create one with folk_create_campaign (target "review") or folk_review_campaign. To change a scheduled campaign before it sends, cancel its schedule with folk_cancel_campaign_schedule; to stop a scheduled or sending campaign for good, use folk_stop_campaign.{{variables}} the subjects and bodies of a campaign can use: the fields of its people or companies, the text and numeric custom fields of its group, {{unsubscribeLink}} and {{signature}}. Write each variable's token exactly as given: custom field names are escaped where needed. A variable without a value for a recipient is removed from their message. {{unsubscribeLink}} is only valid as the whole href of a link in a body, <a href="{{unsubscribeLink}}">, with a custom_domain sender. {{signature}} is only valid alone in the last paragraph of a body, <p>{{signature}}</p>. It inserts the sender's signature on a new step or message (see folk_list_message_senders): end a body with it to sign it, rather than writing the signature yourself. The response includes nextCursor when more results are available; pass it back as cursor to fetch the next page.{{key}} (for example {{firstName}}, or {{customFieldValues.grp_<uuid>.<field name>}} for a group custom field). A signed body ends with <p>{{signature}}</p>, which stands for the sender's signature; an unsubscribe link is <a href="{{unsubscribeLink}}">. The response includes nextCursor when more results are available; pass it back as cursor to fetch the next page.objectField custom fields on person (or company, which returns the same ones): find them with folk_get_workspace_structure or folk_list_group_custom_fields. The name of the field is the object type to pass as objectType. To create an object type, call folk_create_group_custom_field with type objectField. To list the custom fields of the objects of an object type, pass the name of the object type as entityType.grp_<uuid>.{{signature}} inserts on a new step or message: end a body with <p>{{signature}}</p> to sign it, rather than writing the signature yourself. The response includes nextCursor when more results are available; pass it back as cursor to fetch the next page.{ "<attribute>": { "<operator>": <operand> } } | Attribute | Operators | Values | |------------|--------------------------|----------------------------------------------------------------| | status | eq, not_eq, in, not_in | one or more of: pending, in_progress, completed, failed | | createdAt | gt, lt | one date string "YYYY-MM-DD" | | finishedAt | empty, not_empty, gt, lt | empty/not_empty take no value; gt/lt take one date "YYYY-MM-DD" | Examples: - running enrichments: { "status": { "in": ["pending", "in_progress"] } } - finished enrichments: { "finishedAt": { "not_empty": "" } } - requested after a date: { "createdAt": { "gt": "2026-09-01" } } Use combinator to control AND/OR logic across filters. Omit filter to list every enrichment. Returns up to limit enrichments (default and max 10), each with its report once completed (see folk_get_person_enrichment). The response includes nextCursor when more results are available; pass it back as cursor to get the next page.filter, visibleFields, and sort for table views or groupBy and columns for kanban views. - groupId: the group of the view, null for a personal view, which belongs to no group. It never changes. - entityType: person, company or the name of an object type, as in folk_get_workspace_structure. It never changes. - type: table or kanban. It never changes. - position: { after: <viewId> | null }, the view just before this one in its group, null for the first one.processing for a few seconds, then in_review: check with folk_get_campaign before reading its messages with folk_list_campaign_messages. If generation fails, it is in_review with an error. Edit single messages with folk_update_campaign_message, remove recipients with folk_remove_campaign_recipient, or take it back to draft with folk_draft_campaign to edit its steps. Launch it with folk_launch_campaign once the user approves. Every step needs a sender, a subject (apart from follow-ups sent in the same thread) and a body. To review a campaign as you create it, pass target "review" to folk_create_campaign instead.{ "<fieldName>": { "<operator>": <operand> } } Field categories: - Text fields (name, description, industry, emails, phones, urls, addresses, custom fields): operators: eq, not_eq, like, not_like, empty, not_empty - Numeric/date fields (fundingRaised, lastFundingDate, createdAt, custom fields): operators: eq, not_eq, gt, lt, empty, not_empty - Single and multi select fields (custom fields): operators: in, not_in, empty, not_empty - Multi-value reference fields (groups): operators: in, not_in, all, empty, not_empty - Single-value reference fields (createdBy): operators: in, not_in, empty, not_empty Important operand rules: - eq / like / gt / lt → operand is usually a plain string Example: { "name": { "eq": "John Doe" } } - empty / not_empty → operand MUST be an empty string Example: { "industry": { "empty": "" } } - in / not_in / all → operand MUST be an object with a single attribute being a single string or an array of string Example: { "createdBy": { "in": { "id": "usr_123" } } } OR { "groups": { "in": { "id": ["grp_123"] } } } - SingleSelect and multiSelect custom fields → operand is a plain string or array of plain strings (NOT an id object) Examples: { "customFieldValues.grp_xxx.Status": { "in": "Active" } } { "customFieldValues.grp_xxx.Tags": { "in": ["B2C","B2B"] } } - Relationships / Assign / Deals custom fields → operand MUST be an object with a single id being a single string or an array of string Examples: { "customFieldValues.grp_xxx.Relationships": { "in": { "id": "per_aaa" } } } { "customFieldValues.grp_xxx.Owner": { "in": { "id": "usr_aaa" } } } { "customFieldValues.grp_xxx.Deals": { "in": { "id": "obj_aaa" } } } - Date fields → operand is a YYYY-MM-DD date or a relative date: "today", "yesterday", "<n>-<unit>-ago", and on date custom fields only "tomorrow" and "in-<n>-<unit>" too (n from 0 to 99, unit: day(s), week(s), month(s), year(s)) Examples: { "lastFundingDate": { "gt": "6-months-ago" } } { "customFieldValues.grp_xxx.Renewal": { "lt": "in-1-month" } } Custom fields: Use key format customFieldValues.<groupId>.<fieldLabel> Example: { "customFieldValues.grp_xxx.Status": { "in": "Active" } } Use combinator for AND/OR logic. Returns paginated company objects: up to limit companies (default 20, max 100). The response includes nextCursor when more results are available; pass it back as cursor, with the same filter and idsOnly, to get the next page. Acting on many companies: set idsOnly to true to get only the IDs of the matching companies (com_<uuid>) in ids, instead of full objects in companies: up to limit IDs per page (default 100, max 500). Use it before folk_update_companies, which takes up to 100 records per call (one per companyId; addGroupIds and add / remove need no current values). Collect every page before acting on the ids: updating the companies can change which ones match the filter and shift the next pages. Use folk_get_company if companyId is already known.per_<uuid> for a person, com_<uuid> for a company, obj_<uuid> for objects. - query (optional): full-text search against note content. - createdAfter (optional): ISO 8601 timestamp — return only notes created after this date. - createdBefore (optional): ISO 8601 timestamp — return only notes created before this date. - limit / cursor: pagination. Returns paginated note objects with nextCursor when more pages exist.{ "<fieldName>": { "<operator>": <operand> } } Field categories: - Text fields (name): operators: eq, not_eq, like, not_like, empty, not_empty - Date fields (createdAt): operators: eq, not_eq, gt, lt, empty, not_empty - Multi-value reference fields (people, companies): operators: in, not_in, all, empty, not_empty - Single-value reference fields (createdBy): operators: in, not_in, empty, not_empty Important operand rules: - eq / like / gt / lt → operand is usually a plain string Example: { "name": { "eq": "Project Alpha" } } - empty / not_empty → operand MUST be an empty string Example: { "name": { "empty": "" } } - in / not_in / all → operand MUST be an object with a single attribute being a single string or an array of string Examples: { "createdBy": { "in": { "id": "usr_123" } } } { "companies": { "in": { "id": ["com_123", "com_456"] } } } - SingleSelect and multiSelect custom fields → operand is a plain string or array of plain strings (NOT an id object) Examples: { "customFieldValues.Status": { "in": "Active" } } { "customFieldValues.Tags": { "in": ["B2C","B2B"] } } - Assign (user) custom fields → operand MUST be an object with a single id being a single string or an array of string Example: { "customFieldValues.Owner": { "in": { "id": "usr_aaa" } } } - Date fields → operand is a YYYY-MM-DD date or a relative date: "today", "yesterday", "<n>-<unit>-ago", and on date custom fields only "tomorrow" and "in-<n>-<unit>" too (n from 0 to 99, unit: day(s), week(s), month(s), year(s)) Examples: { "createdAt": { "gt": "7-days-ago" } } { "customFieldValues.Close date": { "lt": "in-1-month" } } Custom fields: use the key format customFieldValues.<fieldName>, without group id: an object belongs to a single group. Example: { "customFieldValues.Status": { "in": "Active" } } Use combinator for AND/OR logic. Returns paginated object payloads with name, people, companies, customFieldValues. Use folk_get_object if objectId is already known.{ "<fieldName>": { "<operator>": <operand> } } Field categories: - Text fields (fullName, firstName, lastName, jobTitle, description, emails, phones, urls, addresses, custom fields): operators: eq, not_eq, like, not_like, empty, not_empty - Numeric/date fields (birthday, createdAt, addedToGroupAt, interactionMetadata.workspace.lastInteractedAt, interactionMetadata.user.lastInteractedAt, custom fields): operators: eq, not_eq, gt, lt, empty, not_empty - Enum fields (gender): operators: eq, not_eq, empty, not_empty Values: "Male", "Female", "Unknown", "Other" Example: { "gender": { "eq": "Female" } } - SingleSelect/MultiSelect fields (custom fields): operators: in, not_in, empty, not_empty - Multi-value reference fields (groups, companies): operators: in, not_in, all, empty, not_empty - Single-value reference fields (createdBy, addedToGroupBy, strongestConnection): operators: in, not_in, empty, not_empty createdBy, addedToGroupBy and strongestConnection take workspace members: { "id": "usr_xxx" } or { "email": "jane@example.com" } Group-scoped fields (addedToGroupAt, addedToGroupBy, strongestConnection) hold when true in at least one group of the person: - the groups of a groups filter with "in" or "all", when the filters are combined with "and" - otherwise (no such groups filter, only "not_in", or combinator "or"), every group you can access Example: { "groups": { "in": { "id": "grp_123" } }, "addedToGroupAt": { "gt": "30-days-ago" } } Important operand rules: - eq / like / gt / lt → operand is usually a plain string Example: { "fullName": { "eq": "John Doe" } } - empty / not_empty → operand MUST be an empty string Example: { "jobTitle": { "empty": "" } } - in / not_in / all → operand MUST be an object with a single attribute being a single string or an array of string Example: { "createdBy": { "in": { "id": "usr_123" } } } OR { "groups": { "in": { "id": ["grp_123"] } } } - SingleSelect and multiSelect custom fields → operand is a plain string or array of plain strings (NOT an id object) Examples: { "customFieldValues.grp_xxx.Status": { "in": "Active" } } { "customFieldValues.grp_xxx.Tags": { "in": ["B2C","B2B"] } } - Relationships / Assign / Deals custom fields → operand MUST be an object with a single id being a single string or an array of string Examples: { "customFieldValues.grp_xxx.Relationships": { "in": { "id": "per_aaa" } } } { "customFieldValues.grp_xxx.Owner": { "in": { "id": "usr_aaa" } } } { "customFieldValues.grp_xxx.Deals": { "in": { "id": "obj_aaa" } } } - Date fields → operand is a YYYY-MM-DD date or a relative date: "today", "yesterday", "<n>-<unit>-ago", and on date custom fields only "tomorrow" and "in-<n>-<unit>" too (n from 0 to 99, unit: day(s), week(s), month(s), year(s)) Examples: { "createdAt": { "gt": "7-days-ago" } } { "customFieldValues.grp_xxx.Renewal": { "lt": "in-1-month" } } Custom fields: Use key format customFieldValues.<groupId>.<fieldLabel> Example: { "customFieldValues.grp_xxx.Status": { "in": "Active" } } Company fields: filter people on their primary company with the company. prefix. - Native fields: company.emails, company.phones, company.urls, company.industry, company.addresses, company.fundingRaised, company.lastFundingDate, company.foundationYear, company.employeeRange (same operators as on companies) - Custom fields: company.customFieldValues.<groupId>.<fieldLabel> Example: { "company.industry": { "eq": "Software" } } Use combinator for AND/OR logic. Returns paginated person objects: up to limit people (default 20, max 100). The response includes nextCursor when more results are available; pass it back as cursor, with the same filter and idsOnly, to get the next page. Acting on many people: set idsOnly to true to get only the IDs of the matching people (per_<uuid>) in ids, instead of …{ "<fieldName>": { "<operator>": <operand> } } Attribute → operator → value table: | Attribute | Operators | Values | |-------------------|-----------------------------|------------------------------------------| | dueAt | eq, not_eq, gt, lt | one date string "YYYY-MM-DD" | | createdAt | gt, lt | one date string "YYYY-MM-DD" | | completedAt | empty, not_empty, gt, lt | empty/not_empty take no value; gt/lt take one ISO 8601 datetime string | | assigneeUserId | in, not_in | one or more folk-prefixed user ids | | entity | in, not_in | one or more folk-prefixed entity ids | Operand-shape rules: - dueAt / createdAt → operand is a plain date string. Example: { "dueAt": { "gt": "2025-01-01" } } - completedAt → empty/not_empty take no operand (task not yet completed / already completed). gt/lt take an ISO 8601 datetime string. Example: { "completedAt": { "not_empty": "" } } Example: { "completedAt": { "gt": "2025-01-01T00:00:00.000Z" } } - assigneeUserId → operand is one or more folk-prefixed user ids (usr_...). Obtain ids from folk_get_workspace_structure. Example: { "assigneeUserId": { "in": "usr_7dfc21aa-feb2-40d9-92c9-17ccbe8bbddf" } } Example (exclude): { "assigneeUserId": { "not_in": "usr_7dfc21aa-feb2-40d9-92c9-17ccbe8bbddf" } } - entity → operand is one or more folk-prefixed ids, all of the SAME entity type (per_... for people, com_... for companies, obj_... for objects — do not mix types in one filter). Obtain ids from folk_search_people, folk_search_companies, or folk_search_objects. Example: { "entity": { "in": ["per_7dfc21aa-feb2-40d9-92c9-17ccbe8bbddf"] } } Example (exclude): { "entity": { "not_in": ["per_7dfc21aa-feb2-40d9-92c9-17ccbe8bbddf"] } } Use combinator to control AND/OR logic across multiple filter entries. Omit filter entirely to return every task. onlyAssignedToMe (optional): when true, restricts results to tasks assigned to the current user, combined with any other filters. Returns paginated full task objects: up to limit tasks (default 20, max 100). The response includes nextCursor when more results are available; pass it back as cursor to get the next page. Use folk_get_task if taskId is already known.{{variables}} filled in for each recipient. Variables: For people: {{fullName}}, {{firstName}}, {{lastName}}, {{jobTitle}}, {{description}}, {{urls}}, {{companies.name}}, {{companies.urls}}. For companies: {{name}}, {{description}}, {{fundingRaised}}, {{lastFundingDate}}, {{foundationYear}}, {{industry}}, {{employeeRange}}. Array fields use their first value. A text or numeric custom field of the campaign's group is {{customFieldValues.grp_<uuid>.<field name>}}. A variable without a value for a recipient is removed. Write \{{ for literal braces. Signature: end the body with <p>{{signature}}</p> to sign it with the sender's signature. Don't write the signature yourself: a body without {{signature}} is sent unsigned. Unsubscribe link (custom_domain senders only): <a href="{{unsubscribeLink}}">Unsubscribe</a>. bodyFormat: How body is written. html (default) is read as HTML. text is plain text: a blank line starts a new paragraph, each further blank line adds an empty paragraph, a single newline is a line break, and < and & are literal characters. Bodies always read back as HTML. Follow-ups (steps after the first) take delayDays (1-365, default 1; 0 is only for the first step, as read back) and sameThread (reply in the thread of the previous step, with no subject of their own). More than one step needs sequences on the plan and a sender that is not Gmail. Sender: a root sender for every step, or a sender on every step, as { id } or { email }; not both. Recipients, and whether they are people or companies, can't change.{{variables}} are rejected, apart from {{signature}} and {{unsubscribeLink}}. A body read back ends with <p>{{signature}}</p> when signed: keep it to keep the message's signature as it is, edited or not; a body without it has no signature. <a href="{{unsubscribeLink}}"> links to the unsubscribe page of this message (custom_domain senders only). bodyFormat: How body is written. html (default) is read as HTML. text is plain text: a blank line starts a new paragraph, each further blank line adds an empty paragraph, a single newline is a line break, and < and & are literal characters. Bodies always read back as HTML. A blank subject or body is rejected. A follow-up sent in the same thread takes no subject; a new subject on a first-step message carries to the follow-ups of its thread. Edits are lost if the campaign goes back to draft, with folk_draft_campaign or in the app.{{variables}} are rejected, apart from {{signature}} and {{unsubscribeLink}}. A body read back ends with <p>{{signature}}</p> when signed: keep it to keep the message's signature as it is, edited or not; a body without it has no signature. <a href="{{unsubscribeLink}}"> links to the unsubscribe page of this message (custom_domain senders only). bodyFormat: How body is written. html (default) is read as HTML. text is plain text: a blank line starts a new paragraph, each further blank line adds an empty paragraph, a single newline is a line break, and < and & are literal characters. Bodies always read back as HTML. A blank subject or body is rejected. A follow-up sent in the same thread takes no subject. Edits are lost if the campaign goes back to draft, with folk_draft_campaign or in the app. Accepts at most 100 records per call: split a larger set into several calls, or narrow it down first. Each record is processed on its own: one that fails does not prevent the others from being written. Returns one result per record, in the order of records, with only its id, status and error, and warnings when there are any: call the matching get tool for a full record. Records cannot be deleted through the folk MCP.grp_<uuid>). Obtain from folk_list_groups. name: new name of the group (optional). visibility: "public" or "private" (optional). emoji: a single native emoji, e.g. "🤝" (optional). The emoji can be changed but not removed. Changing visibility resets group membership: all current members are removed and the caller becomes the sole owner. Returns the full updated group object.objectField custom field renames the object type: its objects are then read and written with the new name as objectType. person and company are reserved: an object type can't be renamed after them, whatever the case. To update a custom field of an object type, pass the name of the object type as entityType.lit_<uuid>) can be updated; imported interactions (email, calendar, WhatsApp, calls) cannot. Besides interactionId and entity, at least one updatable field must be provided. Returns the full updated interaction.nte_<uuid>). Obtain from folk_search_notes. content: new markdown body (optional). visibility: "public" or "private" (optional). Returns only noteId. Call folk_search_notes to retrieve the updated note object. Note: only user-authored notes can be updated.filter, visibleFields, sort and columns replace the current value as a whole: to add a condition, call folk_get_view and send back every condition with the new one. The settings returned by folk_get_view (name, filter, visibleFields, sort, groupBy, columns, position) can be sent back as is, without the other keys of the view. groupId, entityType and type never change. sort is for table views only, groupBy and columns for kanban views only. Filter: { combinator: "and" | "or", conditions: [{ field, operator, value }] }. Unlike the filter map of folk_search_people, folk_search_companies and folk_search_objects, conditions is a list: the same field can appear in several conditions. Field keys and operators are those of these search tools, but values differ: - empty and not_empty: no value, not "". - in, not_in, all, and eq / not_eq on select, user and reference fields: always a list, even for a single value. eq and not_eq then mean "exactly this set". Select options by label (["Active"]), users as [{ id: "usr_…" }] or [{ email }], people, companies, objects and groups as [{ id: "com_…" }], never { id: [...] }. - other operators: a single string, or a number on number fields. Dates as YYYY-MM-DD or relative dates (today, 7-days-ago, in-3-months). Kanban: groupBy is the key of a single select field of the view's entity type. If none exists, create one first with folk_create_group_custom_field (needs "Full access"). The pipelines of folk_get_workspace_structure list the existing kanbans. columns: every option of the groupBy field once, plus null for the "No value" column, in display order, each with hidden. A new groupBy without columns resets the columns to the options of the new field. Position: { after: <viewId> | null } or { before: <viewId> | null }, relative to a view of the same group. { after: null } puts the view first, { before: null } last. Reads return { after }. Native field keys, for filter, visibleFields and sort: - people views: companies, jobTitle, emails, interactionMetadata.user.lastInteractedAt (not filterable), interactionMetadata.workspace.lastInteractedAt, interactionMetadata.workspace.lastInteractedBy (not filterable), urls, description, interactionMetadata.user.approximateCount (not filterable), strongestConnection, phones, addresses, firstName, lastName, birthday, gender, groups (not sortable), createdAt, createdBy, addedToGroupAt, addedToGroupBy, fullName (not filterable, not a visible field) - people views, fields of their company: company.emails, company.urls, company.phones, company.addresses, company.fundingRaised, company.lastFundingDate, company.foundationYear, company.employeeRange (not sortable), company.industry - company views: people (not filterable, not sortable), urls, phones, emails, addresses, description, fundingRaised, lastFundingDate, foundationYear, employeeRange (not sortable), industry, groups (not sortable), createdAt, createdBy, addedToGroupAt, addedToGroupBy, name (not a visible field), strongestConnection (not a visible field) - object views: people (not sortable), companies, createdAt, createdBy, name (not a visible field) Custom field keys, from folk_get_workspace_structure: customFieldValues.<groupId>.<Field name> on people and company views, customFieldValues.<Field name> on object views.Click any prompt to copy it.
Add this badge to your site or README. It links to this page.
HTML
<a href="https://mcp-app-store.keenethics-labs.com/app/folk-crm"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>
Markdown
[](https://mcp-app-store.keenethics-labs.com/app/folk-crm)