Updating People from Customer.io

You can run two operations against the platform from a Customer.io workflow (or from a Claude / terminal script):

1. Add a person to a community.
2. Set a person's signup code.

That's it. There are no other operations and nothing else can be changed through this route. Every call is recorded in the audit trail and posted to #ops-webhooks in Slack.

Before You Start

You need a platform access token. Engineering hands these out — they are not self-serve.

• For Customer.io workflows, engineering will set up the token once as a workspace credential. After that, every workflow you build just references it.
• For scripts (Claude, terminal, anything you write yourself), engineering will hand you a separate token. Treat it like any other API key — never paste it into Slack, never commit it to git.

The token only has permission to do these two operations. It cannot read profiles, see investments, or change anything else.

How a Customer.io Webhook Action Is Structured

Every call uses Customer.io's built-in Webhook action. The UI has four parts you fill in, in this order:

1. Method — a dropdown. Always set to POST.
2. URL — a single text field. Paste the full URL for the operation you want (URLs are listed below).
3. Headers — a list of Name / Value rows. Click Add header for each row. You always need three headers (see below).
4. Body — the JSON payload. Click into the body editor and paste the JSON block for the operation.

The three headers are the same for every operation:

The two operations below differ only in their URL and Body. Method and headers are identical.

Operation 1 — Add Someone to a Community

URL:

https://app.letsplaymoney.com/api/v1/ops/people/communities/add

Body:

{
  "data": {
    "type": "communityMembership",
    "attributes": {
      "personId": {{ customer.id }},
      "communityId": 42
    }
  }
}

What to fill in:

• {{ customer.id }} — leave this as Liquid. For every normal investor profile, Customer.io stores the person's Play Money ID here and substitutes it automatically.
• 42 — the numeric ID of the community you want them added to. Open the community in admin and look at the URL: /admin/communities/42 → the ID is 42. Send it as a number, not a string (no quotes).

If you don't have the Play Money ID handy, you can send "email" instead of "personId".

What the response tells you:

• "alreadyMember": false — added them.
• "alreadyMember": true — they were already a member. Nothing changed.

Either way, the call succeeded. It is safe to call this for the same person repeatedly — no duplicate memberships, no duplicate audit entries.

Operation 2 — Set Someone's Signup Code

URL:

https://app.letsplaymoney.com/api/v1/ops/people/code

Body:

{
  "data": {
    "type": "personSignupCode",
    "attributes": {
      "personId": {{ customer.id }},
      "code": "VC-Partners"
    }
  }
}

Replace "VC-Partners" with the code you want to set.

To clear someone's code (reset it to the platform default), send the word null for the code value:

"code": null

What the response tells you:

• "changed": true — the code was updated. "previousCode" shows what it was before.
• "changed": false — the code was already that value. Nothing changed.

Safe to repeat.

When Something Fails

Customer.io will log the HTTP status. Here's what each one means and who fixes it:

Every error response includes a plain-English detail field that says exactly what went wrong. Read it first before asking for help.

Good to Know

• One person, one operation, one call. There is no batch endpoint. To add 50 people to a community, send 50 calls — Customer.io workflows handle this naturally because they run per-person anyway.
• Audit trail. Every successful call shows up in the audit trail attributed to "Customer.io" (or "Marketing Ops" if it came from a script). The previous value, new value, and the originating workflow are all recorded.
• Slack. Watch #ops-webhooks for a live log of every call. If a workflow you just published is misbehaving, you'll see it there immediately.

Running It from a Script Instead

Customer.io isn't the only way to call these. If you're scripting (Claude, a one-off terminal command, a small Python tool), you use the script token engineering gave you instead of the workspace token. The URL and body are identical to what's above. The only difference: scripts only need the Content-Type and Authorization headers — X-CIO-Idempotency-Key is Customer.io-specific, so skip it (or send your own unique value if you want retry safety).