ActionSalesloftUpdated September 2026

How do I log a call in Salesloft?

Short answer: You can salesloft log call in Salesloft by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Salesloft Salesloft Log Call 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.

Salesloft Log Call in Salesloft — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Person ID
person_id
stringRequiredThe person this call is logged against.
Phone Number
to
stringRequiredThe phone number that was called.
Duration (seconds)
duration
numberOptionalCall duration in seconds.
Disposition
disposition
optionsOptionalOutcome of the call.
Sentiment
sentiment
optionsOptionalCaller's read of the conversation.
Notes
notes
stringOptionalFree-form notes about the call.
Sample request
{
"person_id": "1234567",
"to": "+15551234567",
"duration": "180",
"disposition": "{{trigger.disposition}}",
"sentiment": "{{trigger.sentiment}}"
}
Returns
{
"data": {
"id": 999888,
"to": "+15551234567",
"notes": "Booked demo for Friday",
"duration": 180,
"person_id": 1234567,
"sentiment": "Positive",
"created_at": "2026-04-11T10:00:00.000Z",
"disposition": "Connected"
}
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Salesloft Log Call.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Salesloft Log Call.

What does the Salesloft Log Call action do in Salesloft?
Records a call activity tied to a person with notes, duration, disposition. For "external dialler → log to Salesloft for unified sales-activity tracking" workflows.
What inputs does Salesloft Log Call require?
Required: Person ID, Phone Number. 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 Log Call support batch operations?
Run Salesloft Log Call 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.

Salesloft Log Call in Salesloft — start free