All docs

Records, notes, tasks and CSV

Open a record, edit it in place, keep notes and tasks on it, see its history, and bring many records in or out with a CSV file.

Updated . 5 min read.

The record page

Open a record from its table to see everything about it on one page:

  • Details - every field, editable in place. Each type has its own editor: a date picker for dates, coloured choices for selects, a person picker for members.
  • Relations - a panel for every relation, with the linked records and a way to link more.
  • Notes - rich text notes with an author. Pin the ones that matter. Authors change their own notes.
  • Tasks - follow-ups for this record, with a due time and an assignee. They also appear in the workspace's task list.
  • History - who created or changed the record, which fields changed (never the values), and every note and task added. Merged records show the merge here.

Contacts, companies, deals and tasks open here too. Their built-in fields are edited in place like any other field: the change goes through the same rules as on their own pages (a duplicate email is refused, moving a deal to a won or lost stage closes it and announces it, a lost deal asks for a reason). The own pages stay where they are, and each of them links to its table and board here.

Create, delete and restore

New in a table opens a side panel with the fields you can fill in. A contact needs an email, a phone number or a user ID; a deal and a task need a title.

Deleting a record happens in the background. A record of your own object goes to Deleted records (the button in the header of the object's table) instead of vanishing: it leaves lists, search and relation pickers, but it keeps its links and its unique values. From there you can Restore one or several records, Delete permanently one or several, or Empty trash. Deleting permanently is also done in the background and cannot be undone; it removes the record with its notes, tasks and history and frees its unique values. Whoever may delete records of the object may open its deleted records, restore from them and delete from them. The API and agents can do the same. A contact, company, deal or task is erased for good by the same background job as on its own page and has no deleted records. If a relation set to Block still links records to it, you are told which one.

Import records from a CSV

  1. Open the object and choose Import.
  2. Upload the file. Comma and semicolon files both work.
  3. Map each column to a field, or ignore it. Pick a unique field to match rows with records you already have, and say whether a match is updated or skipped.
  4. Run a check. It lists every row that would fail and why, and writes nothing.
  5. Choose Import. It runs in the background.

A Files field cannot be filled from a CSV and is left out of the column choices; add its files on the records after the import.

Contacts, companies, deals and tasks import here too. A contact row is matched to an existing contact by its email, user ID or phone number and updates it; a company row is matched by its domain; deals and tasks are always created. The contact rules stay: someone who was erased is not brought back, an email or phone number that is different from the one on file is added as an extra one instead of replacing it, your plan's contact limit applies, and the contact's source is set to import. Marketing consent cannot be imported here. A deal's stage and pipeline are matched by name, an owner or assignee by email or name, and a contact, company or deal by its id or its name.

A relation column takes the name of the related record. A record that was deleted and matches a row is brought back instead of being created twice. An import does not trigger an automation for every row.

Undo an import removes the records it created that nobody has worked on since (no edits, notes or open tasks) and puts back the values it changed unless they were edited again. Records that a Block relation keeps from being deleted are reported as blocked, not removed.

Export

Choose Export in a table to get a CSV of the records the view shows, or only the ticked ones. Columns follow the view. A file made this way can be imported again. The download link expires. Anyone who may change the records of an object may export them, whether the object is a standard one or your own; a viewer does not see the button. Fields your role cannot see are left out, and a record rule limits the file to the records the role may see. Contacts can be exported too; a role that may not export submissions gets only id, name, company, source, owner and dates, never email, phone or custom fields. Sample data is left out of every export.

Bulk actions

Tick records to Set a field on all of them, Link to or Unlink from a relation, or delete them. Each record is its own change; the ones that were refused are listed with the reason.