Calendly Booking Pauses Outreach and Creates/Updates Contact

Calendly Booking
Description	A new meeting scheduled in Calendly pauses recipients in Mailshake and creates/updates contacts in the CRM
Platform	Zapier
Workflow	New Meeting in Calendly Pauses Outreach and Creates/Updates Contacts in CRM
Schedule/Trigger	New Calendly appointment

When a new meeting is created from Calendly this workflow will create/update contacts in the CRM, pause Mailshake and Linkedin outreach, and sync the meeting status to monday.com.

1. Meeting Created in Calendly searches Hubspot

A new meeting booked in Calendly searches Hubspot by their full name to see if they already exist or not. Whether or not a contact exists sends the data down different paths.

Searching by First Name and Last Name potentially leaves room for middle initials / nicknames messing up searches and missing contacts that did exist. Searching by Email potentially leaves room for them to register for the meeting with a different email than the one that's in Hubspot.

2a. Contact Exists Syncs monday.com

If the contact is found in Hubspot, it will add a delay so that the monday.com automations can trigger on the Expressed Interest workflow and after the Delay step the Deal Stage will be updated as "Meeting Set".

2b. Contact Does Not Exist Creates a Contact

A contact that does not exist in Hubspot will be sent down Path B. and find/create a Company in Hubspot, create a Contact in Hubspot, and find other relevant details about the Contact and sync those changes to the CRM.

It will send a Webhook to Integromat to search for additional information through Growth-Hacking.io.

The Growth-Hacking.io workflow is incomplete.

After searching for the Company field in Hubspot it will get relevant details or create the Company if it doesn't exist yet.

Next we will create a Contact in Hubspot and sync their Full Name, Email and Company fields from the meeting invite details.

Next we will search the Parvenu Universe Sheet for the contact by Full Name. This tells us if they are an existing contact from either Linkedin / Email channels and provide additional information if they exist. If the Contact does not exist in the Parvenu Universe they will go down Path C and if they do exist they will go down Path D.

3bc. Contact not in Universe Adds Details to monday.com

If a contact is not in the Parvenu Universe Sheet, then the automation will go down Path C and update that they have Expressed Interest, marked that the lead came from Calendly in the Status column, and adds the date of the meeting to the Meeting column.

3bd. Contact in Universe Adds Additional Details to monday.com and Pauses Outreach

If a contact is in the Parvenu Universe Sheet, then the automation will go down Path D and update that they have Expressed Interest, marked that the lead came from Calendly in the Status column, and adds the date of the meeting to the Meeting column.

It will the search the Session Cookie Rotation Sheet in the Email Campaign ID tab by the Filter ID to get the Mailshake Campaign ID and Email Campaign Name.

It will then use that information to Pause the recipient in Mailshake and update Hubspot with that information.

Next it will add a Delay step so that the Add Pulse ID to Hubspot workflow can run and then update the Deal Stage as "Meeting Set."

Finally the workflow searches the Parvenu Follow Up Rotation Sheet for the contact by Full Name. It searches both "Sheet1" and "Cold Sequence Archive." If the Contact does not exist in Sheet1 they are added to it and the contact is updated so that it has an "X" in the replied column to prevent future Linkedin messages. See the Linkedin Inbox Scraper workflow for details on how the X filters out future outreach on Linkedin.

Linkedin Reply Detection