Is there any system set up needed to be made before setting up the webhook (I mean set the url, the tokens, write the template, etc...)? Well, of course. If the webhook is sending data to the Dynamics API, then your outbound webhook's payload, token encoding (JSON, XML, or form encoding), destination URL, and so on all need to conform to the requirements of their inbound API. However, you're going to need to use an intermediate API gateway in this case because of authentication requirements. The Dynamics API uses an expiring OAuth token, which (despite some people's hacks to try to make multistep authentication work via multiple webhooks) is just not acceptable for direct Marketo ↔ Dynamics communication. Instead, Marketo will post data → gateway; the gateway will retrieve, cache and refresh the access token; and then the gateway will send data → Dynamics. To Marketo this will look like a single webhook call. It's a simple task if you have a developer who's used to this kind of "webhook adapter" scenario.
... View more
Issue The GoToWebinar service in Admin > Launchpoint shows a Failed API Error - API Error: ERROR -> HTTP Code = '403'
Solution This error occurs due to an issue with the credentials Marketo uses to access the GoToWebinar service. To fix this, you would need to re-login to the GoToWebinar service under Admin > Launchpoint. Once this is done, the error should be resolved. You should also check the program membership for the webinar programs in Marketo, since any leads who attempted to register for a webinar while the error was in effect will have a status of "Registration Error" and will need to have their status corrected to "Registered."
Who This Solution Applies To
Customers integrated with GoToWebinar
... View more