QBank DAM – Integrations

A company’s digital sphere
is rarely limited to a DAM-solution, but often involves several different systems that need to
interact with each other. Beside the DAM there might
be a Product Information System, as well as a number
of different internal networks, public web pages
and software tools used to create and edit files. Here at QBank we
illustrate this relationship
with our flower. Since QBank works
as the central hub, it’s important that it’s
easy to use files and data in any connected systems,
without the user needing to manually download,
or copy and paste. QBank is the master
of integrations, which we like to break
up into three different types: The first and most
powerful connection is QBank as a plugin. This means that the third
party system integrates our QBank Connector in
their native environment. Some examples of popular
platforms where QBank already exist as a plugin
is Episerver, WordPress, Drupal, Office- &
the Adobe suits. Our plugins basically
become “Mini-QBanks”, where you can choose to
activate functionalities to the point where you
can work with files in the same way you do in
the QBank backend. While there may be a dozen
managers working in QBank, there can be thousands
of external users working through the connector in a
streamlined and efficient way, downloading,
uploading and editing files. Since it’s the same
connector implemented everywhere, everyone
can enjoy updates and enhancements as
they are released, regardless of the size or
user base of the platform! The plugin can also be
programmed to deliver the formats and variants of
files that are needed for a specific purpose. This way, editors won’t
have to worry about which pixel sizes should be
used or how to package the image or video to make
sure it’s responsive and works on all devices. Anyone can implement
the QBank Connector, all you need is the URL to
get the javascript code, and a couple of lines
of configuration! The second type of
integration is where QBank builds a bridge against
the third party system. The bridge is built and
maintained by us at QBank entirely, or with the help
of the third party when needed. Examples of solutions
like this are our social media-connections with
facebook and youtube, storage spaces
integrations like Dropbox and Google Drive, and
PIM & CRM-systems like Microsoft Dynamics. The Third and final type
of integration is when the third party integrates
with QBank through our API, to build whatever
solutions they may need. Our API is as modern as
they get and as easy to use, implementing common
authentication and communication protocols. While other systems may
want to restrict you to their tools – we at QBank
recognize the strength that comes from
working together, and we love to explore
those possibilities through openness
and integrations!

Leave a Reply

Your email address will not be published. Required fields are marked *