# Agentic

Agentic is a low-code, no-code platform that enables you to rapidly build and manage powerful AI agents that take action and orchestrate workflows dynamically.

This platform approach enables you to customize and manage purpose-specific AI agents that understand your intent and context to perform the following actions:

Retrieve relevant information from various knowledge bases.
Take action on apps and data securely with governance.
Orchestrate workflows end-to-end dynamically.
Collaborate with other AI agents and humans to execute complex workflows.

# Agentic capabilities

The term agentic derives from the concept of agency, which refers to the ability to act independently and make informed choices. Genies are agents that you can build in Agent Studio. Your genies use the knowledge base and skill sets you configure to manage tasks and workflows.

# Agentic learning ability

Your genie uses a large language model (LLM) and a detailed prompt to learn new information. The knowledge base recipes and skills recipes that you configure continuously learn from new inputs and adapt to handle dynamic situations effectively.

For example, an IT support genie assists employees who reports losing their connection to a critical app. Within minutes, multiple users report the same issue, suggesting a potential system outage or server disruption. The IT genie adapts by relying on the following learning framework:

Identify patterns: Your genie uses an LLM to recognize the spike in lost connection reports as a system-wide issue rather than an isolated incident.
Proactive escalation: Your genie automatically notifies the IT team about the pattern, including key details such as the app affected, the number of users impacted, and the timeframe of the reports.
Provide updates: Your genie shares progress updates with users as the IT team investigates, such as estimated resolution times or alternative workarounds, based on real-time information.
Logging insights: Your genie stores data from the incident, including affected regions and user feedback, for post-resolution analysis and future improvements.

# Configure SAML settings

You can configure Just-in-Time (JIT) provisioning, user group syncing, and select which users require SAML-based authentication. Complete the following steps to configure your SAML settings:

Click Authentication in the sidebar.

Ensure that the SAML-based SSO authentication toggle is enabled.

SAML toggle Ensure the SAML-based SSO authentication toggle is enabled

Go to the Configure SAML settings section.

Configure SAML settings

Use the Enforce SAML authentication for drop-down menu to select who is required to use SAML-based authentication.

Click the Enable SAML Just-in-Time (JIT) provisioning toggle if you plan to automatically create accounts for new users who log in using SAML-based SSO.

Click the Enable user groups syncing toggle if you plan to update user groups from your identity provider. Refer to SAML role sync: maintaining Workato roles in the identity provider for more information.

Click Save changes.

# Get SAML configuration values

The Authentication page provides the Single sign-on URL and Service provider (SP) entity ID for your SSO-based SAML app.

Complete the following steps to access your Workato Single sign-on URL for Agentic:

Go to Workspace admin > Access control > Authentication.

Ensure that the SAML-based SSO authentication toggle is enabled.

Locate the Create a SAML application in your IdP section to access your Single sign-on URL and Service provider (SP) entity ID.

# Identity provider user access

You can add users to the Agentic platform through your external identity provider (IdP). This enables you to authenticate user accounts for Agentic access. You must configure a SAML-based SSO through your IdP before you can provide a user with access to Agentic. Agentic adds users when they sign in through your IdP for the first time. Multiple IdPs are supported. The steps in this section use Okta as an example.

Complete the following steps to configure your IdP:

Go to Applications > Applications and click Create App Integration.

Add application in Okta

Refer to the Okta documentation (opens new window) for more information.

Select SAML 2.0 as the Sign-in method and click Next.

Create a new application in Okta

Enter a name for the app in the App name field. For example, Workato Agentic.

Click Next.

Paste your Workato Single Sign-On URL into the corresponding field in Okta. Refer to Get SAML configuration values for more information.

Select the Use this for Recipient URL and Destination URL checkbox.

Paste the Service provider (SP) entity ID into the Audience URI (SP Entity ID) field.

Set Name ID format to EmailAddress.

Go to the Attribute Statements section and add the following attributes:

Name	Value
`workato_app_user_name`	`user.displayName`
`workato_app_user_groups`	`appuser.workato_app_user_groups`

The resulting attribute statements should look like this:

Add Attribute Statements to your App

Click Next.

Use the App type drop-down menu to choose This is an internal app that we have created.

Click Finish.

Go to Directory > People > and add one or more users. You must complete the verification steps for each user.

Go to Applications > My App > Assignments.

Click Assign > Assign to People and add one or more users for My App.

Click Done.

Go to Applications > [Your App] > Sign On in Okta.

Copy the Metadata URL.

Return to Workato and go to Workspace admin > Access control > Authentication.

Ensure the SAML-based SSO authentication toggle is enabled.

Go to the Provide metadata from your identity provider (IdP) section.

Locate the Do you have your identity provider metadata URL? field and select Yes or No depending on whether you have access to your IdP metadata URL.

Click Save changes.

# Agentic roles and permissions

Workspace owners have access to Agentic by default. Agentic permissions are defined as all or nothing. This means that any workspace collaborators with permission to access Agentic can perform all actions on all genies within the workspace. Agentic permissions are defined within the Orchestrate Workspace admin > Collaborators > Collaborator roles. The workspace owner must specify the Admin role when assigning access to collaborators.

Defined system roles for each collaborator per environment are in development.

Last updated: 5/28/2025, 9:08:17 PM