Automation · Sales and quoting

Log in Attio whoever writes on WhatsApp, add them to the pipeline and leave the team a task

An AI agent logs in Attio the person who writes on WhatsApp, adds them to your deals list and leaves a note and a task.

Show me this with my own operation See every automation

How do I make every WhatsApp prospect land in Attio, in my pipeline and with a next step, without copying them by hand?

A Met connected to Attio looks the person up by email or phone number and creates or updates them by email, so they are not repeated. Before writing, it reads the object's attributes to fill the fields that exist in your workspace. Then it adds them to the list your team uses as a pipeline, leaves a note summarizing what they asked for and creates a task for the team member who will handle them, with a deadline. If someone later asks how that prospect is doing, the Met reads the list entry and the note.

What starts it

When the customer writes

It starts when a prospect writes on WhatsApp asking about your products or services. There is no trigger to configure: the Met assigned to the sales 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 qualifies prospects

Sales team

This is not a named, seeded Met. It is the Met that answers the sales line, with Attio connected. Its work ends when the prospect is in Attio exactly once, inside the pipeline, with the note of what they asked for and the task assigned.

Run by the lead qualification Met

Channels: WhatsApp

What you need connected

Attio Sell and serve

5 steps · 7 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
Look the person up in Attio

The Met searches by the email or phone number the person gave. Search works on indexed attributes, so the phone number and email should be in standard fields.
- search_records Attio
2
Read which fields the object has

Before writing, the Met lists the people object's attributes with their types and valid options. That way it fills the fields that exist in your workspace and does not invent one your team never created.
- list_attribute_definitions Attio
3
Create or update the record without duplicates

With the name, phone number, email and request, the Met creates the person or, if the email already exists, updates that record. That email match is what prevents repeats.
- upsert_record Attio
4
Add them to the pipeline list

The Met adds the record to the list your team uses as a pipeline, for example "Incoming deals". If it was already on the list, it updates its entry with what is new in the conversation.
- add_record_to_list Attio
- update_list_entry_by_record_id Attio
5
Leave the team's note and task

The Met creates a note on the record summarizing what the person asked for and a task for whoever will handle them, with a deadline and the linked record. Whoever opens Attio already knows what to do and when.
- create_note Attio
- create_task Attio

Before you start

What you need ready

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

Attio with the writes you need

In Met, open Connections → Attio → Connect and authorize with a user who has permission over people and the pipeline list. The admin leaves record create or update, lists, notes and tasks switched on.
A list that works as a pipeline

Your team has a deals or people list in Attio that it uses as a pipeline, and writes in the Met's skill which one it is and who receives the tasks.
A WhatsApp line with the Met assigned

The business connects its WhatsApp Business API line and assigns the Met that answers the sales line. The conversation happens there; Attio remains the prospect's record.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not merge duplicates that already existed in your workspace. If the same person is there twice with different emails, the Met works on the one it finds.
It does not find someone by a field Attio does not index. If the phone number lives in a custom attribute that is not indexed, the search may not see it.
It does not ask for confirmation in the chat before creating the record or the task: if the action is on, it runs it. The admin decides which writes stay on.
It does not book the sales meeting. It can search meetings already recorded in Attio, but booking a new one needs another scheduling integration.

FAQ

Questions about this automation

The Met finds them by email and updates the same record. If they were already on the pipeline list, it updates their entry instead of adding them again.

Yes. Each Met has its own skill, and there you write which Attio list it uses for the prospects coming through that line.

To the workspace member you name in the skill. The Met can list the workspace members, but the rule for who gets each case is yours.

Keep going