Use Google actions with automation

You can use automation actions to connect your Jira Service Management projects with Google Calendar and Google Drive, letting you automate common productivity workflows directly from your automation rules. These actions let you retrieve calendar events, create and copy documents, manage comments, and more — without leaving Jira.

Before you begin: To use Google actions in your automation rules, you need to add a connection to Google Drive and Google Calendar in your Jira automation settings. Follow the authentication prompts to authorize access to your Google account.

Google Calendar actions

The following automation actions are available for Google Calendar.

Get calendar events

Use this action to retrieve calendar events for a specified date range from a user's Google Calendar so you can use them later in your rule — for example, to check for scheduling conflicts or trigger follow-up actions based on upcoming meetings.

Fields:

Field	Description	Required
`Calendar ID`	The calendar to query. Use `primary` for the user's main personal calendar, or enter the calendar owner's email address.	Yes
`Min time`	The start of the date range. Use ISO 8601 format in UTC (for example, `2025-06-03T11:00:00Z`).	Yes
`Max time`	The end of the date range. Use ISO 8601 format in UTC (for example, `2025-06-03T11:30:00Z`).	Yes
`Max results`	The maximum number of events to return. Defaults to 250 when not provided.	No
`Order by`	The order in which to return events. Defaults to `startTime` when not provid`ed`.	No
`Timezone`	The timezone for event times. If not provided, event times are returned in the calendar's default timezone.	No

Tip: The Min time and Max time fields require ISO 8601 format in UTC. The format is YYYY-MM-DDTHH:MM:SSZ — for example, 2025-06-03T11:00:00Z. You can use smart values to generate these dynamically — for example, {{now.plusDays(1)}}.

Google Drive actions

The following automation actions are available for Google Drive.

Create blank document

Use this action to create a blank Google Drive document in a specified folder so it can be referenced later in the rule. This is useful for automatically generating project documentation when an issue is created.

Fields:

Field	Description	Required
`Name`	The document name or title to create. You can use smart values — for example, `{{issue.key}} - {{issue.summary}}`.	Yes
`Folder`	The destination folder. You can find the folder ID in the folder URL.	No

Copy document

Use this action to copy an existing Google Drive document. The new document can inherit visibility and other options you specify. This is useful for creating documents from templates.

Fields:

Field	Description	Required
`Source document ID`	The ID of the source document. You can find it in the file URL.	Yes
`Ignore default visibility`	Bypass the domain's default visibility for the created file. Permissions still inherit from parent folders.	No
`Keep revision forever`	Mark the new head revision to be kept forever. Applies to binary files; limited to 200 kept revisions.	No
`OCR language`	ISO 639-1 language code (for example, `en` for English), used as a hint for OCR during image import.	No
`Supports all drives`	Whether the request supports both My Drive and shared drives.	No
`Include permissions for view`	Which additional view's permissions to include. Only `published` is supported.	No
`Include labels`	Comma-separated list of label IDs to include in the labelInfo part of the response.	No

Delete document

Use this action to delete a Google Drive document by its ID.

Fields:

Field	Description	Required
`Document ID`	The ID of the document to delete. You can find it in the file URL.	Yes
`Supports all drives`	Whether the request supports both My Drive and shared drives.	No

Note: Deleting a document is permanent and can't be undone via automation. Make sure you have the correct document ID before using this action in a live rule.

Delete comment

Use this action to delete a comment from a Google Drive document.

Fields:

Field	Description	Required
`File ID`	The document ID. You can find it in the file URL.	Yes
`Comment ID`	The ID of the comment to delete.	Yes

Get comment replies

Use this action to list replies for a specific comment on a Google Drive document. Results can be used later in the rule.

Fields:

Field	Description	Required
`File ID`	The document ID. You can find it in the file URL.	Yes
`Comment ID`	The ID of the comment whose replies to fetch.	Yes
`Include deleted`	Include deleted replies. Deleted replies do not include the original content.	No
`Page size`	Maximum number of replies to return per page.	No
`Page token`	Continue a previous list request with the `nextPageToken` from the previous response.	No
`Fields`	Comma-separated list of fields to return. Prefix each field with `replies/` (for example, `replies/content,replies/author`).	No

Tip: To find a document or folder ID in Google Drive, open the file in your browser. The ID is the long string of characters in the URL between /d/ and /edit — for example, in https://docs.google.com/document/d/abc123xyz/edit, the ID is abc123xyz.

Example: Automatically create a document when a service request is created

Here's how you might use the Create blank document action in a real automation rule:

Trigger: Issue created → Issue type is Service request
Action: Google Drive — Create blank document
- Name: {{issue.key}} - {{issue.summary}}
- Folder: Your service request documents folder ID
Action: Add comment to issue
- Comment: A Google Doc has been created for this request.
Result: A new Google Doc named JSM-456 - Set up new employee laptop is created in the designated folder, and a comment is added to the issue for visibility.

Was this helpful?

It wasn't accurateIt wasn't clearIt wasn't relevant

Still need help?

The Atlassian Community is here for you.

Ask the Community