Build an IT-intake assistant that approved staff use in Studio. It answers routine IT questions from your policy and creates a Zendesk request after an employee confirms a software-review request. The request goes to IT; it does not approve, buy or install software.

Before you begin

  • Project-edit access for the builder and approved staff who will operate the assistant in Run.
  • An authorized Zendesk test account, its subdomain URL and a test requester email you control.
  • Your approved IT request policy. The Northstar example below is fictional.
Create ticket writes to Zendesk, including from Run. Configure the draft connection for your test account before executing it. Drafts use the published connection when no separate draft connection exists.

Build the internal request workflow

1

Create the IT assistant

Create a Chat project named Northstar IT Intake, choose Start from scratch and keep Main selected.

2

Import the IT request policy

Open Knowledge base → Add data source → Plain text and import:

IT request policy
text
Northstar IT request policy

Software requests go to IT for review. Include the application name and business reason. IT reviews security, licensing and access before approval. There is no automatic approval or promised completion date.

For a VPN issue, restart the VPN client and reconnect using the standard company sign-in. If the issue persists, contact IT. Never share passwords, one-time codes or access tokens with an assistant.

Wait for processing to finish, then enable Knowledge base under System tools in Agent. Use approved policy information; never put passwords, API keys or one-time authentication codes in the source or test conversation.

3

Write the intake instructions

In Global prompt, enter:

IT assistant role
markdown
# Role
Help approved Northstar staff follow IT guidance and submit software requests to the IT team.

# Boundaries
Use the approved Knowledge base. Do not invent facts or claim to complete an unavailable action.

In Instructions, enter:

Software-request instructions
markdown
For routine IT questions, search the Knowledge base and give the approved steps. Never request passwords, authentication codes or API keys.

For a software request, collect the employee’s name and work email, application name and business reason. Confirm the summary and ask permission to submit it.

After confirmation, use Create ticket with a subject beginning Software request. Include the application and business reason in the description and comment. Confirm submission only when the tool succeeds. A submitted ticket is not approval, a purchase or an installation.
Separate a request submission from approval, purchase or installation. Photo:
4

Connect the IT queue

Open Integrations → Zendesk → Connect. Enter the account’s Subdomain URL, complete authorization and inspect the published and draft connection destinations. Use the test account first.

5

Attach Create ticket

Return to Agent → Global tools → + → Zendesk → Create ticket. Open the attached tool and set its Trigger to “Submit an IT request only after the employee confirms the details and asks to send it.”

Keep subject, description, requesterName, requesterEmail and comment supplied by the conversation. Leave their customer-specific defaults empty; leave optional priority and custom fields off for this example. Describe the application and business reason in the ticket text rather than assuming an unavailable custom field.

Use the native ticket action to send a confirmed request to the IT team. Photo:

The employee’s stated email is not identity verification. The request remains subject to your IT team’s identity, permission and approval checks.

6

Test submission and cancellation

Click Run. Send “I need a software review for Figma to collaborate on support diagrams. I’m Alex Morgan, alex@northstar.example.” Substitute a requester email you control when running the write.

The assistant should summarize the application, reason, name and email, then ask permission to submit. Confirm that no ticket exists yet.

Reply “Yes, submit it.” Open Debugger in Run and select the Create ticket log to inspect its completed result for its ticket ID and saved fields.

After confirmation, the simulated Create ticket action returns the request for review. Photo:
Inspect the simulated tool input and returned record before verifying the real provider account. Photo:

In Zendesk, find that ticket ID. Compare Subject, Description, the first Comment and the requester’s name and email with the submitted tool input. The application and business reason should describe a request for review. Open the matching Transcripts conversation and verify confirmation came before the tool call. The simulated record above is a worked example; check the real ticket in your test account.

Start a fresh Run, give another request and cancel at confirmation. Verify that this second request created no ticket. Also ask the approved VPN question: it should answer from the policy without opening a software ticket.

7

Roll out to approved staff

Replace the fictional policy and test connection with your approved IT policy and account. Before switching the connection, finish the sandbox acceptance checks. Confirm that only approved operators have access to this project.

Staff use Agent → Run for this workflow. Repeat the acceptance checks after changing its editable draft.

Verify the result

An approved operator can obtain the IT guidance, review a software-request summary and submit it once. The connected Zendesk account contains the expected request, and the matching Transcript shows the employee’s confirmation. Cancellation creates no request; submission grants no software entitlement.

Next steps

To deploy this workflow in an employee app, use the Chat agents developer path, authorize employee access and publish the reviewed agent. Keep IT’s identity and approval checks in the owning systems.

A ticket is missing or duplicated

Inspect the tool result and destination account before submitting again.

Check the requester email, ticket subject, connection account and tool result. Search the account for the original request before retrying. Each confirmed Create ticket call can create a new record; the example does not provide an idempotent approval system.

Use the up and down arrow keys to select a result, Enter to open it, and Escape to close the search.