API Sync Calls -Workato | Community
Skip to main content
Lucas_Metherall
New Participant
May 10, 2021
Solved

API Sync Calls -Workato

  • May 10, 2021
  • 1 reply
  • 2478 views

Hi all,

 

We are testing a middleware "Workato" between our CRM and Marketo. We tested running a payment cycle of approx 1,000 leads, and noticed that the updates trickled into MKTO, over the course of several hours.

 

Questions:

- Is this expected behaviour?

- Would this be in the middleware and how they are sending data?

- Does MKTO allow/support larger data syncs?

 

Thanks everyone.

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

Don't know what a "payment cycle" means in your particular business, but Marketo is perfectly capable of syncing lead fields synchronously — that is, not a background/asynchronous import but one that is guaranteed to be complete as soon as the call is complete — for up to 300 leads in one call.

 

A bulk import, which is limited only by the file size (not technically the number of leads) and can do thousands at a time, runs asynchronously: it isn't complete when the API call is complete, because it was to wait in a queue for there to be an available slot (only 2 imports run at a time). But several hours is not a reasonable delay. The only reason that would happen is if there are hundreds of other imports already queued.

 

So it's overwhelmingly likely that the middleware is sending data piecemeal/suboptimally.

 

 

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
May 10, 2021

Don't know what a "payment cycle" means in your particular business, but Marketo is perfectly capable of syncing lead fields synchronously — that is, not a background/asynchronous import but one that is guaranteed to be complete as soon as the call is complete — for up to 300 leads in one call.

 

A bulk import, which is limited only by the file size (not technically the number of leads) and can do thousands at a time, runs asynchronously: it isn't complete when the API call is complete, because it was to wait in a queue for there to be an available slot (only 2 imports run at a time). But several hours is not a reasonable delay. The only reason that would happen is if there are hundreds of other imports already queued.

 

So it's overwhelmingly likely that the middleware is sending data piecemeal/suboptimally.

 

 

Lucas_Metherall
New Participant
May 11, 2021

Yes, we just heard back from them - their software processes data in batches of 300. Not optimal, we will talk to them about increasing that.

SanfordWhiteman
New Participant
May 11, 2021
But you said it was 1000 only. Are they waiting hours between batches of 300?