Worker Event Types

Triggers before downloading an artifact.

For example, verify user permissions to ensure they can download the artifact.

Platforms entitled to JFrog Advanced Security (JAS) or JFrog Curation can block downloads of artifacts using this Worker's Stop response. Platforms without JAS or Curation can still deploy and run this Worker, but the Stop Action is not enforced: if the Worker returns Stop, the download will not be blocked and a warning will be logged.

For example, log the download activity for analytics purposes.

Triggers before creating a property.

For example, verify that users can create properties.

Triggers before uploading an artifact to cloud storage and without waiting for it to complete.

Platforms entitled to JFrog Advanced Security (JAS) or JFrog Curation can block uploads of artifacts using this Worker's Stop response. Platforms without JAS or Curation can still deploy and run this Worker, but the Stop Action is not enforced: if the Worker returns Stop, the upload will not be blocked and a warning will be logged.

For example, verify user permissions to upload an artifact.

Triggers after successfully creating an artifact in the Artifactory Storage.

For example, add a property value automatically to a newly created artifact.

Triggers before deleting a property for an artifact.

For example, verify user permissions to delete a property for an artifact.

Triggers before deleting an artifact.

For example, terminate deleting an artifact based on certain conditions (tagged as production).

Triggers after moving an artifact successfully from one path to another.

For example, notify the monitoring team after an artifact is moved.

Triggers after saving build info.

For example, start a CI/CD pipeline immediately after saving build info.

Triggers before copying an artifact.

For example, terminate copying an artifact based on certain conditions (tagged as deprecated).

Triggers before creating an artifact in Artifactory Storage.

Platforms entitled to JFrog Advanced Security (JAS) or JFrog Curation can block uploads of artifacts using this Worker's Stop response. Platforms without JAS or Curation can still deploy and run this Worker, but the Stop Action is not enforced: if the Worker returns Stop, the upload will not be blocked and a warning will be logged.

For example, terminate creating an artifact based on certain conditions (avoid duplicates).

Triggers before moving an artifact.

For example, terminate moving an artifact based on certain conditions (tagged as production).

Triggers before querying the remote repository for an artifact's availability.

Platforms entitled to JFrog Advanced Security (JAS) or JFrog Curation can block downloads of remote info using this Worker's Stop response. Platforms without JAS or Curation can still deploy and run this Worker, but the Stop Action is not enforced: if the Worker returns Stop, the download will not be blocked and a warning will be logged.

For example, add an extra header before reaching a remote repository.

Triggers after downloading a remote artifact.

For example, update metadata after successfully downloading a remote artifact.

Triggers before replicating a delete action.

For example, terminate replicating delete action based on certain conditions (particular artifactory instance).

Triggers before replicating a directory.

Platforms entitled to JFrog Advanced Security (JAS) or JFrog Curation can block directory replication using this Worker's Stop response. Platforms without JAS or Curation can still deploy and run this Worker, but the Stop Action is not enforced: if the Worker returns Stop, the replication will not be blocked and a warning will be logged.

For example, terminate replicating a directory based on certain conditions (particular artifactory instance).

Triggers before replicating a file.

Platforms entitled to JFrog Advanced Security (JAS) or JFrog Curation can block file replication using this Worker's Stop response. Platforms without JAS or Curation can still deploy and run this Worker, but the Stop Action is not enforced: if the Worker returns Stop, the replication will not be blocked and a warning will be logged.

For example, terminate replicating a file based on certain conditions (non-production files).

Triggers before replicating a property.

For example, terminate replicating a property based on certain conditions (specific properties).

Triggers before replicating statistics.

For example, terminate replicating statistics based on certain conditions (download count).

Triggers after copying an artifact or directory from one repository to another. If the destination is a custom path and not exists, it is created first and then it copies.

For example, log the copy action for audit purposes.

Triggers after creating a property.

For example, log the create property action for audit purposes or notify another system.

Triggers after deleting a property.

For example, notify upon deletion of significant properties.

Triggers after deleting an artifact.

For example, notify upon deletion of significant artifacts.

Triggers before accessing a remote path.

Platforms entitled to JFrog Advanced Security (JAS) or JFrog Curation can block downloads via an alternative remote path using this Worker's Stop response. Platforms without JAS or Curation can still deploy and run this Worker, but the Stop Action is not enforced: if the Worker returns Stop, the download will not be blocked and a warning will be logged.

For example, ensure the remote path is changed before accessing the old one.

Triggers before downloading an artifact from a remote repository.

Platforms entitled to JFrog Advanced Security (JAS) or JFrog Curation can block downloads of artifacts from a remote repository using this Worker's Stop response. Platforms without JAS or Curation can still deploy and run this Worker, but the Stop Action is not enforced: if the Worker returns Stop, the download will not be blocked and a warning will be logged.

For example, verify the API token before processing the download.

Triggers before downloading an artifact from a remote path for handling responses.

Platforms entitled to JFrog Advanced Security (JAS) or JFrog Curation can block downloads from alternative responses using this Worker's Stop response. Platforms without JAS or Curation can still deploy and run this Worker, but the Stop Action is not enforced: if the Worker returns Stop, the download will not be blocked and a warning will be logged.

For example, replace the remote response to add custom information.

Triggers before downloading the remote content.

Platforms entitled to JFrog Advanced Security (JAS) or JFrog Curation can block downloads of remote content using this Worker's Stop response. Platforms without JAS or Curation can still deploy and run this Worker, but the Stop Action is not enforced: if the Worker returns Stop, the download will not be blocked and a warning will be logged.

For example, send alternate content instead of the requested artifact.

Triggers after an error occurs while downloading an artifact.

For example, monitor and log errors encountered during downloads.

Triggers once a download request has passed all filters (such as authentication), indicating readiness to process the request.

Platforms entitled to JFrog Advanced Security (JAS) or JFrog Curation can block downloads of artifacts from download requests using this Worker's Stop response. Platforms without JAS or Curation can still deploy and run this Worker, but the Stop Action is not enforced: if the Worker returns Stop, the download will not be blocked and a warning will be logged.

For example, verify user permissions again just before processing the download.

Triggers before saving build info.

Platforms entitled to JFrog Advanced Security (JAS) or JFrog Curation can block publishing of build info using this Worker's Stop response. Platforms without JAS or Curation can still deploy and run this Worker, but the Stop Action is not enforced: if the Worker returns Stop, the publication will not be blocked and a warning will be logged.

For example, ensure all required metadata is included before saving build info to maintain data integrity.

Triggers before a repository configuration is persisted. This is a blocking event: a STOP response aborts the repository creation.

For example, enforce naming conventions, allowed package types, or required project assignment for new repositories.

System-managed repositories are excluded.

Triggers before a repository configuration update is persisted. This is a blocking event: a STOP response aborts the update.

For example, prevent disabling security scanning on production repositories.

Triggers before a repository deletion is persisted. This is a blocking event: a STOP response aborts the deletion.

For example, protect critical repositories or enforce deletion approval workflows.

Triggers after a repository is created and persisted successfully. This is a non-blocking event: Worker responses do not affect the create operation.

For example, provision permissions or notify external systems after a repository is created.

Triggers after a repository configuration update is persisted successfully. This is a non-blocking event: Worker responses do not affect the update operation.

For example, push change audits to external systems or trigger downstream synchronization.

Triggers after a repository deletion completes successfully, or after a partial content deletion. This is a non-blocking event: Worker responses do not affect the delete operation.

For example, clean up external resources or record deletion audits. When content deletion is partial, the payload includes partial: true.

Triggers before creating a token.

For example, verify user permissions to ensure they can create a token.

Triggers before revoking a token.

For example, verify whether a token is in active use.

Triggers before a token expires.

For example, send a message to users 24 hours before their token expires.