Feature Requests

It would be nice to have the ability to import json or yaml files that are constructed outside of the existing workflow generation bot and import them. This way, if the bot if having issues generating a playbook, we can develop it outside of the platform, then import it, have the platform validate it and either deploy or return errors for correction. This would give us backups of pre-existing workflows as well. This way if someone deleted or updated a workflow, we would have a backup of the pre-existing workflow. Could even import flows from other platforms, such as n8n, tines, etc.

Currently, any comment added to a standard Jira (not JSM) ticket syncs back to Foqal as a Public Response. We would like to request a setting/toggle in the Jira integration to change this behavior, allowing these comments to sync as Triage Comments (Internal Notes) instead. Why this is helpful Workflow Alignment: Our team does not send public messages from standard Jira. Having them sync as internal notes matches our workflow and prevents confusion. Flexibility: A toggle option allows other Foqal users to choose the behavior that best fits their team's needs.

In the web app, having to open the Request Form tab manually in a ticket gets impractical so I hade to create an automation that adds the request description into a note to see it at first glance...

Add the ability to add comments inside the automation section. In Okta workflows, we can add a note that is visible in the automation flow so that other users who go to edit the automation flow in the future have more context on the "why" or "how". The longer we use foqal, the more complex some of our automation trees get, and it would be helpful to be able to add notes as a separate button that is just visible in the admins with edit access so they have more context before making changes to automations - similar to how in code you can do a "// explanation of code" being able to customize the name of the action has helped some, but a internal note section that you're able to add multiple times in an automation tree would help in orgs that have many cooks

We currently use the "Send Question" action for our user confirmation flow. The next step is executed after a user clicks the button, and a confirmation message is sent. However, the message currently uses the "Requester Name" variable. Because of this, if someone other than the requester clicks the button, the message references the wrong user. Therefore, we need to allow the "Send Question" action to capture the user who clicked the button as a variable.

Submitting a request to leverage AI for reporting. It would be great to ask the AI questions related to tickets on a global scale (ie. what was the avg resolution time or how many tickets were created this month?). Additionally, would be helpful if the AI could help created reports/dashboards via prompts.

Customize notifications so that agents only get notified in slack for tickets that I want to be alerted to specifically

Create a new type of Group Admin that only has access to the settings associated with a group and set of channels. So they can change the settings, automations, etc that affect their group and channels, but not all administrator settings.

Updating automations to make it easier to create/view/clone/test/revision automations

Allow multiple tickets to be merged together in the web application