folk

CRM and sales

folk for AI agents. Managed auth, ready-made tools.

Find, add and update people, companies and groups in folk on behalf of each of your users.

About folk

With the folk connector, your agent works in each user’s own folk workspace. It can list and read people, add or update a person, list and add companies, and list the groups contacts belong to, using only the tools your project allows.

folk is a CRM for managing contacts and relationships, built around people and groups.

Tools

What your agent can do in folk.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own folk connection.

  • List people

    Read
    folk_list_people

    List the people in the workspace.

  • Get a person

    Read
    folk_get_person

    Read a person's details.

  • Add a person

    Write
    folk_create_person

    Add a new person.

  • Update a person

    Write
    folk_update_person

    Change a person's details.

  • List companies

    Read
    folk_list_companies

    List the companies in the workspace.

  • Add a company

    Write
    folk_create_company

    Add a new company.

  • List groups

    Read
    folk_list_groups

    List the groups in the workspace.

Control

Limits you can set.

You decide what your agent may do in folk, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent read and add contacts, and switch off folk_update_person so it can never change a contact.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example people but not companies. A call outside them is refused.

Get started

Connect folk
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect folk

    Each end user authorizes their own folk account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own folk account, once.
    const connection = await agent200
      .user("user_123")
      .connect("folk");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the folk tools

    Name the user, the model and the tools. The model decides which folk tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Add the people I met at the conference to folk",
        tools: ["folk"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, by connecting their own folk account. Each connection is their own.

  • What access is requested

    The connection acts with that user's access in folk, such as reading contacts or writing contacts. Users can revoke it later from their folk account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the folk connector and how to use it.

Agent brief
Connector: folk, through Agent200. In code: "folk".
What it does: Find, add and update people, companies and groups in folk on behalf of each of your users.
Page: https://www.agent200.com/connectors/folk/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on folk's own page, through the authorization link Agent200 returns. Never ask a user for a folk password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: folk_list_people, folk_get_person, folk_list_companies, folk_list_groups. Write tools: folk_create_person, folk_update_person, folk_create_company. Name "folk" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/folk/framework/claude/
   https://www.agent200.com/connectors/folk/framework/chatgpt/
   https://www.agent200.com/connectors/folk/framework/claude-code/
   https://www.agent200.com/connectors/folk/framework/muse/
   https://www.agent200.com/connectors/folk/framework/grok-bot/
   https://www.agent200.com/connectors/folk/framework/openai-dots/
   https://www.agent200.com/connectors/folk/framework/claude-duet/
   https://www.agent200.com/connectors/folk/framework/hermes-agent/
   https://www.agent200.com/connectors/folk/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/folk.md

Guides

Use folk with the AI you build on.

Step-by-step setup for folk with a specific model, assistant or agent framework.

FAQ

folk and Agent200, answered.

Who handles the folk OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for folk.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's folk connection, never another user's. It cannot reach anything the user or folk has not authorized.

Can I limit what my agent can do in folk?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • HubSpot

    HubSpot

    Look up and update contacts, companies and deals in your users' HubSpot CRM.

    Managed OAuth CRM and sales
  • Salesforce

    Salesforce

    Query and update accounts, contacts and opportunities in Salesforce.

    Managed OAuth CRM and sales
  • LinkedIn

    LinkedIn

    Share posts and read profile details on LinkedIn on behalf of each of your users, where the relevant API permissions are available.

    Managed OAuth CRM and sales
  • Zendesk

    Zendesk

    Search, read, create and update Zendesk tickets, and reply to customers, on behalf of each of your users.

    Managed OAuth CRM and sales
200 OK

Start with folk.
Your agent does the rest.

Your users connect their own folk accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)