Skip to main content
Learn these eight words once and the field names explain themselves.

Person

Someone Ziplined has seen around your workspace. They engaged, they follow you, they connected, or you added them.
A person record carries the profile, the relationship and your own notes and tags.
Profile: name, headline, job_title, company, company_id, company_industry, company_size, country, location, seniority, industry, connection degree, follower and connection counts.Relationship: stage, fit, warmth, first_engaged_at, last_engaged_at, last_engaged_type, engagements_30d.Yours: notes, tags, outreach_count, last_outreach_at.Contact details (email, phone and their lookup status) need the separate contacts scope. Without that scope the fields are absent, not null.

Fit

How well someone matches your ideal customer profile.
Score runs 0 to 100. Tier is none, low, medium or high. Fit moves only when their profile or your ICP changes.

Warmth

How engaged someone has been lately.
Score runs 0 to 100. Tier is cold, cool, warm or hot. Warmth decays when they go quiet.
High fit with cold warmth is someone worth warming up. Hot warmth with low fit is an audience member, not a lead.

Stage

Where the relationship stands, as a decision you made.
One of lead, customer, peer, watchlist, disqualified, or null when undecided. Set it with PATCH /v1/people/{person_id} or the update_person tool.
watchlist is a pin: someone you want to keep an eye on.disqualified beats every other stage, so a disqualified person never reads as undecided.

Audience

A named list of people inside your workspace.
Audiences narrow anything that takes a list: a people search, a routing rule, an enrichment run. In MCP you pass the audience name, not the id.
people_count and companies_count are the state of the last scoring round, not of this second.An unknown audience name in MCP answers with the names that do exist, so no lookup call is needed. Archived audiences are left out of list_audiences.

Source

Something whose posts and reactions Ziplined collects. The app calls the set of them your radar.
A source is a person, a company or a keyword query. source_kind is team, competitor, influencer or market. GET /v1/sources answers “why is this person in my list”.
A source is active, paused or removed. Pausing stops collection and keeps everything already gathered.

Post

One of your own posts, with its numbers.
These are your posts, not the posts of the sources you track. Feed a post_id into a people search to see who engaged with it.

Engagement

One act by one person on one post: a like, a comment or a share.
Engagement is the raw layer under warmth. It records a UTC day and the source it arrived through.
GET /v1/engagements requires a person_id. The read binds on the people you name, not on the whole workspace.For “who engaged with this post”, use the people search with the post id instead.

Outreach

What you sent, as opposed to engagement, which is what they did.
A channel is linkedin_message, email, call or other. Logging outreach is what makes “warm and never approached” a filter you can trust.
outreach_count and last_outreach_at on the person record are rebuilt nightly. They lag one night behind. The act itself is readable straight away in the person detail.