Short answer: Drop the "Salesloft → Salesloft Log Email" 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 |
|---|---|---|---|
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). |
{"recipient_email_address": "user@example.com","subject": "{{trigger.subject}}","body": "{{trigger.body}}","mailbox": "rep@yourcompany.com"}
{"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.
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.