ActionOutreachUpdated September 2026
How do I upsert an Outreach prospect?
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.
Inputs
The fields this action accepts.
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. |
Sample request
{"email": "user@example.com","firstName": "Jane","lastName": "Smith","title": "VP of Sales","company": "Acme Inc"}
Returns
{"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.
Triggered by
Apps that pair well as the trigger for Upsert Outreach Prospect.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Upsert Outreach Prospect.
What does the Upsert Outreach Prospect action do in Outreach?
Match by primary email — create or update in one call. The base hook for "CRM contact → push to Outreach for outbound activity" sync workflows.
What inputs does Upsert Outreach Prospect require?
Required: Email. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Outreach returns an error?
The run history shows the failed step with its input and the error message Outreach returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Upsert Outreach Prospect support batch operations?
Run Upsert Outreach Prospect inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Outreach's rate limits.
More actions
Other Outreach actions.
Action
Add Prospect to Sequence
Enrolls a prospect with optional mailbox override. For "qualified lead → start nurture" or "trial signed up → enroll in activation sequence" workflows.
ActionCreate Outreach Task
Creates a follow-up task for a rep (e.g., post-meeting call). For "demo completed → create the proposal-follow-up task" workflows.
ActionList Outreach Sequences
Returns sequence catalog with status and prospect counts. Useful for resolving sequence IDs at workflow setup and for reporting on sequence inventory.
ActionRemove Prospect from Sequence
Stops a prospect's enrollment in a sequence. Common pattern: prospect replied → remove from competing sequences to prevent double-touching.