Double the Power: Marketo to Marketo Integration via Zapier

Scope

Two companies have merged. Let’s call them  Client 1  and  Client 2.  Client 2 ’s Marketo data was integrated with  Client 1’s Marketo. Two hand-raise forms set up on  Client 2 ’s domain were already pushed to  Client 1 ’s Marketo.  

Before the merge was finished, we also wanted to capture submissions from  Client 2’s hand-raise website forms and flow them into their SFDC.  An additional requirement was that all submissions generated using the form on Client 1’s landing pages and a @Client2.com email domain, should also flow into  Client 2’s Marketo.  

The aim of this project was to implement a form and lead routing solution that would allow Client 2 records to be routed to Client 1 and Client 2 Marketo and Salesforce until the websites were merged.  

Sounds tricky, right? See the graphic below, for a better understanding of the requirements:

Process Set-up  

Below is an example of Zapier flow that let us achieve the above, and push records to Client 2’s Marketo as Form Submission activities, with all the data mapped to the correct Person fields.  

Client 1 = Marketo #1
Client 2 =Marketo #2

1. The trigger that captures webhooks, sent from Marketo #1 instance  
2. A setup for field value standardization – removing the “”  special characters that broke down the .json structure  
3. GET query that sends a request for Access Token, which is later stored as Zap token
4. Paths are set to rigger either Form A or Form B submission– depending on what was the form ID captured in Step 1.  

Take a look at the webhook setup in Marketo #1, used to push data to the Marketo #2:  

1. A URL generated by Zapier enables capturing the data sent out from Marketo #1:  
2. FormID  is a static id value, that later helps to identify which form should be submitted in Marketo #2  

In Zapier flow Step 1, we can see all the data sent by Marketo #1:  

Among the captured data, we have noticed that one of the fields contained special characters - “” which later on caused errors in the flow and led to the. json code malfunction.

That’s why the Zapier step which clears extra characters was essential in our setup:  

1. Input – Field with data to clean  
2. Find the special character -  “
3. Replace with an empty value  

Output:  

To transfer all the data to Marketo #2, the next step is to secure permission using Marketo #2's access authorization token.

1. Using Method GET to request for token access  
2. Authorization URL with Marketo #2 ClientSecret and ClientID details

As a response, we receive the authorization token. The next step is to determine which form should be submitted in Marketo #2, based on the formID value from flow Step 1, stored as Zapier token.  Additionally, we create a .json-type input for the form fields when the form submission action is triggered in Marketo #2. Now the data collected from Marketo #1 in Zapflow Step 1 is ready to be pushed to the desired form as fields values inMarketo#2. Finally, we fill in the required header fields with Authorization token values captured in Step 3.

That’s it!  
‍
Don't forget that Zapier's monthly subscription limits how many zaps your account can generate, so make sure to monitor that number each month, especially if you have other Zapier automations enabled!

We would be happy to assist you with preparing similar set-ups. Feel free to reach out to us!