Automation · Sales and quoting

Register in folk the customer who writes on WhatsApp and leave a follow up task

An AI agent registers in folk whoever writes on WhatsApp, leaves a note with what they asked for and creates the follow up task for your team.

Show me this with my own operation See every automation

How do I make every customer who writes on WhatsApp land in folk with their request and a follow up task?

A Met connected to folk first reads your workspace structure, with the groups and fields your team uses. When someone writes on WhatsApp, it looks them up by name or email; if they are not there, it creates them in the right group. Then it leaves a note on their record with what they asked for, logs the conversation as an interaction and creates a follow up task assigned to the teammate who should reply. Nobody has to copy the chat by hand: the context stays in folk, where your team already works.

What starts it

When the customer writes

It starts when someone writes on WhatsApp asking for information, a price or an appointment. There is no trigger to set up: the Met assigned to the line runs the procedure inside that conversation.

Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.

Who runs it

Met that receives and registers new customers

Sales team

It has no seeded name: it is the Met that answers the sales WhatsApp line with folk connected. Its work ends when the person is in folk, with a note of what they asked for and a task assigned to someone on the team.

Run by the lead qualification Met

Channels: WhatsApp

What you need connected

folk Sell and serve

6 steps · 6 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Read how your workspace is organized

The Met loads the folk workspace structure: groups, custom fields with their allowed values and team members. With that it knows which group to register the person in and who it can assign the task to.
- folk_get_workspace_structure folk
2
Check whether the person exists

With the name or email given in the chat, the Met searches folk for the person. If they are already there, it keeps that record and does not create another one.
- folk_search_people folk
3
Create them if they are new

If they do not show up, the Met creates the person with their name, email and phone, and adds them to the group its instructions point to. This step needs the create people action on.
- folk_create_person folk
4
Leave a note with what they asked for

The Met writes a note on the person's record summarizing what they asked for on WhatsApp: the product, the budget or the date they mentioned.
- folk_create_note folk
5
Log the conversation as an interaction

The Met logs the conversation as an interaction with the person, with its date and the WhatsApp type, so the folk history shows there was contact on that channel that day.
- folk_create_interaction folk
6
Create the follow up task

Finally, the Met creates a task linked to the person, assigned by email to whoever should reply. That teammate sees it in folk like any other task.
- folk_create_task folk

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

The folk ready connector

In Met, open Connections → folk → Connect, sign in to folk and authorize access. Then leave on the actions to create people, notes, interactions and tasks.
A WhatsApp line with the Met assigned

You connect your WhatsApp Business API line in Met and assign the sales Met. folk remains the CRM; the conversation happens on WhatsApp.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not ask anyone for confirmation before creating the person or the task. If the actions are on, the Met writes to folk with what was said in the chat.
It does not edit the conversation folk already imported. If folk syncs your messages on its own, the interaction the Met creates is separate and manually logged.
It does not send a WhatsApp notice when a teammate closes the task. folk shows the task to its assignee; a notice back needs a separate automation.
It does not remove duplicates. If the person wrote before with another email, a second record may remain for your team to merge in folk.

FAQ

Questions about this automation

The Met finds them in the search of the second step and keeps that record: it leaves the note, the interaction and the task on the existing record.

Whoever the Met's instructions say, by email or by id. The workspace structure includes the members, so the Met assigns someone who exists in folk.

Yes, the folk page includes the action to create objects such as deals. This automation stops at registering and following up; the deal is added if your instructions ask for it.

folk does not publish a plan requirement for its MCP server in the documentation we checked. Usage runs on your folk account and plan.

Keep going