Short answer: You can create pardot prospect in Pardot by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Pardot Create Pardot Prospect action to a workflow, map its 6 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 | string | 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 | – |
Phone phone | string | Optional | Phone number in E.164 format (with country code, no spaces). |
Campaign ID campaignId | string | Optional | – |
{"email": "e.g. user@example.com","firstName": "e.g. Jane","lastName": "e.g. Doe","company": "{{trigger.company}}","phone": "e.g. +14155551234"}
{"id": 9999,"email": "jane@x.com","firstName": "Jane"}
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.