Individual Workspaces connect to real inboxes (Outlook, Gmail) through an automation platform like Make.com. The flow:
[ New email in Outlook/Gmail ]
| (Make.com trigger)
v
[ HTTP module -> SalesLobe API ]
POST https://<your-saleslobe-endpoint>/inbound-email
Header: X-SalesLobe-Key: <your API key>
Body: { workspace_id, workspace_user_id, from, subject, body, thread_id }
|
v
[ SalesLobe returns the draft + a unique BCC address ]
|
v
[ Make.com creates a draft in the inbox,
with the BCC address pre-filled ]
|
v
[ Team member reviews, edits, sends ]
-> the BCC delivers the sent version back to SalesLobe
-> Corty learns from the difference
Setup steps
- Get your API key from Settings -> API.
- In Make.com, create a scenario: watch emails -> HTTP request to SalesLobe -> create draft with the returned reply and BCC address.
- Send a test email - the draft should appear both in the inbox and under Email Replies in SalesLobe.
API response example
The response from SalesLobe looks like:
{
"success": true,
"suggestion": "<p>Hi Sarah, ...</p>",
"suggestion_id": "4b59c756-...",
"bcc_address": "4b59c756-...@feedback.saleslobe.com",
"email_label": "lead",
"label_confidence": 0.91
}
The
bcc_addressis unique per draft - it’s how Corty matches the sent email back to its own suggestion. Make sure your Make.com scenario always includes it as BCC on the draft.
Outgoing webhook triggers are also available (Settings -> Connections) - e.g. new HOT reply -> Slack notification or reply sent -> update HubSpot.