Integration · Sell and serve
folk and Meteor AI agents
Connect folk to a WhatsApp Met: search people and companies, create contacts and deals, and leave notes and tasks in your CRM with the official MCP.
How does folk connect to Meteor?
With the folk ready connector, your WhatsApp Met works on your team's CRM with the account the admin authorizes. It first reads the workspace structure, with its groups, fields and stages, and then looks up the person or company writing in. If they do not exist, it creates them; if they do, it leaves a note with what they asked for, logs the conversation as an interaction and creates a follow up task for someone on the team. It also creates deals in the pipeline you already use; the update actions start off until the admin turns them on. It is the official folk server: usage runs on your folk account, and the server has no actions to delete records.
What it automates
What a Meteor Met does with folk
Register the new customer who writes in
The Met looks the person up by name or email. If they are not in folk, it creates them with the details they gave in the chat and adds them to the group its instructions point to, together with their company.
Leave context for the team
At the end of the conversation, the Met leaves a note on the person's record with what they asked for and logs the conversation as an interaction, so whoever picks it up sees the history in folk.
Open the deal in the pipeline
If the person wants a quote, the Met creates a deal in the sales group, links it to the person and their company and leaves it at the stage your team uses.
Create the follow up task
The Met creates a task linked to the person, assigned by email to the right teammate, so nobody forgets to write back.
28 tools
Everything your Met can ask folk for
Each one is a real action in the connector. You can switch off the ones you would rather it never used.
| Tool | What it does |
|---|---|
folk_get_current_user | Returns the id, email and name of the folk user who authorized the connection. |
folk_get_workspace_structure | Returns the workspace structure, with groups, record types, custom fields, pipeline views and members. |
folk_search_companies | Searches companies with one or more filters, such as name, group or a custom field. |
folk_get_company | Returns a company by its id, once it came up in an earlier search. |
folk_create_company | Creates a company with at least its name and can add it to one or more groups. |
folk_update_company | Changes only the fields you pass on a company. folk marks it as destructive and it starts off until the admin turns it on. |
folk_search_people | Searches people with one or more filters, such as name, group, company or a custom field. |
folk_get_person | Returns a person's full record, with emails, phones, companies, groups and custom fields. |
folk_create_person | Creates a person with at least a name or an email and returns the created record. |
folk_update_person | Changes only the fields you pass on a person. folk marks it as destructive and it starts off until the admin turns it on. |
folk_search_objects | Searches objects, such as deals, by name, creation date, creator or custom fields. |
folk_get_object | Returns an object, such as a deal, with its people, companies and custom fields. |
folk_create_object | Creates an object, such as a deal, inside a group and links it to people and companies. |
folk_update_object | Changes an object; if you pass people or companies, it replaces the linked ones. folk marks it as destructive and it starts off until the admin turns it on. |
folk_search_notes | Lists recent workspace notes or those of a person or company, with filters by date or content. |
folk_create_note | Creates a note linked to a person, a company or an object. |
folk_update_note | Changes the content or visibility of a note. folk marks it as destructive and it starts off until the admin turns it on. |
folk_list_groups | Lists the workspace groups the connected account can access. |
folk_list_group_members | Lists the members of a group, with pagination. |
folk_create_interaction | Logs a past interaction, such as a call, a meeting or a message, with a person or company. |
folk_list_interactions | Lists the past or upcoming interactions of a person, a company or an object. |
folk_get_interaction | Returns a full interaction, with the email or event body, when privacy rules allow it. |
folk_update_interaction | Changes the title, content, date or type of a manually logged interaction. folk marks it as destructive and it starts off until the admin turns it on. |
folk_search_tasks | Searches tasks by status, due date, assignee or linked record, up to 100 per page. |
folk_create_task | Creates a task linked to a person, company or object, with assignees by id or by email. |
folk_get_task | Returns a task by its id, once it came up in a search or was just created. |
folk_update_task | Changes a task's details, except marking it done. folk marks it as destructive and it starts off until the admin turns it on. |
folk_update_task_todo_or_done | Marks a task as done or moves it back to to do. |
The limits
What the folk integration does NOT do
We would rather say it here than have you find out during rollout.
-
It does not delete records. The folk server has no tools to delete people, companies, deals, notes or tasks: the most destructive thing it does is change data.
-
It does not ask for confirmation in the chat before writing. The admin decides in Connections which actions stay on; folk marks the update actions as destructive, and they start off.
-
It does not create or edit imported interactions. Emails, events, calls and messages that folk syncs from other sources are left alone; only manually logged ones are touched.
-
It sees no more than the account that authorized the connection. Private groups that account does not belong to stay out of reach.
-
It does not change the CRM setup from the chat. Creating groups or managing their members or custom fields is outside this page and is done in folk.
Before you start
What you need to connect folk
- 1
A folk account with access to your team's workspace
The account your team works with in folk. The connector acts with its permissions, so connect one that sees the groups the Met needs.
- 2
Connect it in Met
In Met, open Connections → folk → Connect. A folk window opens so you can sign in and authorize Met. Then you choose which actions stay on.
Frequently asked questions
Questions about folk and Meteor
No. The folk server has no delete tools. It can create and update records, depending on the actions the admin leaves on.
It can list them as the person's interactions, together with emails and events, when folk's privacy rules allow it. What it cannot do is edit them.
Yes. Before writing, the Met reads the workspace structure, with your groups, custom fields and pipeline stages, and uses those same values.
You do, with your own folk account. Meteor does not resell folk: the connector uses your company's account and whatever your folk plan allows.
Step by step
Automations that use folk
Complete tasks, with the steps and the tools that run at each one.
Sell and serve
Other integrations in the same family
Want to see a Met running folk?
We will show you with your own account connected, not with a canned demo.