Webhook field update is asynchronous. So the data value change that results from the webhook answer might occur after a few seconds, or almost immediately, but you cannot control it.
You should use some constraints with you data value changes trigger to make sure you are only capturing changes that come from the webhook:
Otherwise, review in details the activity log of some lead that are supposed to have fired the webhooh and look for the change data value event. If the event is not there, then your webhook is not configured correctly.
Hi Gerg ,
Actually My Webhook will immediately trigger when Data value changes will happen in lead , but that is happen for only old leads , means if I create any lead today and I immediately edit the Attribute field , then my webhook is not triggering , if my webhook configuration is wrong then how it is trigerring for old leads . my webhook screen shot I am sending you
Sorry, I not sure I understand what you are trying to do and what the webhook is supposed to do, and therefore, my previous answer might not be appropriate to what your are trying to do.
- If what you are trying to do is to call a webhook each time a lead is created or the job title is updated, then the way your triggers are set is OK.
- Remember that you need to have a real value change so that the trigger "data value changes" fires.
- Is the "job title" a required information for the webhook? If so, you should add a "job title is not empty" filter to the 2 triggers in your smart campaign.
- You may want to add a wait 1 minute in the flow before calling the webhook.
if I create any lead today and I immediately edit the Attribute field , then my webhook is not triggering , if my webhook configuration is wrong then how it is trigerring for old leads .
Something doesn't make sense here.
In both cases, you're talking about leads that are already committed to your database (just "older" ones beyond some unspecified date vs. newer ones). Marketo doesn't, in normal use, see leads differently based on some arbitrary epoch or anything.
Please show us the Activity Log line and Activity Log Detail for a Data Value Changed activity (change the attribute manually via the Marketo UI) on a "new" lead vs an "old" lead.
I disagree with Greg -- no need for a wait step. Either the trigger fires or it doesn't.
Agreed the wait should not be necessary.