Works with LinkedIn

Why LinkedIn + dassi

LinkedIn is already where the work happens. dassi adds the missing layer: it can read what’s on the page and then take actions (draft, classify, fill, log, summarize) without you rebuilding context in a chat box.

What to automate in LinkedIn

• Log messages to CRM (no integration): Capture key messages and context into Salesforce/HubSpot as activity notes in seconds.
• Job search scoring + normalization: Score listings against your resume and normalize results into consistent badges so you can scan faster.
• Meeting prep briefs from profiles: Pull role/company context from a profile and create a concise prep brief for upcoming calls.

Quick start

1. Open LinkedIn in Chrome.
2. Open the dassi sidebar.
3. Start with a safe workflow: summarize → propose → draft → review → act.

Prompt recipes (copy/paste)

• “Log this message thread to Salesforce under this contact.” (from LinkedIn Message to CRM Note, Zero Integration)
• “Summarize the last 5 messages and add as a note in HubSpot.” (from LinkedIn Message to CRM Note, Zero Integration)
• “Compare this job to my resume and give me a score + gap list.” (from Job Listing That Scores Itself Against Your Resume)
• “Rewrite my summary bullet to match the top 3 requirements.” (from Job Listing That Scores Itself Against Your Resume)
• “Standardize these listings: salary, remote, years, stack.” (from Job Listing Normalizer With Filters)
• “Hide anything requiring 5+ years.” (from Job Listing Normalizer With Filters)
• “Build a prep brief for this meeting: attendee backgrounds + recent threads.” (from Meeting Prep Panel Injected Into Calendar Events)
• “Pull last touchpoints from Salesforce and summarize them.” (from Meeting Prep Panel Injected Into Calendar Events)
• “Summarize what’s on screen and propose next actions.”
• “Do the safe part first (draft / label / preview), then ask me before any irreversible action.”

Safety checklist

• Tell dassi: “Never submit/send without confirmation.”
• If the page contains sensitive data, ask for redaction or aggregated outputs (totals-only, no PII).
• Prefer reversible actions first (drafting, labeling, notes) before destructive ones.