Jaha + Salesforce

When a meeting maps to a deal or contact in Salesforce, Jaha attaches the summary, the decisions and the owned action items to that record — logged as activity, not pasted into a note nobody finds. If no record matches, the delivery says so instead of guessing.

You choose the parts: summary only, action items only, or the lot — per rule, and per one-off send. A one-off send can always narrow what a rule would deliver, never widen it.

Before a customer call, Jaha has already read the deal in Salesforce: recent activity, open items, and what was promised last time. When someone asks “where did we leave this?”, the answer is grounded in your CRM — not in memory.

A rule names Salesforce as a destination, the payload parts, and which meetings apply. Failed deliveries retry; unhealthy connections are flagged before they lose data. And every meeting keeps its “sent to” trail — what went to {name}, when, and by whose rule.

Three steps, once. Here they are as they actually run for Salesforce: