Before
A user would manually search the trouble-ticket system for tickets marked RFC, review the matching records, and compile the list. They would then copy the relevant information into the appropriate team chat and repeat the process for each request.
How it works
- Receive a request through the webhook trigger for RFC ticket information.
- Retrieve the available trouble tickets and identify those matching the RFC status.
- Post the resulting RFC ticket list as a message in the relevant chat.
Workflow details
- Request intake: The workflow starts when a command or data event is received through its webhook trigger, representing a request to retrieve RFC tickets.
- Ticket retrieval: It queries the trouble-ticket system and applies the RFC status criterion to identify the relevant tickets.
- Result preparation: The retrieved RFC ticket information is prepared as a chat message so the list can be shared with the requesting conversation.
- Team delivery: The workflow posts the resulting list to a chat, making the requested ticket information available in the team conversation.
- Scope note: The workflow description mentions retrieving tickets for a specified period as an additional option, but the provided steps only explicitly show retrieval based on RFC status.
What changed
The RFC ticket lookup and status filtering now occur automatically after the request is received, and the resulting list is delivered directly to the chat without a manual search-and-copy handoff.
Work removed
Manually searching for RFC-status tickets, reviewing and compiling the matching list, copying the results into a chat, and sending the update to the team.
Expected outcome
Each request produces a consistent RFC ticket list in the team chat and removes at least three recurring manual actions: searching, compiling, and posting the results.
