ActionSalesloftUpdated September 2026
How do I upsert a Salesloft person?
Short answer: You can salesloft upsert person in Salesloft by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Salesloft Salesloft Upsert Person 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_address | string | Required | The person's email. Used as the dedupe key for upsert. |
First Name first_name | string | Optional | First name. |
Last Name last_name | string | Optional | Last name. |
Job Title title | string | Optional | Job title. |
Phone phone | string | Optional | Primary phone number. |
Mobile Phone mobile_phone | string | Optional | Mobile phone number. |
LinkedIn URL linkedin_url | string | Optional | LinkedIn profile URL. |
Company Name company_name | string | Optional | Person's current company. |
Owner User ID owner_id | string | Optional | Salesloft user ID to own this person record. |
Sample request
{"email_address": "user@example.com","first_name": "Jane","last_name": "Smith","title": "VP of Sales","phone": "+15551234567"}
Returns
{"data": {"id": 1234567,"title": "VP of Sales","last_name": "Smith","created_at": "2026-04-11T10:00:00.000Z","first_name": "Jane","updated_at": "2026-04-11T10:00:00.000Z","company_name": "Acme Inc","email_address": "jane@example.com"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Salesloft Upsert Person.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Salesloft Upsert Person.
What does the Salesloft Upsert Person action do in Salesloft?
Email-based dedupe — create or update in one call. The base hook for "external lead source → push to Salesloft for outbound activity" sync.
What inputs does Salesloft Upsert Person 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 Salesloft returns an error?
The run history shows the failed step with its input and the error message Salesloft 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 Salesloft Upsert Person support batch operations?
Run Salesloft Upsert Person 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 Salesloft's rate limits.
More actions
Other Salesloft actions.
Action
Salesloft Add Person to Cadence
Enrolls a person in a sequence. For "qualified lead → start the outbound cadence" or "trial signed up → enroll in activation sequence" workflows.
ActionList Salesloft Cadences
Returns paginated cadences with metadata. Useful for resolving cadence IDs at workflow setup.
ActionSalesloft Log Call
Records a call activity tied to a person with notes, duration, disposition. For "external dialler → log to Salesloft for unified sales-activity tracking" workflows.
ActionSalesloft Log Email
Records an email activity tied to a person. For "rep replied via Outlook directly → log to Salesloft cadence" sales-activity capture.
ActionSalesloft Remove from Cadence
Stops a person's enrollment in a cadence. Standard pattern: prospect replied → remove from competing cadences to prevent double-touching.