Short answer: You can create mautic contact in Mautic by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Mautic Create Mautic 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 |
|---|---|---|---|
Email email | Required | The email address. Used as the recipient or identifier depending on context. | |
First Name firstname | string | Optional | Contact's first (given) name. |
Last Name lastname | string | Optional | Contact's last (family) name. |
Company company | string | Optional | Company |
Tags tags | string | Optional | Comma-separated |
{"email": "e.g. user@example.com","firstname": "e.g. Jane","lastname": "e.g. Doe","company": "{{trigger.company}}","tags": "lead, newsletter"}
{"contact": {"id": 123,"fields": {"core": {"email": {"value": "john@example.com"},"firstname": {"value": "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.