Short answer: You can create flowlu contact in FlowLu by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the FlowLu Create FlowLu Contact action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 | Optional | Contact's last name |
Email email | Optional | Contact's email address | |
Phone phone | string | Optional | Contact's phone number |
Company Name company_name | string | Optional | Company name for the contact |
{"first_name": "e.g. Jane","last_name": "e.g. Doe","email": "e.g. user@example.com","phone": "e.g. +14155551234","company_name": "{{trigger.company_name}}"}
{"id": 42,"email": "john@example.com","phone": "+1234567890","last_name": "Doe","first_name": "John","company_name": "Acme Corp","created_date": "2025-03-15 10:00:00"}
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.