0:00
/
0:00

Paid episode

The full episode is only available to paid subscribers of RevOps Impact Newsletter

Using Python and Sub-Zaps for an Otter-to-MEDDPIC-to-Salesforce workflow

I'm highlighting two Zapier skills for those who have any third party workflow automation tools embedded within their stack. Here's a quick showcase of taking advantage of 1️⃣ using Python code and 2️⃣ leveraging sub-zaps. The use case highlighted below takes #sales calls and matches it to the right Salesforce opportunity. Details below 👇

➡️ MEDDICC prompts are embedded within the Conversational Intelligence tool to cut down on steps in a Zap

➡️ Resulting MEDDICC outputs are captured in the Zap trigger (example shows Champion, Economic Buyer, Decision Criteria, Decision Process, Paper Process)

➡️ Use API keys from conversational intelligence tool to trigger when a recording is made

➡️ Triggering zap calls a sub-zap. The sub-zap is used to circumvent the need to duplicate a zap across multiple users

➡️ Python for string/text cleanup

➡️ Salesforce SOQL step to identify correct task(s)

➡️ In the event of multiple tasks, then Python is used to loop through each item and correctly identify the correct record

If you're building in Zapier I recommend honing a few core skills: Tables, Agents, Sub-Zaps

If you're handy with Python try building out a few Code-by-Zapier steps also to cut down the number of sub steps

Good luck out there

Go forth and operate 👋

For paid members the Python code is down below:

I'm interested in a Zapier micro course

RevOps Builder Content on Youtube

Listen to this episode with a 7-day free trial

Subscribe to RevOps Impact Newsletter to listen to this post and get 7 days of free access to the full post archives.