Adding hidden values in forms with webhooks integration in a natural language nocode way (not using IDs)

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 🙂