Your app has sign-ups; some pay and most do not. You want a simple list: who created an account, who actually used it, who never paid, so you know who to talk to today. Well-known CRMs solve it with forms, typing or an automation tool, and someone ends up keeping a spreadsheet up to date. The shortest path is for the app to send the facts itself, the moment they happen.
This is how it works with People, from the Customers line (by Ciro Cesar Maciel, who writes this).
The idea: the stage comes from events
Nobody drags cards between columns. Each person's stage is derived from the events that arrived:
| Event | Effect |
|---|---|
| any first event | the person is lead
|
account.created |
prospect |
account.activated |
still prospect, with activation marked |
subscription.paid |
customer, the only way |
subscription.canceled after customer |
back to prospect
|
"Who never paid" becomes an exact question: who is a prospect. "Who signed up and never used it" is a prospect without activation, and you choose what counts as activation: the first project created, the first lesson finished. Customer is never manual: someone becomes a customer because the payment happened.
Step by step
1. Create a source. In the People dashboard, under Data › Sources, with a name and a legal basis. You get the address POST /events/<source-id> and a secret starting with whsec_, shown once: it goes into the app's environment variables.
2. Send events from the app. One protocol, Standard Webhooks with the x-ccm prefix: three headers with the delivery id, the timestamp and an HMAC signature of the body.
{ "type": "account.created",
"timestamp": "2026-10-07T12:00:00Z",
"data": { "person": { "email": "ana@school.example", "name": "Ana Souza" } } }
The agent that wrote your app writes this too; https://mycustomers.click/products/people/llms.txt has a full Node example. The three usual mistakes: signing with the secret without the whsec_ prefix, signing exactly the text you send, and using the server clock. Re-sending the same delivery id does not duplicate. If your system has its own event names, a translation map on the source maps them; an untranslated type is stored as it came, nothing dropped.
3. Bring the old spreadsheet. An import source takes a CSV with headers in English or Portuguese (e-mail, name, phone, company, source, campaign). Importing the same file again changes nothing.
How a record finds the right person
An event joins a record only through an identical identity: same e-mail, same phone, same id from your system. When an event points to two records, it goes to the stronger one and People suggests merging. Two records never merge by themselves.
After you know who did not pay
Each record has a timeline and a next step. People's agents propose it: a welcome message, a reply, an offer. Every action first passes a check with no AI involved: quiet hours, a weekly contact limit, what your Manual forbids promising. Decide one thing early: account Approval starts as Automatic, where agent actions go out on their own; switch to Through you to approve each message. Messages go by e-mail from your verified domain, or to a webhook of yours.
Honest notes
- No ready-made connector for any tool; the open protocol is the integration. Auth, Forms, Videos, Tasks, Blogs, Pages, Links and Newsletter send webhooks in the same protocol.
- No API key that writes: the only key,
prk_, reads. - No lead scoring, third-party enrichment, SMS or messengers.
- An MCP server lets an agent answer "who signed up this week and has not paid?".
- The plan counts sources only; people, events and imports are unlimited. Free: 1 source, no card, no expiry.
- The People dashboard is in Portuguese for now.
Top comments (0)