Streamlining Workflows with Webhooks for Mudstack

We’re excited to introduce Webhooks for Mudstack, a big step forward in automating tasks in your pipeline. Webhooks help your workflow tools react the moment work moves forward in Mudstack, so updates automatically flow to the right people without extra steps.

What are webhooks?

Webhooks are automated HTTP callbacks that Mudstack sends when events occur inside your workspace. When someone uploads a file, leaves a comment, or adds a new version — Mudstack delivers a structured JSON payload to an endpoint you control.

That means:

• Real-time syncing
• No polling
• Unlimited integration possibilities

How this helps game art teams

Here are a few examples of how Webhooks for Mudstack can help automate looping your workflow apps into your Mudstack activity.

• Keep Jira in sync. When an artist updates a file or a reviewer resolves a comment, the related Jira ticket will instantly move to the next status, with a deep link back to the asset in Mudstack.
• Notify without context switching. Using Zapier, you can now make automated posts to apps like Teams or Monday when key activities happen in Mudstack. When a milestone tag is added, or when a review turns “Approved,” Zapier can create a sub‑task or post a short note to Teams in the relevant channel. Producers see the change immediately, artists stay in flow.
• Automate DCC handoffs. When a .blend file lands in a specific folder, trigger a headless Blender export or validation job on your build machine, then post results to Jira.
• Process files through cloud-based conversions post upload. Does your team do any cloud-based batch conversions after sending your content up to the cloud? That processor can listen to a webhook payload and work on files from an artist’s push.

Why outbound webhooks matter

Real time. Updates arrive as the work happens, which means fewer manual check‑ins and faster handoffs.

Less friction. Artists don’t have to jump between tools to post links or manually update tickets. Leads and producers don’t have to worry about artists complying with update protocols, because updates happen automatically.

Better visibility. Producers see accurate status in the tools they work in like Jira, Monday and Teams - with links back to the source of truth in Mudstack.

Getting started with Webhooks for Mudstack

Getting started with Webhooks for Mudstack only takes a few minutes.

• Create your webhook in the app and provide us a destination URL & headers of where you would like the events to go.
• Choose events to subscribe to in Mudstack. Here is a list of what we can post with a webhook.
  • Asset updates
  • New Asset Versions
  • New Commits
  • Comments
  • Review Requests
  • Reviews
• Configure your destination to accept the payloads and transform the data. You can use intermediary apps like Zapier, or internal automation tools, like Jira’s automation tool.
  • You can combine a webhook with API calls in the automation tools to enrich the webhook payloads with more relevant data.
• Test and go live!

For more info on best practices and some examples for webhook uses, check out our documentation on how to get webhooks set up in your workspaces.