Short answer: You can upsert outreach prospect in Outreach by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Outreach Upsert Outreach Prospect action to a workflow, map its 9 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 prospect's email. Used as the dedupe key. |
First Name firstName | string | Optional | First name. |
Last Name lastName | string | Optional | Last name. |
Job Title title | string | Optional | Job title. |
Company company | string | Optional | Company name. |
Mobile Phone mobilePhone | string | Optional | Mobile phone in E.164 format. |
Work Phone workPhone | string | Optional | Work phone in E.164 format. |
LinkedIn URL linkedInUrl | string | Optional | LinkedIn profile URL. |
Owner User ID ownerId | string | Optional | Outreach user ID to own this prospect. |
{"email": "user@example.com","firstName": "Jane","lastName": "Smith","title": "VP of Sales","company": "Acme Inc"}
{"data": {"id": "1234567","type": "prospect","attributes": {"title": "VP of Sales","emails": ["jane@example.com"],"company": "Acme Inc","lastName": "Smith","createdAt": "2026-04-11T10:00:00.000Z","firstName": "Jane","updatedAt": "2026-04-11T10:00:00.000Z"}}}
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.