AI Agent Use Cases
Views —

AI Agent Use Cases

Added today

44All 189

Prompt to Prepare a Shopping Cart from a Recipe Photo

The author reports that Grok Bot receives a recipe photo, organizes the ingredients and quantities, and creates a shopping list by excluding ingredients already available at home.

Grok Bot
Life & Hobbies

1–20 of 189

Work & ResearchWalkthrough

Agent for Reviewing Internal IT Inquiries and Choosing Account Actions or Ticket Creation

The author reports that an agent responding to internal IT inquiries searches knowledge resources and checks user information, then chooses either to take account action or to create a ticket.

n8n

How it works

  1. The author connects internal knowledge resources, an Entra ID test account, and a Jira project.
  2. After checking the procedure through knowledge search and looking up the Entra ID user, the author chooses either to reset the password or to create a Jira ticket.

Results

In the public example, the intended outcomes are the processing result for each inquiry and the Jira ticket.

Notes

This is a public implementation example. Account changes are only possible in environments where actual operational permissions and approval criteria are set. The author confirms that public settings and tool connections were checked, but reports that they were not executed directly.

Source

n8n 공개 워크플로 #4560 Original post ↗

Example prompt · n8n

Goal: Handle internal IT inquiries from review to account action.

Input/Environment: [IT inquiry example], [internal knowledge resources], [test user], [approval criteria].

Reference original: https://n8n.io/workflows/4560

Prepare the settings and connections so that a test environment can be created with the public configuration from the original. If there are any missing sub-workflows, APIs, or account permissions, mark them as incomplete until actually connected.

Connections and resources to prepare: Connect internal knowledge resources, an Entra ID test account, and a Jira project.

Agent actions to implement: Check the procedure through knowledge search, look up the Entra ID user, and then choose either password reset or Jira ticket creation.

Scope of actions: This is a public implementation example. Account changes are only possible in environments where actual operational permissions and approval criteria are set.

The outcomes are the processing result for each inquiry and the Jira ticket. Please also organize the necessary setup steps and actual execution method. After checking the results returned by the tools, choose the next action, and separately note any resources that could not be accessed or actions that could not be executed.

Verification: Test cases where the user cannot be found and where permissions are insufficient, and check the account change target and approval status before taking action. Clearly distinguish the input used for verification, the actual output, and any items not yet confirmed.