CRM and sales
folk in your product and your AI agents, through one API
The folk toolkit covers groups and their custom fields, people, companies, deals (and other objects of a group) and notes: list, create and update them. Customers connect with an API key that Connect stores, and every execution is logged, so your product or AI agent works the CRM without a custom integration.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/folk_create_person/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"firstName": "<firstName>"
}
}How it works
From a connected customer to the first folk call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their folk account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with folk.
Sync leads into the CRM
When a signup happens in your SaaS, create a person, link them to a company and add them to a group so they show up in the pipeline.
Move deals through the pipeline
List the deals of a group and update the Status custom field when your product detects a change, which moves the deal in the pipeline.
Notes written by an AI agent
An agent summarizes a call or an email and adds the text as a Markdown note to the right person, company or deal.
Tools
13 folk tools
- List groupsGETLists the groups of the workspace with id and name. Groups hold people, companies and deals. The next page comes from the cursor inside pagination.nextLink; the last page has no nextLink.
- List group custom fieldsGETLists the custom fields of a group for people, companies or one object type, with name, type and the options of select fields. On person or company, each field of type objectField is an object type of the group, like Deals, and its name is the objectType of the object tools.
- List peopleGETLists the people of the workspace with id, names, emails, phones, job title, companies, groups and custom field values. The next page comes from the cursor inside pagination.nextLink; the last page has no nextLink.
- Create personPOSTCreates a person, optionally in groups and linked to companies. folk merges duplicates in the background, which can overwrite part of the data sent. A person in no group only shows up in the folk search.
- Update personPATCHUpdates a person, changing only the fields sent. A list (groups, companies, emails, phones, addresses, urls) replaces the current one, so send it whole. Leaving a group out removes the person from it, along with their custom field values in that group.
- List companiesGETLists the companies of the workspace with id, name, industry, emails, phones, URLs, groups and custom field values. The next page comes from the cursor inside pagination.nextLink; the last page has no nextLink.
- Create companyPOSTCreates a company, optionally in groups. Names are unique in the workspace: an existing name returns that company instead of creating another one. A company in no group only shows up in the folk search.
- Update companyPATCHUpdates a company, changing only the fields sent. A list (groups, emails, phones, addresses, urls) replaces the current one, so send it whole. Leaving a group out removes the company from it, along with its custom field values in that group. A name already used by another company fails.
- List objectsGETLists the deals, or the objects of another type, of a group, with id, name, linked people and companies and custom field values, like the deal Status. The next page comes from the cursor inside pagination.nextLink; the last page has no nextLink. An unknown objectType answers 404 with the object types of the group.
- Create objectPOSTCreates a deal, or an object of another type, in a group. Linked people and companies must already be in the group, or folk ignores them. An unknown custom field name fails the whole request with 422.
API key
Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.
Questions about the folk toolkit
Do I need to build against the folk API?
No. Connect ships 13 folk tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their folk account?
With the mode the toolkit accepts: API key. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
