Integromat to Front

Integromat to Front
Description	New replies to messages on Linkedin get sent to Integromat and then to Front.
Platform	Integromat
Workflow	Linkedin to Front
Schedule/Trigger	Webhook from Linkedin to Integromat

The workflow is triggered by a Webhook and Searches a Contact in Hubspot to find the Pulse ID and the VID. We then use a Router to determine if the Front ID exists and what type of Front Handle exists.

Contact Exists

If the Front Handle exists and contains "Linkedin" then it will call the Import a Custom Message in Front API to import the Linkedin Message. Then it will Search the Parvenu Inbox Scraper by Filter and Update the Done column with "X." Then we map the Pulse ID and the VID to the contact in Front.

Contact Doesn't Exist - No Email

If the contact doesn't exist and doesn't have an email associated with them, we will Create a Contact in Front using Linkedin (written) as the Front Handle.Then we will Update the Front Handle and Update the Contact in Front to fill in additional context. Then we will Import a Custom Message, search the Parvenu Inbox Scraper, and update Done with an "X."

Contact Doesn't Exist - Email

If the contact doesn't exist in Front, but we have an Email for them, then this path will trigger. We will Create a Contact in Front. Then we'll Update the Front Handle and Update the Contact in Front. Then we will Import a Custom Message, search the Parvenu Inbox Scraper, and update Done with an "X."

It's necessary to split the contact depending on whether or not they have an Email, because otherwise it will create an error.

Contact Exists - No Linkedin in Handle

If the contact exists, but doesn't have Linkedin in their Front Handle then this path will trigger. This will update the Front Handle to be Linkedin (written) as a phone value. Then we'll Import a Custom Message , search the Parvenu Inbox Scraper, and update Done with an "X." Then we map the Pulse ID and the VID to the contact in Front.