Short answer: You can create sendfox contact in SendFox by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the SendFox Create SendFox Contact action to a workflow, map its 4 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 first_name | string | Optional | Contact's first (given) name. |
Last Name last_name | string | Optional | Contact's last (family) name. |
List IDs lists | string | Optional | Comma-separated list IDs |
{"email": "e.g. user@example.com","first_name": "e.g. Jane","last_name": "e.g. Doe","lists": "{{trigger.lists}}"}
{"id": 123,"email": "john@example.com","created_at": "2026-04-11T10: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.