The 3 Coolest Webhooks I've seen (and or) Implemented | Community
Skip to main content
John_M
Adobe Employee
John_MAdobe Employee
Adobe Employee
October 6, 2015

The 3 Coolest Webhooks I've seen (and or) Implemented

  • October 6, 2015
  • 10 replies
  • 5756 views

Having been in Marketo Enterprise consulting for about 2 years I've seen a fair few cool Webhook solutions.. here are a few of my favorites that may give you some inspiration

1. Calling a service that generates a unique software download URL

     One of our clients wanted to generate a UNIQUE URL for a software download when a Lead filled out a form (and as a bonus, they became known marketable leads when they requested it). A third party takes in a unique super secret ID and generates that unique URL.

As you can see below, the jSON coming back is mapped into an attribute on the lead. We can then trigger a campaign to the user and send them their trial.

2. Sending SMS messages with Twilio

     This one was one of mine, and I documented it right here on the Marketo Whisperer blog recently (Sending an SMS using Twilio)

3. Sending push notifications with Urban Airship from a mobile app (before there was Marketo Mobile Engagement)

     Before there was Marketo Mobile Engagement, which you should absolutely check out immediately, there were other providers of simple Server Side Push messaging such as Urban Airship.

     This one is really powerful because it also leverages other parts of Marketo like Custom Activities​. You can imagine how cool it is to sign up for a mobile app and receive push notifications along with other marketing content. We can send reminders, contact other people and even do deep linking back into the Mobile app.

     Here you'll notice that we get back some interesting tracking information from UA, which we could then report on using the UA Reporting API.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    10 replies

    Kenny_Elkington
    Adobe Employee
    Kenny_ElkingtonAdobe Employee
    Adobe Employee
    October 7, 2015

    Slack is pretty slick as well: http://developers.marketo.com/blog/integrating-slack-with-marketo/

      John_M
      Adobe Employee
      John_MAdobe EmployeeAuthor
      Adobe Employee
      October 7, 2015

      This is a great one. Thanks!

      Justin_Norris1
      Justin_Norris1
      Level 10
      October 9, 2015

      Webhook for doing the associate lead is really neat. Wish I had known about that a few years ago...

      A
      Anonymous
      October 9, 2015

      This is very helpful. Thanks for sharing.

      A
      Anonymous
      November 23, 2015

      Hey @John Mattos​ i'm getting a failed server returned 302 error url moved temporarily. Any idea on this? Trying to implement the create duplicates webhook.

      A
      Anonymous
      November 23, 2015

      Hi Tim,

      Did you change the webhook url from localhost/ to 'your marketo server url'?

      Also, are you including munchkin id of your Marketo server and appropriate form id which exist in your Marketo instance?

      Rajesh Talele

      A
      Anonymous
      November 23, 2015

      Didn't know I would need to update the url to "my Marketo server url"... can I find this/what is the format? Everything else I did.

      A
      Anonymous
      December 3, 2015

      Those looking to create duplicate leads. My webhook did not work until i changed my formid to look as so formid=mktoForm_####

      A
      Anonymous
      July 11, 2016

      In case anyone is still having trouble running a lead duplication webhook, here are a few instructions on one way to find the actual URL you should be using:

      1. In Firefox, run the FireBug add on.

      2. Open any of your existing Marketo pages that has a form.

      3. In the FireBug add on, select "Persist" so that your console log is saved.

      4. Fill out the form and hit submit.

      5. In the console log, look for the POST event (you can just search for "post"). You can pull the URL directly from here. In our case, we had to change it to instead of . You may need to test both.

      *You may also need to use formVid instead of formid (they are the same number, see above screenshot).

      Hopefully that helps.

        SanfordWhiteman
        SanfordWhiteman
        Level 10
        July 11, 2016

        *You may also need to use formVid instead of formid (they are the same number, see above screenshot).

        Actually, you must pass formVid when using the /save2 endpoint, and omitting formid is not supported.

        I appreciate your follow-up because it's been found that the generic loopback post (to localhost/.../save) is broken on some instances.

        Terms & ConditionsAccessibility statement

        Loading footer...