We have a smart campaign, "test send to instance", that is triggered based on fill out form = test_form. Under the flow tab, we added Call webhook where webhook = "webhook_send". Under the schedule tab, campaign status is active and Run each leave through the campaign flow = every time.
The goal is to send data from one Marketo instance (foo_instance) to another one (bar_destination) through the webhook_send securely after the form has been submitted. We were able to load test_form onto a web page and are able to see the data come into foo_instance successfully and when we view the Activity Log we can see the webhook_send being triggered with no errors. However, when we go to bar_destination instance, we do not see the lead created or updated.
How would we use the webhook to send data from foo_instance to bar_destination?
Template does include the following:
Solved! Go to Solution.
After switching from REST to SOAP field names, I was able to get this to work properly. In review, I found this to be a flexible solution as the webhook can be added to any Smart Campaign, but would you say this is secure enough when sending data to another instance?
Form posts are SSL-encrypted. They don't require authentication. So this is the same as any Marketo form post, security-wise.
Reliability-wise, it is subject to significant restrictions relative to form posts straight into the other instance, as you can't execute 100s of thousands of webhooks (but could post hundreds of thousands of forms, i.e. if you get a hacker's attention).
Security wise, I wanted to make sure it was encrypted and it sounds like it is same as other form post. In terms of the number of hooks, this will be the only hook that we implement. This is only a temporary solution as we will eventually move to a single instance.
Is there any option in Marketo to ignore the SSL verification when calling webhooks, so that I can test it using development endpoint ?
No, it's not, but you can send to a plain-text http:// endpoint instead.
Also please change your profile to use a real name, as recommended by Community Guidelines.