One of the many ways that Mediagraph integrates with other apps is through the use of webhooks. Mediagraph can use webhooks to automatically send information to other apps when something new happens. A webhook is triggered under specific and designated circumstances, such as when a new file is uploaded or added to a specific container. Most webhook integrations with Mediagraph will make use of a webhook client called Zapier. Zapier helps forward information from Mediagraph to other web apps.

Let's take a close look at one example of a webhook integration to learn more about how they work.

Each webhook communication consists of three parts: a trigger event, a payload and an action.

In this case, the upload of the new file is the trigger event. When Mediagraph sees the new file come in, it sends a message in the form of an HTTP request to a unique URL provided by Zapier. This message contains information about the file, referred to as the payload. After Zapier receives the message, an action takes place according to a protocol chosen during setup. In this example, Zapier selects and formats some of the information from the payload and forwards it to a Slack channel.

All this occurs instantaneously each time a new file is added to the Mediagraph container selected during setup. This is just one example of an integration possible with webhooks. 

Mediagraph supports a number of different trigger events. Webhooks must be connected to a specific container in Mediagraph: a Storage Folder, Collection, or Lightbox. Any time a new asset is added to the container, information about the asset is sent. Source containers may be chosen to trigger a webhook under many different circumstances.

When Mediagraph sends a webhook, the payload includes rich data about the asset that triggered it.