SOLVED

Is Webhook flow step on the radar for Executable Campaigns?

Go to solution
cagarwal
Level 1

Is Webhook flow step on the radar for Executable Campaigns?

I am very thrilled about Executable Smart Campaigns; but wondering if there is a reason why it does not support Call a webhook flow step. Is there a technical challenge behind that or purely product prioritisation?

1 ACCEPTED SOLUTION

Accepted Solutions
SanfordWhiteman
Level 10 - Community Moderator

Re: Is Webhook flow step on the radar for Executable Campaigns?

To explain further, Marketo webhooks happen to have been implemented in an asynchronous fashion. There's nothing inherent to webhooks in general that makes them asynchronous, but Marketo's are.

 

Data value changes from a Marketo webhook's Response Mappings happen in the background. Even if the flow has continued to the next step, there's no guarantee that the changes have been made in the database.

 

You can think of Call Wehook as like calling Request Campaign, so embedding that within an Execute Campaign breaks the "contract" of Execute Campaign.

 

If the webhook implementation changed, it would be compatible with Execute, but I wouldn't be hopeful about that.

View solution in original post

2 REPLIES 2
JessicaMeyers
Level 3

Re: Is Webhook flow step on the radar for Executable Campaigns?

Given that the intention of the new Executable Campaigns is to finish processing the campaign before moving on to the next flow step in the campaign that "executed" it, it would be technically challenging to confirm the webhook has completed doing all things the webhook is intended to do.

SanfordWhiteman
Level 10 - Community Moderator

Re: Is Webhook flow step on the radar for Executable Campaigns?

To explain further, Marketo webhooks happen to have been implemented in an asynchronous fashion. There's nothing inherent to webhooks in general that makes them asynchronous, but Marketo's are.

 

Data value changes from a Marketo webhook's Response Mappings happen in the background. Even if the flow has continued to the next step, there's no guarantee that the changes have been made in the database.

 

You can think of Call Wehook as like calling Request Campaign, so embedding that within an Execute Campaign breaks the "contract" of Execute Campaign.

 

If the webhook implementation changed, it would be compatible with Execute, but I wouldn't be hopeful about that.

View solution in original post