Short answer: Drop the "Salesloft → Salesloft Log Call" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Person ID person_id | string | Required | The person this call is logged against. |
Phone Number to | string | Required | The phone number that was called. |
Duration (seconds) duration | number | Optional | Call duration in seconds. |
Disposition disposition | options | Optional | Outcome of the call. |
Sentiment sentiment | options | Optional | Caller's read of the conversation. |
Notes notes | string | Optional | Free-form notes about the call. |
{"person_id": "1234567","to": "+15551234567","duration": "180","disposition": "{{trigger.disposition}}","sentiment": "{{trigger.sentiment}}"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.