Short answer: Drop the "Tidio → Upsert Contact" 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 | The email address. Used as the recipient or identifier depending on context. |
Name name | string | Optional | — |
Phone phone | string | Optional | Phone number in E.164 format (with country code, no spaces). |
Tags tags | array | Optional | — |
{"email": "e.g. user@example.com","name": "{{trigger.name}}","phone": "e.g. +14155551234","tags": "{{trigger.tags}}"}
{"id": "con_abc","name": "Jane","email": "jane@x.com"}
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.