The Data Catalog, with its comprehensive metadata, constitutes a valuable asset for any organization. However, merely using the Data Catalog as a consultative tool means underestimating its potential. Indeed, by actively integrating it into various governance processes, one can fully harness its capabilities.
But how can it be actively included within an organization’s ecosystem? Blindata offers several solutions to easily leverage the metadata it contains.
Firstly, it provides open REST APIs, allowing integration with external computer systems and the development of tailor-made solutions.
Secondly, Blindata offers two powerful tools, the main focus of this webinar, namely Web Hooks and Web Actions.
By combining Blindata’s REST APIs (inbound) and Web Hooks or Actions (outbound), it is possible to interconnect Blindata with any external information system in a bidirectional manner.
For instance, one can integrate Blindata into DevOps workflows, extend collaborative features to external systems like Jira or Slack, and also integrate Blindata with custom processes on proprietary systems.
Core Concepts of Web Actions and Hooks
Both tools are based on a templating mechanism that allows the definition of HTTP requests in a parametric manner. These templates are filled using user-defined mappings, leveraging the data contained in the Data Catalog.
Once the template is filled, the HTTP request can be sent to any reachable endpoint.
Represent one of the major feature of the metadata activation module. Operating at the graphical interface level, Web Actions empower users to add functionalities at points of interest. They enhance Blindata’s capabilities, enabling integration with one’s technological stack. Additionally, Web Actions facilitate improved communication within the organization by integrating messaging systems or issue reporting.
Web Hooks are a tool that enables Blindata to communicate externally what happens internally. We have events occurring within Blindata, and these events can have one or more rules attached to filter and capture only the events of interest. Once the event is captured, it is used to fill the HTTP template, through which the HTTP request is then made.
|Method of communication between different online applications. It is a mechanism in which an application can send a request to another application when a specific event occurs, without the need for continuous and active information requests.
|Action executed through an HTTP request on a web resource. It is an operation that is performed via an HTTP request to a specific URL.
|User-defined rule to make a web action available for a given page.
|User-defined rule that specifies when a web hook should be triggered.