Workflows & Automation
Common questions about agents and automation in Harmony
Can custom form fields be dynamically populated from an external REST API?
Dynamic population of multiple-choice fields from external data sources is a planned roadmap feature. Two implementation approaches are being considered:
Custom agent: An agent sends an HTTP request to an external endpoint and returns the results to populate the field.
Harmony API: Harmony acts as the intermediary, exposing an internal endpoint that the form field queries.
This capability is not yet available as a self-serve configuration.
AI agent submitting service catalog items
If the portal AI agent is unable to submit requests from the service catalog, this is a known issue currently under investigation. Contact support with your configuration details so it can be reviewed.
Why didn't my agent trigger when a ticket was created through the AI assistant?
Agent not triggering
Check the run history (available in the top-right corner of the agent editor) to see if a run was attempted and why it failed.
A common cause is a misconfigured approval step. If the Requester attribute on the approval step has not been set, the agent will not complete as expected.
Triggering agents from conversations
Direct triggering from a Slack or Teams conversation is not yet supported. Agents are currently triggered via ticket creation only. This is planned for an upcoming release.
Can Harmony automatically assign a user to a JumpCloud group after an access request is approved?
Yes. Once an app owner approves a request, Harmony can automatically provision the user into the relevant JumpCloud group.
Setup
Configure an application access automation in Harmony for the target app.
Set the approval step to require app owner sign-off.
Define the post-approval action to assign the user to the designated JumpCloud group.
Can Agents support Password Reset, Account Unlock, and Add User to Group for Microsoft Entra?
Yes, these agents will be supported in Agents for Microsoft Entra.
How can I automatically assign and remove Entra groups when an employee joins or changes departments?
Use Harmony agents triggered by employee lifecycle events (onboarding or department changes).
Recommended approach
Trigger the agent on a new hire or department change event.
Read the relevant employee attribute (e.g., department name) to determine the target groups.
Assign the employee to the appropriate Entra groups.
Remove the employee from groups associated with their previous department.
Recommended attributes to map groups by
Department name
Most common, maps cleanly to Entra groups
Team name
When team-level granularity is needed
Direct manager
When group membership follows reporting structure
Last updated
Was this helpful?