When working with Apps or Workflows that require API keys you must use an agent accounts API key. It would be great if there was a built in service account that had an API key you could use instead of having to utilize that of an agent. This could avoid issues with updating the API key if said agent is deactivated or converted to a requester.
Planned
Built In Service Account for API Keys
+1
+2This one might already be considered (or at least voted upon): Grant Extra License for Integrations Requiring API Key | Freshworks Community
I completely agree, it just takes one slip of an inattentive admin to break integrations.
We’ve “worked around the problem” simply by purchasing an extra license. It’s DEFINITELY not the way to do it, as it ends up being a seriously expensive service account.
Currently running into this issue now when using the Ninja One Intergration. The tickets created for NinjaOne are associated by agents because the keys are agent specific. I didn’t even think about the implications if an agent account being deactivated. The work around being pay for an extra agent to be a service account is a bit frustrating.
I agree with everyone above and the ability to create various Service Accounts each with different permissions would be amazing for API automations across systems.
+7- Top Contributor ⭐
One of our customers got burned by this one. They did an Active Directory update that went wrong changed the email address of the API key holder, and boom, no workflows, no Jira Integration.
Join the Community
Already have an account? Login
Welcome back to Freshworks Community
No account yet? Create an account
Social Login
Login for Freshworks Employees Login with LinkedInor sign up below
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.