did you update this @Josef Bell?
", "commentId": "d24587e3-b04f-43ef-bf9a-7d3316405db8", "createdAt": "2025-10-02T21:23:38.891Z" }, "id": "cc02b8c1-45e4-4cc4-b6fd-6a0b9a8c31f5" } ``` ### `asset_reviewer_added` ```json theme={null} { "accountId": "b8f71389-2a45-4938-b6d5-0a70f9b9858c", "workspaceId": "2c8a5e43-58cb-47ec-b8a5-f0de2dcf9121", "type": "asset_reviewer_added", "payload": { "assetId": "b5e1af7b-1f24-48a5-81b2-83f374ec3e35", "createdAt": "2025-10-02T21:25:01.770Z", "requesterName": "Joe Bell", "requesterEmail": "josef@mudstack.com", "requesterId": "c5ec24a9-46b9-4d13-a441-7a2f9d9deeb7", "reviewerId": "0dbe34a8-9a9a-4e4f-b4b1-78f0d67a0b8f" }, "id": "0dc7597c-0e1f-4b9e-a52a-20689b69d52b" } ``` ### `asset_review_added` ```json theme={null} { "accountId": "b8f71389-2a45-4938-b6d5-0a70f9b9858c", "workspaceId": "2c8a5e43-58cb-47ec-b8a5-f0de2dcf9121", "type": "asset_review_added", "payload": { "assetId": "9d0ee2e7-3f25-4e38-b1cc-2cfb88f57df1", "createdAt": "2025-10-02T21:25:01.770Z", "authorName": "Joe Bell", "authorEmail": "josef@mudstack.com", "reviewId": "8f0c9b6e-24f5-4b9e-b5ac-6e593d6cd5ea", "reviewText": "The color space on this export didn’t convert properly.
", "reviewType": "change_request" }, "id": "6a4f9cb0-2a2b-4b38-b621-d3db4cf94936" } ``` Reviews will have a `reviewType` of `approved` or `change_request` depending on the message. If `Allow sensitive data` is unchecked, the responses will only include the type, date, and ids. ## Example Integrations ### Jira Use our [downloadable sample](/images/Mudstack_JiraWebhookSample.json) to automatically create Jira issues when new assets or tasks are added in Mudstack. You can [import this into an Automation Rule](https://support.atlassian.com/cloud-automation/docs/import-and-export-jira-automation-rules/) and enter your webhook URL info
The sample will parse a ticket id found at in the `commitTitle` on the `commit_added` event. This allows us to map the message to a specific ticket in Jira
### Zapier
A general Zap structure will contain the following:
1. Webhook catch (use the zap url in Mudstack, and generate some events to show in Zapier)
2. IF USING THE API, an Authentication step to use the API
3. Formatter for the Date/Time conversion
4. Paths to do specific action based on the `type` of event from Mudstack
5. Code to generate a url to the file for the message
6. API calls to enrich webhook data
7. Integration point to send the data out of Zapier
#### Best Practices
* Use **Paths** for splitting multiple event types in a single Zap
* Use **Formatter** to convert Date / Time into something more human readable before sending to other systems.
* You can use the **Code** block to concatenate assetIDs to generate links, make sure you pass in the input data from the webhook. These urls are only accessbile by users that have permssions in the account and workspace of the file.
```py theme={null}
# Extract the input values
account_id = input_data.get('accountId', '')
workspace_id = input_data.get('workspaceId', '')
asset_id = input_data.get('assetId', '')
# Construct the URL using string formatting
url = f"https://app.dev.mudstack.com/sh/asset/{account_id}/{workspace_id}/{asset_id}"
# Prepare the output as a dictionary
output = {'url': url}
```
## Using the API with Webhooks
Webhooks push essential event data, but often you’ll need more context.
You can use the Mudstack API in conjunction with webhooks to:
* Fetch full asset metadata from an asset\_id.
* Retrieve commit details with a commit\_id.
* Join user and workspace information to enrich webhook payloads, like the user name or other file metadata.
Make sure to add this to your Automation
1. Make sure you have a step to [authenticate](/api-reference/authentication#using-the-api-key-%2B-secret-key) before using the API.
2. GET Requests to gather additional information
The webhook response will contain the account, workspace, and object IDs for you to collect additional data from the API
If you don't currently have your API Key, [ask us about generating your API Key](/api-reference/authentication#generating-api-key-%2B-secret-key)
Example:
* When a webhook sends asset\_created with only an asset ID, call the API to fetch additional fields like tags, linked versions, or folder structure.
* Adding an attachment to a comment or review
* Adding change context to a commit
### Best Practices with the API
* When attempting to GET Attachments from a comment or review, make sure to have an error handler. This will allow you to support posting when it returns with an error if there are no attachments on the comment.
* Make sure file attachments are uploaded to their destination, NOT referencing the url. Our file urls have a 15 min time limit, so they must be uploaded and stored elsewhere to have any permanence.