Custom fields
The record has the fields we thought of. Custom fields are the ones you did.
Typed fields, whole tabs, cards, tags, statuses and personas. They filter, they merge into mail, they show in lists.
The record has the fields we thought of. Custom fields are the ones you did. Add them from any list or record page, and they behave like the built-in ones everywhere: filters, columns, merge fields, the assistant.
Fields
- Types: text, number, date, select, multi-select, checkbox, URL, and more.
- On people, companies or deals.
- They filter like built-in fields and show as list columns.
- Every custom field is a merge field. A Trial Phase column becomes a variable in a subject line.
Tabs
A whole section on a record page. An Onboarding tab on companies with go-live date, CSM and health. A Renewal tab on deals with the term, the notice period and the risk. The tab is a form the whole team fills in the same way.
Cards
A compact panel on the Overview tab, beside the Brief. Three or four fields you want in view every time you open the record.
Through the assistant
Set them up inline on any record page, or ask. Add a renewal date field to companies is one line. Add an onboarding tab with go-live, CSM and health is one more.
Around custom fields
The parts of the workspace this one works with.
Tags, statuses and personas
The labels that filters, enrollment criteria, workflows and bulk edits all key off.
Three kinds of label, each for a different question. Tags for cross-cutting groups. Status for where someone is in the lifecycle. Persona for their role in the buying process.
People, companies and deals
The workspace memory of who you know and what you are selling them, with every conversation attached.
A record is not a row you keep up to date by hand. Email, texts, LinkedIn threads, meetings, tickets, documents and website visits attach themselves to the person and company they belong to, so the page reads as a history. The list pages are how you find your way to one.
Select everything a filter matches
Filter a list, select all of it, act on all of it. Not just the page you can see.
Selecting the fifty rows that happen to be loaded was never what you wanted. Now a selection can mean everything the filter matches, however many that is.
Questions
Can a custom field be required?+
A form can require it. On a record it is optional, and a workflow can flag records missing it.
Do custom fields import from a CSV?+
Yes. Map a column to a custom field on import, or create the field during the import.
Where do I edit the status list?+
From the status strip on People or Companies, or from Workspace settings for the colours.
Can a tag be private?+
Tags are shared. Use a saved view for a personal list.
How do records get created?+
From the extension on LinkedIn, from a CSV import, from a form, from an email or meeting with someone new, from the assistant, or by hand.
Can I hide columns for the whole team?+
Column layouts are per person. A shared saved view carries its own column set, which is the way to give the team one layout.
Is there an API?+
Everything is an MCP server, and the assistant can import, export and edit in bulk. Ask it for the CSV.
Is there an undo?+
Bulk edits are logged in Member activity with what changed. A status change can be reversed with the opposite filter.
What is the limit?+
None. The action runs in the background for a large set and reports when it is done.
Try custom fields on your own data
Connect your email, then open a person. Most of the product shows up on that one page once the mail is in.
More in Records
People, companies, deals and customers, with every conversation attached.
Every person is a live mirror of their LinkedIn profile. It updates itself every time you visit.
The people, their roles, the deals, the paperwork, the conversations, and who is hiring for what.
Stages you define, a board you drag, and a deal that already knows when it last heard from them.
MRR, subscriptions, past-due state and payment history from Stripe, next to the conversations.
A name and a company is enough. Verification checks deliverability instead of guessing a pattern.