Webhooks

Webhooks notify external applications and services about actions that occur in P4 DAM.

You can add webhooks to integrate P4 Plan and Jira with P4 DAM or add custom webhooks to integrate with other external services.

You must be a company administrator to work with webhooks at the company level. You must be a company administrator or project administrator to work with webhooks at the project level.

P4 Plan webhooks

P4 Plan webhooks integrate P4 Plan with P4 DAM for information sharing between the applications. After an administrator adds a P4 Plan webhook, users can select the webhook that connects to the P4 Plan item when they add links to assets. Basic information about the item, including a link to the item, are displayed with the asset. When the asset is updated, the status changes, or a comment is added, information is automatically sent to P4 Plan and displayed in the related item as a comment.

By default, P4 Plan webhooks run when users perform the following actions in P4 DAM:

  • Update assets, which includes:
    • Adding new asset versions
    • Moving assets
    • Renaming assets
    • Deleting assets
  • Update the status of assets from the Open state to an In progress or Closed state type. See Create company workflows. The webhook will not run for any other asset status change. For example, the webhook will not run if you change the asset status from an In progress state to a Closed state type.
  • Add comments to assets.
  • Add links to assets or asset bundles.

  • Update asset bundles, which include adding or excluding items, such as assets, folders, or other asset bundles, from an asset bundle. To manage the path rules for an asset bundle, see Manage items in an asset bundle.

To learn more about adding P4 Plan webhooks, see Add P4 Plan webhooks.

Jira webhooks

Jira webhooks integrate P4 DAM with a Jira instance for information sharing between the applications. After an administrator adds a Jira webhook, users can select the webhook that connects to the Jira instance when they add links to assets. Basic information about and a link to the Jira issue are displayed with the asset. When the asset is updated, the status changes, or a comment is added, information is automatically sent to Jira and displayed in the related Jira issue as a comment.

By default, Jira webhooks run when users perform the following actions in P4 DAM:

  • Update assets, which includes:

    • Adding new asset versions

    • Moving assets

    • Renaming assets

    • Deleting assets

  • Update the status of assets from the Open state to an In progress or Closed state type. See Create company workflows. The webhook will not run for any other asset status change. For example, the webhook will not run if you change the asset status from an In progress state to a Closed state type.

  • Add comments to assets.

  • Add links to assets or asset bundles.

  • Update asset bundles, which include adding or excluding items, such as assets, folders, or other asset bundles, from an asset bundle. To manage the path rules for an asset bundle, see Manage items in an asset bundle.

To learn more about adding Jira webhooks, see Add Jira webhooks.

Custom webhooks

Custom webhooks integrate P4 DAM with external services.

For example, P4 DAM may not support previews for asset types your team works with. To add asset previews for these file types, you can use a webhook to communicate with an external service to automatically generate previews for the assets. Then, the previews can be added to the appropriate assets in P4 DAM.

When a custom webhook runs, P4 DAM sends an HTTP post request with a JSON payload to the specified endpoint URL. You can use any endpoint that can process the request.

Custom webhooks run when users perform the following actions in P4 DAM:

  • Add new assets and new asset versions

  • Move assets

  • Rename assets

  • Delete assets

You can add custom webhooks at the company or project level.

  • Webhooks added at the company level can run on collections in multiple P4 DAM projects. Company administrators can configure webhooks at the company level.

  • Webhooks added at the project level only run on collections for the selected P4 DAM project. Company administrators and project administrators can configure webhooks at the project level.

To learn more about adding custom webhooks, see Add custom webhooks.