Hi!

Currently, the product does not allow you to set responses for webhooks.
 

We have created a feature request for the R&D team to add this functionality in future. 

Best regards, 
Anton

Hello Aren, 
 

Could you please provide more details about the use case you need to address with the response from the webhook service? Understanding the specific requirements and context will help us better tailor the solution in the future. 


Best regards,
Victoria

Hi!

Currently, only Facebook forms have been adapted for Freedom UI. You can also add the old section with ALL forms to Classic UI and use it, it still works.
 

For now, we do not plan to evolve the use of Landing Page object. 

As you know, landing pages are a great way to capture leads and generate interest in your products or services. However, they can be limited in terms of the data they can collect and how they can be integrated with other systems. 

Webhooks, on the other hand, are a more powerful and flexible way to collect data from your landing pages. They allow you to send real-time data to your Creatio CRM system, which can then be used to trigger automated workflows, update customer records, and generate reports. 

Here are just a few of the benefits of switching to webhooks: 

1. More automated workflows: Webhooks can be used to trigger automated workflows in your Creatio CRM system, such as creating new records of any type. 
2. Better integrations: Webhooks can be integrated with a variety of other systems, such as marketing automation platforms and customer support software. 
3. Enhanced error handling: Webhooks provide robust error handling capabilities, ensuring that data is delivered successfully even in the event of unexpected issues. This minimizes data loss and ensures that your Creatio CRM system remains up-to-date with accurate information. 

If you're looking for a more efficient and effective way to collect data from your landing pages, I highly recommend switching to webhooks. 

To help you get started, I've included a link to our webhook setup guide below: https://academy.creatio.com/docs/8.x/no-code-customization/base-integrations/webhook-service-integration/overview

Best regards, 
Anton
 

Anton Starikov,

Hi Anton, 

Thank you for your detailed answer :). 

However, it seems you do not have understood my question.

I have switched already webhooks. It does indeed possibilities. But, on a business marketing user side, the use of webhooks is really incomplete today in Creatio, there's loads to build, for things that honestly could easily be there OOTB...

For example, everytime we have a new form we want to integrate with (Landingi, Wordpress, etc...) for which we have fields we need to map in Creatio with specific values (drop downs and all), we need to work with IDs... it's not a natural nocode work like it used to be. 

Also, when sychronising the webhooks in Creatio, using the FormSubmit object for example, we only have a list of Formsubmits section rather than a structured way to put them all together under one name, like the "Facebook form" section offers... This is quite inconvenient way to work.

Also, the documentation and examples on how to use webhooks is really scarce in the academy, and mainly limited to using FormSubmit. Which has unforeseen limitations, such as creating a contact record not using all the contact fields available (Eg: https://community.creatio.com/questions/contact-data-submitted-form ). 

On theory, it is great that possibility of using Webhooks is provided. 

In practice, the use of them is not polished and could be greatly improved both on the admin and on the non-admin user side of things.

Damien

I do love using webhooks for landing pages, much more flexible for the most part. However, one thing I miss is the ability to set defaults. For the older landing pages, you had a record defined for each form, and then could define default values for a specific form inside of Creatio. You could change those defaults in Creatio without needing to modify the HTML for the form on the website. That was great and is a missing part of using webhooks. 

I would love to see the following changes for webhooks. 

1. Ability to create a specific webhook for a specific purpose (it could be named in a way that defines it's purpose)
2. Records could be tied back to the webhook it came in through, so you know it came from webhook "ABC" in the same way you knew a record came from Landing Page ABC. This is really more of a way to identify the form (in the same way you could identify a record came from a landing page) - this one might not really be doable since not every usage of webhooks is a "form", but maybe that could be a simple option on the webhook to add an entry to some table that can generically link to any object type?
3. Defaults could then be added on a webhook-by-webhook basis so any record that came in via a specific webhook would have those default values added

Sure, you can do all of this with webhooks now by including extra data or maybe an extra process to add some of the default values based on data that identifies where it came from, which would exist as hidden values in the HTML of the form. But that means possibly changing the HTML if the defaults ever need to change and it was so easy to manage the defaults for landing pages before - it would be great to have for webhooks. Plus, it's up to you to include some way to identify that a record came from a specific webhook (really meaning from a specific form)

Ryan

Ryan Farley,

thanks, exactly what I was trying to say for the setting defaults part, but in much better writing 😅

There is a section with defaults used at the moment in Freedom UI, the Facebook form section. If you create  a form their with defaults, and you add that form ID in your webhook (field that already exists by the way...), there should be an easy and OOTB way to add those defaults. Which as such is not a new feature, just bringing back classic UI landing page integration feature of defaults... 

We would have then the best of both worlds 🙂

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