know-customers

原文涵盖的主题

• Know your customers
• 1. Sign in to the Customers line (once)
• 2. Create the source
• 3. Send the app's moments
• 4. Prove it
• 5. Read people in the conversation
• What comes next, offered once
• Suggest it in the open

The person has users and does not know which of them are trying, which are using, which are paying, and who needs a word today. The app already knows: every sign-up, activation and payment happens in its code. Send those moments to People, and the answer comes from the app itself. The CLI lives two folders above this skill's base directory: node " /../../bin/ccm.js" line .... People starts free, without a card and without expiry, with 1 source. PEOPLEEVENTSURL and PEOPLEEVENTSSECRET go into the env file, kept out of git. The secret is shown only once, at creation. Find where the app creates an account, activates it (the first real use) and receives a payment, and send one event at each, on the server, never from the browser: | Moment | Type | |---|---| | Account created | account.created | | First real use | account.activated | | Paid | subscription.paid or purchase.completed | | Cancelled | subscription.canceled | The app's own names also work (aula.concluida): People keeps them and asks for a translation. Sign each delivery the way the webhooks skill shows, with the x-ccm- headers, and this body: Use the same x-ccm-id when you retry a delivery: People treats it as a resend and do

这里只展示节选，请以完整原文和当前要求为准。