top of page

TeamsWork Ticketing + Power Automate in Action

Nov 10
3 min read

Your helpdesk shouldn't be an island. Requests start in forms, chats and lists. Resolving them often needs an approval, a task for another team, or a file stored somewhere official.

With the TeamsWork Ticketing connector for Power Automate, you can link these steps together without writing code. This post walks through ready-to-build flows in two directions:


•         Inbound: other apps create or enrich tickets, so every request lands in one queue with the context agents need.

•         Outbound: ticket events drive work in other apps, so approvals, escalations and follow-ups happen on their own.


Each flow includes the trigger, the steps and the outcome, so you can build it in your own tenant today.


Before you start

Licensing, API keys and connection setup are covered in the TeamsWork Ticketing Power Automate Connector — Getting Started.


Inbound: bring every request into Ticketing

These flows capture requests where people already make them and add the context agents would otherwise look up by hand.


Before you build them, create your TeamsWork Ticketing connection as described in the TeamsWork Ticketing Power Automate Connector — Getting Started (link to add). Use the read-write API key, since these flows create or update tickets.


1. Turn a Microsoft Forms request into a ticket

Outcome: a structured intake form (equipment request, facilities issue, access request) creates a complete ticket on submit, with the right fields already filled.

1.       Trigger: When a new response is submitted (Microsoft Forms). Select your form.

2.       Action: Get response details (Microsoft Forms), to read the answers.

3.       Action: Create a ticket (TeamsWork Ticketing):

o        Title: the form's subject question.

o        Requestor: the responder's email.

o        Description: the remaining answers.

o        Priority, Tags, Custom fields: map them from the matching questions.





Tip: keep the form's choice values identical to your Ticketing priorities (Low, Medium, Important, Urgent) and tags, so they map without conversion.


2. Create a ticket from a Teams message

Outcome: when someone asks for help in a channel, anyone can turn that message into a ticket in two clicks, and the thread gets a link back.


1.       Trigger: For a selected message (Microsoft Teams). It adds the flow to the message's More actions menu.

2.       Action: Create a ticket (TeamsWork Ticketing):

o        Title: a short prefix plus the start of the message.

o        Requestor: the message author's email.

o        Description: the message content.


3.       Action: Reply with a message in a channel (Microsoft Teams). Post the Ticket No. and Ticket URL returned by Create a ticket.



How It Looks in Microsoft Teams


Once the flow is saved and turned on, anyone in your team can turn a help request into a tracked ticket without ever leaving Microsoft Teams. Trigger the flow from the message:  Hover over the message requesting assistance in your channel . Click the More options (...) menu, select More actions, and click Create a ticket from teams message.


In the Workflows dialog, verify the flow name: Create a ticket from a Teams message. Click the Run button at the bottom right.


3. Create recurring tickets on a schedule

Outcome: routine work such as monthly patching, quarterly access reviews or equipment checks appears in the queue on time, already assigned.

1.       Trigger: Recurrence (Schedule). For example, every month on the 1st.


2.       Action: Create a ticket (TeamsWork Ticketing):

o        Title: for example "Monthly server patching".

o        Requestor and Assignee: the owning team's emails.

o        Expected date: a date in YYYY-MM-DD format, for example the expression addDays(utcNow(), 7, 'yyyy-MM-dd').

o        Tags: for example "Category"/"Maintenance".



Ticket Succesfully Created from PowerAutomate


This also fills a gap in Ticketing's built-in automation rules, which react to ticket changes rather than run on a schedule.


4. Add the requestor's manager to every new ticket

Outcome: agents and approval flows always know who the requestor reports to, without searching the directory.

1.       Trigger: When a ticket is created (TeamsWork Ticketing).

2.       Action: Get manager (V2) (Office 365 Users), using the trigger's Requestor email.


3.       Action: Update a ticket (TeamsWork Ticketing). Set a custom field such as "Manager" to the manager's email.


The Outcome still needs to ask whois the manager in the 365 office


Prerequisite: create the "Manager" custom field in Ticketing first.


Ready to build? Read the TeamsWork Ticketing Power Automate Connector — Getting Started (link to add) for setup and the full list of triggers and actions. New to Ticketing? Start a free trial.


Ticket automation is available on the Professional and Leader plans. If you do not have Ticketing as a Service yet, try it for free.


Still switching tabs to get things done? TeamsWork brings your business apps into Microsoft Teams — Ticketing, CRM, Checklist, and Billing — so support, sales, and tasks all live where your team already works. Microsoft Solutions Partner certified, trusted by 500+ organizations.


 
 
 

Comments


bottom of page