is /index.php/leadCapture/save2 depreciated?

[Diego_Lineros2]

Hi, Anyone knows if /index.php/leadCapture/save2 is still working? I was trying to sync two Mkto instances with a simple webhook posting a dummy form, I have all the bits such as formVid but...  Could not execute a webhook to the given URL   .

If depreciated, any clever alternative?

Happy Friday

[SanfordWhiteman · Accepted solution]

Yes, direct use of /save or /save2 is deprecated. It's supposed to be completely removed by midyear but that may have rolled out early.

But that may not be the cause of your problem... hitting endpoints within the Marketo infrastructure, other than localhost, has always been unsupported.

[SanfordWhiteman · Accepted solution]

Yes, direct use of /save or /save2 is deprecated. It's supposed to be completely removed by midyear but that may have rolled out early.

But that may not be the cause of your problem... hitting endpoints within the Marketo infrastructure, other than localhost, has always been unsupported.

[SanfordWhiteman]

(by which I mean hitting them via webhook)

[Diego_Lineros2]

ohh man...that is bad news... you always very prompt in your responses, much appreciated. Wondering a walkaround and I am lacking of inspiration today.

[Diego_Lineros2 · Accepted solution]

For anyone interested, I found the walkaround using two webhooks, one to get the rest access token and the other using this token to push the changes.

All done.

[Kacper_Gawlik1]

Hi Diego,

I would love to hear more details about this as I am trying to Trigger action between Marketo instances.
In this case particularly from submission.
I tired to test submission with bearer token already placed statically using below urls.

rest/v1/leads/submitForm.json
js/forms2/js/forms2.min.js

First one works perfectly in Postman but in Marketo I am getting ConnectionTimeOut response.

Second shows webhook is sent but Response shows some really mysterious code and do not see submission action in the other Marketo instance

Not sure what I am doing wrong, appreciate any help on this!

Thanks,
Kacper

[SanfordWhiteman]

Hi Kacper,

I know you really want this to work natively, but it just won’t anymore! Also your second webhook is just requesting the Forms 2.0 JS library, so the response is the JS source.

[Kacper_Gawlik]

Hi Sanford,

Yeah I am trying not to give up and check different methods but seems that without 3rd Party I would not receive my goal 🙂

Thanks for the follow up!

Kacper

[Diego_Lineros2]

Do this at your own risk, I did it and did work for me as temporal fix and last resort .

1. Create a field marked as sentitive

2. Create a webhook to populate the field

URL is the other instace

https://xxx.mktorest.com/identity/oauth/token?grant_type=client_credentials&client_id=xxxxx&client_s...

Create another webhook to push the values you want, use the value stored in the sesitive field in the header as follow, and push your payload.

Create a trigger, with a flow to call bewhook1, then webhook 2.

You can create a batch to trigger but just a limited amount of updated will be done.

Good luck

[SanfordWhiteman]

---

Create a trigger, with a flow to call bewhook1, then webhook 2.

---

This is just making the race condition worse! At least if you're gonna do it this way, you should trigger the second webhook only when the second webhook completes updating the access token field (using Data Value Changes). There's no guarantee that 2 webhooks called in "sequence" will actually complete in that order.

Of course you still have the access token expiration condition, plus the API limits concern.

[Diego_Lineros2]

I did use it, both in the same flow, short waiting step in between, did work for me in over 60k records, I had a smart list for error control using webhook response. The race was not the issue, the issue is the volume that Marketo handle per minute. So yes, this is not perfect solution, it doesnt pretend to be, but its the best I had and made the job and nobody has shown me anythong better. withouth using an external data pool.

[SanfordWhiteman]

Oof... that approach has a race condition, I wouldn't put it in production.