Many systems are missing the API settings for creating the Webhook API keys. If you switch to Freedom UI Shell you'd be seeing an error message like this: 

You'll need to contact support for them to get the settings enabled for you to create the keys.

Ryan 

Hello,



In order for us to assist you in resolving this issue, please contact customer support.

I have unbounce landing pages that are using webhooks in Creatio but haven't figured out how to use it in campaigns yet. I'm assuming I just need to populate a table somewhere, but just starting to piece it together so not sure yet

Ryan

Hello,

At the moment, there is no separate element for working with web hooks in marketing campaigns yet. If what's needed is to add such contacts to the audience of the campaign, then this can be done with the help of the  appropriate filtering based on data from the record that came from a landing page, taking into account the channel, source, tags (if necessary for the case).

So you get leads from landing pages, put these leads in a separate folder and create a mailing list in the campaign that will take the audience from this folder.

Is there any plan to make easily part of marketing automation campaigns like the classic landing page element is ?

Yes. You can add a Case (or any entity) using a webhook. All you need to do is specify EntityName: Case in the payload and include any of the fields needed for the case, including any default values. 

What I've not tested yet (and I suspect cannot be done with a webhook) is include a nested payload for related data - such as an account)

You can also specify in webhook an entity which will be used as an intermediate object before case registration. 

For ex, Submitted form. 

You will need to add your case relating fields in Submitted form (including nested payload) and then to write a process which will be triggered when a form is submitted and 

to manage nested data, perform any searches and register a case from this process.

More than using the webhook to entity conversion using the OOTB process, I've been just adding my own. If the payload from the webhook doesn't contain an "EntityName" the ootb process rejects it, however, you can still create your own process that triggers from a signal of webhook added, plus you can add filters for the headers or payload containing some specific values. Then deserialize the JSON payload and do whatever you want with it. I'll have an article written up on this topic soon.

Ryan

Hi!

 

Currently, the webhooks service only works when JSON is sent in the correct format. We don't recommend changing this logic because It is a bad idea to change the way requests are processed it can lead to unknown consequences, it would be better to use ad-hoc services for this. 

You can read more about the webhook service here - https://academy.creatio.com/docs/user/setup_and_administration/base_int…

Also, it looks like you have the correct process in your screenshot. To investigate the log issue in more detail, we recommend you contact our support team. You can send us an email at support@creatio.com.

 

Best regards, 

Anton

Anton Starikov,

could you please provide the community with the correct format of JSON that should be sent to webhook for correct processing.

cause uncertainty about "the way requests are processed can lead to unknown consequences, it would be better to use ad-hoc services for this" ... and webhook functionality became hardly appliable to the real tasks

Oleksandr Lisovyi,

 

View an example of the webhook that the [ Create object records based on incoming webhook ] business process can parse below:

 

{

"Contact": "Testing1",

"PhoneNumber": "+38077777887",

"Email": "test@testting.com",

"EntityName": "Contact",

"Name": "Testing1"

}

You can read more here - https://academy.creatio.com/docs/user/setup_and_administration/base_int…

Hello, 

Such error occurs when variables (ContactName, ContactPhone and ContactList) are not defined in the function, the code itself should be revised a bit. 

After adding 

var ContactName = Get<string>("ContactName");

var ContactPhone = Get<string>("ContactPhone");

.... etc

at the beginning of the Script Task element the process can be saved and published with no errors. 

Best regards, 

Anastasiia Zhuravel