Stay organized with collections
Save and categorize content based on your preferences.
With assistant actions, the assistant can take actions on behalf of
your users in connected applications.
For example, users can ask the assistant to perform actions such as creating
calendar events in Google Calendar or editing issues in Jira Cloud.
Your end users can accomplish tasks in your connected applications by chatting
with the assistant through the app. When an end user asks the assistant to
do something, the assistant automatically determines whether this can be done
using an available action that the administrator has enabled. If needed,
the assistant asks the user follow-up questions about the task, then performs
the requested action with confirmation from the user.
You can turn on assistant actions for the following connectors. For information
on how to set up actions for each of these connectors, see the respective page:
To add actions for a connector, you must configure an OAuth 2.0 (3LO) app with
action-specific scopes and redirect URIs. This process is similar to configuring
OAuth 2.0 (3LO) apps for search. However, because some configuration settings
for actions are different from settings used for search, actions require a
separate connector and OAuth 2.0 (3LO) app setup from search.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-03 UTC."],[],[],null,["# Set up assistant actions\n\nWith assistant actions, the assistant can take actions on behalf of\nyour users in connected applications.\n\nFor example, users can ask the assistant to perform actions such as creating\ncalendar events in Google Calendar or editing issues in Jira Cloud.\n\nYour end users can accomplish tasks in your connected applications by chatting\nwith the assistant through the app. When an end user asks the assistant to\ndo something, the assistant automatically determines whether this can be done\nusing an available action that the administrator has enabled. If needed,\nthe assistant asks the user follow-up questions about the task, then performs\nthe requested action with confirmation from the user.\n\nYou can turn on assistant actions for the following connectors. For information\non how to set up actions for each of these connectors, see the respective page:\n\n- [Gmail and Google Calendar](/agentspace/docs/assistant-actions-google)\n- [Jira Cloud](/agentspace/docs/assistant-actions-jira) (Private preview)\n- [Outlook email and Outlook calendar](/agentspace/docs/assistant-actions-outlook) (Private preview)\n- [ServiceNow](/agentspace/docs/assistant-actions-servicenow) (Private preview)\n- [Workday](/agentspace/docs/assistant-actions-workday) (Private preview)\n\nTo add actions for a connector, you must configure an OAuth 2.0 (3LO) app with\naction-specific scopes and redirect URIs. This process is similar to configuring\nOAuth 2.0 (3LO) apps for search. However, because some configuration settings\nfor actions are different from settings used for search, actions require a\nseparate connector and OAuth 2.0 (3LO) app setup from search.\n| **Note:** You can configure actions even if the connector ingestion failed. If you don't want to share your Workday data with Google, you can enter fake strings during the connector setup."]]