Getting Started with Webhooks

Mediagraph Support
Mediagraph Support
  • Updated

Who can use this feature?

All members, but only Admins and Managers can configure webhooks.

Available on all plans

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.

One of the uses for webhook integration, as shown in the diagram below, is to send an automatic Slack message any time a new file is uploaded or added to a designated container in Mediagraph.


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.

Some examples of events that can trigger a webhook are:

  • A new file has been uploaded by a specific user, or a member of a specific user group.
  • A file has been moved into a Lightbox or Collection designated to trigger a webhook integration.
  • A new file has come in through a contribution request.
  • A file reaches a certain stage in an approval workflow.
  • A new file has been shared with you.

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

Payload data includes:

  • The identity of the user who added it to the container (name username, and user ID).
  • File name and location.
  • Download URLs for full size (optional), 1200px-downsized, and a thumbnail.
  • All other metadata, including all Tags and information about their location in the Tag Tree.

Webhook clients like Zapier support many different actions. To learn more about the thousands of apps that Zapier supports, see their website here:

Explore All Apps | Zapier

To learn more about how to use webhooks with your Mediagraph account, see our guides on how to:

Add a New Webhook

Set up Slack notifications with Webhooks and Zapier

Set up Wordpress integration with Webhooks and Zapier

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request