Skip to main content
An intro request is the tracked ask on a path: you, asking a connector to introduce you to someone at an account. It moves through four states.

States

A path holds at most one open request at a time.

Requesting an intro

From a path’s drawer, draft the message and send the request. This marks the path requested and stores your message. The drawer shows where the request stands. Move it along to Sent, Accepted or Declined through the intro request endpoints or the set_intro_status MCP tool. In the People table, track where a path stands with its tags: the default Status field carries the states a path goes through, and a tag is a column you can filter, sort and save as a view.

Why this exists

An intro request is the one action only Clustr can drive end to end, because it runs through a person, not a database. Tracking it turns “did that intro ever happen” from a question you’d have to ask your connector into a record you can read back and build a Workflow on.

Filtering on it

The API still filters warm intros on intro_status (requested, sent, accepted, declined), so an integration can list the paths at a given stage.