Sai, Webhooks is only available in triggered campaigns. Please share more details about your usecase with me (email@example.com) so that we can consider supporting it in batch campaigns as well. What does the URL do - does it return any values that have to be processed? What are the filters in your smart list?
Just a quick solution to the original question -- I set up a small webservice to perform a custom data validation and needed to run it on my whole database. Attempting to call the webhook directly from a batch campaign resulted in the "Cannot call webhook in batch campaign" error on each call. However, the following abstraction permitted this use case:
1) Place the webhook call in a trigger campaign with a trigger of "Campaign is requested" 2) In your batch campaign, use a flow step of "Request Campaign", rather than calling the webhook directly
This allows the webhook requests to queue up properly and execute for each qualified lead. Hope this helps someone.
Jim, What you are proposing will flood the system with trigger campaigns and is precisely what we don't support. Depending on how many leads you are processing, it could bring down your own subscription. So, please refrain from doing this.
I would like to know more about this. The constraints placed on the system led me to believe that this was the "right" way to achieve a batch execution of a webhook. My assumption being that queueing up campaign requests (rather than direct webhook calls) would give Marketo an opportunity to throttle the calls to an acceptable rate.
I definitely have an infrequent need to call an external web service on a group of leads, and would very much like to do it the right way. Can you offer rough numbers of acceptable use, or a best practice to suit this use case?
Jim, Giving you a number is difficult, because there are a number of other factors at play. For e.g, if you already have a big backlog of trigger campaigns, you do not want to use this method to call WH on even 5 more leads. This is a slippery slope that I'd rather not go down, so the answer remains - "this is not a supported configuration"