Contacts & Inbox API

Contacts list

Every person who contacted or bought from the business, newest activity first: form leads, bookings, waitlist, orders and quotes, shop accounts, newsletter contacts and helpdesk tickets, matched by email, then phone. Only the sources the project's package includes and this member may open.

One contact and their timeline

The person (name, email, phone, consent, tags, notes) and everything they did across the tools, newest first, each with a link to the tool's own record. By key (from the list), by email, or the first match of a search.

Needs your answer

What still waits for the owner, newest first: new leads (30 days), open tickets, bookings to confirm, paid orders to ship and quote requests (30 days), until they are handled in their tool or marked done.

Mark an item done

The item leaves Needs your answer (done = false brings it back). The lead, booking, order or ticket itself does not change.

Add a note

A note on the person for the team (never sent to them).

Delete a note

Save the tags

The person's tags, all of them (an empty list removes every tag).

Contacts as CSV

The list with the same filters, one person per row. Only the sources this member may open.

A person's data (privacy export)

Everything the project holds about one person, from every source the package includes (archived records too), as one JSON document to hand to them (GDPR Art. 15 and 20). The owner, an Admin or a platform manager only.

Delete a person (privacy delete)

Without confirm: the plan, per source what goes and what stays and why. With confirm: each tool deletes the person's records through its own delete path (form answers, tickets, waitlist, shop account, newsletter contact); orders and bookings stay for the bookkeeping. The owner, an Admin or a platform manager, signed in to the dashboard (never an API or AI token).