Monitor a new vendor by their primary hostname

Search an identity breach by ID

JQL allows for complex searching and filtering in JIRA. Be sure to include the order by created desc but you can provide as more or as little filtering! Read more documentation on JQL..

The issue's numeric ID, or the key (like "XYZ-123").

The file to be attached to the issue.

The issue's key (like XYZ-123), which can be specified from a previous step (using a "Custom Value"), or found using a search. If you're not seeing custom fields for your issue, please use this workaround.

API docs for Jira Software Server are located here https://docs.atlassian.com/jira/REST/cloud/

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, {"foo": "bar"} is perfectly valid.

Searches the name, email, and username fields within JIRA.

Search a data leak by ID

Search a vendor by ID

The issue's key (like AB-123), which can be specified from a previous step (using a "Custom Value"), or found using a search step. You must be an administrator of the project the issue belongs to in order to add watchers.

The user's username (likejon.snow) which can be specified from a previous step (using a "Custom Value"), or found using a search step.

Determines which App Extensions will appear in the dropdown below.

Searches for an issue with a matching key, such as "XYZ-123".

If provided, find the issue with the "best match" of the summary text.