Should be in the format: HH:MM

Should be in the format: HH:MM

Break time in minutes

The ID of the employee.

ID of the document category.

A file from a previous step or a URL pointing to the desired file.

Must have the file extension (e.g. .pdf, .jpg, .docx, etc.).

Optional comment(s) that can be added to the uploaded document.

Not sure of the employee ID? Add an Employee search step before this one.

Employee ID

Absence Start Date

Absence End Date

Whether the start date is a half-day off

Whether the end date is a half-day off

Optional, default value is true. If set to false, the approval status of the absence request will be "pending" if an approval rule is set for the absence type in Personio. The respective approval flow will be triggered.

Find the Employee with this email.

A file from a previous step or a URL pointing to the desired file.

Title of the file to be uploaded (Required if uploading a file).

ID of the document Category (Required if uploading file).

Optional comment that can be added to the uploaded document.

The ORDER BY keyword is not allowed in your query. Learn more about JQL.

This Trigger does not use one of your App Connections between Jira and Zapier. Instead, Zapier uses the fields below to connect to your Jira account and adds a Jira webhook that triggers this Zap.

Your Jira account must have the "Administer Jira" global permission.

You can create an API token here.

Use this field to trigger on comments in specific projects. If you leave this field empty, the Zap will trigger on comments in all projects.

Make sure you map the issue key instead of the ID (e.g. TEST-123 not 12345).

Make sure you map the issue key instead of the ID (e.g. TEST-123 not 12345).

Make sure you map the issue key instead of the ID (e.g. TEST-123 not 12345).

Determines which App Extensions will appear in the dropdown below.

The search by name is not case sensitive and ignores any blank space.

Searches the name, email, and username fields within Jira Cloud.

A file from a previous step or a URL pointing to the desired file.

Title of the file to be uploaded (Required if uploading a file).

ID of the document Category (Required if uploading file).

Optional comment that can be added to the uploaded document.

Not sure of the employee ID? Add an Employee search step before this one.

Not sure of the employee ID? Add an Employee search step before this one.

Returns Attendances with a status of pending as well as confirmed.

Employee ID

Date of the attendance period

Must be in the format: "HH:MM"

Must be in the format: "HH:MM"

Break time in minutes

Only trigger when issues are first moved to this status eg. Done.

Only trigger when issues with a particular status are updated eg. In progress.

This Trigger does not use one of your App Connections between Jira and Zapier. Instead, Zapier uses the fields below to connect to your Jira account and adds a Jira webhook that triggers this Zap.

Your Jira account must have the "Administer Jira" global permission.

You can create an API token here.

Use this field to trigger on updated comments in specific projects. If you leave this field empty, the Zap will trigger on updated comments in all projects.

Make sure you map the issue key instead of the id (e.g. TEST-123 not 12345).

Make sure you map the issue key instead of the id (e.g. TEST-123 not 12345).

Select or search for a user to watch the issue. If no user is specified, you will be assigned as the issue watcher

Make sure you map the issue key instead of the id (e.g. TEST-123 not 12345). Note that if you are using a search for this, you'll need to select a similar field from the dropdown first and then map the issue over as a custom value so that the fields load first.

We can only list available statuses for the issue given in the above field. You may have workflows in place which can prevent certain statuses from appearing here. Make sure whichever issue is specified above is in the status you expect it to be when your Zap runs.

API docs for Jira Software Cloud 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.

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

If you already know the issue's key, enter it here and we will look up that specific issue (Example: XYZ-123).