Hey folks! 👋 Just spent my weekend automating something I think a lot of us might need: getting Sembly AI meeting notes *directly* into Salesforce as actionable tasks. No more manual copy-pasting!
I'm a big fan of Sembly for those quick, automated summaries, but my team lives in Salesforce. The built-in integrations weren't hitting the exact flow I wanted, so I turned to Zapier as the "glue." It's actually pretty smooth once you get the mapping right.
Here's the core workflow I set up:
**The Zap:**
1. **Trigger:** New Summary in Sembly (from the "Summaries & Recordings" section in Zapier).
2. **Action:** Create Task in Salesforce.
**The tricky part** is parsing Sembly's rich summary text to get clean, useful data for Salesforce fields. Here's a sample of the Zapier setup for the Task "Subject" and "Description":
```text
In the Zapier action step for Salesforce "Create Task":
Subject: {{(trigger.data.summary_title)}} - Sembly Notes
Description:
Key Points:
{{trigger.data.key_points}}
Action Items:
{{trigger.data.action_items}}
```
**Key Configuration Details & Pitfalls:**
* You'll need to connect both your Sembly and Salesforce accounts in Zapier, obviously.
* The Sembly trigger provides data in chunks: `summary_text`, `key_points`, `action_items`. I found `key_points` and `action_items` most useful for task descriptions.
* **Watch out for field limits in Salesforce!** If your summary is huge, you might hit the 32,768 character limit for a Task's "Description" field. I added a Filter step before the action to check length and truncate if needed.
* For the "Related To" field in Salesforce, I used a static Contact ID for testing. For production, you'd want to use a Zapier search step to find the Contact based on meeting attendees from the Sembly data (if available).
This has saved our team a solid few hours a week already. The magic is seeing a task pop up in Salesforce with the exact action items from the meeting, ready for assignment and tracking. Anyone else tried this or similar? Curious if you used a different field mapping or ran into other issues!
#k8s