Quickstart
Connect Claude Code to Customer.lite over MCP, then let it create a customer and a workflow, take the workflow live with your approval, and show you what it sent. About ten minutes.
Before you start
Section titled “Before you start”- A browser, to sign in to the dashboard.
- Claude Code, or another MCP client that speaks Streamable HTTP and can send a header.
- A domain to send from that your installation’s operator has verified (Sending). You can do steps 1 to 4 without one.
In the commands below, <app-origin> is the address of the Customer.lite app you sign in to, for example https://app.example.com. On a self-hosted installation it is your Worker’s APP_ORIGIN.
1. Sign in and create a workspace
Section titled “1. Sign in and create a workspace”Open <app-origin> in a browser and sign in with an email code or Google. Create a workspace when the dashboard asks for one. You become its admin.
2. Create a project and an API key
Section titled “2. Create a project and an API key”A workspace holds one project, and an API key acts on one project. In the dashboard, open Settings › API keys. If the workspace has no project yet, select Create project first. Then select Create API key.
The new key starts with cl_sk_. Copy it now: the dashboard shows it only once and keeps only a hash. If you lose it, revoke it on the same page and create another. Only an admin of the workspace can create the project and its keys. Authentication covers what a key can do.
3. Connect Claude Code
Section titled “3. Connect Claude Code”Read the key into a shell variable without echoing it or leaving it in your shell history, then add the server:
read -rs CUSTOMER_LITE_API_KEY # paste the key from step 2, then press Enterclaude mcp add --transport http customer-lite <app-origin>/mcp \ --header "Authorization: Bearer $CUSTOMER_LITE_API_KEY"The dashboard’s Overview shows the same claude mcp add command with your address filled in.
Claude Code stores the header, key included, in your own user configuration. Keep its default scope: --scope project would write the key into a .mcp.json in your repository, where it could be committed.
Start Claude Code and run /mcp: customer-lite should be listed as connected, with tools such as customers_upsert and workflows_upsert. Then check the connection with a question that changes nothing:
Using customer-lite, show this project’s delivery metrics.
Claude Code calls metrics_get and reports zeros for a new project. If /mcp shows the server as failed, the key is wrong or revoked: the endpoint answers 401 before any tool runs. Any MCP client that speaks Streamable HTTP and can send a header connects the same way.
4. Ask for a workflow
Section titled “4. Ask for a workflow”Ask Claude Code in plain language. For example:
Using customer-lite, add a customer
user_123with the emailada@example.comand the attributeplan: "trial". Then create a workflowwelcomethat starts on the eventuser.signed_up, waits a minute, checks thatplanis stilltrial, and sends a short welcome email fromhello@yourdomain.example.
Claude Code calls customers_upsert and workflows_upsert. The workflow is saved as a draft: nothing runs, and nothing is sent. The definition it saves looks like this:
{ "trigger": { "type": "event", "event": "user.signed_up" }, "steps": [ { "id": "wait", "type": "delay", "seconds": 60 }, { "id": "still-trial", "type": "condition", "attribute": "plan", "operator": "equals", "value": "trial" }, { "id": "welcome", "type": "send_email", "from": "hello@yourdomain.example", "subject": "Welcome aboard", "body": "Thanks for signing up. Reply to this email if you get stuck." } ]}5. Go live, with a person in the loop
Section titled “5. Go live, with a person in the loop”Ask Claude Code to activate the workflow. Two checks stand between that request and any email:
- A preview. The first
workflows_activatecall changes nothing. It answersconfirmation_requiredwith a preview of who would be sent what, and a token. Claude Code shows you the preview; only if you agree does it call again with the token. - A human approval. Because the workflow sends email, the confirmed call does not make it live yet. It returns a pending send approval, and each approver of the workspace gets an approval link by email. The link does not go to the caller, so the assistant cannot approve its own work (unless a self-hosted installation chose otherwise; see Self-hosting). Once an approver approves, the workflow is live.
Two refusals are common here, and neither changes anything: sender_not_verified means a from domain is not a verified sending domain of the workspace yet, and no_approvers that the workspace has nobody to approve. Both are set up by whoever operates your installation; see Sending.
6. Send an event and watch it run
Section titled “6. Send an event and watch it run”When a user signs up, your application records the event with your API key:
curl -X POST <app-origin>/api/events \ -H "Authorization: Bearer $CUSTOMER_LITE_API_KEY" \ -H "content-type: application/json" \ -d '{ "customerId": "user_123", "name": "user.signed_up", "idempotencyKey": "signup-user_123" }'The live workflow starts a run for user_123, which waits a minute before it sends. Then ask Claude Code what happened: it reads the result with messages_list and messages_get, which show each message’s state, its delivery result, and the step log that explains why a message was or was not sent.
- Workflows: every step type and how versions work.
- Sending: approval, confirmation, unsubscribe, and message states.
- API reference: every tool’s input, output, and errors.