qibb provides a large set of generic connector Nodes to integrate e.g. OpenAPI compliant interfaces, read databases, monitor S3 buckets, and parse various file formats. Furthermore, qibb provides Nodes to a variety of media applications like MAM, DAM, CMS, or playout systems. Through these pre-built Nodes alongside several template Flows to facilitate metadata mapping, connecting different 3rd parties has never been easier.
For example, qibb triggers when a new video file incl. XML sidecar arrives at an S3 or FTP and automatically trigger ingest of the asset – either directly or upon approval, transcoding, file check or metadata enhancement.
This is an ideal place to trigger additional qibb Flows to create e.g. AI-generated metadata, summaries, or QC workflows on assets.
Additionally, qibb’s dashboard system is the ideal combination to prompt users without access to the central asset stores to provide sufficient and correct metadata. Connected with qibb Nodes like Slack or Microsoft Teams, including approval loops or notifications, deeply integrates the ingest processes into daily operations.