Mesh

Connect AI agents to Mesh (formerly Clay), a personal relationship manager that keeps track of who you owe a reply. Agents enrich contacts, organize them into groups, and surface the relationships that have gone quiet.

13 actions API key available

Platform Documentation ↗

A calendar meeting ends or an intro email thread goes quiet

Agent reads the attendees and the thread subject from the source system

Search Contacts looks each attendee up so an existing relationship is not duplicated

Create Contact adds anyone Mesh has never seen, with their handles set correctly

Add Note writes what was discussed onto the contact's record

A weekly digest names the relationships that have gone quiet past their cadence

You decide which of those cadences to change or stop before the agent writes it

What This Integration Enables

Mesh, formerly Clay, is not a sales CRM and it is a mistake to automate it like one. There is no pipeline here, no forecast, no deal stage. The object at the centre of the product is the reconnect cadence, and the job it does is telling you who you have stopped talking to. Everything else in the API serves that: contacts, notes, timelines, groups, and an activity feed. So the useful automation is not moving records through stages, it is making sure the record is complete enough for the reminder to be worth acting on. A reconnect nudge with no note attached is just guilt. A reconnect nudge that says what you last talked about is a reason to write.

FlowRunner agents keep that record fed. They create contacts from meetings, signups, and inbound email, log notes and interactions from the tools where the conversation actually happened, keep group membership in step with an external source of truth, and enrich an email address into a full profile before it goes anywhere else. Mesh does not publish a webhook subscription API, so this connector ships no triggers and agents poll Get Activity Feed or Search Contacts on a schedule instead. The vendor also describes this API as being in private beta for select customers and states that endpoints and responses may change, so treat key availability as something to confirm on your own account. What FlowRunner adds is the part a personal CRM cannot do for itself: the agent handles the typing, and you keep the judgment about who matters. That is human-in-the-loop applied to a system whose entire value is your attention.

Without FlowRunner

Notes that never get written The meeting ends, the context lives in your head, and a week later it is gone

Follow-ups you meant to do Important people go quiet and nothing in the system ever raises them again

Contacts scattered by source The same person exists in a calendar invite, an inbox, and nowhere durable

With FlowRunner

Context captured at the moment Notes land on the record while the meeting is still fresh, without you typing

Quiet relationships surfaced The reconnect cadence does its job because it is actually being maintained

One place that knows the person Every touch from every tool arrives on the same contact record

Use Case Scenarios

Meetings that log themselves

A meeting ends in Google Calendar. The agent reads the attendee list, calls Search Contacts on each email address, and uses Create Contact for anyone Mesh has not met, taking care to store social fields as handles rather than URLs because that is what the API expects. Add Note writes the agenda and the outcome onto each attendee's record. Set Reconnect Cadence proposes a follow-up rhythm based on the meeting type. What lands in Mesh is not just a name and a date, it is the reason you spoke, which is the thing you actually need three months later.

Groups kept in step with the real list

An investor list, an alumni cohort, or a customer segment lives in Airtable as the source of truth. On a schedule, the agent calls List Groups to find the target group, reads the current Airtable rows, and uses Create Group or Edit Group to bring Mesh into line. People who have joined the list get Create Contact and a starting cadence. People who have left are reported rather than removed, because a group in a personal CRM is often the only record that a relationship existed at all.

Inbound email enriched before it becomes a relationship

A new signup or intro arrives with nothing but an email address. The agent calls Look Up Profile by Email to pull name, bio, location, avatar, and social links, then Search Contacts to check whether this is someone you already know under a different address. If it is new, Create Contact writes the enriched profile and Add Note records how the introduction happened. If it matches an existing contact, the agent proposes the additions rather than applying them, so a stale third-party bio does not overwrite something you wrote yourself. Note that Look Up Profile by Email requires expanded account permissions, so a valid key alone may not be enough for this step.

Human-in-Loop Highlight

Disable Reconnect is the quietest destructive action in this connector. It does not delete anything. It removes a person from the only mechanism in Mesh that would ever raise them again, and after that the contact simply stops appearing. Set Reconnect Cadence carries the same weight in slower motion, because moving someone from monthly to yearly is a decision that this relationship is now background. So an agent tuning cadences from an external signal, say a CRM field or a last-contacted date in a spreadsheet, does not write them. It assembles the proposal and sends it: "Fourteen contacts have had no logged interaction in over a year. Nine are in the Investors group and are set to quarterly. Three are set to weekly and have never had a note added, which usually means the cadence was set by an import rather than by you. Proposed: move the nine to yearly, disable reconnect on the three, leave the rest. Confirm, edit, or skip." You answer, and only then does the agent call Set Reconnect Cadence and Disable Reconnect. The system that reminds you who to call is the one thing you should never let an automation silence on its own.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

13 actions

Contacts

Search Contacts Searches your contacts and returns matches with their numeric IDs. Used as the lookup step before any create, and as the polling surface for change detection since this connector has no triggers.
Get Contact Retrieves a single contact by its numeric ID. Used to load the full profile before an update or a cadence decision.
Create Contact Creates a new contact in Mesh. Used to turn a meeting attendee, a signup, or an inbound email into a tracked relationship instead of a name you half remember.
Update Contact Updates an existing contact. Social fields for Twitter, LinkedIn, Instagram, Facebook, GitHub, and YouTube are stored as handles or slugs rather than full URLs, so agents normalize before writing.
Get Contact Timeline Returns the interaction history for a contact by numeric ID. Used to see what actually happened with someone before you reach out again.
Look Up Profile by Email Enriches an email address into a profile with name, bio, location, avatar, and social links. Requires expanded account permissions, so this action may be rejected even with a valid key.

Notes and Reconnects

Add Note Writes a note onto a contact by numeric ID. Used so the context from a call, a meeting, or a thread lands on the record while it is still accurate.
Set Reconnect Cadence Sets a reconnect rhythm of weekly, monthly, quarterly, or yearly on a contact, with group cadences additionally accepting disabled and auto. Used to decide how often a relationship should surface, and gated because that decision is yours.
Disable Reconnect Turns off reconnect reminders for a contact. Nothing else in the product will raise that person again, so agents propose this rather than performing it unprompted.

Groups

List Groups Returns your groups with their IDs. Used to resolve the right group before a membership change.
Create Group Creates a new group such as investors, alumni, or customers. Used to stand up a segment before contacts are organized into it.
Edit Group Updates an existing group. Used to keep group definitions in step with an external source of truth.

Activity

Get Activity Feed Returns your activity feed. Used on a schedule to drive reporting and follow-up automations, which is how change detection works here in the absence of webhooks.

Frequently Asked Questions

What can FlowRunner do with Mesh?

FlowRunner agents can run Search Contacts, Get Contact, and Get Contact Timeline in Mesh, plus 10 more actions.

Does connecting Mesh to FlowRunner require OAuth?

No. Mesh connects to FlowRunner with an API key, no OAuth flow required.

Can Mesh trigger a FlowRunner workflow automatically?

Mesh doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Mesh

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us