Delete Device

customer_io.delete_device
ActionCRM & salesconnection required

Calls the Customer.io API with the connection's credentials.

Remove a push device token from a person's profile so that device stops receiving push messages.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Customer.io
Secret shape
{"site_id": "…", "api_key": "…", "app_api_key": "…"} — the Site ID and Track API key for the Track nodes, the App API key for the rest
Config it needs
region, workspace_id
Resolved by
config.connection_id, else node.connection_id

Configuration

2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
identifier
How this person is addressed in the Track API: their id, their email address, or their Customer.io id prefixed with 'cio_'. A phone number is read as an id here, so it will not match.
stringYes——ada@example.com
device_id
The device token to remove.
stringYes———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

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

Output

One shape.

result

FieldTypeExample
accepted
True when Customer.io queued the write. Track writes are applied asynchronously, so this reports acceptance, not that the change is live.
boolean—
identifier
The identifier the person was addressed by.
string—
device_id
The device token that was removed.
string—
deleted
Always true; the delete was accepted.
boolean—
{
  "accepted": false,
  "deleted": false,
  "device_id": "",
  "identifier": ""
}

See Delete Device run in a workflow.

In a technical demo we add the Customer.io connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.