Short answer: Drop the "Klaviyo → Create Profile" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Email email | string | Required | Email address of the profile |
First Name first_name | string | Optional | First name of the profile |
Last Name last_name | string | Optional | Last name of the profile |
Phone Number phone_number | string | Optional | Phone number in E.164 format (e.g. +15551234567) |
{"email": "customer@example.com","first_name": "John","last_name": "Doe","phone_number": "+15551234567"}
{"data": {"id": "01JABCDEF123456789","type": "profile","attributes": {"email": "customer@example.com","created": "2026-04-23T10:00:00+00:00","updated": "2026-04-23T10:00:00+00:00","last_name": "Doe","first_name": "John","phone_number": "+15551234567"}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.