Short answer: You can create keap contact in Keap by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Keap Create Keap 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 given_name | string | Optional | First Name |
Last Name family_name | string | Optional | Last Name |
Phone phone | phone | Optional | Phone number in E.164 format (with country code, no spaces). |
Company company | string | Optional | Company |
{"email": "e.g. user@example.com","given_name": "{{trigger.given_name}}","family_name": "{{trigger.family_name}}","phone": "e.g. +14155551234","company": "{{trigger.company}}"}
{"id": 123,"given_name": "John","family_name": "Doe","email_addresses": [{"email": "john@example.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.