Delete Person: Customer.io action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Customer Identifier identifier	string	Required	Customer Identifier. e.g. "user@example.com"

Sample request

{
  "identifier": "user@example.com"
}

Returns

{
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Delete Person.

What does the Delete Person action do in Customer.io?

Hard-deletes the person and history. Irreversible — used for GDPR right-to-erasure compliance flows. For soft-removal use suppression list or unsubscribe.

What inputs does Delete Person require?

Required: Customer Identifier. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Customer.io returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Delete Person support batch operations?

Yes. Run Delete Person inside a Loop node to process arrays. Tiny Command handles Customer.io's rate limits automatically so you don't have to throttle manually.

More actions