New

Client contacts over the API, and finding a client before creating one

The API can manage client contacts, look clients and projects up by exact name, and find-or-create them in one call.

For integrations such as Zapier that keep clients in step with another system:

  • Client contacts over the API. List, add, update and remove the people at a client at /v1/clients/{id}/contacts. An email can be on a client only once, ignoring capitalization. A second one is refused with a conflict that says which contact already has it. The Clients page now applies the same rule.
  • Look a client or project up by its whole name with name_exact. Projects can now also be filtered by a name fragment.
  • Find-or-create in one call with find_existing on creating a client or project. A match is returned as it is, unchanged.
  • Client responses include notes.
  • Archived clients and projects are left out of lists unless you ask for them with include_archived=true. Until now they were mixed in. If something you built relies on seeing archived records, add that parameter.
  • A project or contact can no longer be filed under another workspace's client. Both used to be accepted.

The assistant can now find clients that have no projects yet, read their notes and contacts, and, for owners and admins, add a contact or update one. It does not remove contacts.

← Everything that has changed

The hours, the invoices, and what they earned

Free for unlimited people. One paid plan, $10 per member per month, when you want HR, scheduling, timesheet approvals, scheduled backups, email from your own domain and scheduled reports.

Start free