Short answer: Drop the "SuiteDash → Create SuiteDash 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 |
|---|---|---|---|
First Name first_name | string | Required | Contact's first name |
Last Name last_name | string | Required | Contact's last name |
Email email | Required | Contact's email address | |
Phone phone | string | Optional | Contact's phone number |
Company company | string | Optional | Contact's company name |
{"first_name": "e.g. Jane","last_name": "e.g. Doe","email": "e.g. user@example.com","phone": "e.g. +14155551234","company": "{{trigger.company}}"}
{"uid": "ct_abc124","email": "john@example.com","phone": "+1234567890","company": "Acme Corp","last_name": "Doe","created_at": "2025-03-15T10:00:00Z","first_name": "John"}
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.