ActionSalesloftUpdated September 2026

How do I log an email in Salesloft?

Short answer: You can salesloft log email in Salesloft by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Salesloft Salesloft Log Email action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Salesloft Log Email in Salesloft — start free All 6 Salesloft actions

Salesloft Log Email 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.

Field	Type	Required	Description
Recipient Email recipient_email_address	string	Required	The email address that received this message.
Subject subject	string	Required	Email subject line.
Body body	string	Optional	Email body. HTML or plain text.
Sender Email mailbox	string	Optional	The email address that sent this message (must be a Salesloft user's mailbox).

Sample request

{
  "recipient_email_address": "user@example.com",
  "subject": "{{trigger.subject}}",
  "body": "{{trigger.body}}",
  "mailbox": "rep@yourcompany.com"
}

Returns

{
  "data": {
    "id": 778899,
    "status": "sent",
    "subject": "Following up on our chat",
    "created_at": "2026-04-11T10:00:00.000Z",
    "recipient_email_address": "user@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 Log Email.

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

Google Sheets → Salesloft

2 Google Sheets triggers

HubSpot → Salesloft

18 HubSpot triggers

FAQ

Questions about Salesloft Log Email.

What does the Salesloft Log Email action do in Salesloft?

Records an email activity tied to a person. For "rep replied via Outlook directly → log to Salesloft cadence" sales-activity capture.

What inputs does Salesloft Log Email require?

Required: Recipient Email, Subject. 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 Email support batch operations?

Run Salesloft Log Email 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